Overload control information from NF service consumers in 5G core network service architecture

Abstract

The present disclosure relates to overload control information from NF service consumers in a 5G core network service architecture. Systems, methods, devices, and computer program products for load and / or overload control in a 5GC SBA are provided. A method may include sending overload control information (OCI) including scope information from a network function (NF) service consumer to a network function (NF) service producer or a service communication agent (SCP). The scope information may include at least one of: a scope set to a notification uniform resource identifier (URI), or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 993,961, filed on March 24, 2020. The entire contents of this previously filed application are hereby incorporated by reference. Technical Field

[0003] Some exemplary embodiments may generally relate to mobile or wireless telecommunication systems, such as long term evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communication systems. For example, certain embodiments may relate to systems and / or methods for load and / or overload control in a fifth generation core network (5GC) based service architecture (SBA). Background Art

[0004] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to next generation (NG) wireless systems and network architectures. 5G systems are primarily built on 5G New Radio (NR), but 5G (or NG) networks may also be built on E-UTRA radio. It is estimated that NR provides bit rates of approximately 10-20 Gbit / s or higher and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide extreme broadband and ultra-robust, low latency connectivity and large-scale networks to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more widespread, there will be an increasing demand for networks that meet the requirements of low power consumption, low data rates, and long battery life. The Next Generation Radio Access Network (NG-RAN) represents the RAN for 5G, which can provide NR and LTE (and LTE upgrade) radio access. It should be noted that in 5G, a node capable of providing radio access functions to user equipment (i.e., similar to a Node B, NB in ​​UTRAN or an evolved NB, eNB in ​​LTE) can be named a Next Generation NB (gNB) when built on an NR radio, and can be named a Next Generation eNB (NG-eNB) when built on an E-UTRA radio. Summary of the invention

[0005] One embodiment may be directed to a device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code may be configured with the at least one processor to cause the device to at least perform: sending an overload control information (OCI) including scope information to a network function (NF) service producer or a service communication agent (SCP). The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0006] One embodiment may be directed to a device comprising a component for sending an overload control information (OCI) including scope information to a network function (NF) service producer or a service communication proxy (SCP). The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0007] One embodiment may be directed to a method, the method comprising sending an overload control information (OCI) including scope information from a network function (NF) service consumer to a network function (NF) service producer or a service communication proxy (SCP). The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0008] One embodiment may be directed to a computer-readable medium including program instructions stored thereon, the program instructions being used to at least perform the following operations: sending an overload control information (OCI) including scope information to a network function (NF) service producer or a service communication agent (SCP). The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, and a network function (NF) set, and optionally a scope set to a service name.

[0009] One embodiment may be directed to a device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code may be configured with the at least one processor so that the device at least performs: receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), throttling notifications toward an overload target and / or redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0010] One embodiment may relate to a device comprising a component for receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), a component for throttling notifications toward an overload target and / or a component for redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0011] One embodiment may be directed to a method comprising receiving, at a network function (NF) service producer or a service communication proxy (SCP), overload control information (OCI) including scope information from a network function (NF) service consumer. Based on the received overload control information (OCI), the method may include throttling notifications toward overload targets and / or redirecting notifications to other targets to reduce traffic of callback requests. The scope information may include at least one of: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0012] One embodiment may be directed to a computer-readable medium including program instructions stored thereon, the program instructions being used to perform at least the following operations: receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), a component for throttling notifications toward an overload target and / or a component for redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include at least one of the following: a scope set to at least one callback uniform resource identifier (URI), and / or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0013] One embodiment may be directed to a device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code may be configured with the at least one processor to cause the device to at least perform: sending overload control information (OCI) including scope information to a network function (NF) service producer or a service communication agent (SCP). The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, and a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to be applied to a notification or callback request having a callback uniform resource identifier (URI) matching the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, optionally set together with a service name, the overload control information (OCI) is configured to be applied to a notification or callback request having a matching binding indication.

[0014] One embodiment may be directed to a device comprising a component for sending overload control information (OCI) including scope information to a network function (NF) service producer or a service communication agent (SCP). The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to apply to a notification or callback request with a callback uniform resource identifier (URI) matching the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, optionally set together with a service name, the overload control information (OCI) is configured to apply to a notification or callback request with a matching binding indication.

[0015] An embodiment may be directed to a method that may include sending overload control information (OCI) including scope information from a network function (NF) service consumer to a network function (NF) service producer or a service communication agent (SCP). The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to apply to a notification or callback request having a callback uniform resource identifier (URI) matching the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, optionally set together with a service name, the overload control information (OCI) is configured to apply to a notification or callback request having a matching binding indication.

[0016] One embodiment may be directed to a computer-readable medium including program instructions stored thereon, the program instructions being used to perform at least the following operations: sending overload control information (OCI) including scope information to a network function (NF) service producer or a service communication agent (SCP). The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to be applied to a notification or callback request having a callback uniform resource identifier (URI) matching the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, optionally set together with a service name, the overload control information (OCI) is configured to be applied to a notification or callback request having a matching binding indication.

[0017] One embodiment may be directed to a device that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured with the at least one processor to cause the device to at least perform: receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), throttling notifications toward an overload target and / or redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to be applied to a notification or callback request having a callback uniform resource identifier (URI) that matches the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, the overload control information (OCI) is configured to apply to notifications or callback requests with a matching binding indication.

[0018] One embodiment may relate to a device that may include a component for receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and a component for throttling notifications toward an overload target and / or a component for redirecting notifications to other targets to reduce traffic of callback requests based on the received overload control information (OCI). The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to apply to notifications or callback requests having a callback uniform resource identifier (URI) that matches the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, the overload control information (OCI) is configured to apply to notifications or callback requests with a matching binding indication.

[0019] One embodiment may relate to a method that may include receiving, at a network function (NF) service producer or a service communication proxy (SCP), overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), throttling notifications toward an overload target and / or redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include a scope set to one of: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to be applied to notifications or callback requests having a callback uniform resource identifier (URI) that matches the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, the overload control information (OCI) is configured to apply to notifications or callback requests with a matching binding indication.

[0020] One embodiment may be directed to a computer-readable medium including program instructions stored thereon, the program instructions being used to perform at least the following operations: receiving overload control information (OCI) including scope information from a network function (NF) service consumer, and based on the received overload control information (OCI), throttling notifications toward an overload target and / or redirecting notifications to other targets to reduce the traffic of callback requests. The scope information may include a scope set to one of the following: at least one callback uniform resource identifier (URI), a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally set to a service name. When the scope is set to at least one callback uniform resource identifier (URI), the overload control information (OCI) is configured to be applied to a notification or callback request having a callback uniform resource identifier (URI) matching the at least one callback uniform resource identifier (URI) set in the scope. When the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, the overload control information (OCI) is configured to apply to notifications or callback requests with a matching binding indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings, in which:

