Method, apparatus, and computer program

Abstract

Embodiments of the present disclosure relate to a method, an apparatus, and a computer program. There is provided an apparatus comprising means for: sending a first service request to a first producer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; and receiving a service response to the first service request from the first producer network function.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate to methods, apparatuses, systems, and computer programs, and particularly, but not limited to, requesting and providing Network Function (NF) services. Background Art

[0002] A communication network can be considered as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards provided by 3GPP are the so-called 3GPP standards for generations of cellular technology, such as the 3GPP standards for 4G technology and the 3GPP standards for 5G technology. Summary of the Invention

[0004] Some example embodiments of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate the key or essential features of the embodiments of the present disclosure, nor are they intended to be used to limit the scope thereof. In view of the present disclosure, those skilled in the art will readily understand other features, aspects, and elements.

[0005] According to one aspect, an apparatus is provided, comprising components for: sending a first service request to a first producer network function, the first service request comprising: information indicating the requested service, and information identifying a second producer network function that is unable to provide the requested service; and receiving a service response to the first service request from the first producer network function.

[0006] The component may also be configured to: send a second service request to a second producer network function, the second service request including information indicating a requested service; determine that no response to the second service request is received from the second producer network function within a time period; and, in response to determining that no response to the second service request is received within a time period, send the first service request to the first producer network function.

[0007] The component may also be configured to: send a second service request to a second producer network function, the second service request including information indicating a requested service; receive a second service response from the second producer network function rejecting the second service request; and send the first service request to the first producer network function in response to receiving the second service response rejecting the second service request.

[0008] The component can also be used to: send a second service request to the second producer network function, the second service request including: information indicating the requested service; receive a second service response from the second producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function; and in response to receiving the second service response, send the first service request to the first producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function.

[0009] The second service response may include information indicating a reason for the redirection, and wherein the first service request further includes information indicating a reason for the redirection.

[0010] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0011] The component may also be configured to: determine, based on previously received information, that the second producer network function is unable to provide the requested service; and send the first service request in response to determining that the second producer network function is unable to provide the requested service.

[0012] The first producer network function and the second producer network function may be the same type of network function.

[0013] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0014] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0015] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0016] According to one aspect, an apparatus is provided that includes components for: receiving a first service request from a consumer network function, the first service request including: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; determining whether to provide the requested service; and based on the determination, sending a service response to the first service request to the consumer network function.

[0017] The first service request may further include information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

[0018] The first service request may also include information indicating that the second producer network function did not respond to, rejected, or redirected the second service request for the requested service.

[0019] The first service request may further include information indicating that the first service request is a redirection request, and the first service request may further include information indicating a reason for the redirection.

[0020] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0021] The component may also be configured to determine, based on the first service request, to avoid redirecting the first service request and / or one or more additional service requests for the requested service to the second producer network function.

[0022] The component may also be configured to: receive a first service request and / or one or more additional service requests for a requested service; determine that the first service request and / or one or more additional service requests are to be redirected away from a first producer network function; and in response to determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function and determining to avoid redirecting the first service request and / or one or more additional service requests to a second producer network function, discover one or more candidate producer network functions to which the first service request and / or one or more additional service requests may be redirected, wherein the one or more candidate producer network functions exclude the second producer network function.

[0023] Discovering one or more candidate producer network functions may include: sending a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the second producer network function is to be excluded from a list of candidate producer network functions; and receiving from the network repository function a list of candidate producer network functions for providing the requested service, wherein the list of candidate producer network functions excludes the second producer network function.

[0024] The information indicating that the second producer network function is to be excluded from the list of candidate producer network functions may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0025] The first producer network function and the second producer network function may be the same type of network function.

[0026] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0027] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0028] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0029] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: send a first service request to a first producer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that is unable to provide the requested service; and receive a service response to the first service request from the first producer network function.

[0030] At least one processor may also be configured to cause the apparatus to: send a second service request to a second producer network function, the second service request including information indicating a requested service; determine that no response to the second service request is received from the second producer network function within a time period; and in response to determining that no response to the second service request is received within a time period, send the first service request to the first producer network function.

[0031] At least one processor can also be configured to cause the device to: send a second service request to the second producer network function, the second service request including: information indicating the requested service; receive a second service response from the second producer network function rejecting the second service request; and in response to receiving the second service response rejecting the second service request, send the first service request to the first producer network function.

[0032] At least one processor can also be configured to cause the device to: send a second service request to the second producer network function, the second service request including: information indicating the requested service; receive a second service response from the second producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function; and in response to receiving the second service response, send the first service request to the first producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function.

[0033] The second service response may include information indicating a reason for the redirection, and wherein the first service request further includes information indicating a reason for the redirection.

[0034] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0035] The at least one processor may be further configured to cause the apparatus to: determine, based on previously received information, that the second producer network function is unable to provide the requested service; and send the first service request in response to determining that the second producer network function is unable to provide the requested service.

[0036] The first producer network function and the second producer network function may be the same type of network function.

[0037] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0038] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0039] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0040] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a first service request from a consumer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that is unable to provide the requested service; determine whether to provide the requested service; and based on the determination, send a service response to the first service request to the consumer network function.

[0041] The first service request may further include information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

[0042] The first service request may also include information indicating that the second producer network function did not respond to, rejected, or redirected the second service request for the requested service.

