Message Processing in 5th Generation Networks

Abstract

To provide a method for processing a message in a fifth generation network, and a node that operates in conformity with the method.SOLUTION: A method is performed by a first service communication proxy (SCP) node 10 of a service consumer, and configured to receive a message from a second network node 30. The message includes an indication that a second NF node is under testing in the network. The indication signals that the second NF node is a candidate for selection when selecting at least one second NF node towards which network traffic is to be transmitted, and the message includes load information for the second NF node. The indication signals that the load information represents a predefined amount of network traffic that the second NF node is required to receive.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a method for processing messages in a fifth generation network, and a node configured to operate in accordance with the method. [Background technology]

[0002] Various techniques exist for handling requests for services within a network. A service request is generally from a consumer of a service ("service consumer") to a producer of a service ("service producer"). For example, a service request may be from a service consumer's Network Function (NF) node to a service producer's NF node. The service consumer's NF node and the service producer's NF node may communicate directly or indirectly, referred to as direct communication and indirect communication, respectively. In the case of indirect communication, the service consumer's NF node and the service producer's NF node may communicate via a Service Communication Proxy (SCP) node.

[0003] Figures 1A-1D show different existing systems for processing service requests, as described in 3GPP TS 23.501 v16.4.0. More specifically, Figures 1A and 1B show a system using direct communication, and Figures 1C and 1D show a system using indirect communication.

[0004] In the systems shown in FIGS. 1A and 1B, a service request is sent directly from the service consumer's NF node to the service producer's NF node. A response to the service request is sent directly from the service producer's NF node to the service consumer's NF node. Similarly, any subsequent service requests are sent directly from the service consumer's NF node to the service producer's NF node. The system shown in FIG. 1B also includes a network repository function (NRF) node. Thus, in the system shown in FIG. 1B, the service consumer's NF node may query the NRF node to discover an appropriate service producer's NF node to send the service request to. In response to such a query, the service consumer's NF node may receive NF profiles for one or more service producer's NF nodes and may select the service producer's NF node to send the service request to based on the received NF profile(s). In the system shown in FIG. 1A, an NRF node is not used; instead, the NF node of the service consumer may be configured with the NF profile(s) of the NF node(s) of the service producer.

[0005] In the systems shown in Figures 1C and 1D, a service request is sent indirectly from the service consumer NF node to the service producer NF node via a service communication proxy (SCP) node. A response to the service request is sent indirectly from the service producer NF node to the service consumer NF node via the SCP node. Similarly, any subsequent service requests are sent indirectly from the service consumer NF node to the service producer NF node via the SCP node. The systems shown in Figures 1C and 1D also include an NRF node.

[0006] In the system shown in FIG. 1C , a service consumer's NF node may query an NRF node to discover a suitable service producer's NF node to which to send a service request. In response to such a query, the service consumer's NF node may receive NF profiles for one or more service producer's NF nodes and select a service producer's NF node to which to send a service request based on the received NF profile(s). In this case, a service request sent from the service consumer's NF node to the SCP node includes the address of the service producer's selected NF node. The service consumer's NF node may forward the service request without performing further discovery or selection. If the service producer's selected NF node is inaccessible for some reason, it may be up to the service consumer's NF node to find an alternative. In other cases, the SCP node may communicate with the NRF node to obtain selection parameters (e.g., location, capacity, etc.), and the SCP node may select a service producer's NF node to which to send a service request.

[0007] In the system shown in Figure 1D, the service consumer's NF node does not perform the discovery or selection process. Instead, the service consumer's NF node adds any necessary discovery and selection parameters (needed to find a suitable NF node of the service producer) to the service request it sends via the SCP node. The SCP node uses the requested address and discovery and selection parameters in the service request to route the service request to the suitable NF node of the service producer. The SCP node may perform discovery using the NRF node.

[0008] For the 5th Generation Core (5GC), from Release 16 onwards, SCP nodes are included as network elements that enable indirect communication between service consumer NF nodes and service producer NF nodes. The indirect communication used can be either of the two indirect communication options described above with reference to Figures 1C and 1D.

[0009] According to the above-described system, the NF node of the service consumer or SCP node needs to initially select (or, in the case of a failure, reselect, for example) the service producer's NF node, for example, from among multiple functionally equivalent instances of the service producer's NF node. Typically, this selection (or reselection) is based on one or more characteristics (or attributes) of the service producer's NF node, such as those defined in the service producer's NF node's profile. Examples of characteristics include a priority assigned to the service producer's NF node, the locality of the service producer's NF node, the capacity of the service producer's NF node, and the load on the service producer's NF node. In some cases, the selection (or reselection) may take into account other information from the service producer's NF node, such as load information received in a response from the service producer's NF node, and / or any configured policies, such as which locality should be preferred over another.

[0010] 3GPP TS 29.500 v17.1.0 defines two load control mechanisms. The first load control mechanism relies on the service producer's NF node updating its load information in its profile stored in the NRF node, so that the service consumer or SCP node's NF node can discover this NF profile containing the load information. The second load control mechanism relies on the service producer's NF node signaling the load information to the service consumer or SCP node's NF node. Generally, the load information in both mechanisms contains a value between 0 (minimum) and 100 (maximum), which provides an indication of resource usage at the service producer's NF node. For example, if the load information of the service producer's NF node contains a value of 100, the service consumer or SCP node's NF node interprets this as an indication that new requests should not be sent to the service producer's NF node. On the other hand, if the load information of the service producer's NF node contains a value of 0, the service consumer's or SCP node's NF node interprets this as an indication that the service producer's NF node is not processing network traffic (i.e., the service producer's NF node has no load). As a result, based on the load information, the service consumer's NF node or SCP node can select a target with a lesser load. Summary of the Invention

[0011] A network may need to introduce new resources and / or new upgrades (e.g., features). For example, there may be some situations in which a customer may request this. However, this currently requires specific implementation and / or configuration in the NF nodes of the service consumer or SCP nodes, and there are currently no art-defined mechanisms to support this.

[0012] 5GC specifies that an application programming interface version (API version) can be included in the profile of a service producer NF node. This API version allows a service consumer NF node to select only NF node instances with this specific API version. In some cases, a new API version, or even a dummy API version, can be defined for testing purposes. However, the use of an API version when including upgraded software (e.g., to be tested before final deployment in the network), requires that the service consumer NF node must select a specific API version (e.g., API version X). This requires specific logic in the service consumer NF node. This can be problematic because it may only be possible to include specific logic for instances from the same vendor or based on an integration project.

[0013] It is an object of the present disclosure to obviate or obviate at least some of the above-mentioned disadvantages associated with existing technology.

[0014] Thus, according to an aspect of the present disclosure, there is provided a method for processing messages in a fifth-generation network. The method is performed by a first network node. The first network node is a first Network Function (NF) node of a service consumer, or a first SCP node configured to act as a Service Communication Proxy (SCP) between the first NF node and one or more second NF nodes of a service producer. The method includes receiving a message from the second network node. The message includes an indication that a second NF node of one or more second NF nodes is under test in the network. The indication informs the first network node that the second NF node is a candidate for selection when selecting at least one second NF node among the one or more second NF nodes to which to send network traffic, and / or the message includes load information about the second NF node, the indication informing the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0015] According to another aspect of the present disclosure, there is also provided a first network node comprising processing circuitry configured to operate in accordance with the method described with respect to the first network node. In some embodiments, the first network node may comprise at least one memory for storing instructions that, when executed by the processing circuitry, cause the first network node to operate in accordance with the method described with respect to the first network node.

[0016] According to another aspect of the present disclosure, another method for processing a message in a fifth generation network is also provided. The method is performed by a second network node. The method includes initiating transmission of a message to a first network node. The first network node is a first Network Function (NF) node of a service consumer or a first Service Communication Proxy (SCP) node configured to operate as a Service Communication Proxy (SCP) between the first NF node and one or more second NF nodes of a service producer. The message includes an indication that a second NF node of the one or more second NF nodes is being tested in the network. The indication signals to the first network node that the second NF node is a candidate for selection when selecting at least one second NF node among one or more second NF nodes to which to send network traffic, and / or the message includes load information for the second NF node, and the indication signals to the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0017] According to another aspect of the present disclosure, there is provided a second network node comprising processing circuitry configured to operate in accordance with this method described with respect to the second network node. In some embodiments, the second network node may comprise at least one memory for storing instructions that, when executed by the processing circuitry, cause the second network node to operate in accordance with this method described with respect to the second network node.

[0018] According to another aspect of the present disclosure, there is provided a method performed by a system, the method including a method described with respect to a first network node and a method described with respect to a second network node.

[0019] According to another aspect of the present disclosure, there is provided a system including at least one first network node as described above and at least one second network node as described above.

[0020] According to another aspect of the present disclosure, there is provided a computer program comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform a method described with respect to a first network node and / or a method described with respect to a second network node.

[0021] According to another aspect of the present disclosure, there is provided a computer program product embodied on a non-transitory machine-readable medium that includes instructions executable by a processing circuit to cause the processing circuit to perform a method described with respect to a first network node and / or a method described with respect to a second network node.

[0022] Thus, improved techniques for processing messages in fifth generation networks are provided. [Brief explanation of the drawings]

[0023] For a better understanding of the present techniques and to show how they may be carried into effect, reference will now be made, by way of example only, to the accompanying drawings in which:

[0024] [Figure 1] 1A-1D are block diagrams illustrating different existing systems. [Figure 2] FIG. 2 is a block diagram illustrating a second network node according to one embodiment. [Figure 3] FIG. 3 is a block diagram illustrating a method performed by a second network node according to one embodiment. [Figure 4] FIG. 4 is a block diagram illustrating a first network node according to one embodiment. [Figure 5] FIG. 5 is a block diagram illustrating a method performed by a first network node according to one embodiment. [Figure 6] FIG. 6 is a signaling diagram illustrating signaling in a system according to one embodiment. [Figure 7] FIG. 7 is a signaling diagram illustrating signaling in a system according to one embodiment. [Figure 8] FIG. 8 is a signaling diagram illustrating signaling in a system according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0025] Some of the embodiments discussed herein are described more fully below with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0026] As mentioned above, advantageous techniques for processing messages in a fifth generation network are described herein. The techniques described herein may be used in connection with any fifth generation (5G) network, such as any 5G communication or telecommunication network (e.g., a cellular network). In some embodiments, the network may be a core network or a radio access network (RAN). The techniques described herein are implemented by a first network node and a second network node. The first network node is a first network function (NF) node of a service consumer or a first SCP node configured to act as a service communication proxy (SCP) between the first NF node and one or more second NF nodes of a service producer. The second network node is a second NF node of a service producer or a network repository function (NRF) node.

[0027] Although the present technology is described herein with reference to one or more NF nodes of one or more service consumers and one or more NF nodes of one or more service producers, it should be understood that an NF node may behave (e.g., operate) as an NF node of a service consumer and / or as an NF node of a service producer.

[0028] An NF is a processing function within a network adopted by or specified by the 3rd Generation Partnership Project (3GPP®), which has specified functional behavior and 3GPP-specified interfaces. An NF may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform (e.g., on a cloud infrastructure). As used herein, the term "node" with respect to an "NF node" will be understood to cover each of these scenarios. As used herein, reference to multiple NF nodes of a service producer may refer, for example, to functionally equivalent instances of the service producer's NF nodes.

[0029] 2 illustrates a second network node 30, 60 according to one embodiment. The second network node 30, 60 is for processing messages in a fifth generation network. In some embodiments, the second network node 30, 60 may be, for example, a physical machine (e.g., a server) or a virtual machine (VM). The second network node 30, 60 may be a second NF node 30 or an NRF node 60 of a service producer.

[0030] As shown in FIG. 2 , the second network node 30, 60 comprises processing circuitry (or logic) 32. The processing circuitry 32 controls the operation of the second network node 30, 60 and may implement the methods described herein with respect to the second network node 30, 60. The processing circuitry 32 may be configured or programmed to control the second network node 30, 60 with the methods described herein. The processing circuitry 32 may comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors, and / or one or more modules. In particular implementations, each of the one or more hardware components may be configured to perform or is for performing an individual step or steps of the methods described herein with respect to the second network node 30, 60. In some embodiments, the processing circuitry 32 may be configured to execute software to perform the methods described herein with respect to the second network node 30, 60. The software may be stored according to some embodiments. Thus, in some embodiments, the processing circuitry 32 may be configured to execute a container to perform the methods described herein with respect to the second network node 30,60.