[0022] Figure 1 shows an example signaling diagram according to one embodiment;

[0023] Figure 2 shows an example signaling diagram according to another embodiment;

[0024] Figure 3a An example flow chart of a method according to one embodiment is shown;

[0025] Figure 3b An example flow chart of a method according to one embodiment is shown;

[0026] Figure 4a An example block diagram showing a device according to one embodiment; and

[0027] Figure 4b An example block diagram of a device according to one embodiment is shown. DETAILED DESCRIPTION

[0028] It will be readily appreciated that the components of certain exemplary embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Accordingly, the following detailed description of some exemplary embodiments of systems, methods, devices, and computer program products for load and / or overload control in a 5GC SBA is not intended to limit the scope of certain embodiments, but is representative of selected exemplary embodiments.

[0029] The features, structures, or characteristics of the exemplary embodiments described in this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the use of the phrases "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Thus, the appearance of the phrases "certain embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification does not necessarily all refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

[0030] In addition, if necessary, the different functions or processes discussed below can be performed in different orders and / or concurrently with each other. In addition, if necessary, one or more of the functions and processes can be optional or can be combined. Therefore, the following description should be considered as an explanation of the principles and teachings of some exemplary embodiments, rather than a limitation thereof.

[0031] The 3rd Generation Partnership Project (3GPP) is considering providing load and overload control solutions for 5GC service-based interfaces in Release-16. One issue under consideration is to determine the scope of overload information sent by network function (NF) service consumers to NF service producers (to throttle notifications generated by producers to consumers that are overloaded). Note that 3GPP Technical Specifications (TS) 23.501 and TS 23.502 include details on 5GC SBA.

[0032] Overload control enables an NF service producer or NF service that is about to be overloaded or is overloaded to reduce its incoming signaling load smoothly. For example, overload control may include instructing an NF service consumer to send less service requests or instructing an NF service producer to send less notification requests, respectively, based on its available signaling capacity to successfully process requests. When an NF service producer or NF service consumer operates at more than its signaling capacity, it is in an overloaded state.

[0033] An NF service producer or NF service consumer experiencing overload may provide overload control information (OCI) to its peer, for example, by including a 3GPP Service Based Interface (SBI)-OCI header in a service request or response. The OCI may contain a timestamp when the OCI was generated, a traffic reduction metric indicating a percentage of traffic reduction that the recipient of the OCI should apply, a validity period for the OCI, and / or scope information indicating the applicability of the OCI.

[0034] Figure 1 An example signaling diagram describing the signaling between NF Service Consumer and NF Service Producer is shown. Figure 1 The example shows that the NF service consumer sends overload signaling to the NF service producer within the notification response (any status code, i.e., success or failure response). Figure 2 Another example signaling diagram describing the signaling between NF Service Consumer and NF Service Producer is shown. Figure 2 The example shows that an NF service consumer that is overloaded sends OCI signaling to the NF service producer in a service request (sent to the service of the same producer).

[0035] For the OCI sent by the NF Service Producer, the scope of the OCI can take any of the following values: NF-Instance, NF-Set, NF-Service, and / or NF-service-set. NF-Instance indicates that the OCI applies to all services of the NF Instance identified by the NF-Instance ID. NF-Set indicates that the OCI applies to all services of all NF Instances of the NF Set identified by its NF-Set ID. NF-Service indicates that the OCI applies to a specific service instance identified by the NF-Service ID. NF-Service-Set indicates that the OCI applies to all service instances of the NF Service Set identified by its NF-Service-Set ID.

[0036] However, it is not yet defined in the 3GPP specifications what scope information the NF Service Consumer should be able to signal to the NF Service Producer, and how the NF Service Producer should identify the corresponding notifications and / or callback requests that should be throttled.

[0037] Note that the scenario where a service consumer signals an overload to a service producer is very different and more complex than the scenario where a NF service producer signals an overload to a service consumer. This is because in the scenario where a NF service producer signals an overload to a service consumer, the service consumer or service communication proxy (SCP) always knows the target recipient (NF instance ID, NF service instance, NF set, NF service set) of the service request (so it can throttle the communication as requested by the OCI signaled by the producer). However, in the scenario where a service consumer signals an overload to a service producer, the NF service producer may not have available information about the consumer that created the subscription, so caution is needed so that the service producer can interpret the scope announced by the service consumer.

[0038] According to certain embodiments, an overload in an NF service consumer may affect the entire NF or only specific services within the NF service consumer, e.g., service(s) that handle certain notifications. In the former case, the NF service producer may be configured to throttle any notifications sent to the NF service consumer (based on a traffic reduction metric). In the latter case, the NF service producer may be configured to throttle only notifications handled by the overloaded services. Alternatively, the NF service producer may be configured to send these notifications to an alternative NF consumer instance (if possible).

[0039] In some embodiments, the overload may also affect not only the NF service consumer, but also the entire NF set to which the NF service consumer belongs (e.g., the entire access and mobility management function (AMF) or unified data management (UDM) set), or the entire NF service set within the NF service consumer instance, e.g., the SMF service set. In this case, according to an embodiment, the NF service producer may be configured to throttle notifications targeting the entire NF set or NF service set.

[0040] Certain embodiments are configured to support one or both of the following scope information for OCI: (a) set to the scope of a notification (callback) uniform resource identifier (URI), and / or (b) set to the scope of an NF service instance, NF service set, NF instance, or NF set, and optionally set to a service name. In one embodiment, OCI can be sent by an NF service consumer to an NF service producer or possibly an SCP.

[0041] According to one embodiment, an OCI (with a scope set to a notification (callback) URI), as defined in IETF RFC 3986, may include an authority (host and optional port) and an optional path. An OCI received using this scope is applied to all notification or callback requests with a notification (callback) URI that matches the notification URI received in the scope. In one embodiment, a notification URI of a notification (or callback) request matches a notification URI received in the scope of the OCI when the notification URI of the notification (or callback) request contains the same scheme, the same authority, and / or has a path that contains the path of the notification URI received in the scope of the OCI.