[0043] The first service request may further include information indicating that the first service request is a redirection request, and the first service request may further include information indicating a reason for the redirection.

[0044] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0045] The at least one processor may be further configured to cause the apparatus to: determine, based on the first service request, to avoid redirecting the first service request and / or one or more additional service requests for the requested service to the second producer network function.

[0046] At least one processor may also be configured to cause the apparatus to: receive a first service request and / or one or more additional service requests for a requested service; determine that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function; and in response to determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function and determining to avoid redirecting the first service request and / or one or more additional service requests to a second producer network function, discover one or more candidate producer network functions to which the first service request and / or one or more additional service requests may be redirected, wherein the one or more candidate producer network functions exclude the second producer network function.

[0047] At least one processor may also be configured to cause the apparatus to: send a discovery request to the network repository function, the discovery request including information identifying the requested service and indicating that the second producer network function is to be excluded from the list of candidate producer network functions; and receive from the network repository function a list of candidate producer network functions for providing the requested service, wherein the list of candidate producer network functions excludes the second producer network function.

[0048] The information indicating that the second producer network function is to be excluded from the list of candidate producer network functions may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0049] The first producer network function and the second producer network function may be the same type of network function.

[0050] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0051] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0052] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0053] According to one aspect, a method is provided, comprising: sending a first service request to a first producer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; and receiving a service response to the first service request from the first producer network function.

[0054] The method may further include: sending a second service request to a second producer network function, the second service request including information indicating the requested service; determining that no response to the second service request is received from the second producer network function within a certain time period; and in response to determining that no response to the second service request is received within the certain time period, sending the first service request to the first producer network function.

[0055] The method may also include: sending a second service request to a second producer network function, the second service request including: information indicating the requested service; receiving a second service response from the second producer network function rejecting the second service request; and sending the first service request to the first producer network function in response to receiving the second service response rejecting the second service request.

[0056] The method may also include: sending a second service request to the second producer network function, the second service request including: information indicating the requested service; receiving a second service response from the second producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function; and in response to receiving the second service response, sending the first service request to the first producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function.

[0057] The second service response may include information indicating a reason for the redirection, and wherein the first service request further includes information indicating a reason for the redirection.

[0058] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0059] The method may further include determining, based on previously received information, that the second producer network function is unable to provide the requested service; and sending the first service request in response to determining that the second producer network function is unable to provide the requested service.

[0060] The first producer network function and the second producer network function may be the same type of network function.

[0061] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0062] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0063] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0064] According to one aspect, a method is provided, comprising: receiving a first service request from a consumer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; determining whether to provide the requested service; and based on the determination, sending a service response to the first service request to the consumer network function.

[0065] The first service request may further include information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

[0066] The first service request may also include information indicating that the second producer network function did not respond to, rejected, or redirected the second service request for the requested service.

[0067] The first service request may further include information indicating that the first service request is a redirection request, and the first service request may further include information indicating a reason for the redirection.

[0068] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0069] The method may further include determining, based on the first service request, to avoid redirecting the first service request and / or one or more further service requests for the requested service to the second producer network function.

[0070] The method may also include: receiving a first service request and / or one or more additional service requests for a requested service; determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function; and in response to determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function and determining to avoid redirecting the first service request and / or one or more additional service requests to a second producer network function, discovering one or more candidate producer network functions to which the first service request and / or one or more additional service requests can be redirected, wherein the one or more candidate producer network functions exclude the second producer network function.

[0071] Discovering one or more candidate producer network functions may include: sending a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the second producer network function is to be excluded from a list of candidate producer network functions; and receiving from the network repository function a list of candidate producer network functions for providing the requested service, wherein the list of candidate producer network functions excludes the second producer network function.

[0072] The information indicating that the second producer network function is to be excluded from the list of candidate producer network functions may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0073] The first producer network function and the second producer network function may be the same type of network function.

[0074] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0075] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0076] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0077] According to one aspect, a computer-readable medium is provided, comprising instructions that, when executed by an apparatus, cause the apparatus to at least perform the following: send a first service request to a first producer network function, the first service request comprising: information indicating the requested service, and information identifying a second producer network function that is unable to provide the requested service; and receive a service response to the first service request from the first producer network function.

[0078] When executed by the device, the instruction can also cause the device to perform: sending a second service request to the second producer network function, the second service request including information indicating the requested service; determining that no response to the second service request is received from the second producer network function within a certain time period; and in response to determining that no response to the second service request is received within a certain time period, sending the first service request to the first producer network function.

[0079] When executed by the device, the instruction can also cause the device to perform: sending a second service request to the second producer network function, the second service request including: information indicating the requested service; receiving a second service response from the second producer network function rejecting the second service request; and in response to receiving the second service response rejecting the second service request, sending the first service request to the first producer network function.

[0080] When executed by the device, the instruction can also cause the device to perform: sending a second service request to the second producer network function, the second service request including: information indicating the requested service; receiving a second service response from the second producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function; and in response to receiving the second service response, sending the first service request to the first producer network function, the second service response including: information indicating that the second service request will be redirected to the first producer network function.

[0081] The second service response may include information indicating a reason for the redirection, and wherein the first service request further includes information indicating a reason for the redirection.