[0031] Briefly, the processing circuitry 32 of the second network node 30, 60 is configured to initiate transmission of a message to a first network node, the first network node being a first NF node of a service consumer or a first SCP node configured to act as an SCP between the first NF node and one or more second NF nodes of a service producer, the message including an indication that a second NF node of the one or more second NF nodes is being tested in the network, the indication signaling to the first network node that the second NF node is a candidate for selection when selecting at least one second NF node of the one or more second NF nodes to which to send network traffic, and / or the message including load information for the second NF node, the indication signaling to the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0032] 2, in some embodiments, the second network node 30, 60 may optionally include a memory 34. The memory 34 of the second network node 30, 60 may include volatile or non-volatile memory. In some embodiments, the memory 34 of the second network node 30, 60 may include a non-transitory medium. Examples of the memory 34 of the second network node 30, 60 include, but are not limited to, random access memory (RAM), read-only memory (ROM), a mass storage medium such as a hard disk, a removable storage medium such as a compact disc (CD) or digital video disc (DVD), and / or any other memory.

[0033] The processing circuitry 32 of the second network node 30, 60 may be communicatively coupled (e.g., connected) to a memory 34 of the second network node 30, 60. In some embodiments, the memory 34 of the second network node 30, 60 may be for storing program code or instructions that, when executed by the processing circuitry 32 of the second network node 30, 60, cause the second network node 30, 60 to operate in a manner described herein with respect to the second network node 30, 60. For example, in some embodiments, the memory 34 of the second network node 30, 60 may be configured to store program code or instructions that, when executed by the processing circuitry 32 of the second network node 30, 60, cause the second network node 30, 60 to operate in a manner described herein with respect to the second network node 30, 60. Alternatively or additionally, the memory 34 of the second network node 30, 60 may be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or the like described herein. The processing circuitry 32 of the second network node 30, 60 may be configured to control the memory 34 of the second network node 30, 60 to store the information, data, messages, requests, responses, indications, notifications, signals, or the like described herein.

[0034] 2, the second network node 30, 60 may optionally comprise a communications interface 36. The communications interface 36 of the second network node 30, 60 may be communicatively coupled (e.g., connected) to the processing circuitry 32 of the second network node 30, 60 and / or the memory 34 of the second network node 30, 60. The communications interface 36 of the second network node 30, 60 may be operable to enable the processing circuitry 32 of the second network node 30, 60 to communicate with the memory 34 of the second network node 30, 60 and / or vice versa. Similarly, the communications interface 36 of the second network node 30, 60 may be operable to enable the processing circuitry 32 of the second network node 30, 60 to communicate with the first network node and / or any other nodes mentioned herein. The communication interface 36 of the second network node 30, 60 may be configured to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like, as described herein. In some embodiments, the processing circuitry 32 of the second network node 30, 60 may be configured to control the communication interface 36 of the second network node 30, 60 to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like, as described herein.

[0035] While the second network node 30, 60 is shown in Figure 2 as including a single memory 34, it will be understood that the second network node 30, 60 may include at least one memory (i.e., a single memory or multiple memories) 34 that operate in the manner described herein. Similarly, while the second network node 30, 60 is shown in Figure 2 as including a single communication interface 36, it will be understood that the second network node 30, 60 may include at least one communication interface (i.e., a single communication interface or multiple communication interfaces) 36 that operate in the manner described herein. It will also be understood that Figure 2 shows only the components necessary to illustrate an embodiment of the second network node 30, 60, and that in an actual implementation the second network node 30, 60 may include additional or alternative components to those shown.

[0036] Figure 3 illustrates a method performed by a second network node 30, 60, according to one embodiment, for processing messages in a fifth generation network. The second network node 30, 60, as described above with reference to Figure 2, may be configured to operate according to the method of Figure 3. In some embodiments, the method may be performed by or under the control of processing circuitry 32 of the second network node 30, 60. As previously mentioned, the second network node may be a second NF or NRF node of the service producer.

[0037] As shown in block 302 of FIG. 3 , transmission of a message is initiated toward a first network node. As previously mentioned, the first network node may be a first NF node of a service consumer or a first SCP node configured to operate as an SCP between the first NF node and one or more second NF nodes of a service producer. As used herein, the term “initiate” may mean, for example, to cause or establish. Thus, the second network node 30, 60 (e.g., the processing circuitry 32 of the second network node 30, 60) may be configured to transmit a message itself or to cause another node to transmit a message (e.g., via the communication interface 36 of the second network node 30, 60).

[0038] The message includes an indication that a second NF node of one or more second NF nodes is being tested in the network, the indication signaling to the first network node that the second NF node is a candidate for selection when selecting at least one second NF node of the one or more second NF nodes to send network traffic to, and / or the message includes load information about the second NF node, advantageously the indication signaling to the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0039] In existing load control mechanisms, the load information indicates the load (e.g., resource usage) on the second NF node. However, with the indications referred to herein, these standard load control mechanisms may be updated so that the load information does not refer to the load on the second NF node, but instead advantageously refers to the expected load that is transmitted to the second NF node. In the art, the load information may also be referred to as load control information.

[0040] As used herein, a second NF node, or an update (such as software, e.g., a new service, or an update) to one or more second NF nodes that is being tested in the network, may be fully or partially tested in isolation from the network, such as in a lab (e.g., at a vendor's premises), before being tested in the network. In some situations, for example, the second NF node may be tested in isolation from the network, but the second NF node's interactions with other NF nodes may need to be tested in the network. Similarly, for example, a newly introduced service (or any other update to the second NF node) in the second NF node may be tested in isolation from the network, but the newly introduced service's interactions with other services may need to be tested in the network. These interactions may cause errors. Thus, as used herein, second NF nodes may be deployed in a network in a controlled manner by signaling to a first network node that the second NF node is a candidate for selection of at least one second NF node among one or more second NF nodes to which network traffic is to be sent. This control allows errors to be identified and action taken (e.g., by a network operator) to avoid errors occurring in the wider network.

[0041] For example, if a second NF node in a network is found to produce errors when tested, the second NF node may be removed from the network, or any upgrades (e.g., software upgrades) or modifications to the second NF node may be removed or discarded. The second NF node under test in the network may be, for example, a second NF node newly introduced to the network, or a second NF node already included in the network but upgraded or modified (e.g., upgraded or modified and / or one or more services it may provide), or the second NF node may be under test in the network for any other reason. Thus, the methods described herein can limit the impact of a newly introduced NF node and / or newly introduced upgrade or modification that may be malfunctioning, because action can be taken before expanding the use of the NF node and / or upgrade or modification in the network (e.g., throughout the network).

[0042] In some embodiments, the profile of the second NF node 30 may include the indications and / or load information referred to herein. In some embodiments, the profile may include one or more attributes for the second NF node 30, and an attribute of the one or more attributes for the second NF node 30 may be set to the indication. Although not shown in FIG. 3 , in some embodiments, the method may include setting the attribute to the indication. The attribute may be, for example, a local attribute indicating the location of the second NF node 30 or any other attribute for the second NF node 30. In some embodiments, the attribute may be an attribute that is prioritized (e.g., considered first) when selecting at least one second NF node 30.

[0043] In some embodiments, an attribute may be an attribute that matches or at least partially matches a corresponding attribute of the first NF node. In some embodiments, for example, an attribute may be set to a value, and if the value of the attribute is the same as the value of the corresponding attribute, the attribute may match the corresponding attribute. Similarly, for example, an attribute may be set to multiple values, and if the value of the attribute is the same as the value of the corresponding attribute, the attribute may match the corresponding attribute, or if one or more (or a predetermined percentage) of the attribute's values ​​are the same as one or more of the corresponding attribute's values, the attribute may partially match the corresponding attribute. In some embodiments, the first NF node may also be under test in the network.

[0044] In some embodiments where the second network node is a second NF node, the message may be a response to a service request. A service request is a request for the second NF node to provide a service requested by a service consumer's first NF node. Generally, a service is software intended to be managed for a user. As used herein, a service may be any type of service, such as a communication service (e.g., a notification service or a callback service), a context management (e.g., a user equipment context management (UECM)) service, a data management (DM) service, or any other type of service. As used herein, reference to providing a service may refer, for example, to running or operating a service.

[0045] In other embodiments where the second network node is an NRF node, the message may include a profile of the second NF node. In some of these embodiments, transmission of the message may be initiated in response to a change in load information (e.g., included in the profile) and / or in response to a discovery request. A discovery request is a request for information indicating one or more second NF nodes for providing a service requested by the first NF node. In some embodiments, the first network node may be subscribed to be notified of changes in load information.

[0046] In some embodiments, the message may include a load control information (LCI) header, and the LCI header may include an indication that, in some embodiments, the predetermined amount of network traffic that the second NF node needs to receive may be a predetermined percentage of the total amount of network traffic available for transmission.

[0047] In some embodiments, selecting at least one second NF node 30 among the one or more second NF nodes may be for the at least one second NF node 30 to provide a service requested by the first NF node 20, and / or the network traffic may include a service request that is a request for a service (requested by the first NF node 20) to be provided.

[0048] Although not shown in FIG. 3 , in some embodiments where the second network node is a second NF node 30, the method may include receiving network traffic, such as a predetermined amount of network traffic (e.g., via a communications interface 36 of the second NF node 30). In some embodiments, the network traffic, such as the predetermined amount of network traffic, may also be received by at least one other second NF node that is of the same type as the second NF node 30 (e.g., in the case of initial selection) and / or is in the same group of second NF nodes as the second NF node 30 (e.g., in the case of reselection). In some embodiments, network traffic, such as a remaining amount of network traffic (or a remainder of the traffic) available for transmission, may be received by at least one other second NF node of the one or more second NF nodes. In some embodiments, at least two other second NF nodes of the one or more second NF nodes may receive the network traffic (e.g., the remaining amount of network traffic). In these embodiments, the network traffic may be distributed among the at least two other second NF nodes to balance the load on the at least two other second NF nodes.

[0049] As mentioned above, in existing load control mechanisms, the load information may indicate the load (e.g., resource usage) on the second NF node. However, with the indications referred to herein, these standard load control mechanisms may be updated so that the load information does not refer to the load on the second NF node, but instead advantageously refers to the expected load, which is transmitted to the second NF node. In some embodiments, the load information described herein may include a value that normally indicates the load on the second NF node, such as a value between 0 and 100. For example, in existing control mechanisms, a value of 0 indicates that there is no load on the second NF node (e.g., no resources are in use at the second NF node), and a value of 100 indicates that the second NF node has a full load (e.g., all resources are in use at the second NF node). However, with the indications referred to herein, the first network node may be notified that this value actually indicates the expected load, which is transmitted to the second NF node. For example, if the load information includes a value of 30, the first network node may be notified with an indication that 30% of the total network traffic needs to be sent toward the second NF node, and the remainder of the network traffic (i.e., 70%) may be distributed (e.g., load balanced) among other second NF nodes.

[0050] 4 illustrates a first network node 10, 20 according to one embodiment. The first network node 10, 20 is for processing messages in a fifth generation network. In some embodiments, the first network node 10, 20 may be, for example, a physical machine (e.g., a server) or a virtual machine (VM). The first network node 10, 20 may be a first NF node 20 of a service consumer, or a first SCP node 10 configured to act as an SCP between the first NF node 20 and one or more second NF nodes of a service producer.

[0051] As shown in FIG. 4 , the first network node 10, 20 comprises processing circuitry (or logic) 12. The processing circuitry 12 controls the operation of the first network node 10, 20 and may implement the methods described herein with respect to the first network node 10, 20. The processing circuitry 12 may be configured or programmed to control the first network node 10, 20 with the methods described herein. The processing circuitry 12 may comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors, and / or one or more modules. In particular implementations, each of the one or more hardware components may be configured to perform or is for performing an individual step or steps of the methods described herein with respect to the first network node 10, 20. In some embodiments, the processing circuitry 12 may be configured to execute software to perform the methods described herein with respect to the first network node 10, 20. The software may be stored according to some embodiments. Thus, in some embodiments, the processing circuitry 12 may be configured to execute a container for performing the methods described herein with respect to the first network node 10,20.

[0052] Briefly, the processing circuitry 12 of the first network node 10, 20 is configured to receive a message from a second network node, the message including an indication that a second NF node of one or more second NF nodes is under test in the network, the indication signaling to the first network node that the second NF node is a candidate for selection when selecting at least one second NF node of the one or more second NF nodes to which to send network traffic, and / or the message including load information for the second NF node, the indication signaling to the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0053] 4, in some embodiments, the first network node 10, 20 may optionally include a memory 14. The memory 14 of the first network node 10, 20 may include volatile or non-volatile memory. In some embodiments, the memory 14 of the first network node 10, 20 may include a non-transitory medium. Examples of the memory 14 of the first network node 10, 20 include, but are not limited to, random access memory (RAM), read-only memory (ROM), a mass storage medium such as a hard disk, a removable storage medium such as a compact disc (CD) or digital video disc (DVD), and / or any other memory.