[0042] In one embodiment, an OCI received with the scope set to NF Service Instance, NF Service Set, NF Instance or NF Set, plus an optional Service Name, may be applied to all Notification or Callback Requests received with a matching Binding Indication (Binding Indication for Notification / Callback, i.e., with the scope set to "Callback"). (See 3GPP TS 29.500, clause 6.12.4).

[0043] Therefore, certain embodiments enable NF service consumers to signal an overload condition to NF service producers. This allows reducing the traffic of notification / callback requests generated by NF service producers to consumers for different scope levels (e.g., for all notifications to consumer NF instances, for notifications to a specific service of a consumer NF, for a specific notification to the same consumer service, or for all notifications to a NF set or NF service set). Furthermore, certain embodiments enable NF service producers or SCPs receiving signaling about an overload condition to reduce the load by suppressing notifications towards overloaded targets and / or redirecting notifications to other targets.

[0044] As described above, an overload in a NF service consumer may affect the entire NF, or may only affect specific services within the NF service consumer, such as services that handle certain notifications. According to an embodiment, in the case where the entire NF is affected, the NF service producer may need to throttle (based on a traffic reduction metric) any notifications sent to the NF service consumer. According to one embodiment, in the case where only specific services within the NF service consumer are affected, the NF service producer should only throttle notifications handled by the overloaded services.

[0045] Alternatively, in another embodiment, the NF service producer or SCP may send these notifications to an alternative NF consumer instance (if possible). For example, if the NF service consumer provides a binding indication with the NF service set level when subscribing to notifications, and an overload is reported for the NF service instance, the NF service producer or SCP (the latter based on the route binding indication carried in the notification request) may send the notification to another NF service instance. If the NF service consumer provides a binding indication with the NF set level when subscribing to notifications, and an overload is reported for the NF service instance, the NF service producer or SCP (the latter based on the route binding indication carried in the notification request) may send the notification to another NF instance.

[0046] In one embodiment, if the SCP decides to redirect the notification as described above, the SCP may remove the overload control information from the messages (eg, notification responses) from which it receives the overload control information before forwarding those messages to the NF service producer.

[0047] In addition, the overload may also affect not only the NF service consumer, but also the entire NF set to which the NF service consumer belongs, such as the entire AMF set, or the entire NF service set within the NF service consumer instance, such as the SMF service set. In this case, the NF service producer can throttle notifications for the entire NF set or NF service set.

[0048] It should be noted that the subscription request (subscription notification) may or may not contain the NF instance ID of the NF service consumer and the name of the service that handles the notification in the 5GC application programming interface (API). The subscription request contains the notification (also called callback) URI, which contains the URI to be used to send the notification. The callback URI can contain the http scheme, the host part and the path (e.g. https: / / amf1.example.com / xyz / 1234).

[0049] 3GPP Release-16 also introduces a new binding concept (see TS 23.501, 23.502 and TS 29.500), which allows NF service consumers to provide binding indications to NF service producers when subscribing to notifications. For example, if the notification URI provided in the subscription request is unreachable, the binding indication allows the notification to be routed towards an alternative consumer notification endpoint.

[0050] Therefore, as described above, some embodiments are configured to support scope information for OCI that is: (a) set to a notification (callback) uniform resource identifier (URI), and / or (b) set to a NF service instance, NF service set, NF instance or NF set, and optionally set to a service name. This allows throttling or redirecting of notification or callback requests sent by NF producers to overloaded consumers.

[0051] Below, some examples will be provided to illustrate the operation of some embodiments. In the following examples, it is assumed that the scope is set to the notification (callback) URI, and the NF service consumer (e.g., the policy control function (PCF)) has created three subscriptions in the NF service producer (e.g., AMF) to receive notifications corresponding to different events, respectively using the following notification URIs:

[0052] Subscription 1, Notification URI = https: / / pcf12.example.com / serviceX / 1234;

[0053] Subscription 2, Notification URI = https: / / pcf12.example.com / serviceY / abc; and

[0054] Subscription 3, Notification URI = https: / / pcf12.example.com / serviceY / def.

[0055] As a first example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response to an NF service producer (e.g., AMF) that includes an OCI header whose scope includes the notification URI set to "https: / / pcf12 / example / com". In this case, the OCI (and therefore the traffic throttling) is applied to the notifications generated for all three subscriptions. For example, this corresponds to a scenario where the entire NF service consumer (e.g., PCF12) is overloaded.

[0056] As a second example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response to an NF service producer (e.g., AMF) that includes an OCI header whose scope includes the notification URI set to "https: / / pcf12 / example / com / serviceY". In this case, the OCI (and therefore the traffic throttling) is applied to the notifications generated for subscription 2 and subscription 3. For example, this corresponds to a scenario where a particular NF service consumer service (service Y) is overloaded. The OCI does not affect the notifications generated for subscription 1, i.e., notifications for service X sent to PCF 12.

[0057] As a third example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response to an NF service producer (e.g., AMF) that includes an OCI header whose scope includes the notification URI set to "https: / / pcf12 / example / com / serviceY / abc". In this case, the OCI (and therefore the traffic throttling) is applied to the notifications generated for subscription 2. For example, this corresponds to a scenario where the NF service consumer only needs to limit the notifications received for a given service (service Y). The OCI does not affect the notifications generated for subscription 1 and subscription 3.

[0058] In some embodiments, how the NF service consumer constructs its notification URI in the subscription request and in the scope of the OCI can be implementation specific. This leaves ample freedom for the NF service consumer implementation to decide how it wants to handle overload based on its software architecture.

[0059] As described above, some embodiments are configured to be able to support scope information for OCI, where the scope information is set to NF service instance, NF service set, NF instance or NF set, and optionally set to the service name in the NF service consumer to handle notifications. OCIs received under this scope are applied to all notification / callback requests received with a matching binding indication (binding indication of notification / callback, i.e., under the scope set to "callback"). The use of this scope assumes that the subscription request (when subscribing to notifications) includes a binding indication. The binding indication with a scope set to "callback" indicates the NF instance ID, NF set ID, NF service instance ID and / or NF service set ID, and optionally the service name for routing the notification / callback request to the consumer, for example, when the notification URI received in the subscription is not reachable.

[0060] According to certain embodiments, the scope of an OCI matches a binding indication associated with a subscription in the following cases: the OCI indicates an NF set ID and the subscription is bound to the same NF set ID, the OCI indicates an NF instance ID and the subscription is bound to the same NF instance ID, the OCI indicates an NF service set ID and the subscription is bound to the same NF service set, the OCI indicates an NF service instance and the subscription is bound to the same service instance, and / or the OCI indicates any of the above IDs plus a service name and the subscription is bound to the same ID and the same service name.