[0082] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0083] When executed by the device, the instruction may also cause the device to perform: determining, based on previously received information, that the second producer network function cannot provide the requested service; and sending the first service request in response to determining that the second producer network function cannot provide the requested service.

[0084] The first producer network function and the second producer network function may be the same type of network function.

[0085] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0086] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0087] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0088] According to one aspect, a computer-readable medium is provided, comprising instructions that, when executed by an apparatus, cause the apparatus to at least perform the following: receive a first service request from a consumer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that is unable to provide the requested service; determine whether to provide the requested service; and based on the determination, send a service response to the first service request to the consumer network function.

[0089] The first service request may further include information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

[0090] The first service request may also include information indicating that the second producer network function did not respond to, rejected, or redirected the second service request for the requested service.

[0091] The first service request may further include information indicating that the first service request is a redirection request, and the first service request may further include information indicating a reason for the redirection.

[0092] The information indicating the reason for the redirection may include at least one of: information indicating that the second producer network function is overloaded; information indicating that the second producer network function is shutting down; or information indicating that another producer network function owns the resource for which the second service request is directed.

[0093] When executed by the apparatus, the instructions may further cause the apparatus to: based on the first service request, determine to avoid redirecting the first service request and / or one or more additional service requests for the requested service to a second producer network function.

[0094] When executed by the device, the instruction may also cause the device to perform: receiving a first service request and / or one or more additional service requests for the requested service; determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function; and in response to determining that the first service request and / or one or more additional service requests are to be redirected away from the first producer network function and determining to avoid redirecting the first service request and / or one or more additional service requests to the second producer network function, discovering one or more candidate producer network functions to which the first service request and / or one or more additional service requests can be redirected, wherein the one or more candidate producer network functions exclude the second producer network function.

[0095] Discovering one or more candidate producer network functions may include: sending a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the second producer network function is to be excluded from a list of candidate producer network functions; and receiving from the network repository function a list of candidate producer network functions for providing the requested service, wherein the list of candidate producer network functions excludes the second producer network function.

[0096] The information indicating that the second producer network function is to be excluded from the list of candidate producer network functions may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0097] The first producer network function and the second producer network function may be the same type of network function.

[0098] The first producer network function and the second producer network function may belong to the same network function set, or the same network function service instance set.

[0099] The information identifying the second producer network function that cannot provide the requested service may include at least one of the following items: an identifier of the second producer network function; an identifier of a service instance of the second producer network function; an identifier of a set of producer network functions to which the second producer network function belongs; or an identifier of a set of service instances of the second producer network function.

[0100] The first service request may further include information indicating that the second producer network function rejected the service request for the requested service due to an overload of the second producer network function.

[0101] According to one aspect, a non-transitory computer-readable medium is provided, comprising program instructions, which, when executed by an apparatus, cause the apparatus to perform a method according to at least any one of the preceding aspects.

[0102] In the above, many different embodiments have been described. It should be understood that further embodiments can be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0103] Some example embodiments will now be described, by way of non-limiting and illustrative examples only, with reference to the accompanying drawings, in which:

[0104] Figure 1 shows a representation of a 5th generation communication system;

[0105] Figure 2 According to some example embodiments, Figure 1 representation of a device of a communication system;

[0106] Figure 3 shows a representation of an apparatus according to some example embodiments;

[0107] Figure 4 A method / methods according to some examples are shown;

[0108] Figure 5 shows a signaling procedure according to some examples; and

[0109] Figure 6 Schematic representations of apparatus according to some examples are shown. DETAILED DESCRIPTION

[0110] Various exemplary embodiments will be explained below with reference to a communication device capable of communicating with a communication system. Figure 1 、 Figure 2 ,as well as Figure 3 Briefly explain the 5th Generation Communication System (5GS), its access network and core network (5GC), and communication equipment.