[0054] The processing circuitry 12 of the first network node 10, 20 may be communicatively coupled (e.g., connected) to a memory 14 of the first network node 10, 20. In some embodiments, the memory 14 of the first network node 10, 20 may be for storing program code or instructions that, when executed by the processing circuitry 12 of the first network node 10, 20, cause the first network node 10, 20 to operate in a manner described herein with respect to the first network node 10, 20. For example, in some embodiments, the memory 14 of the first network node 10, 20 may be configured to store program code or instructions that, when executed by the processing circuitry 12 of the first network node 10, 20, cause the first network node 10, 20 to operate in a manner described herein with respect to the first network node 10, 20. Alternatively or additionally, the memory 14 of the first network node 10, 20 may be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or the like described herein. The processing circuitry 12 of the first network node 10, 20 may be configured to control the memory 14 of the first network node 10, 20 to store the information, data, messages, requests, responses, indications, notifications, signals, or the like described herein.

[0055] 4, the first network node 10, 20 may optionally comprise a communications interface 16. The communications interface 16 of the first network node 10, 20 may be communicatively coupled (e.g., connected) to the processing circuitry 12 of the first network node 10, 20 and / or the memory 14 of the first network node 10, 20. The communications interface 16 of the first network node 10, 20 may be operable to enable the processing circuitry 12 of the first network node 10, 20 to communicate with the memory 14 of the first network node 10, 20 and / or vice versa. Similarly, the communications interface 16 of the first network node 10, 20 may be operable to enable the processing circuitry 12 of the first network node 10, 20 to communicate with the second network node 30, 60 and / or any other node mentioned herein. The communication interface 16 of the first network node 10, 20 may be configured to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like, as described herein. In some embodiments, the processing circuitry 12 of the first network node 10, 20 may be configured to control the communication interface 16 of the first network node 10, 20 to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like, as described herein.

[0056] While the first network nodes 10, 20 are shown in Figure 2 as including a single memory 14, it will be understood that the first network nodes 10, 20 may include at least one memory (i.e., a single memory or multiple memories) 14 that operate in the manner described herein. Similarly, while the first network nodes 10, 20 are shown in Figure 4 as including a single communication interface 16, it will be understood that the first network nodes 10, 20 may include at least one communication interface (i.e., a single communication interface or multiple communication interfaces) 16 that operate in the manner described herein. It will also be understood that Figure 4 shows only the components necessary to illustrate an embodiment of the first network nodes 10, 20, and that in an actual implementation the first network nodes 10, 20 may include additional or alternative components to those shown.

[0057] Figure 5 shows a method performed by a first network node 10, 20 according to one embodiment. The method is for processing messages in a fifth generation network. The first network node 10, 20 described above with reference to Figure 4 may be configured to operate according to the method of Figure 5. In some embodiments, the method may be performed by or under the control of processing circuitry 12 of the first network node 10, 20.

[0058] As shown in block 102 of Figure 5, a message is received from a second network node (e.g., via the communication interface 16 of the first network node 10, 20), the message including an indication that a second NF node of one or more second NF nodes is being tested in the network, the indication signaling to the first network node that the second NF node is a candidate for selection when selecting at least one second NF node of the one or more second NF nodes to which to send network traffic, and / or the message including load information about the second NF node, advantageously signaling to the first network node that the load information represents a predetermined amount of network traffic that the second NF node needs to receive.

[0059] In some embodiments, the profile of the second NF node 30 may include an indication and / or load information. In some embodiments, the profile may include one or more attributes for the second NF node 30, and an attribute of the one or more attributes for the second NF node 30 may be set to the indication. The attribute may be, for example, a local attribute indicating the location of the second NF node 30 or any other attribute for the second NF node 30. In some embodiments, the attribute may be an attribute that is prioritized when selecting at least one second NF node 30. In some embodiments, the attribute may be an attribute that matches or at least partially matches a corresponding attribute of the first NF node, for example, as described above. In some embodiments, the first NF node may be under test in the network.

[0060] As previously mentioned, the second network node may be a second NF node 30 or an NRF node 60. In some embodiments where the second network node is a second NF node 30, the message may be a response to a service request. The service request is a request for the second NF node 30 to provide a service requested by the first NF node 20. In other embodiments where the second network node is an NRF node 60, the message may include a profile of the second NF node as previously described.

[0061] In some embodiments, the message may be received in response to a change in load information (e.g., included in a profile) and / or in response to a discovery request, which is a request for information indicating one or more second NF nodes for providing a service requested by the first NF node 20. In some embodiments, the first network node 10, 20 may be subscribed to be notified of changes in load information.

[0062] In some embodiments, the message may include a Load Control Information (LCI) header, which may include an indication that, in some embodiments, the predetermined amount of network traffic that the second NF node 30 needs to receive may be a predetermined percentage of the total amount of network traffic available for transmission.

[0063] Although not shown in FIG. 5 , in some embodiments, the method may include selecting at least one second NF node 30 from among the one or more second NF nodes to which to transmit the network traffic. In these embodiments, the selection may be based on an indication. For example, at least one second NF node 30 indicated by such an indication to be a candidate for selection may be selected from the one or more second NF nodes. In some cases, there may be only one second NF node signaled as a candidate for selection, in which case this second NF node may be selected. In other cases, there may be multiple second NF nodes signaled as candidate for selection, in which case at least one of these second NF nodes may be selected, for example, based on one or more criteria. The one or more criteria may include, for example, load (e.g., a second NF node requiring a predetermined load and / or currently having the lowest load may be selected), locality (e.g., a second NF node closest to the first NF node may be selected), priority (e.g., a second NF node with the highest priority may be selected), capacity (e.g., a second NF node with the greatest capacity or the greatest available capacity may be selected), and / or any other criteria. In some embodiments, selecting at least one second NF node 30 among the one or more second NF nodes may be for the at least one second NF node to provide a service requested by the first NF node 20, and / or the network traffic may include a service request that is a request for a service 40 (requested by the first NF node 20) to be provided.

[0064] Although not shown in FIG. 5 , in some embodiments, the method may include initiating transmission of network traffic (e.g., a predetermined amount of network traffic that the second NF node needs to receive) toward the second NF node. For example, the first network node 10, 20 (e.g., the processing circuitry 12 of the first network node 10, 20) may itself be configured to transmit this network traffic or may be configured to cause another node (e.g., via the communication interface 16 of the first network node 10, 20) to transmit this network traffic. Alternatively or additionally, in some embodiments, the method may include initiating transmission of network traffic (e.g., a predetermined amount of network traffic that the second NF node needs to receive) toward at least one other second NF node of the same type as the second NF node (e.g., in the case of initial selection) and / or at least one other second NF node in the same group as the second NF node (e.g., in the case of reselection).

[0065] Although not shown in FIG. 5 , in some embodiments, the method may include initiating transmission of network traffic, e.g., a remaining amount of network traffic available for transmission (or a remainder of the traffic), toward at least one other second NF node of the one or more second NF nodes. For example, the first network node 10, 20 (e.g., the processing circuitry 12 of the first network node 10, 20) may be configured to transmit this network traffic itself or to cause another node (e.g., via the communication interface 16 of the first network node 10, 20) to transmit this network traffic. In some of these embodiments, the transmission of the network traffic, e.g., the remaining amount of network traffic, may be initiated toward at least two other second NF nodes of the one or more second NF nodes. In these embodiments, the network traffic may be distributed among the at least two other second NF nodes to balance the load on the at least two other second NF nodes.

[0066] Methods performed by the system are also provided, including methods described herein with respect to the first network nodes 10, 20 and methods described herein with respect to the second network nodes 30, 60. Systems are also provided comprising at least one first network node 10, 20 as described herein and at least one second network node 30, 60 as described herein.

[0067] FIG. 6 is a signaling diagram illustrating signal exchanges in a system according to one embodiment. The system illustrated in FIG. 6 includes a first network node 10, 20 and one or more second NF nodes 30, 50 ("NFp1," "NFp2") of a service producer. The system of FIG. 6 illustrates an embodiment in which the second network node is a second NF node 30 of the one or more second NF nodes 30, 50. Thus, the second NF node 30 may be as described above with reference to FIGS. 2 and 3. The first network node 10, 20 may be as described above with reference to FIGS. 4 and 5. The first network node 10, 20 may be a first SCP node 10 ("SCP") or a first NF node 20 ("NFc") of a first service consumer. Although not illustrated in FIG. 6, in some embodiments in which the first network node 10 is a first SCP node 10, the system may further include a first NF node 20. The first SCP node 10 may be configured to act as an SCP between the first NF node 20 and one or more second NF nodes 30, 50.

[0068] One or more second NF nodes 30, 50 may each be for providing (e.g., configured to provide) a service 40 ("Service A"). In some embodiments, as shown in Figure 6, a group (or set) 402 ("Set 1") of second NF nodes may include one or more second NF nodes 30, 50. While two second NF nodes 30, 50 are shown in Figure 6, it will be understood that the group 402 of second NF nodes may include a single second NF node according to some embodiments, or multiple (e.g., two, three, or more) second NF nodes according to other embodiments.

[0069] Although not shown in FIG. 6 , in some embodiments, the system may further include an NRF node. In some of these embodiments, if the system also includes a first SCP node 10, the entity may include the first SCP node 10 and an NRF node. That is, in some embodiments, the first SCP node 10 may be merged with the NRF node in a composite entity. In general, an NRF node is a node that provides NF service registration and discovery. As such, an NRF node allows an NF node to identify services provided by other NF nodes.

[0070] Although only one first network node 10, 20 (e.g., one first SCP node 10 or one first NF node 20) is shown in FIG. 6 , the system may include one or more first network nodes (e.g., one or more first SCP nodes 10 and / or one or more first NF nodes 20). Similarly, although only one group (or set) 402 of second NF nodes 30, 50 is shown in FIG. 6 , the system may include one or more groups (or sets) of second NF nodes. In some embodiments, one or more second NF nodes 30, 50 may be grouped according to the type of NF node and / or according to the services they can provide. For example, second NF nodes 30, 50 of the same type and / or capable of providing the same service 40 may be part of the same group 402.

[0071] In some embodiments, the first SCP node 10 and the first NF node 20 may be located in separate deployment units, and / or the first SCP node 10 and at least one of the one or more second NF nodes 30, 50 may be located in separate deployment units. Thus, an SCP node based on separate deployment units may be provided, as described in 3GPP TS 23.501 v16.4.0. In other embodiments, the first SCP node 10 may be located as a distributed network element. For example, in some embodiments, a portion of the first SCP node 10 (e.g., a service agent) may be located in the same deployment unit as the first NF node 20, and / or a portion of the first SCP node 10 (e.g., a service agent) may be located in the same deployment unit as at least one of the one or more second NF nodes 30, 50. Thus, an SCP node based on a service mesh may be provided, as described in 3GPP TS 23.501 v16.4.0.

[0072] In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node 20 and the first SCP node 10, and / or at least one third SCP node may be configured to operate as an SCP between the first SCP node 10 and at least one of the one or more second NF nodes 30, 50. Thus, there may be multiple paths of SCP nodes. In some of these embodiments, the first SCP node 10 and one or more of the at least one second SCP node and the at least one third SCP node may be deployed in independent deployment units. In some embodiments, the at least one second SCP node and / or the at least one third SCP node may be deployed as distributed network elements.

[0073] As indicated by block 600 in FIG. 6 , the first network node 10, 20 selects a second NF node 50 (or an instance of a second NF node 50) to provide the service 40 requested by the first NF node 20. Thus, in some embodiments, the first NF node 20 itself may select the second NF node 50 to provide the service 40. In other embodiments, the first SCP node 10 may select the second NF node 50 to provide the service 40. For example, although not shown in FIG. 6 , in some of these other embodiments, the first NF node 20 may initiate transmission of a service request toward the first SCP node 10 (e.g., may transmit or have another node transmit, such as via the communication interface 16 of the first NF node 20). Thus, the first SCP node 10 may receive this service request (e.g., via the communication interface 16 of the first SCP node 10). This service request received by the first SCP node 10 may be a request for the second NF node 50 to provide the service 40 requested by the first NF node 20. In some embodiments, this service request may include discovery and / or selection parameters. For example, the first NF node 20 may provide the first SCP node 10 with any capability parameters needed to find a suitable second NF node for providing the service 40. In other embodiments, the first NF node 20 itself is responsible for selecting the second NF node 50 for providing the service 40, and it is the first NF node 20 that finds the suitable second NF node.

[0074] The first network node 10, 20 may find a suitable second NF node using a discovery process. For example, although not shown in FIG. 6 , in some embodiments, the first network node 10, 20 may initiate transmission of a discovery request toward the NRF node (e.g., it may transmit itself or cause another node to transmit, such as via the communication interface 16 of the first network node 10, 20). The NRF node then receives the discovery request. The discovery request is a request for information indicating one or more second NF nodes of one or more service producers for providing the service 40 requested by the first NF node 20. The discovery request may include discovery and / or selection parameter(s). Based on the received discovery parameter(s), the NRF node may discover profiles of potential destination second NF nodes of the one or more service producers.