[0061] In the following, some additional examples will be discussed to illustrate some additional exemplary embodiments. In the following examples, it is assumed that an NF service consumer (e.g., PCF) creates three subscriptions in an NF service producer (e.g., AMF) to receive notifications corresponding to different events, with the following notification URIs and binding indications:

[0062] Subscription 1, Notification URI = https: / / pcf12.example.com / serviceX / 1234, bound to PCF service set X in PCF12 instance ID in PCF set Z;

[0063] Subscription 2, Notification URI = https: / / pcf12.example.com / serviceY / abc, bound to PCF service set Y in PCF12 instance ID in PCF set Z;

[0064] Subscription 3, Notification URI = https: / / pcf12.example.com / def, bound to PCF service name "def" in PCF12 instance ID in PCF set Z.

[0065] As a fourth example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response (or service request) to an NF service producer (e.g., AMF) that includes an OCI header with a scope that includes the PCF12 (NF) instance ID. In this case, the OCI (and therefore the traffic throttling) is applied to notifications generated for all three subscriptions of PCF12. For example, this corresponds to a scenario where the entire NF service consumer (PCF12) is overloaded.

[0066] As a fifth example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response to an NF service producer (e.g., AMF) that includes an OCI header with a scope that includes service set Y of PCF12. In this case, OCI (and therefore traffic throttling) is applied to notifications generated for subscription 2 to PCF12. For example, this corresponds to a scenario where a particular NF service set of the NF consumer is overloaded. OCI does not affect notifications generated for subscription 1 and subscription 3, i.e., notifications sent to service set X or service "def" of PCF12.

[0067] As a sixth example, an NF service consumer (e.g., PCF) that is overloaded sends a notification response to an NF service producer (e.g., AMF) that includes an OCI header whose scope includes the PCF12 (NF) instance ID and the service name "def". In this case, the OCI (and therefore the traffic throttling) is applied to the notifications generated for subscription 3. For example, this corresponds to a scenario where the NF service consumer only needs to throttle specific notifications received for a given service (service "def"). The OCI does not affect the notifications generated for subscription 1 and subscription 2.

[0068] For a service, there can be multiple notifications, and the overload only applies to one of them. To support such scenarios with the above scopes, the scope parameter can additionally contain the path part of the URI, or other notification correlation ID. For example, if the scope of the OCI indicates the PCF12(NF) instance ID, and the "path" parameter is set to " / serviceY / abc", this will result in throttling notifications for subscription 2 only.

[0069] It should be noted that the examples discussed above are provided to illustrate some exemplary embodiments; however, the exemplary embodiments are not limited to these examples in any way and can be applied in various ways.

[0070] Figure 3a An exemplary flow chart of a method for load and / or overload control in a 5GC according to an exemplary embodiment is shown. In an exemplary embodiment, Figure 3a The flowchart of may be executed by a network entity or a network node associated with a communication system such as LTE or 5G NR. For example, in some exemplary embodiments, the execution Figure 3a The network node of the method may include a base station, an eNB, a gNB, a NG-RAN node and / or a service consumer or a PCF. In an exemplary embodiment, Figure 3a The method can be executed by NF service consumers, such as Figure 1 or Figure 2 Those shown.

[0071] like Figure 3a As shown in the example of , the method may include sending an OCI including scope information to a NF service producer or SCP at 300. In some embodiments, the scope information may include at least one of: (a) a scope set to a notification (callback) uniform resource identifier (URI), and / or (b) a scope set to a NF service instance, a NF service set, a NF instance, or a NF set, and optionally a scope set to a service name.

[0072] According to one embodiment, when an OCI is transmitted with a scope set to a notification (callback) URI, the OCI applies to all notifications or callback requests with a notification (callback) URI that matches a notification URI received in the scope. In one embodiment, a notification URI of a notification (or callback) request matches a notification URI received in the scope of the OCI when the notification URI of the notification (or callback) request contains the same scheme, the same authority, and / or has a path that contains the path of the notification URI received in the scope of the OCI.

[0073] In one embodiment, when an OCI is transmitted with scope set to one of NF Service Instance, NF Service Set, NF Instance, and NF Set, plus optionally set to Service Name, the OCI applies to notifications or callback requests with a matching binding indication. This binding indication allows the notification to be routed to another consumer notification endpoint. In some embodiments, Figure 3a The method may also optionally include, at 310, receiving a service response from the NF service producer or the SCP.

[0074] Figure 3b An exemplary flow chart of a method for load and / or overload control in a 5GC according to an exemplary embodiment is shown. In an exemplary embodiment, Figure 3b The flowchart of may be performed by a network entity or a network node associated with a communication system such as LTE or 5G NR. For example, in some exemplary embodiments, the execution Figure 3b The network node of the method may include a base station, an eNB, a gNB, a NG-RAN node and / or a service producer, an SCP and / or an AMF. In an exemplary embodiment, Figure 3b The method can be performed by a NF service producer, such as Figure 1 or Figure 2 Those shown.

[0075] like Figure 3b As shown in the example of , the method may include receiving an OCI including scope information from a NF service consumer at 350. In some embodiments, the scope information may include at least one of: (a) a scope set to a notification (callback) uniform resource identifier (URI), and / or (b) a scope set to a NF service instance, a NF service set, a NF instance, or a NF set, and optionally a service name.

[0076] In one embodiment, the method may also include, at 360, throttling notifications toward the overloaded target and / or redirecting notifications to other targets based on the received OCI.

[0077] According to one embodiment, when an OCI is received with the scope set to notifications (callback URIs), the OCI is applied to all notifications or callback requests with notification (callback) URIs that match the notification URIs received in the scope. In one embodiment, a notification URI of a notification (or callback) request matches a notification URI received in the scope of the OCI when the notification URI of the notification (or callback) request contains the same scheme, the same authority, and / or has a path that contains the path of the notification URI received in the scope of the OCI.

[0078] In one embodiment, when an OCI is received with scope set to one of NF Service Instance, NF Service Set, NF Instance, and NF Set, and optionally set to Service Name, the OCI applies to notifications or callback requests received with a matching binding indication. This binding indication allows routing of notifications to another consumer notification endpoint.

[0079] Thus, in some embodiments, throttling 360 may include throttling any notifications sent to NF service consumers. According to some embodiments, throttling 360 may include throttling notifications handled by overloaded services. In one embodiment, throttling 360 may include throttling notifications for an entire NF set or NF service set.