[0111] Figure 1A schematic representation of a 5G communication system (5GS) is shown. The 5GS may include a user equipment (UE), or terminal 100, an access network (such as a 5G radio access network (5G-RAN) 101 or a next generation radio access network (NG-RAN), a 5G core network 102, and one or more application functions 103. The application functions 103 may be deployed in the 5GS as trusted application functions, or may be deployed or hosted on one or more application servers in a data network (DN) 104. Such application functions are non-trusted application functions. The 5GS connects the UE to the data network, the access network, and the 5GC 102 (e.g., the UPF of the 5GC).

[0112] The 5G-RAN 101 may include one or more radio access nodes, such as gNodeBs (gNBs). A gNB may include one or more gNodeB (GNB) distributed units connected to one or more gNodeB (GNB) centralized units.

[0113] The 5GC may include the following network functions: network slice selection function (NSSF); network exposure function (NEF) 105; network repository function (NRF); policy control function (PCF); unified data management (UDM) 106; application function (AF) 103; authentication server function (AUSF) 107; access and mobility management function (AMF) 108; session management function (SMF) 109; and user plane function (UPF) 110. Figure 1 Also shown are the various interfaces (N1, N2, etc.) that may be implemented between the various elements of the system.

[0114] Figure 2 Diagram for controlling Figure 1 The illustrated access network (eg, Figure 1, an example of a control device 200 for controlling functions of a 5G-RAN or NG-RAN (as illustrated in FIG). The control device 200 may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and a network interface 214. The at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute appropriate software code 215. Execution of the software code 215 may, for example, cause the device to perform operations for controlling functions of an access network. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 to control another function of the 5G-RAN or NG-RAN. In some embodiments, each function of the 5G-RAN or NG-RAN is deployed or hosted on the control device 200. In alternative embodiments, two or more functions of the 5G-RAN or NG-RAN may share a control device.

[0115] Figure 3 An example of a communication device 300 is shown, such as Figure 1 . The communication device 300 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples of the communication device 300 include: user equipment, a mobile station (MS) or a mobile device, such as a mobile phone or a so-called "smartphone", a computer equipped with a wireless interface card or other wireless interface facility (e.g., a USB dongle), a personal data assistant (PDA) or tablet computer provided with wireless communication capabilities, a machine type communication (MTC) device, an Internet of Things (IoT) type communication device, or any combination of these devices or similar devices. The communication device 300 may include a transceiver for sending and / or receiving wireless signals, such as radio signals, for example, carrying communications. The communication may be one or more of voice, electronic mail (email), text messaging, multimedia data, machine data, etc.

[0116] The communication device 300 may receive wireless signals (eg, radio signals) over the air or radio interface 307 via suitable means for receiving, and may transmit wireless signals via suitable means for transmitting radio signals. Figure 3 , a transceiver is schematically represented by block 306. The transceiver 306 may include, for example, radio components and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna.

[0117] The communication device 300 may be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for software and hardware assistance to perform the tasks it is designed to perform, including controlling access to the network (e.g. Figure 1 The at least one processor 301 is coupled to RAM 302b and ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, enable execution of one or more operations of the communication device. The software code 308 may be stored in ROM 302a.

[0118] The processor, ROM and RAM, transceiver, and other circuitry (e.g., a modem) of the communication device may be provided on a circuit board, a chipset, or a system on a chip. The circuit board, chipset, or system on a chip is indicated by reference numeral 304. The communication device 300 may optionally have a user interface, such as a keyboard 305, a touch screen or touchpad, a combination thereof, or the like. Depending on the type of communication device, one or more displays, speakers, and microphones may also be provided.

[0119] 5GC has been defined as a service-based architecture (SBA), whereby NF service producers (pNFs - producer network functions) expose services that NF service consumers (cNFs - consumer network functions) can consume using SBIs (service-based interfaces). To request a service, a cNF can send a request message (e.g., an HTTP request) to a pNF, where the request message includes the information required to invoke a specific service or service operation.

[0120] After receiving the request message, the pNF can determine whether to provide the requested service. In some cases, the request may be rejected by the pNF, for example, because the pNF cannot provide the requested service, is temporarily overloaded, or is scheduled to shut down. The pNF can indicate in a response message to the cNF that the cNF should perform pNF reselection to an alternative pNF.

[0121] After receiving a response message from the pNF (indicating that the request has been rejected or redirected) or after not receiving a response message within a certain period of time, the cNF may send another request message to the alternative pNF. For example, when the response message from the pNF indicates that the cNF should perform pNF reselection to the alternative pNF, the cNF may send another request message to the alternative pNF. The additional request message may include additional information indicating that the additional request message is being resent due to receiving an error or rejection / redirection response—for example, the additional information may indicate that the additional request message is related to the reselection of the alternative NF; or that the additional request message is a resend of an earlier request message (for example, a request message that was sent but was rejected due to a temporary failure or timeout).

[0122] It should be noted that the SBA model can present issues. For example, in one scenario, three pNFs (pNF1, pNF2, and pNF3) support the same service. A cNF sends a request to pNF1, and pNF1 rejects or redirects the request because it cannot provide the requested service. The redirection could be due to overload or administrative reasons (e.g., pNF1 shutting down gracefully). Consequently, the cNF redirects the request to pNF2 or pNF3.

[0123] As explained above, when a service request is rejected by pNF1 or redirected by pNF1 to pNF2, the cNF may resend the request to pNF2 including additional information indicating that the request was resent to pNF2 due to an error or redirection response. However, pNF2 does not obtain any information about the identity of pNF1 initially selected by the cNF or the identity of pNF1 that rejected or redirected the request.

[0124] Therefore, pNF2 may not be able to determine from which pNF (i.e., pNF1) the request was redirected, nor the pNF that rejected the request. In other words, pNF2 may not be able to determine from which pNF the redirection came or due to which pNF's error the particular request was received from the cNF.

[0125] If pNF2 is unable to provide the requested service (e.g., due to overload), pNF2 may attempt to redirect the request to pNF1, resulting in a redirection loop and failure to provide the requested service. Furthermore, because pNF2 is unaware of whether pNF1 is facing a temporary or permanent problem, pNF2 may consider pNF1 for future redirections. That is, more generally, pNF2 may be unaware of the status and health of other pNFs, which can lead to poor network performance. Debugging and eliminating such errors can become more difficult, and optimizing the planning of pNF resources and enabling K8 orchestration to scale in and out more dynamically may also become more difficult.

[0126] Some examples of the present disclosure address one or more of these issues. In some examples of the present disclosure, when a cNF sends a service request to a pNF, the cNF can include in the service request information identifying one or more pNFs that are unable to provide the requested service. In this way, the pNF receiving the service request can understand the status of other pNFs and can use this information to optimize network performance. For example, based on the request, the pNF can avoid redirecting one or more additional service requests to one or more pNFs identified in the service request as unable to provide the requested service, thereby avoiding redirection loops.

[0127] right Figure 4 Reference is made to FIG, which illustrates methods according to some examples.

[0128] At 400, the cNF sends a first service request to the first pNF, the first service request including information indicating a requested service and information identifying a second pNF that cannot provide the requested service.

[0129] At 402, the cNF receives a service response to a first service request from a first pNF.

[0130] At 404, the first pNF receives a first service request from the cNF, the first service request including information indicating a requested service and information identifying a second pNF that cannot provide the requested service.

[0131] At 406, the first pNF determines whether to provide the requested service.

[0132] At 408, the first pNF sends a service response to the first service request to the cNF.

[0133] The first pNF and the second pNF can be the same type of NF—for example, the first pNF and the second pNF can both be AMFs or SMFs. In some examples, the first pNF and the second pNF can belong to the same NF set or the same NF service instance set. In some examples, from the perspective of the first pNF, the second pNF can be referred to as a peer NF. In some examples, the information included in the first service request can identify / indicate one or more second pNFs.

[0134] In some examples, the information identifying the second pNF that is unable to provide the requested service may include at least one of the following:

[0135] The identifier of the second pNF (e.g., NF-Instance);

[0136] The identifier of the service instance of the second pNF (e.g., NF-Set);

[0137] an identifier of the pNF set to which the second pNF belongs (e.g., NF-Service-Instance and / or NF-Instance); or

[0138] The identifier of the service instance set of the second pNF (e.g., NF-Service-Set).

[0139] Table 1 below provides an example of the OCI support scope signaled by the CNF in the service request.

[0140]

[0141]

[0142] Table 1 - Example of OCI support scope signaled by a CNF in a service request

[0143] In some examples, the cNF may send a second service request to the second pNF, the second service request including information indicating the requested service. The second service request may be sent to the second pNF before the first service request is sent to the first pNF.

[0144] In some examples, when no response to the second service request is received within a certain period of time, the cNF may send the first service request. For example, the cNF may determine that no response to the second request is received within a certain period of time, and in response to determining that no response to the second request is received within the certain period of time, send the first service request to the first pNF.

[0145] In some examples, the cNF may receive a second service response from the second pNF that rejects the second service request. In response to receiving the second service response that rejects the second service request, the cNF may send the first service request to the first pNF.

[0146] In some examples, the cNF may receive a second service response from the second pNF, the second service response including information indicating that the second service request is to be redirected to the first pNF. In response to receiving the second service response redirecting the second service request, the cNF may send the first service request to the first pNF.

[0147] In some examples, the second service response may further include information indicating a reason why the second pNF rejected or redirected the second service request. The information indicating the reason why the second pNF rejected or redirected the second service request may, for example, include at least one of the following: information indicating that the second pNF is overloaded; information indicating that the second pNF is shutting down; or information indicating that another pNF owns the resources targeted by the second service request. In some examples, the information indicating the reason why the second pNF rejected or redirected the second service request may be as defined in clause 5.2.3.2.9 of 3GPP TS 29.500.

[0148] In some examples, the second service response may include a temporary redirection response or a permanent redirection response. Table 2 below provides an example of the content of a redirection response message.

[0149]

[0150] Table 2 — Example content of a redirect message

[0151] In some examples, a first service request sent to a first pNF may include information associated with a second producer network function that is unable to provide the requested service. For example, the first service request may include information indicating why the second pNF is unable to provide the requested service. For example, the first service request may include information indicating that the second pNF did not respond to, rejected, or redirected the second service request for the requested service. In some examples, the first service request may also include information indicating that the first service request is a request to be resent or redirected to an alternative pNF.

[0152] In some examples, the information included in the first service request may include at least one of the following:

[0153] - Peer NF Instance ID (e.g., NF Instance ID of the second pNF);

[0154] - Peer NF service instance ID (e.g., the service instance of the second pNF);

[0155] - Peer NF Set ID (e.g., the Set ID of the second pNF);

[0156] - Peer NF service set ID (e.g., the service set ID of the second pNF);

[0157] -Redirection reason: The redirection reason may be received by the cNF from the second pNF in the second service response; or

[0158] - Overload scope: When / if the redirection reason indicates "overload", the overload scope may inform / indicate whether the second pNF rejects the request due to an NF service instance, NF instance, NF service set, or NF set being overloaded. In some examples, the overload scope may be signaled from the second pNF to the cNF in a header (e.g., a 3gpp-SBI-Oci header).

[0159] In some embodiments, this information may be included in the SBI header.

[0160] In some examples, the first pNF can determine, based on the first service request, to avoid redirecting the first service request and / or one or more additional service requests to the second pNF. In some examples, the first pNF can determine to avoid redirecting the first service request and / or one or more additional service requests to the second pNF for a certain duration. For example, the determination can be based on information identifying the second pNF that cannot provide the requested service and information indicating a reason why the second pNF rejected or redirected the second service request (if such information was included in the first service request).

[0161] In some examples, a first pNF may receive one or more additional service requests for a requested service from a cNF and / or one or more other cNFs. The first pNF may determine that the first service request and / or the one or more additional service requests need to be redirected away from the first pNF. In response to determining to redirect the first service request and / or the one or more additional service requests away from the first pNF and to avoid redirecting the first service request and / or the one or more additional service requests to a second pNF, the first pNF may discover one or more candidate pNFs to which the first service request and / or the one or more additional service requests may be redirected. The one or more candidate pNFs may exclude the second pNF.

[0162] For example, a first pNF may send a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the second pNF is to be excluded from a list of candidate producer network functions. The first pNF may then receive from the network repository function a list of candidate pNFs for providing the requested service, wherein the list of candidate pNFs excludes the second pNF.

[0163] The information identifying / indicating that the second pNF is to be excluded from the candidate pNF list may include at least one of the following:

[0164] The identifier of the second pNF;

[0165] The identifier of the service instance of the second pNF;

[0166] an identifier of the pNF set to which the second pNF belongs; or

[0167] The identifier of the service instance set of the second pNF.

[0168] Table 3 below provides an example definition of the content of a discovery request that may be sent from the first pNF to the network repository function:

[0169]

[0170]

[0171] Table 3 - Example definition of discovery request content

[0172] In some examples, event logs and key performance indicators (KPIs) can be generated based on information included in the first service request. The event logs and KPIs can be used to scale out corresponding pNF types and / or for debugging and troubleshooting operations. For example, when a certain pNF type sends a greater number of redirects / rejections to service requests than expected (which can be indicated in the first service request), it can be determined to increase the number of pNFs of that type.

[0173] right Figure 5 Reference is made to FIG, which shows a signaling procedure according to some examples.

[0174] At 500, the cNF discovers one or more pNFs to which it will send a service request for a service and selects one of the pNFs. Figure 5 In the example, cNF finds pNF1 and pNF2 and selects pNF2.

[0175] At 502, the cNF sends a second service request to the pNF2. The second service request may be as described above.

[0176] At 504, the cNF may determine that pNF2 is unable to provide the requested service. As previously described, this may be based on:

[0177] Determining that no response to the second request is received within a certain period of time (as shown at 504a);

[0178] A second service response is received from pNF2, which denies the second service request (as shown at 504b) or redirects the second service request to pNF1 (as shown at 504c); or

[0179] Based on previously received information (eg, a service response previously received from pNF2), the cNF may determine that pNF2 is unable to provide the requested service (as shown at 504d).

[0180] At 506, the cNF sends a first service request to the pNF1. The first service request is as described above. That is, the first service request includes: information identifying a second pNF that cannot provide the requested service, i.e., information identifying pNF2.

[0181] In some embodiments, the cNF sends the first service request to the pNF1 if / when the following occurs:

[0182] -(Determine) No response to the second request is received within a certain period of time;

[0183] -A second service response is received from pNF2 that rejects the second service request or redirects the second service request to the pNF1; or

[0184] -(Determine) pNF2 cannot provide the requested service (e.g., based on previously received information).

[0185] At 508, the pNF1 determines whether to provide the requested service.

[0186] At 510, based on the determination at 508, the pNF1 sends a service response to the first service request to the cNF.

[0187] The following provides several non-limiting examples of the information included in the first service request (3gpp-Sbi-Request-Info) only by way of example to further illustrate the concepts of the present disclosure.

[0188] Example 1: For a request that is re-sent to the pNF1 because it was rejected by the original target pNF2 due to a temporary rejection reason:

[0189] 3gpp-Sbi-Request-Info: retrans = true; redirect = true; reason = temporary-rejection-cause; receivedrejectioncause = INSUFFICIENT_RESOURCES; NF-instance:

[0190] <pNF2 NF instance ID>; NF-service-instance: <pNF2 NF service instance ID>

[0191] Example 2: For a request that is sent to an alternative NF because the original target NF (pNF2) is inaccessible:

[0192] 3gpp-Sbi-Request-Info: redirect=true; reason=unreachable; NF-instance: <pNF2NF instance ID>; NF-service-instance: <pNF2NF service instance ID>;

[0193] Example 3: For a request sent to an alternative NF due to the original target NF (pNF2) redirecting the request for some specific reasons: 3gpp-Sbi-Request-Info: redirect=true; reason=3xx-redirect; NF-instance: <pNF2NF instance ID>; NF-service-instance: <pNF2NF service instance ID>; redirection-cause: <cause information>

[0194] Example 4: For a request sent to an alternative NF due to the original target NF (pNF2) being overloaded:

[0195] 3gpp-Sbi-Request-Info: redirect=true; reason=overloaded; NF-instance: <pNF2NF instance ID>; NF-service-instance: <pNF2NF service instance ID>; overload-scope: <overload scope, e.g., indicating the overload of the pNF2 service instance>

[0196] Some examples have been described where the cNF sends a service request for the requested service to the first pNF, and the service request includes information indicating that the second pNF cannot provide the requested service. This helps to optimize the functionality of the network, for example, by enabling the first pNF to avoid redirecting the service request for the service to the second pNF.

[0197] In some examples, a device is provided that includes components for: sending a first service request to a first producer network function, the first service request including: information indicating the requested service, and information identifying a second producer network function that cannot provide the requested service; and receiving a service response to the first service request from the first producer network function.

[0198] In some examples, a device is provided that includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: send a first service request to a first producer network function, the first service request including: information indicating the requested service, and information identifying a second producer network function that cannot provide the requested service; and receive a service response to the first service request from the first producer network function.

[0199] In some examples, the apparatus is or includes a consumer NF. In the present disclosure, an apparatus being / including a consumer NF refers to an apparatus / device configured to provide / perform at least part of the functionality of a consumer NF.

[0200] In some examples, an apparatus is provided that includes components for: receiving a first service request from a consumer network function, the first service request including: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; determining whether to provide the requested service; and based on the determination, sending a service response to the first service request to the consumer network function.

[0201] In some examples, a device is provided, comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receive a first service request from a consumer network function, the first service request comprising: information indicating a requested service, and information identifying a second producer network function that cannot provide the requested service; determine whether to provide the requested service; and send a service response to the first service request to the consumer network function.

[0202] In some examples, the apparatus is or includes a producer NF. In the present disclosure, a device that is / includes a producer NF refers to an apparatus / device configured to provide / perform at least part of the functionality of a producer NF.

[0203] Figure 6 Schematic representations of non-volatile storage media 1100a (e.g., a computer compact disc (CD) or digital versatile disc (DVD)) and 1100b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 1102 that, when executed by a processor, allow the processor to perform Figure 4 One or more steps of a method.

[0204] It should be understood that the above references to various network functions (e.g., AMF, SMF, TNF, etc.) may include devices that perform at least some functionality associated with these network functions. In addition, the device including the network function may include a virtual network function instance of the network function.

[0205] It should be understood that the apparatus may include or be coupled to other units or modules for transmission and / or reception, such as a radio part or a radio head. Although the apparatus is described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0206] It should be noted that although some embodiments have been described in relation to 5G networks, similar principles can be applied to other networks and communication systems. Thus, although certain embodiments have been described above by way of example with reference to certain example architectures of wireless networks, technologies, and standards, the embodiments can be applied to any other suitable form of communication system in addition to the communication system illustrated and described herein.

[0207] It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0208] As used herein, “at least one of: ” and “at least one item of ” and similar expressions, where a list of two or more elements is linked by “and” or “or”, mean at least any one element, or at least two or more elements, or at least all elements.

[0209] In general, various embodiments may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although various aspects of the present disclosure may be illustrated and described using block diagrams, flow charts, or other graphical representations, it is fully understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0210] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0211] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only) and