[0075] At block 600 of FIG. 6, the first network node 10, 20 may then select a second NF node 50 (or instance of a second NF node 50) from the corresponding profile(s). That is, at block 600 of FIG. 6, the first network node 10, 20 may select one second NF node 50 from among those provided (i.e., from the available candidates 30, 50). Those skilled in the art will recognize various criteria, such as any of those described above, upon which the selection may be made. Because this is a first service request, the first network node 10, 20 does not have load information for one or more second NF nodes 30, 50 from which to select a second NF node 50. Therefore, the first network node 10, 20 may assume that there is zero load on each of the one or more second NF nodes 30, 50.

[0076] Returning to FIG. 6 , as indicated by arrow 602, the first network node 10, 20 may initiate transmission of a service request (e.g., it may transmit or cause another node to transmit, such as via the communication interface 16 of the first network node 10, 20) toward the selected second NF node 50. This service request 602 is referred to herein as a “first service request.” In embodiments where the first network node 10, 20 is the first NF node 20, the first NF node 20 may transmit the first service request 602 directly to the selected second NF node 50, or may transmit the first service request 602 indirectly toward the selected second NF node 50 via the first SCP node 10 and / or any other SCP node. The selected second NF node 50 receives the first service request 602 (e.g., via the communication interface of the selected second NF node 50). The first service request 602 is a request to a selected second NF node 50 to provide a service 40 requested by a first NF node 20. The service 40 may be requested by the first NF node 20, for example, on behalf of a subscriber (e.g., a user or user equipment (UE)).

[0077] 6 , the selected second NF node 50 may begin transmitting (e.g., by itself or by having another node transmit, such as via a communication interface of the selected second NF node 50) a first response to the first service request 602 toward the first network node 10, 20. Thus, the first network node 10, 20 receives this first response 604 from the second NF node 50 selected to provide the service 40. In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may receive the first response 604 directly from the selected second NF node 50, or may receive the first response 604 indirectly from the selected second NF node 50 via the first SCP node 10 and / or any other SCP node. The first response 604 includes load information for a selected second NF node 30 of the one or more second NF nodes 30, 50. In some embodiments, the first response 604 may include a Load Control Information (LCI) header, which may include the load information.

[0078] The first network node 10, 20 may need to send another request to a second NF node to provide the service 40 requested by the first NF node 20. In this case, as indicated by block 606 of FIG. 6 , the first network node 10, 20 may check the load on one or more second NF nodes 30, 50 and select a second NF node 30 (or an instance of a second NF node 30) from the one or more second NF nodes 30, 50 to provide the service 40 requested by the first NF node 20. This selection may be a new initial selection. In some embodiments, the one or more second NF nodes 30, 50 may be one or more candidate second NF nodes 30, 50 discovered in the discovery process described above. The selected second NF node 30 may be the same second NF node as previously selected, or a different second NF node from the previously selected one. For purposes of illustration, it is assumed that a different second NF node 30 is selected. This selection may be based on load information. For example, if the load information for a second NF node 30 indicates that the load on the second NF node 30 is zero, then the second NF node 30 may be selected. In another example, if load information is received for at least two second NF nodes, then the second NF node 30 that is known from the load information to have the lowest load among the at least two second NF nodes may be selected.

[0079] Although not shown in FIG. 6 , in some embodiments, the first network node 10, 20 may check one or more other criteria before considering the load information. For example, in some embodiments, the first network node 10, 20 may first check the locality of one or more second NF nodes 30, 50 and / or the priority assigned to one or more second NF nodes 30, 50 before checking the load on one or more second NF nodes 30, 50. Thus, in some embodiments, the selection of a second NF node to provide a service requested by the first NF node 20 may be performed based on load and, optionally, one or more other criteria. In some embodiments, when there are multiple candidate second NF nodes, the first network node 10, 20 may make the selection based on the relative load for each candidate second NF node, where the relative load is based on the absolute (or actual) load on the second NF node and the capacity of the second NF node.

[0080] As indicated by arrow 608 in FIG. 6 , the first network node 10, 20 begins transmitting (e.g., transmitting or causing another node to transmit, such as via the communication interface 16 of the first network node 10, 20) a service request to the selected second NF node 30. This service request 608 is referred to herein as a “second service request.” In embodiments where the first network node 10, 20 is the first NF node 20, the first NF node 20 may transmit the second service request 608 directly to the selected second NF node 30, or may transmit the second service request 608 indirectly via the first SCP node 10 and / or any other SCP node(s) toward the selected second NF node 30. The selected second NF node 30 receives the second service request 608 (e.g., via the communication interface 36 of the selected second NF node 30). The second service request 608 is a request to the selected second NF node 30 to provide the service 40 requested by the first NF node 20. The service 40 may be requested by the first NF node 20, for example, on behalf of a subscriber (e.g., a user or user equipment (UE)).

[0081] As indicated by arrow 610 in FIG. 6 , the selected second NF node 30 begins transmitting (e.g., by itself or by having another node transmit, such as via a communication interface of the selected second NF node 50) a second response toward the first network node 10, 20. Thus, the first network node 10, 20 receives this second response 610 from the second NF node 30 selected to provide the service 40. This second response 610 may also be referred to herein as a “message.” In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may receive the second response 610 directly from the selected second NF node 30, or may receive the second response 610 indirectly from the selected second NF node 30 via the first SCP node 10 and / or any other SCP node.

[0082] The second response includes an indication (e.g., a flag) that a selected second NF node 30 of the one or more second NF nodes 30, 50 is being tested in the network. The second response further includes load information for the selected second NF node 30. Advantageously, the indication signals (e.g., a flag) to the first network node 10, 20 that the load information represents a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive. That is, the second response advantageously includes an indication signaling (e.g., a flag) that the load information should be interpreted as an expected amount of network traffic (or load) to be received by the second NF node 30. The second NF node 30 may require a predetermined amount of network traffic, for example, to undergo testing (e.g., canary testing) in the network. In some embodiments, the second response 610 may include an LCI header, which may include the load information and / or the indication. In some embodiments, the profile of the selected second NF node 30 may include load information and / or indications.

[0083] To this end, the first network node 10, 20 advantageously has knowledge that the selected second NF node 30 requires a predetermined amount of traffic (or load). In some embodiments, the predetermined amount of network traffic that the selected second NF node 30 needs to receive may be a predetermined percentage of the total amount of network traffic available for transmission. For example, if the load information includes a value of 20, this may indicate that the selected second NF node 30 needs to receive 20% of the total amount of network traffic available for transmission.

[0084] As indicated by arrow 612 in Figure 6, the method may be repeated one or more times, for example, by the first network node 10, 20 again checking the load of one or more second NF nodes 30, 50 as described above with reference to block 606. However, this time the first network node 10, 20 knows that the load information it checks in block 606 of Figure 6 represents a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive, and this may therefore be taken into account when selecting a second NF node 30, 50 to which to send network traffic.

[0085] For example, although not shown in FIG. 6 , in some embodiments, the first network node 10, 20 may begin transmitting (e.g., itself or causing another node to transmit, such as via the communication interface 16 of the first network node 10, 20) a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive, toward the second NF node 30. In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may transmit the predetermined amount of network traffic directly to the selected second NF node 30, or may transmit the predetermined amount of network traffic indirectly via the first SCP node 10 and / or any other SCP node(s) toward the selected second NF node 30. The selected second NF node 30 receives the predetermined amount of network traffic (e.g., via the communication interface of the selected second NF node 30).

[0086] 6 , in some embodiments, the first network node 10, 20 may begin transmitting a remaining amount of network traffic (or load) available for transmission toward at least one other second NF node 50 of the one or more second NF nodes. For example, if the predetermined amount of network traffic (or load) that the second NF node 30 needs to receive is 10% of the total amount of network traffic available for transmission, the first network node 10, 20 may begin transmitting 10% of the total amount of network traffic to the second NF node 30 and transmitting the remaining 90% of the total amount of network traffic to at least one other second NF node 50.

[0087] In an embodiment in which the first network node 10, 20 is a first NF node 20, the first NF node 20 may directly transmit the remaining amount of network traffic to at least one other second NF node 50, or may indirectly transmit the remaining amount of network traffic to at least one other second NF node 50 via the first SCP node 10 and / or any other SCP node. The at least one other second NF node 50 receives the remaining amount of network traffic (e.g., via a communication interface of the selected second NF node 30). The at least one other second NF node 50 may be at least one other second NF node 50 that does not provide any indication (e.g., a flag) as described above (i.e., does not indicate that the at least one other second NF node 50 needs to receive the predetermined amount of network traffic (or load)).

[0088] In some embodiments, transmission of the remaining amount of network traffic (or load) may be initiated, for example, in the manner described above, to at least two other second NF nodes of the one or more second NF nodes, which may be at least two other second NF nodes that have not provided any indication (e.g., a flag) as described above (i.e., have not indicated that the at least two other second NF nodes need to receive the predetermined amount of network traffic (or load)).

[0089] In some of these embodiments, the remaining amount of network traffic may be distributed among at least two other second NF nodes, e.g., to balance the load on the at least two other second NF nodes. For example, in some embodiments, the first network node 10, 20 may load balance the remaining amount of network traffic among the at least two other second NF nodes 50 by taking into account the relative load on the at least two other second NF nodes.

[0090] Network traffic referred to herein may be any type of network traffic (e.g., any network traffic transmitted by a first network node 10, 20 toward one or more second NF nodes 30, 50). For example, the network traffic may include one or more requests for a service 40 to be provided by one or more second NF nodes 30, 50, one or more other requests, data associated with one or more of these requests, and / or any other data.

[0091] In some embodiments where the network traffic includes one or more requests for a service 40 to be provided by one or more second NF nodes 30, 50, the first network node 10, 20 may determine, at block 612 of FIG. 6 , which of the possible candidate second NF nodes 30, 50 will receive the one or more requests based on the load information. For example, if one of the candidate second NF nodes 30 needs to receive a certain amount of additional network traffic to reach a predetermined amount of network traffic it needs to receive, the one or more requests may be sent toward that candidate second NF node 30. Otherwise, the one or more requests may be sent to one or more other of the candidate second NF nodes 50. In some embodiments, the method described with reference to block 612 et seq. of FIG. 6 may be repeated each time a service needs to be requested by the first NF node 20.

[0092] FIG. 7 is a signaling diagram illustrating signal interactions in a system according to one embodiment. The system illustrated in FIG. 7 includes a first network node 10, 20, one or more second NF nodes 30, 50 of service producers (“NFp1”, “NFp2”), and an NRF node 60. The system of FIG. 7 illustrates an embodiment in which the second network node is the NRF node 60. Thus, the NRF node 60 may be as described above with reference to FIGS. 2 and 3. The first network node 10, 20 may be as described above with reference to FIGS. 4 and 5. The first network node 10, 20 may be a first SCP node 10 (“SCP”) or a first NF node 20 of a first service consumer (“NFc”). Although not illustrated in FIG. 7, in some embodiments in which the first network node 10 is a first SCP node 10, the system may further include a first NF node 20. The first SCP node 10 may be configured to act as an SCP between the first NF node 20 and one or more second NF nodes 30, 50.

[0093] One or more second NF nodes 30, 50 may each be for providing (e.g., configured to provide) a service 40 ("Service A"). In some embodiments, as shown in Figure 7, a group (or set) 402 ("Set 1") of second NF nodes may include one or more second NF nodes 30, 50. While two second NF nodes 30, 50 are shown in Figure 7, it will be understood that the group 402 of second NF nodes may include a single second NF node according to some embodiments, or multiple (e.g., two, three, or more) second NF nodes according to other embodiments.

[0094] In some embodiments, when the system includes a first SCP node 10, the entity may include the first SCP node 10 and the NRF node 60. That is, in some embodiments, the first SCP node 10 may be merged with the NRF node 60 in a composite entity. In general, the NRF node 60 is the node that provides NF service registration and discovery. As such, the NRF node 60 allows NF nodes to identify services provided by other NF nodes.

[0095] Although only one first network node 10, 20 (e.g., one first SCP node 10 or one first NF node 20) is shown in FIG. 7, the system may include one or more first network nodes (e.g., one or more first SCP nodes 10 and / or one or more first NF nodes 20). Similarly, although only one group (or set) 402 of second NF nodes 30, 50 is shown in FIG. 7, the system may include one or more groups (or sets) of second NF nodes. In some embodiments, the one or more second NF nodes 30, 50 may be grouped according to the type of NF node. For example, second NF nodes 30, 50 of the same type and / or capable of providing the same service 40 may be part of the same group 402.