[0080] According to certain embodiments, redirecting 360 may include sending a notification to an alternative NF consumer instance. For example, if the NF service consumer provides a binding indication with an NF service set level when subscribing to the notification, and an overload is reported for the NF service instance at 350, redirecting 360 may include sending a notification to another NF service instance. If the NF service consumer provides a binding indication with an NF set level when subscribing to the notification, and an overload is reported for the NF instance at 350, redirecting 360 may include sending a notification to another NF instance. In one embodiment, the method may include removing the OCI from the notification before sending the notification to the alternative NF consumer instance.

[0081] Figure 4a An example of a device 10 according to an embodiment is shown. In one embodiment, the device 10 may be a node, host, or server in a communication network, or serve such a network. For example, the device 10 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), an IAB node, and / or a WLAN access point associated with a wireless access point such as an LTE network, 5G, or NR. In an exemplary embodiment, the device 10 may be or may include an NG-RAN node, an eNB in ​​LTE, a gNB in ​​5G, a NF service consumer, a PCF, etc. For example, in one embodiment, the device 10 may correspond to Figure 1 or Figure 2 The NF service consumer shown in the example.

[0082] It should be understood that in some exemplary embodiments, the device 10 may include an edge cloud server as a distributed computing system, wherein the server and the radio nodes may be independent devices that communicate with each other via a radio path or via a wired connection, or wherein they may be located in the same entity that communicates via a wired connection. For example, in certain exemplary embodiments where the device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management. The CU may control the operation of the DU via a front-end interface. Depending on the functional splitting option, the DU may be a logical node that includes a subset of the gNB functionality. It should be noted that a person of ordinary skill in the art will understand that the device 10 may include Figure 4a Components or features not shown.

[0083] like Figure 4a As shown in the example of , device 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general-purpose or special-purpose processor. In fact, as examples, processor 12 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Figure 4a A single processor 12 is shown in FIG. 1 , but according to other exemplary embodiments, multiple processors may be used. For example, it should be understood that in some embodiments, device 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, processor 12 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0084] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including processing related to communication resource management.

[0085] The device 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static memory (e.g., magnetic or optical disks), hard disk drives (HDDs), or any other type of non-transitory machine or computer readable media. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform tasks as described herein.

[0086] In one embodiment, device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by processor 12 and / or device 10.

[0087] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for sending signals and / or data to and receiving signals and / or data from the device 10. The device 10 may also include or be coupled to a transceiver 18 configured to send and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna 15. In some embodiments, the radio interface may correspond to a plurality of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identifier (RFID), Ultra-Wideband (UWB), MulteFire, etc. According to an exemplary embodiment, the radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., for example, to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via an uplink).

[0088] Thus, transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by antenna 15, and demodulate information received via antenna 15 for further processing by other elements of device 10. In other exemplary embodiments, transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, device 10 may include input and / or output devices (I / O devices).

[0089] In one embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for device 10. Memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0090] According to some embodiments, the processor 12 and the memory 14 may be included in or may form part of a processing circuit or a control circuit. Furthermore, in some embodiments, the transceiver 18 may be included in or may form part of a transceiver circuit.

[0091] As used herein, the term "circuit" may refer to a hardware-only circuit implementation (e.g., analog and / or digital circuits), a combination of hardware circuits and software, a combination of analog and / or digital hardware circuits and software / firmware, a combination of any portion of a hardware processor and software (including a digital signal processor) that works together to enable a device (e.g., device 10) to perform various functions, and / or hardware circuits and / or processors or portions thereof that operate using software but where the software may not be present when the software is not required for operation. As another example, as used herein, the term "circuit" may also cover an implementation of a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuit may also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0092] As described above, in some embodiments, the device 10 may be a network node or a RAN node, such as a base station, an access point, a Node B, an eNB, a gNB, an IAB node, a WLAN access point, a NF service consumer, a PCF, etc. For example, in some embodiments, the device 10 may be configured to perform one or more of the processes depicted in any of the flowcharts or signaling diagrams described herein, e.g. Figure 1 , Figure 2 , Figure 3a or Figure 3bIn some embodiments, device 10 may be configured to perform processes related to load or overload control in 5G, as discussed herein.

[0093] According to this embodiment, the device 10 may be controlled by the memory 14 and the processor 12 to send an OCI including scope information to the NF service producer or SCP. In some embodiments, the scope information may include at least one of the following: (a) a scope set to a notification (callback) uniform resource identifier (URI), and / or (b) a scope set to a NF service instance, a NF service set, a NF instance, or a NF set, and optionally a scope set to a service name.

[0094] According to one embodiment, when the control device 10 sends an OCI with the scope set to a notification (callback) URI, the OCI is applied to all notifications or callback requests with a notification (callback) URI that matches a notification URI received in the scope. In one embodiment, the notification URI of a notification (or callback) request matches a notification URI received in the scope of the OCI when the notification URI of the notification (or callback) request contains the same scheme, the same authority, and / or has a path that contains the path of the notification URI received in the scope of the OCI.

[0095] In one embodiment, when the control device 10 sends an OCI with scope set to one of NF service instance, NF service set, NF instance or NF set, plus optionally set to service name, then the OCI applies to notifications or callback requests received with a matching binding indication. This binding indication allows the notification to be routed to another consumer notification endpoint. In some embodiments, the device 10 can be controlled by the memory 14 and the processor 12 to receive a service response from a NF service producer or SCP.

[0096] Figure 4b An example of a device 20 according to another embodiment is shown. In one embodiment, the device 20 may be a node or element in a communication network, or be associated with such a network, such as a UE, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. In some embodiments, the device 20 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), an IAB node, a WLAN access point, and / or a NF service producer, SCP, AMF associated with a wireless access network such as an LTE network, 5G, or NR. In an exemplary embodiment, the device 10 may be or may include a NG-RAN node, an eNB in ​​LTE, a gNB in ​​5G, or the like. For example, in one embodiment, the device 20 may correspond to Figure 1 or Figure 2NF service producer shown.

[0097] In some exemplary embodiments, the device 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some embodiments, the device 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that a person of ordinary skill in the art will understand that the device 20 may include Figure 4b Components or features not shown.

[0098] like Figure 4b As shown in the example of , the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, as examples, the processor 22 may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Figure 4b A single processor 22 is shown in FIG. 1 , but according to other exemplary embodiments, multiple processors may be used. For example, it should be understood that in some embodiments, device 20 may include two or more processors, which may form a multiprocessor system that may support multiprocessing (e.g., in this case, processor 22 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0099] Processor 22 may perform functions associated with the operation of device 20 including, as some non-limiting examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 20, including processing related to communication resource management.