[0212] (b) a combination of hardware circuitry and software, such as (if applicable):

[0213] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0214] (ii) hardware processor(s) (including digital signal processor(s)) with software, software, and any portion of memory(s) that act together to enable a device (such as a mobile phone or server) to perform various functions), and (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) to operate, but in which case the software may not be present when not required for operation.

[0215] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. By way of example and where applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0216] The embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products) include software routines, applets and / or macros that can be stored in a data storage medium readable by any device, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. The one or more computer executable components may be at least one software code or a portion thereof.

[0217] Furthermore, it should be noted in this regard that any block of the logic flow in the figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media implemented within the processor such as memory chips or memory blocks, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, CDs. Physical media are non-transitory media.

[0218] The term "non-transitory" as used herein is a restriction to the medium itself (ie, tangible, not a signal), not to the persistence of data storage (eg, RAM versus ROM).

[0219] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0220] Various example embodiments of the present disclosure may be implemented in various components, such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert a logic-level design into a semiconductor circuit design that can be etched and formed on a semiconductor substrate.

[0221] The protection scope of various exemplary embodiments of the present disclosure is defined by the independent claims. The exemplary embodiments described in the present disclosure and their features (if any) that do not belong to the scope of the independent claims should be interpreted as examples that help understand the various exemplary embodiments of the present disclosure.