[0096] In some embodiments, the first SCP node 10 and the first NF node 20 may be located in separate deployment units, and / or the first SCP node 10 and at least one of the one or more second NF nodes 30, 50 may be located in separate deployment units. Thus, an SCP node based on separate deployment units may be provided, as described in 3GPP TS 23.501 v16.4.0. In other embodiments, the first SCP node 10 may be located as a distributed network element. For example, in some embodiments, a portion of the first SCP node 10 (e.g., a service agent) may be located in the same deployment unit as the first NF node 20, and / or a portion of the first SCP node 10 (e.g., a service agent) may be located in the same deployment unit as at least one of the one or more second NF nodes 30, 50. Thus, an SCP node based on a service mesh may be provided, as described in 3GPP TS 23.501 v16.4.0.

[0097] In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node 20 and the first SCP node 10, and / or at least one third SCP node may be configured to operate as an SCP between the first SCP node 10 and at least one of the one or more second NF nodes 30, 50. Thus, there may be multiple paths of SCP nodes. In some of these embodiments, the first SCP node 10 and one or more of the at least one second SCP node and the at least one third SCP node may be deployed in independent deployment units. In some embodiments, the at least one second SCP node and / or the at least one third SCP node may be deployed as distributed network elements.

[0098] As indicated by arrow 700 in FIG. 7 , a second NF node 30 of the one or more second NF nodes 30, 50 may initiate transmission (e.g., by itself or by having another node transmit, such as via a communication interface of the second NF node 30) of a message to the NRF node 60. The message 700 includes an indication (e.g., a flag) that the second NF node 30 is being tested in the network. The message 700 also includes load information for the second NF node 30. Advantageously, the indication may be based on the load information of the second NF node 30. The message signals (e.g., flags) to the NRF node that the load information represents a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive. That is, the message advantageously includes an indication that signals (e.g., flags) that the load information should be interpreted as an expected amount of network traffic (or load) to be received by the second NF node 30. The second NF node 30 may require the predetermined amount of network traffic, for example, to undergo a test (e.g., canary test) in the network.

[0099] In some embodiments, the second NF node 30 may initiate transmission of such a message towards the NRF node 60 in response to a change in load information for the second NF node 30. That is, the message may, according to some embodiments, notify the NRF node 60 of a change to the load information for the second NF node 30. The NRF node 60 receives the message (e.g., via the communication interface 36 of the NRF node 60).

[0100] As indicated by arrow 702 in FIG. 7 , in some embodiments, the NRF node 60 may initiate transmission of a response to the message (e.g., it may transmit itself or have another node transmit, such as via a communication interface of the second NF node 30) toward the second NF node 30. The response may acknowledge receipt of message 700. In some embodiments, the profile of the second NF node 30 stored in the NRF node 60 may include load information for the second NF node 30. In these embodiments, the NRF node 60 may update the load information in the profile of the second NF node 30 with the load information received in message 700. In these embodiments, the response to the message may include information indicating that the profile has been updated with the received load information. In some embodiments, the profile of the second NF node 30 may include an indication signaling that the load information represents a predetermined amount of network traffic that the second NF node 30 requires to be received.

[0101] As indicated by arrow 704 in FIG. 7 , the NRF node 60 initiates transmission of a message (e.g., itself or causes another node to transmit, such as via a communication interface of the second NF node 30) toward the first network node 10, 20. The message 704 includes an indication (e.g., a flag) that the second NF node 30 is being tested in the network. The message 704 also includes load information about the second NF node 30. Advantageously, the indication signals (e.g., a flag) to the first network node 10, 20 that the load information represents a predetermined amount of network traffic that the second NF node 30 needs to receive. In some embodiments, the predetermined amount of network traffic that the selected second NF node 30 needs to receive may be a predetermined percentage of the total amount of network traffic available for transmission. For example, if the load information includes a value of 20, this may indicate that the selected second NF node 30 needs to receive 20% of the total amount of network traffic available for transmission.

[0102] In embodiments where there are changes to the load information for the second NF node 30, the NRF node 60 may initiate transmission of such message 704 to the first network node 10, 20 in response to the changes. Thus, the load information included in message 704 may be updated load information. In some embodiments, message 704 may include a profile of the second NF node 30, which profile may include the load information. In embodiments where the profile of the second NF node 30 is updated, message 704 may include the updated profile of the second NF node 30.

[0103] The first network node 10, 20 receives the message 704 from the NRF node 60. Thus, the first network node 10, 20 has knowledge that the second NF node 30 requires a predetermined amount of traffic (or load). In embodiments where there is a change to the load information, the message 704 may be received in response to the change to the load information (e.g., as may be included in the profile of the second NF node 30). In some embodiments, the first network node 10, 20 may subscribe to be notified of the change. As indicated by arrow 706 in FIG. 7, in some embodiments, the first network node 10, 20 may initiate transmission of a response to the message to the NRF node 60 (e.g., it may transmit or have another node transmit, such as via the communication interface 16 of the first network node 10, 20). The response may acknowledge that the message was received.

[0104] In some embodiments, any one or more of the steps indicated by arrows 700-706 may be performed for all second NF nodes 30, 50. For example, while FIG. 7 shows these steps being performed for only one second NF node 30, it will be understood that these steps may also be performed for at least one other second NF node 50, and the same description of these steps applies. In the case of at least one other second NF node 50 that does not require the predetermined amount of network traffic, these steps may still be performed for the at least one other second NF node 50, but the message does not include an indication signaling that the predetermined amount of network traffic is required. In some embodiments, although not shown in FIG. 7, the steps indicated by arrows 700-706 may be repeated for a second NF node 30, 50 if the load on the second NF node 30, 50 changes or needs to be updated.

[0105] Although not shown in FIG. 7 , instead of or in addition to the steps indicated by arrows 704 and 706, the first network node 10, 20 may perform the discovery process described above. Specifically, the first network node 10, 20 may initiate transmission of a discovery request to the NRF node 60. As previously described, a discovery request is a request for information indicating one or more second NF nodes 30, 50 for providing the service 40 requested by the first NF node 20. The NRF node 60 may receive the discovery request. Thus, in these embodiments, the NRF node 60 may initiate transmission of a message to the first network node 10, 20 in response to the discovery request. The message includes load information and an indication that advantageously signals that the load information represents a predetermined amount of network traffic that the second NF node 30 needs to receive.

[0106] The first network node 10, 20 may need to send a service request to a second NF node 30, 50 to provide the service 40 requested by the first NF node 20. In this case, as indicated by block 708 of FIG. 7 , the first network node 10, 20 may check the load on one or more second NF nodes 30, 50 and select a second NF node 30 (or instance of a second NF node 30) from the one or more second NF nodes 30, 50 to provide the service 40 requested by the first NF node 20. In some embodiments, the one or more second NF nodes 30, 50 may be one or more candidate second NF nodes 30, 50 discovered in the discovery process described above. The selection may be based on the load information. In this regard, the first network node 10, 20 knows that the load information it checks in block 708 of FIG. 7 represents a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive, and this can therefore be taken into account when selecting the second NF node 30, 50 to which to send the service request.

[0107] More specifically, the first network node 10, 20 may determine, based on the load information, which of the possible candidate second NF nodes 30, 50 will receive the service request at block 708 of Figure 7. For example, if one of the candidate second NF nodes 30 needs to receive a certain amount of additional network traffic to reach a predetermined amount of network traffic that it needs to receive, the service request may be sent toward this candidate second NF node 30. Otherwise, the service request may be sent to another candidate second NF node 50.

[0108] Although not shown in FIG. 7 , in some embodiments, the first network node 10, 20 may check one or more other criteria before considering the load information. For example, in some embodiments, the first network node 10, 20 may first check the locality of one or more second NF nodes 30, 50 and / or the priority assigned to one or more second NF nodes 30, 50 before checking the load on the one or more second NF nodes 30, 50. Thus, in some embodiments, the selection of a second NF node to provide a service requested by the first NF node 20 may be performed based on load and, optionally, one or more other criteria. In some embodiments, if there are multiple candidate second NF nodes, the first network node 10, 20 may make the selection based on the relative load of each candidate second NF node, where the relative load is based on the absolute (or actual) load on the second NF node and its capacity.

[0109] As indicated by arrow 710 in FIG. 7 , the first network node 10, 20 initiates transmission of a service request to the selected second NF node 30 (e.g., by itself transmitting or causing another node to transmit, such as via the communication interface 16 of the first network node 10, 20). In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may transmit the service request 710 directly to the selected second NF node 30, or may transmit the service request 710 indirectly via the first SCP node 10 and / or any other SCP node(s) toward the selected second NF node 30. The selected second NF node 30 receives the service request 710 (e.g., via the communication interface of the selected second NF node 30). The service request 710 is a request to the selected second NF node 30 to provide the service 40 requested by the first NF node 20. The service 40 may be requested, for example, by a first NF node 20 for a subscriber (e.g., a user or user equipment (UE)).

[0110] 7, the selected second NF node 30 begins transmitting (e.g., by itself or by having another node transmit, such as via a communication interface of the selected second NF node 50) a second response toward the first network node 10, 20. Thus, the first network node 10, 20 receives this response 712 from the second NF node 30 selected to provide the service 40. In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may receive the response 712 directly from the selected second NF node 30, or may receive the response 712 indirectly from the selected second NF node 30 via the first SCP node 10 and / or any other SCP node.

[0111] 7 is described with reference to a service request, it will be understood that the method may be applied to any other network traffic. As previously mentioned, the network traffic referred to herein may be any type of network traffic (e.g., any network traffic transmitted by a first network node 10, 20 toward one or more second NF nodes 30, 50). For example, the network traffic may include one or more requests for a service 40 to be provided by one or more second NF nodes 30, 50, one or more other requests, data associated with one or more of these requests, and / or any other data.

[0112] Thus, more generally, although not shown in FIG. 7 , the first network node 10, 20 may begin transmitting (e.g., itself transmitting or causing another node to transmit, such as via the communication interface 16 of the first network node 10, 20) a predetermined amount of network traffic (or load) that the second NF node 30 needs to receive, toward the second NF node 30. In embodiments in which the first network node 10, 20 is the first NF node 20, the first NF node 20 may transmit the predetermined amount of network traffic directly to the selected second NF node 30, or may transmit the predetermined amount of network traffic indirectly via the first SCP node 10 and / or any other SCP node(s) toward the selected second NF node 30. Thus, the selected second NF node 30 receives the predetermined amount of network traffic (e.g., via the communication interface of the selected second NF node 30).

[0113] 7, in some embodiments, the first network node 10, 20 may begin transmitting a remaining amount of network traffic (or load) available for transmission toward at least one other second NF node 50 of the one or more second NF nodes. For example, if the predetermined amount of network traffic (or load) that the second NF node 30 needs to receive is 10% of the total amount of network traffic available for transmission, the first network node 10, 20 may begin transmitting 10% of the total amount of network traffic to the second NF node 30 and transmitting the remaining 90% of the total amount of network traffic to the at least one other second NF node 50.

[0114] In an embodiment in which the first network node 10, 20 is a first NF node 20, the first NF node 20 may directly transmit the remaining amount of network traffic to at least one other second NF node 50, or may indirectly transmit the remaining amount of network traffic to at least one other second NF node 50 via the first SCP node 10 and / or any other SCP node. The at least one other second NF node 50 receives the remaining amount of network traffic (e.g., via a communication interface of the selected second NF node 30). The at least one other second NF node 50 may be at least one other second NF node 50 that does not provide any indication (e.g., a flag) as described above (i.e., does not indicate that the at least one other second NF node 50 needs to receive the predetermined amount of network traffic (or load)).

[0115] In some embodiments, transmission of the remaining amount of network traffic (or load) may be initiated toward at least two other second NF nodes of the one or more second NF nodes, e.g., in the manner described above. The at least two other second NF nodes may be at least two other second NF nodes that have not provided any indication (e.g., a flag) as described above (i.e., have not indicated that the at least two other second NF nodes need to receive the predetermined amount of network traffic (or load)). In some of these embodiments, the remaining amount of network traffic may be distributed among the at least two other second NF nodes, e.g., to balance the load on the at least two other second NF nodes. For example, in some embodiments, the first network node 10, 20 may load balance the remaining amount of network traffic among the at least two other second NF nodes by taking into account the relative load on the at least two other second NF nodes 50.

[0116] As indicated by arrow 714 in Figure 7, the method may be repeated one or more times, for example, by the first network node 10, 20 again checking the load of one or more second NF nodes 30, 50 as described above with reference to block 708 of Figure 7. In some embodiments, the method described with reference to block 708 et seq. of Figure 7 may be repeated each time service is requested by the first NF node 20.

[0117] Figure 8 is a signaling diagram illustrating signal exchange in a system according to one embodiment. The system shown in Figure 8 includes multiple NF nodes 20, 30, and 50. The multiple NF nodes 20, 30, and 50 include a first NF node ("NF1") 20, a second NF node ("NF3") 30, and a third NF node ("NF5") 50. In the embodiment shown in Figure 8, the first NF node 20, the second NF node 30, and the third NF node 50 are under test in the network. For example, they may be newly upgraded, newly introduced into the system, and / or under test in the network for any other reason.