[0100] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static memory (e.g., magnetic or optical disks), hard disk drives (HDDs), or any other type of non-transitory machine or computer readable media. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform tasks as described herein.

[0101] In one embodiment, device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by processor 22 and / or device 20.

[0102] In some embodiments, the device 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals from the device 20 and / or for transmitting via an uplink. According to some embodiments, the device 20 may also include a transceiver 28 configured to send and receive information. In one example, the transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. In some embodiments, the radio interface may correspond to a plurality of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. In further exemplary embodiments, the radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by a downlink or uplink, such as OFDMA symbols.

[0103] For example, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna 25, and to demodulate information received via the antenna 25 for further processing by other elements of the device 20. In other exemplary embodiments, the transceiver 28 may be capable of directly sending and receiving signals or data. Additionally or alternatively, in some embodiments, the device 20 may include input and / or output devices (I / O devices). In some embodiments, the device 20 may also include a user interface, such as a graphical user interface or a touch screen.

[0104] In one embodiment, the memory 24 stores software modules that provide functionality when executed by the processor 22. The modules may include, for example, an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to the device 20. The components of the device 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an exemplary embodiment, the device 20 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (such as NR).

[0105] According to some embodiments, the processor 22 and / or the memory 24 may be included in or may form part of a processing circuit or a control circuit. In addition, in some embodiments, the transceiver 28 may be included in or may form part of a transceiver circuit.

[0106] As described above, according to some embodiments, the device 20 may be, for example, a NF service producer SCP, AMF. According to some embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with the exemplary embodiments described herein. For example, in some embodiments, the device 20 may be configured to perform one or more of the processes depicted in any of the flowcharts or signaling diagrams described herein, such as Figure 1 , Figure 2 , Figure 3a or Figure 3b In some embodiments, the device 20 may include or represent an NF service producer and may be configured to perform processes related to load or overload control in, for example, 5G.

[0107] In some embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to receive an OCI including scope information from a NF service consumer or a PCF. In some embodiments, the scope information may include at least one of: (a) a scope set to a notification (callback) uniform resource identifier (URI), and / or (b) a scope set to a NF service instance, a NF service set, a NF instance, or a NF set, and optionally a scope set to a service name.

[0108] In one embodiment, device 20 may be controlled by memory 24 and processor 22 to throttle notifications to overloaded targets and / or redirect notifications to other targets based on received OCIs.

[0109] According to one embodiment, when an OCI is received with the scope set to notifications (callback URIs), the OCI is applied to all notifications or callback requests with notification (callback) URIs that match the notification URIs received in the scope. In one embodiment, a notification URI of a notification (or callback) request matches a notification URI received in the scope of the OCI when the notification URI of the notification (or callback) request contains the same scheme, the same authority, and / or has a path that contains the path of the notification URI received in the scope of the OCI.

[0110] In one embodiment, when an OCI is received with scope set to one of NF Service Instance, NF Service Set, NF Instance, and NF Set, and optionally set to Service Name, then the OCI applies to notifications or callback requests received with a matching binding indication. This binding indication allows the notification to be routed to another consumer notification endpoint.

[0111] In some embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to throttle any notifications sent to NF service consumers. According to some embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to throttle notifications handled by overloaded services. In one embodiment, the device 20 may be controlled by the memory 24 and the processor 22 to throttle notifications for an entire NF set or NF service set.

[0112] According to certain embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to redirect the notification by sending the notification to an alternative NF consumer instance. For example, if the NF service consumer provides a binding indication with an NF service set level when subscribing to the notification, and an overload is reported for the NF service instance, the device 20 may be controlled by the memory 24 and the processor 22 to redirect the notification by sending the notification to another NF service instance. If the NF service consumer provides a binding indication with an NF set level when subscribing to the notification, and an overload is reported for the NF instance, the device 20 may be controlled by the memory 24 and the processor 22 to redirect the notification by sending the notification to another NF instance. In one embodiment, the device 20 may be controlled by the memory 24 and the processor 22 to remove the OCI from the notification before sending the notification to the alternative NF consumer instance.

[0113] Therefore, certain exemplary embodiments provide several technical improvements, enhancements and / or advantages over existing technical processes, and constitute improvements in at least the technical field of wireless network control and management. For example, certain embodiments enable NF service consumers to send signals of overload conditions to NF service producers, thereby allowing the traffic of notification / callback requests generated by NF service producers to consumers to be reduced for different scope levels. For example, the scope level may include, for all notifications for consumer NF instances, for notifications for specific services for consumer NFs, for specific notifications for the same consumer service, or for all notifications for NF sets or NF service sets. In addition, certain embodiments enable NF service producers or SCPs that receive signaling about overload conditions to reduce load by suppressing notifications for overloaded targets and / or redirecting notifications to other targets. Therefore, the use of certain exemplary embodiments results in improvements in the functionality of communication networks and their nodes (such as but not limited to base stations, eNBs, GNBs, and / or UEs or mobile stations).

[0114] In some exemplary embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms, or flow charts described herein may be implemented by software and / or computer program code or portions of code stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0115] In some exemplary embodiments, the device may include or be associated with at least one software application, module, unit or entity configured for arithmetic operations, or configured as a program or part thereof (including added or updated software routines) executed by at least one computing processor. Programs, also known as program products or computer programs, including software routines, applets and macros, may be stored in any device-readable data storage medium and may include program instructions for performing specific tasks.

[0116] The computer program product may include one or more computer executable components that are configured to perform some exemplary embodiments when the program is run. The one or more computer executable components may be at least one software code or part of a code. Modifications and configurations for implementing the functionality of the exemplary embodiments may be performed as routines that may be implemented as added or updated software routines. In one example, the software routines may be downloaded to a device.

[0117] As an example, the software or computer program code or part of the code may be in source code form, object code form or some intermediate form, and it may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include a recording medium, a computer memory, a read-only memory, an optoelectronic and / or electrical carrier signal, a telecommunication signal and / or a software distribution package. Depending on the processing power required, the computer program may be executed in a single electronic digital computer, or it may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0118] In other exemplary embodiments, the functions may be performed by hardware or circuitry included in the device, such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another exemplary embodiment, the functions may be implemented as a signal, such as a non-tangible component, which may be carried by an electromagnetic signal downloaded from the Internet or other network.