[0222] The foregoing description has been provided by way of non-limiting and illustrative examples, providing a complete and informative description of various exemplary embodiments of the present disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant art when the foregoing description is read in conjunction with the accompanying drawings and the appended claims. However, all such and similar teachings and modifications will still fall within the various exemplary embodiments of the present disclosure as set forth in the appended claims. As a non-limiting and illustrative example, yet another exemplary embodiment comprises a combination of one or more exemplary embodiments with any other exemplary embodiment previously discussed.

Claims

1. An apparatus comprising at least one processor and at least one memory, the memory storing instructions for consumer network functionality, the instructions, when executed by the at least one processor, causing the apparatus to at least: Sending a first service request to a first producer network function, the first service request including: Information indicating the service requested; receiving a first service response from the first producer network function, the first service response comprising: information indicating that the first service request is to be redirected to a second producer network function; Based on receiving the first service response, sending a second service request to the second producer network function, wherein the second service request includes: information indicating the requested service, and information identifying the first producer network function that cannot provide the requested service; and A second service response to the second service request is received from the second producer network function.

2. The apparatus according to claim 1, wherein the second service request further comprises: Information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

3. The apparatus according to claim 1, wherein the second service request further comprises: Information instructing the first producer network function to redirect the first service request for the requested service.