[0118] As shown in FIG. 8 , the multiple NF nodes 20, 30, and 50 may also include one or more other NF nodes (“NF2,” “NF4,” and “NF6”). In the embodiment shown in FIG. 8 , the first NF node 20 functions as an NF node for a first service consumer, the second NF node 30 functions as an NF node for a second service producer and also functions as an NF node for the first service consumer, and the third NF node 50 functions as an NF node for the second service producer. The first service consumer may be the same service consumer as the second service consumer, or the first service consumer may be a different service consumer from the second service consumer. Similarly, the first service producer may be the same service producer as the second service producer, or the first service producer may be a different service producer from the second service producer.

[0119] The system of FIG. 8 illustrates an embodiment in which the first network node is a service consumer NF node and the second network node is a service producer NF node. Specifically, the first NF node 20 may be one of those described above with reference to FIGS. 4 and 5, and the second NF node 30 and / or the third NF node 50 may be one of those described above with reference to FIGS. 2 and 3. While the first network node in the embodiment illustrated in FIG. 8 is the first service consumer NF node 20, it will be understood that the first network node may instead be a first SCP node according to other embodiments. Thus, steps in FIG. 8 described with reference to the first NF node 20 will be understood to be steps that may instead be performed by the first SCP node. For example, although not illustrated in FIG. 8, in some embodiments in which the first network node is a first SCP node, the system may further include the first NF node 20. In embodiments in which the system includes a first SCP node, the first SCP node may be configured to act as an SCP between the first NF node 20 and any one or more other NF nodes of the plurality of NF nodes 30, 50.

[0120] Each of the multiple NF nodes 20, 30, 50 may be for providing (e.g., configured to provide) a service. For example, a first NF node 20 may be for providing a first service 40 (“Service A”), a second NF node 30 may be for providing a second service 60 (“Service B”), and a third NF node 50 may be for providing a third service 80 (“Service C”). In some embodiments, there may also be at least one other NF node for providing the first service 40, at least one other NF node for providing the second service 60, and at least one other NF node for providing the third service 80, as shown in FIG. 8 . Any two or more (e.g., all) of the first service 40, the second service 60, and the third service 80 may be the same service, or any two or more (e.g., all) of the first service 40, the second service 60, and the third service 80 may be different services.

[0121] In some embodiments, the NF nodes may be grouped, as shown in Figure 8. That is, the NF nodes may be divided into multiple groups (or sets) 402, 404, 406. For example, as shown in Figure 8, a first group (or set) 402 of NF nodes ("Set X") may include a first NF node 20 and, optionally, one or more other NF nodes, a second group (or set) 404 of NF nodes ("Set Y") may include a second NF node 30 and, optionally, one or more other NF nodes, and a third group (or set) 406 of NF nodes ("Set Z") may include a third NF node 50 and, optionally, one or more other NF nodes. While each group 402, 404, 406 of NF nodes is illustrated in FIG. 8 as including two NF nodes, it will be understood that each of these groups 402, 404, 406 of NF nodes may include a single NF node according to some embodiments, or multiple (e.g., two, three, or more) NF nodes according to other embodiments. Also, while the NF nodes are considered to be deployed within groups (or sets) 402, 404, 406 in the embodiment illustrated in FIG. 8 (e.g., such that one particular NF node 20, 30, 50 within group 402, 404, 406 may be under test in the network), this is not necessarily the case. For example, in other embodiments, individual NF nodes may be deployed, or a combination of one or more groups of NF nodes and one or more individual NF nodes may be deployed.

[0122] While a particular number of NF nodes are shown in FIG. 8, it will be understood that the system may include any other number (e.g., one or more) of NF nodes. Similarly, while FIG. 8 shows three groups (or sets) 402, 404, and 406 of NF nodes, it will be understood that the system may include any other number (e.g., one or more) of groups of NF nodes. In some embodiments, NF nodes may be grouped according to NF node type. For example, NF nodes of the same type and / or capable of providing the same service 40, 60, and 80 may be part of the same group 402, 404, and 406.

[0123] In some embodiments where the system includes a first SCP node (not shown in FIG. 8 ), the first SCP node and at least one NF node of the plurality of NF nodes 20, 30, 50 may be located in a separate deployment unit. Thus, an SCP node based on a separate deployment unit may be provided, as described in 3GPP TS 23.501 v16.4.0. In other embodiments where the system includes a first SCP node (not shown in FIG. 8 ), the first SCP node may be located as a distributed network element. For example, in some embodiments, a portion of the first SCP node (e.g., a service agent) may be located in the same deployment unit as at least one NF node of the plurality of NF nodes 20, 30, 50. Thus, an SCP node based on a service mesh may be provided, as described in 3GPP TS 23.501 v16.4.0.

[0124] In some embodiments (not shown in FIG. 8), at least one second SCP node may be configured to act as an SCP between the first SCP node and at least one NF node of the plurality of NF nodes 20, 30, 50. Thus, there may be multiple paths of SCP nodes. In some of these embodiments, the first SCP node and one or more of the at least one second SCP node may be deployed in independent deployment units. In some embodiments, the first SCP node and one or more of the at least one second SCP node may be deployed as distributed network elements.

[0125] The method illustrated in FIG. 8 may be performed subsequent to (e.g., in response to) the method described above with reference to FIG. 3 and FIG. 5. More specifically, although not shown in FIG. 8, as described above with reference to FIG. 3 and FIG. 5, a second network node (e.g., a second NF node 30 or NRF node) initiates transmission of a message toward a first NF node 20 (operable as the aforementioned first network node), and the first NF node 20 receives the message. The message includes an indication that an NF node of a plurality of NF nodes is under testing in the network. For purposes of the embodiment illustrated in FIG. 8, it is assumed that the message includes an indication that the second NF node 30 is under testing in the network. Thus, the following method may be performed subsequent to (e.g., in response to) the first NF node 20 receiving a message including this indication. The indication signals to the first NF node 20 that the second NF node 30 is a candidate for selection in selecting at least one second NF node of the one or more second NF nodes 30, 50 to provide the service requested by the first NF node 20.

[0126] In the embodiment shown in FIG. 8 , the first NF node 20 functions as a service consumer NF node. As indicated by arrow 800 in FIG. 8 , the first NF node 20 selects at least one other NF node from the plurality of NF nodes to provide the first service 40 (e.g., an instance thereof) requested by the first NF node 20. In some embodiments, the at least one other NF node may be one or more (e.g., available) NF nodes found in a discovery process, such as those described above. The selection is based on an indication. Thus, the first NF node 20 may select the second NF node 30 to provide the first service 40 in the embodiment shown in FIG. 8 because the indication signals to the first NF node 20 that the second NF node 30 is a candidate for selection. For purposes of illustration, it is assumed that the second NF node 30 is selected. However, it will be understood that any other NF node of the service producer that the indication signals as a candidate for selection may be selected.

[0127] Although not shown in FIG. 8 , in some embodiments, the first NF node 20 may check one or more attributes of the other NF nodes 30, 50 to make the selection. An NF node attribute may indicate a characteristic of the NF node. For example, a locality attribute of an NF node may indicate the locality (or location) of the NF node. Thus, in some embodiments, the first NF node 20 may first check the locality attribute and / or any other attribute(s) of the other NF nodes 30, 50. Thus, in some embodiments, the selection of at least one other NF node among the plurality of NF nodes to provide the first service 40 requested by the first NF node 20 may be performed based on one or more attributes of the at least one other NF node.

[0128] In some embodiments, the profile of an NF node may include an indication and / or one or more attributes for the NF node. For example, an attribute of the one or more attributes for the NF node may be set to an indication (e.g., Locality = "testing"). In some embodiments, the attribute may be a value. Thus, for example, a specific value may be defined to indicate "testing." The indication may also be in any other form, provided that it is the same indication used by all NF nodes. Thus, if an NF node is under testing in the network, it may be easily implemented as such by simply changing the attribute to indicate that it is under testing in the network. In some embodiments, the attribute may be an attribute that should (or must) be prioritized (i.e., considered first and / or always used) when selecting at least one NF node to provide a service requested by the NF node. In this way, it may be ensured that the indication is always considered, thereby selecting a testing NF node in the network and thereby performing testing in the network.

[0129] In some embodiments, the attribute may be an attribute that matches (i.e., is the same as) or at least partially matches (i.e., is at least partially the same as) a corresponding attribute of the NF node requesting the first service 40. Thus, referring to the embodiment shown in FIG. 8 , the attribute may be an attribute that matches or at least partially matches a corresponding attribute of the first NF node 20. The first NF node 20 may also be under test in the network. Thus, when the attribute is set to the above indication, the first NF node 20 under test in the network may also select a second NF node 30 under test in the network. For example, the first NF node 20 may use a certain attribute (e.g., locality) as a first selection criterion to find other NF nodes with the same (e.g., locality) attribute. When this attribute is set to the above indication (e.g., “under test”), this means that the first NF node 20 will select an NF node under test in the network at the same time, such as the second NF node 30. In this case, the selected second NF node 30 is operating as an NF node for the service producer. However, as will be explained in more detail later, this selected second NF node 30 may also operate as a service consumer for another service producer, and thus may perform the same steps as the first NF node 20, thereby obtaining an end-to-end path for the NF node under test in the network.

[0130] As indicated by arrow 802 in FIG. 8 , the first NF node 20 may initiate transmission of a service request to the selected second NF node 30 (e.g., it may transmit or have another node transmit, such as via the communication interface 16 of the first NF node 20). This service request 802 is referred to herein as a “first service request.” The first NF node 20 may transmit the first service request 802 directly to the selected second NF node 30, or it may transmit the first service request 802 indirectly to the selected second NF node 30 via the aforementioned first SCP node and / or any other SCP node (not shown in FIG. 8 ). The selected second NF node 30 receives the first service request 802 (e.g., via the communication interface of the selected second NF node 30). The first service request 802 is a request to a selected second NF node 30 to provide a first service 40 requested by a first NF node 20. The first service 40 may be requested by the first NF node 20 for a subscriber (e.g., a user or user equipment (UE)), for example.

[0131] As indicated by arrow 804 in FIG. 8 , the selected second NF node 30 may begin transmitting (e.g., by itself or by having another node transmit, such as via a communication interface of the selected second NF node 30) a first response to the first service request 802 toward the first NF node 20. Thus, the first NF node 20 receives this first response 804 from the second NF node 30 selected to provide the first service 40. The first NF node 20 may receive the first response 804 directly from the selected second NF node 30, or may receive the first response 804 indirectly from the selected second NF node 30 via the aforementioned first SCP node 10 and / or any other SCP node (not shown in FIG. 8 ). 8, the first request 802 and second response 804 are between two NF nodes 10, 30 that are under test (e.g., possibly by different vendors) in the network. However, in other embodiments, only the second NF node 30 of the two NF nodes may be under test in the network.

[0132] In some embodiments, such as that shown in FIG. 8 , the second NF node 30 itself may need to transmit a request to an NF node to provide a service. For example, the second NF node 30 may need to transmit a request to an NF node to provide a third service 80. In this case, the second NF node 30 acts as a service consumer NF node. As noted above, the method illustrated by FIG. 8 may be performed subsequent to (e.g., in response to) the method described above with reference to FIGS. 3 and 5 . More specifically, although not shown in FIG. 8 , as described above with reference to FIGS. 3 and 5 , the second network node (e.g., the third NF node 50 or NRF node) initiates transmission of a message toward the second NF node 30 (operating as the aforementioned first network node), and the second NF node 30 receives the message. The message includes an indication that an NF node of a plurality of NF nodes is being tested in the network. For purposes of the embodiment shown in Figure 8, it is assumed that the message includes an indication that the third NF node 50 is under testing in the network. As such, the following method may be performed by the second NF node 30 following (e.g., in response to) receiving a message including this indication. The indication signals to the second NF node 30 that the third NF node 50 is a candidate for selection in selecting at least one second NF node of the one or more second NF nodes 20, 50 to provide a service requested by the second NF node 30.

[0133] In this case, the second NF node 30 functions as a service consumer NF node, and the third NF node 50 functions as a service producer NF node. As indicated by block 806 in Figure 8, the second NF node 30 selects at least one other NF node from the plurality of NF nodes to provide the third service 80 (e.g., an instance thereof) requested by the second NF node 30. The selection is based on an indication, and in the embodiment shown in Figure 8, the second NF node 30 selects the third NF node 50 to provide the third service 80, such as an indication that the second NF node 30 has signaled that it is a candidate for selection. However, it will be understood that any other NF node of the service producer that the indication signals as a candidate for selection may be selected.

[0134] 8, in some embodiments, the second NF node 30 may check one or more attributes of the NF node 20, 50 to make the selection, such as any of those described above. Thus, in some embodiments, the selection of at least one other NF node of the plurality of NF nodes for providing the third service 80 requested by the second NF node 30 may be performed based on one or more attributes of the at least one other NF node.