[0119] According to an exemplary embodiment, a device such as a node, an apparatus or a corresponding component may be configured as a circuit, a computer or a microprocessor (such as a single-chip computer element), or a chipset, which may include at least a memory for providing storage capacity for arithmetic operations and / or an operation processor for performing arithmetic operations.

[0120] Those skilled in the art will readily appreciate that the exemplary embodiments described above may be practiced with processes in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative structures will be apparent while remaining within the spirit and scope of the exemplary embodiments.

[0121] A first embodiment may be directed to a method, the method comprising sending an overload control information (OCI) including scope information from a network function (NF) service consumer to a network function (NF) service producer or a service communication agent (SCP). The scope information may include at least one of: a scope set to a notification or callback uniform resource identifier (URI), or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, or a network function (NF) set, and optionally a scope set to a service name.

[0122] In one variation, the method may include, when the scope is set to a notification or callback uniform resource identifier (URI), overload control information (OCI) being configured to apply to all notification or callback requests having a notification or callback uniform resource identifier (URI) that matches the notification or callback uniform resource identifier (URI) set in the scope.

[0123] In one variation, the method may further include sending a binding indication from a network function (NF) service consumer to a network function (NF) service producer matching one or more notification or callback requests, and, when the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance) and a network function (NF set), optionally together with a service name, the overload control information (OCI) is configured to apply to the notification or callback request having the matching binding indication.

[0124] A second embodiment may be directed to a method, the method comprising receiving, at a network function (NF) service producer or a service communication proxy (SCP), overload control information (OCI) including scope information from a network function (NF) service consumer. Based on the received overload control information (OCI), the method may include throttling notifications toward an overload target and / or redirecting notifications to other targets to reduce traffic of callback requests. The scope information may include at least one of: a scope set to a notification or callback uniform resource identifier (URI), or a scope set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance, and a network function (NF) set, and optionally a scope set to a service name.

[0125] In one variation, when the scope is set to a notification uniform resource identifier (URI), the overload control information (OCI) is configured to apply to all notification or callback requests having a notification or callback uniform resource identifier (URI) that matches the notification or callback uniform resource identifier (URI) set in the scope.

[0126] In one variation, the method may further include receiving, at a network function (NF) service producer, a binding indication from a network function (NF) service consumer that matches one or more notification or callback requests, and when the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, overload control information (OCI) is configured to apply to the notification or callback request with a matching binding indication.

[0127] In one variation, the method may further include receiving, at a service communication proxy (SCP), a routing binding indication from a network function (NF) service producer within one or more notifications or callback requests, and when the scope is set to one of a network function (NF) service instance, a network function (NF) service set, a network function (NF instance), or a network function (NF set), optionally together with a service name, overload control information (OCI) is configured to apply to notifications or callback requests with a matching binding indication.

[0128] In one variation, throttling may include throttling any notifications sent to network function (NF) service consumers.

[0129] In one variation, throttling may include throttling notifications handled by the overloaded service.

[0130] In one variation, throttling may include notification that throttling is directed to an entire network function (NF) set or a network function (NF) service set.

[0131] In one variation, redirecting may include sending a notification to an alternative network function (NF) consumer instance.

[0132] In one variation, the method may further include removing overload control information (OCI) from the notification response before sending the notification response to the NF service producer.

[0133] In one variation, the notification or callback uniform resource identifier (URI) may include at least one of: an authority and / or an optional path including a host and an optional port.

[0134] In one variant, a notification or callback uniform resource identifier (URI) of a notification or callback request matches a notification or callback uniform resource identifier (URI) received in the scope of overload control information (OCI) when the notification or callback uniform resource identifier (URI) of the notification or callback request contains the same scheme, the same authority, and has a path that contains the notification or callback uniform resource identifier (URI) received in the scope of overload control information (OCI).

[0135] In one variant, the scope of the overload control information (OCI) matches the binding indication associated with the subscription when at least one of the following occurs: the overload control information (OCI) indicates an NF set ID, and the subscription is bound to the same NF set ID; the overload control information (OCI) indicates an NF instance ID, and the subscription is bound to the same NF instance ID; the overload control information (OCI) indicates an NF service set ID, and the subscription is bound to the same NF service set; the overload control information (OCI) indicates an NF service instance, and the subscription is bound to the same service instance; or the overload control information (OCI) indicates any one of the NF set ID, NF instance ID, or NF service set ID, plus a service name, and the subscription is bound to the same ID and the same service name.

[0136] In one variant, the scope is set to a network function (NF) service instance, a network function (NF) service set, a network function (NF) instance or a network function (NF set), and optionally set to a scope of a service name, including: a scope parameter containing a path portion of a uniform resource identifier (URI) or some other notification related ID.

[0137] A third embodiment relates to a device comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code can be configured with the at least one processor so that the device at least performs the method according to the first embodiment, the second embodiment and / or any other embodiment discussed herein, or any variant thereof.

[0138] A fourth embodiment relates to an apparatus which may include circuitry configured to perform the method according to the first embodiment, the second embodiment, and / or any other embodiment discussed herein or any variations thereof.

[0139] A fifth embodiment is directed to an apparatus which may include means for performing a method according to the first embodiment, the second embodiment, and / or any other embodiment discussed herein, or any variations thereof.

[0140] A sixth embodiment relates to a non-transitory computer-readable medium including program instructions stored thereon for executing at least the method according to the first embodiment, the second embodiment, and / or any other embodiment discussed herein, or any variations thereof.

Claims

1. A device for a communication network, the device comprising: A network function service consumer is configured to send overload control information OCI to a network function NF service producer or a service communication agent SCP, wherein the OCI includes scope information, wherein the scope information includes a scope set to one of the following: callback uniform resource identifier URI, network function NF service instance, network function NF service set, network function NF instance, or network function NF set, and service name; Wherein, when the scope is set to the callback uniform resource identifier URI, the overload control information OCI is configured to be applied to a notification request or a callback request, and the notification request or the callback request has a callback uniform resource identifier URI that matches the callback uniform resource identifier URI; Among them, when the scope is set to the network function NF service instance, the network function NF service set, the network function NF instance, or the network function NF set, and the service name, the overload control information OCI is configured to be applied to a notification request or callback request with a matching binding indication.

2. The device according to claim 1, wherein the network function service consumer is further configured to send the binding indication matching one or several notification requests or callback requests to the network function NF service producer.