4. The apparatus of claim 1 , wherein the first service response comprises: Information indicating a reason for the redirection, and wherein the second service request further comprises: the information indicating a reason for the redirection.

5. The apparatus of claim 4 , wherein the information indicating the reason for the redirection comprises at least one of the following: Information indicating that a network function of the first producer is overloaded; Information indicating that the first producer network function is shutting down; or Information indicating that another producer network function owns the resource to which the first service request is directed.

6. An apparatus comprising at least one processor and at least one memory, the memory storing instructions for a second producer network function, the instructions, when executed by the at least one processor, causing the apparatus to at least: receiving a second service request from the consumer network function, the second service request comprising: information indicating a requested service, and information identifying a first producer network function that is unable to provide the requested service; determining whether to provide the requested service; as well as Based on the determination, a second service response to the second service request is sent to the consumer network function.

7. The apparatus according to claim 6, wherein the second service request further comprises: Information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

8. The apparatus according to claim 6, wherein the second service request further comprises: Information instructing the first producer network function to redirect a first service request for the requested service.

9. The apparatus according to claim 6, wherein the second service request further comprises: Information indicating the reason for the redirection.

10. The apparatus of claim 9, wherein the information indicating the reason for the redirection comprises at least one of the following: Information indicating that a network function of the first producer is overloaded; Information indicating that the first producer network function is shutting down; or Information indicating that another producer network function owns the resource targeted by the second service request.