[0135] As mentioned above, in some embodiments, the profile of an NF node may include an indication and / or one or more attributes for the NF node. For example, an attribute among one or more attributes for the NF node may be set to the indication. In some embodiments, the attribute may be an attribute that should be prioritized when selecting at least one NF node to provide a service requested by the NF node. In this manner, it may be ensured that the indication is always taken into account, thereby selecting an NF node under test in the network and thereby conducting testing in the network. In some embodiments, the attribute may be an attribute that matches (i.e., is the same as) or at least partially matches (i.e., is at least partially the same as) a corresponding attribute of the NF node requesting the third service 80. Thus, with reference to the embodiment shown in FIG. 8 , the attribute may be an attribute that matches or at least partially matches a corresponding attribute of the second NF node 30. The second NF node 30 may also be under test in the network. Thus, when the attribute is set to the indication, the second NF node 30 under test in the network may also select the third NF node 50 under test in the network.

[0136] As indicated by arrow 808 in FIG. 8 , the second NF node 30 may initiate transmission of a service request to the selected third NF node 50 (e.g., it may transmit or have another node transmit, such as via the communication interface 36 of the second NF node 30). This service request 808 is referred to herein as a “second service request.” The second NF node 30 may transmit the second service request 808 directly to the selected third NF node 50, or it may transmit the second service request 808 indirectly to the selected third NF node 50 via the aforementioned first SCP node and / or any other SCP node (not shown in FIG. 8 ). The selected third NF node 50 receives the second service request 808 (e.g., via the communication interface of the selected third NF node 50). The second service request 808 is a request to the selected third NF node 50 to provide a third service 80 requested by the second NF node 30. The third service 80 may be requested by the second NF node 30, for example, on behalf of a subscriber (e.g., a user or user equipment (UE)).

[0137] As indicated by arrow 810 in FIG. 8 , the selected third NF node 50 may begin transmitting (e.g., by itself or by having another node transmit, such as via a communication interface of the selected third NF node 50) a second response to the second service request 808 toward the second NF node 30. Thus, the second NF node 30 receives this second response 810 from the third NF node 50 selected to provide the third service 80. The second NF node 30 may receive the second response 810 directly from the selected third NF node 50, or may receive the second response 810 indirectly from the selected third NF node 50 via the aforementioned first SCP node 10 and / or any other SCP node (not shown in FIG. 8 ). In the embodiment shown in FIG. 8 , the second request 808 and second response 810 are between two NF nodes 30, 50 (e.g., possibly by different vendors). However, in other embodiments, only the third NF node 50 of the two NF nodes may be under test in the network according to other embodiments.

[0138] Although not shown in FIG. 8 , the method may be repeated any number of times, e.g., by the same NF node and / or by other NF nodes, e.g., each time the NF node needs to send network traffic (e.g., another service request) to another NF node. As described with reference to FIG. 8 , it is advantageous for the NF node to have knowledge of which other NF nodes to select to ensure that the NF node under test in the network receives the necessary network traffic to be able to undergo the test. This enables end-to-end testing in the network. Furthermore, the method allows upgraded or newly introduced NF nodes (or instances of NF nodes), e.g., of different NF types and / or from different vendors, to be tested in the network without affecting the rest of the network and without requiring any specific configuration changes for its implementation.

[0139] 8 is described with reference to a service request, it will be understood that the method may be applied to any other network traffic. As mentioned above, the network traffic referred to herein may be any type of network traffic (e.g., any network traffic to be transmitted by a first network node (e.g., the first NF node 10, the second NF node 30, or the first SCP node) toward one or more NF nodes (e.g., the second NF node 30 or the third NF node 50) of one or more service producers). For example, the network traffic may include one or more requests for services 40, 60, 80 to be provided by one or more NF nodes 20, 30, 50, one or more other requests, data associated with one or more of these requests, and / or any other data.

[0140] Although the present techniques have been described herein with respect to the selection of a second NF node 30, 50, it will be appreciated that the present techniques may also be applied to the reselection of a second NF node 30, 50 (e.g., following a failure of a previously selected second NF node).

[0141] Other embodiments include those defined in the following numbered statements:

[0142] Embodiment 1. A method for processing messages in a fifth generation network, the method being performed by a first network node (10, 20), the first network node (10, 20) being a first NF (Network Function) node (20) of a service consumer, or a first SCP node (10) configured to act as an SCP (Service Communication Proxy) between the first NF node (20) and one or more second NF nodes (30, 50) of a service producer, the method comprising: receiving (102, 610, 704) a message from a second network node (30, 60), said message comprising: an indication that a second NF node (30) of the one or more second NF nodes (30, 50) is under test in the network; and The indication signals to the first network node (10, 20) that the second NF node (30) is a candidate for selection when selecting at least one second NF node (30) among the one or more second NF nodes (30, 50) to which network traffic is to be transmitted; and / or The method, wherein the message includes load information about the second NF node (30), and the indication signals to the first network node (10, 20) that the load information represents a predetermined amount of network traffic that the second NF node (30) needs to receive.

[0143] Embodiment 2. The method of embodiment 1, comprising: The second network node (30, 60) the second NF node (30); or The method is a network repository function node (60).

[0144] Embodiment 3. The method of embodiment 1 or 2, comprising: The method, wherein the profile of the second NF node (30) includes the indication and / or the load information.

[0145] Embodiment 4. The method of embodiment 3, comprising: the profile includes one or more attributes for the second NF node (30); A method wherein an attribute of the one or more attributes for the second NF node (30) is set to the indication.

[0146] Embodiment 5. The method of embodiment 4, comprising: The method, wherein the attribute is a locality attribute indicating the location of the second NF node (30).

[0147] Embodiment 6. The method of embodiment 4 or 5, The attribute is an attribute to be prioritized when selecting the at least one second NF node (30).

[0148] Embodiment 7. The method of any one of embodiments 4 to 6, comprising: The attribute is an attribute that matches or at least partially matches a corresponding attribute for the first NF node (20).

[0149] Embodiment 8. The method of any one of embodiments 3 to 7, where embodiment 3 is dependent on embodiment 2, comprising: the second network node is the network repository function node (60); The method, wherein the message includes the profile of the second NF node (30).

[0150] Embodiment 9. The method of embodiment 8, comprising: The message may include: changes to said load information; and / or 1. A method according to claim 1, wherein the discovery request is received in response to a discovery request, the discovery request being a request for information indicating one or more second NF nodes (30, 50) for providing a service requested by the first NF node (20).

[0151] Embodiment 10. The method of embodiment 9, comprising: The method wherein the first network node (10, 20) is subscribed to receive the change.

[0152] Embodiment 11. The method of embodiment 2, or any of embodiments 3 to 7 when embodiment 3 is dependent on embodiment 2, comprising: the second network node is the second NF node (30); The method, wherein the message is a response to a service request, the service request being a request for the second NF node (30) to provide a service (40) requested by the first NF node (20).

[0153] Embodiment 12. The method of any one of embodiments 1 to 11, comprising: The method, wherein the message includes a Load Control Information (LCI) header, the LCI header including the indication.

[0154] Embodiment 13. The method of any one of embodiments 1 to 12, comprising: The method, wherein the first NF node (20) is under test in the network.

[0155] Embodiment 14. The method of any one of embodiments 1 to 13, comprising: selecting at least one second NF node (30) of the one or more second NF nodes (30, 50) to which to send network traffic, the selection being based on the indication.

[0156] Embodiment 15. The method of any one of embodiments 1 to 14, comprising: the selection of at least one second NF node (30) of the one or more second NF nodes is such that the at least one second NF node (30) is for providing the service (40) requested by the first NF node (20); and / or The method, wherein the network traffic includes a service request, the service request being a request for the requested service (40) to be provided by the first NF node (20).

[0157] Embodiment 16. The method of any one of embodiments 1 to 15, comprising: The method of claim 1, wherein the predetermined amount of network traffic that the second NF node (30) needs to receive is a predetermined percentage of a total amount of network traffic available for transmission.

[0158] Embodiment 17. The method of any one of embodiments 1 to 16, comprising: and commencing transmission, toward the second NF node (30), of a predetermined amount of network traffic that the second NF node (30) needs to receive.

[0159] Embodiment 18 The method of embodiment 17, comprising: commencing transmission of a remaining amount of network traffic available for transmission toward at least one other second NF node of the one or more second NF nodes.

[0160] Embodiment 19. The method of embodiment 18, comprising: transmitting the remaining amount of network traffic to at least two other second NF nodes among the one or more second NF nodes, and distributing the network traffic among the at least two other second NF nodes to balance the load on the at least two other second NF nodes.

[0161] Embodiment 20. The method of any one of embodiments 1 to 19, comprising: The first SCP node (10) and the first NF node (20) are deployed in separate deployment units; and / or The method, wherein the first SCP node (10) and the second NF node (30) are deployed in independent deployment units.

[0162] Embodiment 21. The method of any one of embodiments 1 to 19, comprising: The method, wherein the first SCP node (10) is deployed as a distributed network element.

[0163] Embodiment 22. The method of embodiment 21, comprising: A portion of the first SCP node (10) is located within the same deployment unit as the first NF node (20); and / or The method, wherein a portion of the first SCP node (10) is deployed within the same deployment unit as the second NF node (30).

[0164] Embodiment 23. The method of any one of embodiments 1 to 22, comprising: At least one second SCP node is configured to act as an SCP between the first NF node (20) and the first SCP node (10); and / or The method, wherein at least one third SCP node is configured to act as an SCP between the first SCP node (10) and the second NF node (30).

[0165] Embodiment 24. The method of embodiment 23, comprising: The method, wherein the first SCP node (10) and one or more of the at least one second SCP node and the at least one third SCP node are deployed in separate deployment units.

[0166] Embodiment 25. The method of embodiment 23, comprising: The method, wherein the at least one second SCP node and / or the at least one third SCP node are deployed as distributed network elements.

[0167] Embodiment 26. The method of any one of embodiments 1 to 25, comprising: The method, wherein the entities include the first SCP node (10) and an NRF (Network Repository Function) node (60).

[0168] Embodiment 27. A first network node (10, 20), 27. A first network node comprising a processing circuit (12) configured to operate according to any one of embodiments 1 to 26.

[0169] Embodiment 28. The first network node (10, 20) according to embodiment 27, wherein the first network node (10, 20) A first network node comprising at least one memory (14) for storing instructions that, when executed by the processing circuit (12), cause the first network node (10, 20) to operate according to any one of embodiments 1 to 26.

[0170] Embodiment 29. A method for processing messages in a fifth generation network, the method being performed by a second network node (30, 60), the method comprising: Initiating (302, 610, 704) a message transmission toward a first network node (10, 20), the first network node (10, 20) being a first Network Function (NF) node (20) of a service consumer or a first Service Proxy (SCP) node (10) configured to act as a Service Communication Proxy (SCP) between the first NF node (20) and one or more second NF nodes of a service producer; The message may include: an indication that a second NF node (30) of the one or more second NF nodes (30, 50) is under test in the network; and The indication signals to the first network node (10, 20) that the second NF node (30) is a candidate for selection when selecting at least one second NF node (30) among the one or more second NF nodes (30, 50) to which network traffic is to be transmitted; and / or The method, wherein the message includes load information about the second NF node (30), and the indication signals to the first network node (10, 20) that the load information represents a predetermined amount of network traffic that the second NF node (30) needs to receive.

[0171] Embodiment 30. The method of embodiment 29, comprising: The second network node (30, 60) the second NF node (30); or The method is a network repository function node (60).

[0172] Embodiment 31 The method of embodiment 29 or 30, The profile of the second NF node (30) includes the indication and / or load information.

[0173] Embodiment 32. The method of embodiment 31, comprising: the profile includes one or more attributes for the second NF node (30); A method wherein an attribute of the one or more attributes for the second NF node (30) is set to the indication.

[0174] Embodiment 33 The method of embodiment 32, comprising: setting the attribute to the indication.

[0175] Embodiment 34 The method of embodiment 32 or 33, The method, wherein the attribute is a locality attribute indicating the location of the second NF node (30).

[0176] Embodiment 35. The method of any one of embodiments 32 to 34, comprising: The attribute is an attribute to be prioritized when selecting the at least one second NF node (30).

[0177] Embodiment 36. The method of any one of embodiments 32 to 35, comprising: The attribute is an attribute that matches or at least partially matches a corresponding attribute for the first NF node (20).

[0178] Embodiment 37. The method of any one of embodiments 31 to 36, when embodiment 31 is dependent on embodiment 30, comprising: the second network node is the network repository function node (60); The method, wherein the message includes the profile of the second NF node (30).