3. A method for a network function NF service consumer of a communication network, the method comprising: Sending overload control information OCI including scope information to the network function NF service producer or service communication agent SCP, The range information includes a range set to one of the following: The scope of the callback URI, or A network function NF service instance, a network function NF service set, or a network function NF instance or a network function NF set, and a service name; Wherein, when the scope is set to the callback uniform resource identifier URI, the overload control information OCI is configured to be applied to a notification request or a callback request, and the notification request or the callback request has a callback uniform resource identifier URI that matches the callback uniform resource identifier URI; Among them, when the scope is set to the network function NF service instance, the network function NF service set, the network function NF instance, or the network function NF set, and the service name, the overload control information OCI is configured to be applied to a notification request or callback request with a matching binding indication.

4. The method according to claim 3 further includes sending the binding indication matching the notification request or the callback request to the network function NF service producer.

5. A device for a communication network, the device comprising: The network function NF service producer or service communication agent SCP is configured to: receiving overload control information OCI from a network function NF service consumer, the OCI including scope information; as well as Based on the received overload control information OCI, throttling notifications toward overload targets and / or redirecting notifications toward other targets to reduce the flow of callback requests, The range information includes a range set to one of the following: The callback URI, or Network function NF service instance, network function NF service set, network function NF instance, or network function NF set, and service name; Wherein, when the scope is set to the callback uniform resource identifier URI, the overload control information OCI is configured to be applied to a notification request or a callback request, and the notification request or the callback request has a callback uniform resource identifier URI that matches the callback uniform resource identifier URI; Among them, when the scope is set to the network function NF service instance, the network function NF service set, the network function NF instance, or the network function NF set, and the service name, the overload control information OCI is configured to be applied to a notification request or callback request with a matching binding indication.

6. The apparatus according to claim 5, wherein the network function service producer or service communication agent is further configured to: A binding indication matching the notification request or the callback request is received from the network function NF service consumer.

7. The device according to claim 5, wherein the device comprises the service communication agent SCP, and wherein the service communication agent is further configured to: A route binding indication is received from the network function NF service producer in one or more of the notification requests or callback requests.

8. The apparatus of claim 5, wherein the throttling comprises: Throttle any notifications sent towards the network function NF service consumer.

9. The device of claim 5, wherein the throttling notification comprises: Throttling notifications handled by the overloaded service.

10. The apparatus of claim 5, wherein the throttling comprises: The throttling notification targets the entire network function NF set or the network function NF service set.

11. The apparatus of claim 5, wherein the redirecting comprises: The notification is sent to the alternative network function NF consumer instance.

12. The apparatus according to any one of claims 5 to 11, wherein: When the callback uniform resource identifier URI of a notification request or a callback request contains the same scheme, the same authority, and has a path that includes the callback uniform resource identifier URI set within the scope of the overload control information OCI, the callback uniform resource identifier URI of the notification request or the callback request matches the callback uniform resource identifier URI set in the scope of the scope information of the overload control information OCI.

13. The apparatus according to any one of claims 5 to 11, wherein: The scope of the scope information of the overload control information OCI matches the binding indication, and the binding indication is associated with a subscription when at least one of the following occurs: The overload control information OCI indicates an identifier of a network function NF set, and the subscription is bound to the identifier of the network function NF set; The overload control information OCI indicates an identifier of a network function NF instance, and the subscription is bound to the identifier of the network function NF instance; The overload control information OCI indicates an identifier of a network function NF service set, and the subscription is bound to the identifier of the network function NF service set; The overload control information OCI indicates an identifier of the network function NF service instance, and the subscription is bound to the identifier of the network function service instance; or The overload control information OCI indicates any one of the following: the identifier of the network function NF set, the identifier of the network function NF instance, or the identified network function NF service set, and the service name, and the subscription is bound to the identifier of the network function NF set, the identifier of the network function NF instance, or the identified network function NF service set, and the service name.

14. A method performed by a network function NF service producer or a service communication agent SCP in a communication network, the method comprising: Receiving overload control information OCI from a network function NF service consumer, wherein the OCI includes scope information; as well as Based on the received overload control information OCI, throttling notifications toward the overload target and / or redirecting notifications toward other targets to reduce the flow of callback requests, The range information includes a range that can be set to at least one of the following: The callback URI, or A network function NF service instance, a network function NF service set, or a network function NF instance or a network function NF set, and a service name; Wherein, when the scope is set to the callback uniform resource identifier URI, the overload control information OCI is configured to be applied to a notification request or a callback request, and the notification request or the callback request has a callback uniform resource identifier URI that matches the callback uniform resource identifier URI; Among them, when the scope is set to the network function NF service instance, the network function NF service set, the network function NF instance, or the network function NF set, and the service name, the overload control information OCI is configured to be applied to a notification request or callback request with a matching binding indication.

15. The method according to claim 14, further comprising: A binding indication is received from the network function NF service consumer, where the binding indication matches the notification request or the callback request.

16. The method according to claim 14, wherein the method is performed by the service communication agent SCP, and wherein the method further comprises receiving, at the service communication agent SCP, a route binding indication in one or more of the notification requests or callback requests from the network function NF service producer.

17. The method according to claim 14, wherein the throttling comprises throttling any notifications sent towards the network function NF service consumer, or wherein the throttling comprises throttling notifications handled by the overloaded service, or The throttling includes throttling notifications targeting the entire network function NF set or the network function NF service set.

18. The method according to claim 14, wherein the redirecting comprises sending the notification to an alternative network function NF consumer instance.

19. The method according to any one of claims 14 to 18, wherein: When the callback uniform resource identifier URI of a notification request or a callback request contains the same scheme, the same authority, and has a path that includes the callback uniform resource identifier URI set within the scope of the overload control information OCI, the callback uniform resource identifier URI of the notification request or the callback request matches the callback uniform resource identifier URI set in the scope of the scope information of the overload control information OCI.

20. The method according to any one of claims 14 to 18, wherein: The scope of the scope information of the overload control information OCI matches the binding indication, and the binding indication is associated with a subscription when at least one of the following occurs: The overload control information OCI indicates an identifier of a network function NF set, and the subscription is bound to the identifier of the network function NF set; The overload control information OCI indicates an identifier of a network function NF instance, and the subscription is bound to the identifier of the network function NF instance; The overload control information OCI indicates an identifier of a network function NF service set, and the subscription is bound to the identifier of the network function NF service set; The overload control information OCI indicates an identifier of the network function NF service instance, and the subscription is bound to the identifier of the network function service instance; or The overload control information OCI indicates any one of the following: the identifier of the network function NF set, the identifier of the network function NF instance, or the identified network function NF service set, and the service name, and the subscription is bound to the identifier of the network function NF set, the identifier of the network function NF instance, or the identified network function NF service set, and the service name.

Images