11. The apparatus of claim 6, wherein the apparatus is further configured to: Based on the first service request, redirecting the second service request or one or more further service requests for the requested service to the first producer network function is avoided.

12. The device according to claim 11, wherein the device is further configured to receiving the one or more further service requests for the requested service; determining that the one or more further service requests are to be redirected away from the second producer network function; and In response to determining to redirect the one or more additional service requests away from the second producer network function and to avoid redirecting the one or more additional service requests to the second producer network function, discover one or more candidate producer network functions to which the one or more additional service requests may be redirected, wherein the one or more candidate producer network functions exclude the first producer network function.

13. The apparatus of claim 12, wherein discovering the one or more candidate producer network functions comprises: sending a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the first producer network function is to be excluded from a list of candidate producer network functions; and A list of candidate producer network functions for providing the requested service is received from the network repository function, wherein the list of candidate producer network functions excludes the first producer network function.

14. The apparatus of claim 6, wherein the first producer network function and the second producer network function are the same type of network functions. 15 . The apparatus according to claim 6 , wherein the first producer network function and the second producer network function belong to the same network function set or the same network function service instance set.

16. A method for consumer network functionality, the method comprising: sending a first service request to a first producer network function, the first service request comprising: information indicating a requested service; receiving a first service response from the first producer network function, the first service response comprising: information indicating that the first service request is to be redirected to a second producer network function; Based on receiving the first service response, sending a second service request to the second producer network function, wherein the second service request includes: information indicating the requested service, and information identifying the first producer network function that cannot provide the requested service; and A second service response to the second service request is received from the second producer network function.

17. The method according to claim 16, wherein the second service request further comprises: Information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

18. The method according to claim 16, wherein the second service request further comprises: Information instructing the first producer network function to redirect the first service request for the requested service.

19. The method of claim 16, wherein the first service response comprises: Information indicating a reason for the redirection, and wherein the second service request further comprises: the information indicating a reason for the redirection.

20. The method of claim 16, wherein the information indicating the reason for the redirection comprises at least one of: Information indicating that a network function of the first producer is overloaded; Information indicating that the first producer network function is shutting down; or Information indicating that another producer network function owns the resource targeted by the second service request.

21. A method for a second producer network function, the method comprising: receiving a second service request from a consumer network function, the second service request comprising: information indicating a requested service, and information identifying a first producer network function that is unable to provide the requested service; determining whether to provide the requested service; and Based on the determination, a second service response to the second service request is sent to the consumer network function.

22. The method according to claim 21, wherein the second service request further comprises: Information indicating that the first service request is a request sent to, or resent to, an alternative producer network function.

23. The method according to claim 21, wherein the second service request further comprises: Information instructing the first producer network function to redirect a first service request for the requested service.

24. The method according to claim 21, wherein the second service request further comprises: Information indicating the reason for the redirection.

25. The method of claim 24, wherein the information indicating the reason for the redirection comprises at least one of: Information indicating that a network function of the first producer is overloaded; Information indicating that the first producer network function is shutting down; or Information indicating that another producer network function owns the resource targeted by the second service request.

26. The method of claim 21, further comprising: Based on the first service request, redirecting the second service request or one or more further service requests for the requested service to the first producer network function is avoided.

27. The method of claim 21, further comprising: receiving the one or more further service requests for the requested service; determining that the one or more further service requests are to be redirected away from the second producer network function; as well as In response to determining to redirect the one or more additional service requests away from the second producer network function and to avoid redirecting the one or more additional service requests to the second producer network function, discover one or more candidate producer network functions to which the one or more additional service requests may be redirected, wherein the one or more candidate producer network functions exclude the first producer network function.

28. The method of claim 27, wherein discovering the one or more candidate producer network functions comprises: sending a discovery request to a network repository function, the discovery request including information identifying the requested service and indicating that the first producer network function is to be excluded from a list of candidate producer network functions; and A list of candidate producer network functions for providing the requested service is received from the network repository function, wherein the list of candidate producer network functions excludes the first producer network function.

29. The method of claim 21, wherein the first producer network function and the second producer network function are the same type of network functions.

30. The method of claim 21, wherein the first producer network function and the second producer network function belong to the same network function set or the same network function service instance set.

Images