[0179] Embodiment 38 The method of embodiment 37, comprising: The sending of the message changes to said load information; and / or The method is initiated in response to a discovery request, the discovery request being a request for information indicating one or more second NF nodes (30, 50) for providing a service requested by the first NF node (20).

[0180] Embodiment 39. The method of embodiment 38, comprising: The method wherein the first network node (10, 20) is subscribed to receive the change.

[0181] Embodiment 40. The method of embodiment 30, or any of embodiments 31 to 36 when embodiment 31 depends on embodiment 30, the second network node is the second NF node (30); The method, wherein the message is a response to a service request, the service request being a request for the second NF node (30) to provide a service (40) requested by the first NF node (20).

[0182] Embodiment 41. The method of any one of embodiments 29 to 40, comprising: The method, wherein the message includes a Load Control Information (LCI) header, the LCI header including the indication.

[0183] Embodiment 42. The method of any one of embodiments 29 to 41, comprising: The method, wherein the first NF node (20) is under test in the network.

[0184] Embodiment 43. The method of any one of embodiments 29 to 42, comprising: the selection of at least one second NF node (30) of the one or more second NF nodes is such that the at least one second NF node (30) is for providing the service (40) requested by the first NF node (20); and / or The method, wherein the network traffic includes a service request, the service request being a request for the requested service (40) to be provided by the first NF node (20).

[0185] Embodiment 44. The method of any one of embodiments 29 to 43, comprising: The method of claim 1, wherein the predetermined amount of network traffic that the second NF node (30) needs to receive is a predetermined percentage of a total amount of network traffic available for transmission.

[0186] Embodiment 45. The method of any one of embodiments 29 to 44, comprising: The first SCP node (10) and the first NF node (20) are deployed in separate deployment units; and / or The method, wherein the first SCP node (10) and the second NF node (30) are deployed in independent deployment units.

[0187] Embodiment 46. The method of any one of embodiments 29 to 44, comprising: The method, wherein the first SCP node (10) is deployed as a distributed network element.

[0188] Embodiment 47 The method of embodiment 46, comprising: A portion of the first SCP node (10) is located within the same deployment unit as the first NF node (20); and / or The method, wherein a portion of the first SCP node (10) is deployed within the same deployment unit as the second NF node (30).

[0189] Embodiment 48. The method of any one of embodiments 29 to 47, comprising: At least one second SCP node is configured to act as an SCP between the first NF node (20) and the first SCP node (10); and / or The method, wherein at least one third SCP node is configured to act as an SCP between the first SCP node (10) and the second NF node (30).

[0190] Embodiment 49 The method of embodiment 48, comprising: The method, wherein the first SCP node (10) and one or more of the at least one second SCP node and the at least one third SCP node are deployed in separate deployment units.

[0191] Embodiment 50. The method of embodiment 48, comprising: The method, wherein the at least one second SCP node and / or the at least one third SCP node are deployed as distributed network elements.

[0192] Embodiment 51. The method of any one of embodiments 29 to 50, comprising: The method, wherein the entities include the first SCP node (10) and an NRF (Network Repository Function) node (60).

[0193] Embodiment 52. A second network node (30, 60), wherein the second network node (30, 60) A second network node comprising a processing circuit (32) configured to operate according to any of embodiments 29 to 51.

[0194] Embodiment 53. A second network node (30, 60) according to embodiment 52, wherein the second network node (30, 60) A second network node comprising at least one memory (34) for storing instructions that, when executed by the processing circuit (32), cause the second network node (30, 60) to operate according to any of embodiments 29 to 51.

[0195] Embodiment 54. A method performed by a system, comprising: 27. A method according to any one of claims 1 to 26, 52. The method of any one of embodiments 29 to 51, A method comprising:

[0196] Embodiment 55. A system comprising: At least one first network node (10, 20) according to embodiment 27 or 28; At least one second network node (30, 60) according to embodiment 52 or 53; Including, the system.

[0197] Embodiment 56. A computer program comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform the method of any of embodiments 1 to 26 and / or any of embodiments 29 to 51.

[0198] Embodiment 57. A computer program product embodied on a non-transitory machine-readable medium, comprising instructions executable by a processing circuit to cause the processing circuit to perform the method of any one of embodiments 1 to 26 and / or the method of any one of embodiments 29 to 51.

[0199] Also provided is a computer program comprising instructions that, when executed by a processing circuit (such as the processing circuit 12 of the aforementioned first network node 10, 20 and / or the processing circuit 32 of the aforementioned second network node 30, 60), cause the processing circuit to perform at least a portion of the methods described herein. A computer program product embodied on a non-transitory machine-readable medium is provided, the computer program product comprising instructions executable by the processing circuit (such as the processing circuit 12 of the aforementioned first network node 10, 20 and / or the processing circuit 32 of the aforementioned second network node 30, 60) to cause the processing circuit to perform at least a portion of the methods described herein. A computer program product is provided comprising a carrier comprising instructions for causing a processing circuit (such as the processing circuit 12 of the aforementioned first network node 10, 20 and / or the processing circuit 32 of the aforementioned second network node 30, 60) to perform at least a portion of the methods described herein. In some embodiments, the carrier may be any one of an electronic signal, an optical signal, an electromagnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer readable storage medium.

[0200] In some embodiments, the first network node functionality and / or the second network node functionality described herein may be performed by hardware. Thus, in some embodiments, any one or more of the first network nodes 10, 20 and second network nodes 30, 60 described herein may be hardware nodes. However, it will be understood that, optionally, at least some or all of the first network node functionality and / or the second network node functionality described herein may be virtualized. For example, the functionality performed by any one or more of the first network nodes 10, 20 and second network nodes 30, 60 described herein may be implemented in software running on general-purpose hardware configured to orchestrate the node functionality. Thus, in some embodiments, any one or more of the first network nodes 10, 20 and second network nodes 30, 60 described herein may be virtualized nodes. In some embodiments, at least some or all of the first network node functionality and / or the second network node functionality described herein may be performed in a network-enabled cloud. The functionality of the first network node and / or the functionality of the second network node described herein may all be co-located, or at least some of the node functionality may be distributed.

[0201] It will be appreciated that at least some or all of the method steps described herein may be automated in some embodiments, i.e., in some embodiments, at least some or all of the method steps described herein may be performed automatically. The methods described herein may be computer-implemented methods.

[0202] Thus, the methods described herein advantageously provide improved techniques for processing messages in fifth generation networks that may provide mechanisms for supporting in-network testing (e.g., canary testing) at one or more NF nodes 30, 50 of one or more service producers.

[0203] For example, the present technique allows one or more NF nodes 30, 50 of one or more service producers to be tested within the network when they are newly introduced and / or upgraded (e.g., with new software and / or functionality). The present technique provides an end-to-end signaling path within the network for the NF node under test (e.g., isolated) within the network, without affecting the rest of the NF nodes. It is possible to test interactions between NF nodes within the network (e.g., for different vendors), such as those that have not been tested in a lab before being included in the network and / or those that have not been previously tested in the network. This can be particularly beneficial because new NF nodes and / or upgrades (e.g., software) to existing NF nodes typically need to be introduced into the network in a controlled manner to allow them to be tested within the network before being fully included in the network. For example, a new upgrade can be tested on a single NF node of a service producer within the network before the upgrade is considered for all NF nodes of the service producer within the network.

[0204] This technique is also advantageously compatible with existing load control mechanisms. Moreover, the technique does not require any specific configuration (or modification) in the first network node 10, 20, since it allows the second NF node 30 to signal its expected behavior (e.g., in its profile). The first network node 10, 20 can identify which second NF nodes 30, 50 require network traffic (e.g., because they are under test in the network) and / or the amount of network traffic that needs to be sent towards them.

[0205] It should be noted that the above-described embodiments are illustrative rather than limiting concepts, and that those skilled in the art can design many alternative embodiments without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim, and the words "a" or "an" do not exclude a plurality; a single processor or other unit may fulfill the functions of several units recited in a claim. Any reference signs in the claims should not be construed as limiting their scope.

Claims

1. A method performed by a first network node (10, 20) in a fifth generation network, the first network node (10, 20) being a first Network Function (NF) node (20) of a service consumer or a first SCP node (10) configured to act as a Service Communication Proxy (SCP) between the first NF node (20) and one or more second NF nodes (30, 50) of a service producer, the method comprising: receiving a message (704) from an NRF (Network Repository Function) node (60), wherein the message includes an indication that a second NF node (30) of the one or more second NF nodes (30, 50) is being tested in the fifth generation network; the first network node (10, 20) sending a service request (710) to the second NF node (30) that is indicated to be under test; A method comprising:

2. 10. The method of claim 1, The method, wherein the message (704) from the NRF node (60) is an NFStatusNotify message.

3. 10. The method of claim 1, The method of claim 7, wherein the message from the NRF node includes load information about the test as a percentage of the total traffic load for the second NF node indicated as being under test.

4. 4. The method of claim 3, The message (704) is received from the NRF node (60) that received a message (700) from the second NF node (30) including the indication that the second NF node (30) is under test and the load information about the test.

5. 5. The method of claim 4, The NRF node (60) updates a profile of the second NF node (30) using the load information in the message (700) received from the second NF node (30).

6. 10. The method of claim 1, The method further includes initiating a discovery request to the NRF node (60) to discover one or more network nodes capable of providing the service (40).

7. 10. The method of claim 1, The method further comprises checking the load on the second NF node (30) before sending the service request (710) to the second NF node (30).

8. 8. The method of claim 7, The method of claim 1, wherein the first network node (10, 20) applies further criteria when selecting the second NF node (30) from among candidate second NF nodes (30, 50) provided by the NRF node (60).

9. 9. The method of claim 8, The method, wherein the further criteria includes locality of the second NF node (30).

10. A method performed by a second network node (30, 60) in a fifth generation network, comprising: Initiating transmission of a message (700) towards an NRF (Network Repository Function) node (60), wherein the message (700) includes an indication that a second NF node (30) of one or more second NF (Network Function) nodes (30, 50) is being tested in the fifth generation network; receiving a service request (710) from a first network node that has received a message (704) from the NRF node (60) containing the indication that the second NF node (30) is under test; A method comprising:

11. 11. The method of claim 10, The method, wherein the message (700) directed to the NRF node (60) is an NFUpdate message.

12. 11. The method of claim 10, The method of claim 7, wherein the message (700) directed to the NRF node (60) further includes load information for a test or a change to the load information for a test.

13. 11. The method of claim 10, The method, wherein the message (704) from the NRF node (60) is an NFStatusNotify message.

14. 11. The method of claim 10, The method of claim 7, wherein the message from the NRF node includes load information about the test as a percentage of the total traffic load for the second NF node indicated as being under test.

15. 15. The method of claim 14, The NRF node (60) updates a profile of the second NF node (30) using the load information in the message (700) received from the second NF node (30).

16. A method performed by a Network Repository Function (NRF) node (60) in a fifth generation network, the method comprising: receiving a message (700) from a second NF node (30) of one or more second NF (Network Function) nodes (30, 50) including an indication that the second NF node (30) is being tested in the fifth generation network; sending a message (704) to a first network node (10, 20) including the indication that the second NF node (30) of the one or more second NF nodes (30, 50) is being tested in the fifth generation network; A method comprising:

17. 17. The method of claim 16, The method, wherein the message (700) from the second NF node (30) is an NFUpdate message.

18. 17. The method of claim 16, The method of claim 7, wherein the message (700) from the second NF node (30) further includes load information for a test or a change to the load information for a test.

19. 20. The method of claim 18, The method further comprises updating a profile of the second NF node (30) using the load information in the message (700) received from the second NF node (30).

20. 20. The method of claim 18, The method of claim 1, wherein the message from the NRF node includes the load information as a percentage of the total traffic load for the second NF node indicated as being under test.

21. 20. The method of claim 18, The NRF node (60) sends the message (704) to the first network node (10, 20) when a change in the load information is received from the second NF node (30).

22. 17. The method of claim 16, receiving a discovery request from the first network node (10, 20) to discover one or more network nodes capable of providing a service (40) requested by the first network node (10, 20); providing a test indication of a candidate second NF node (30, 50) to said first network node (10, 20); The method further comprises:

23. 23. The method of claim 22, The NRF node (60) further provides load information about the testing of the candidate second NF node (30, 50) to the first network node (10, 20).

24. a first network node (10, 20), A first network node comprising processing circuitry (12) configured to operate according to the method of any one of claims 1 to 9.

25. a second network node (30, 60), A second network node comprising processing circuitry (32) configured to operate in accordance with the method of any one of claims 10 to 15.

26. An NRF (Network Repository Function) node (60), An NRF node comprising processing circuitry (32) configured to operate in accordance with the method of any one of claims 16 to 23.

27. A computer program comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform the method of any one of claims 1 to 9.

28. A computer program comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform a method according to any one of claims 10 to 15.

29. 24. A computer program comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform a method according to any one of claims 16 to 23.

Images