Management of information transmission and reception

Abstract

A method for managing the transmission and reception of information between networks is provided. The method is performed by the first Network Repository Function (NRF) node. The method comprises providing information to a second NRF node (102). The visited network of the first Network Function (NF) node includes a second NRF node, and the home network of the first NF node includes a first NRF node. The information indicates whether the home network is capable of performing tasks delegated to it from the visited network.

Description

Technical Field

[0001] The present disclosure relates to methods for managing information transmission and reception between networks and nodes configured to operate in accordance with those methods.

Background Art

[0002] There are various techniques for processing requests for services in a network. Service requests are generally from a consumer of a service (service consumer) to a producer of the service (service producer). For example, a service request may be from a network function (NF) node of a service consumer to an NF node of a service producer. The NF node of the service consumer and the NF node of the service producer can communicate directly or indirectly. These are referred to as direct communication and indirect communication, respectively. In the case of indirect communication, the NF node of the service consumer and the NF node of the service producer may communicate via a service communication proxy (SCP) node.

[0003] A to D in FIG. 1 show different existing systems for processing service requests defined in Technical Specification (TS) 23.501 Version (V) 17.3.0 of the 3rd Generation Partnership Project (3GPP (registered trademark)). More specifically, A and B in FIG. 1 show systems using direct communication, and C and D in FIG. 1 show systems using indirect communication. It can be said that A, B, C, and D in FIG. 1 represent models A, B, C, and D, respectively, and these may be referred to herein.

[0004] In the systems shown in Figures 1A and 1B, service requests are sent directly from the service consumer's NF node to the service producer's NF node. Responses to service requests are 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 Figure 1B also includes a Network Repository Function (NRF) node. Therefore, in the system shown in Figure 1B, the service consumer's NF node can query the NRF node to find the appropriate NF node of the service producer to which it should send a service request. In response to such a query, the service consumer's NF node can receive NF profiles for one or more NF nodes of the service producer and, based on the received NF profiles, can select the NF node of the service producer to which it should send a service request. In the system shown in Figure 1A, the NRF node is not used; instead, the NF profiles of the service producer's NF nodes may be configured on the service consumer's NF node.

[0005] In the systems shown in Figures 1C and 1D, service requests are indirectly transmitted from the service consumer's NF node to the service producer's NF node via a Service Communication Proxy (SCP) node. Responses to service requests are indirectly transmitted from the service producer's NF node to the service consumer's NF node via an SCP node. Similarly, any subsequent service requests are indirectly transmitted from the service consumer's NF node to the service producer's NF node via an SCP node. The systems shown in Figures 1C and 1D also include an NRF node.

[0006] In the system shown in Figure 1C, a service consumer's NF node can query an NRF node to find the appropriate NF node of a service producer to which it should send a service request. In response to such a query, the service consumer's NF node can receive NF profiles for one or more service producer NF nodes and, based on the received NF profiles, can select the NF node of a service producer to which it should send a service request. In this case, the service request sent from the service consumer's NF node to the SCP node will include the address of the selected service producer NF node. The service consumer's NF node can then forward the service request without further discovery or selection. If the selected service producer NF node is inaccessible for any 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 the NF node of a service producer to which it should send a service request.

[0007] In the system shown in Figure 1D, the service consumer's NF node does not perform a discovery or selection process. Instead, the service consumer's NF node adds any necessary discovery and selection parameters (required to find the appropriate NF node of the service producer) to the service request sent via the SCP node. The SCP node uses the request address and discovery and selection parameters in the service request to route the service request to the appropriate NF node of the service producer. Thus, in the system shown in Figure 1D where indirect communication with delegated discovery is used, the service consumer's NF node sends a service request to the SCP node, providing the discovery and selection parameters necessary to discover and select the NF node of the service producer within the service request to the SCP node. The SCP node can perform discovery using the NRF node to discover the target NF node of the service producer to which the service request should be routed. The SCP node can discover the target NF node of the service producer in the manner described in 3GPP® TS 23.502 V17.3.0.

[0008] In the fifth-generation core (5GC), starting with Release 16, SCP nodes are included as a network element to enable indirect communication between service consumer NF nodes and service producer NF nodes. In other words, SCP nodes can be used in indirect routing scenarios, as previously described with reference to Figures 1C and 1D. [Overview of the project]

[0009] As previously stated, indirect communication from a first NF (e.g., an NF consumer, NFc) node to a second NF (e.g., an NF producer, NFp) node via a first SCP node is defined at Stage 2 level in 3GPP®. Indirect communication provides a means for the first NF node to delegate all or part of the logic required for the initial selection of the required second NF node and / or the re-selection of an alternative second NF node (e.g., in the event of failure of the initially selected second NF node) to the SCP.

[0010] However, while delegating (re)selection logic has several advantages, Stage 2 has the problem that it does not consider any requirements for indirect communication across public land mobile networks (PLMNs) (e.g., the model shown in Figure 1C). Separately, generally, delegating the (re)selection logic of a NF from a visited network (e.g., a visited public land mobile network, vPLMN) to a home network (e.g., a home public land mobile network, hPLMN) means that the information necessary for the (re)selection of the NF is provided from the visited network to the home network. However, the home network may not be able to support the requested logic delegation, which can lead to errors.

[0011] The purpose of this disclosure is to avoid or eliminate at least some of the aforementioned shortcomings associated with existing technologies.

[0012] Accordingly, according to one aspect of this disclosure, a first method is provided for managing the transmission and reception of information between networks. The first method is performed by a first network repository function (NRF) node. The first method includes providing information to a second NRF node. The visited network of the first network function (NF) node includes the second NRF node, and the home network of the first NF node includes the first NRF node. The information indicates whether the home network is capable of performing a task delegated to it from the visited network.

[0013] According to another aspect of this disclosure, a second method is provided for managing the transmission and reception of information between networks. The second method is performed by a first NRF node. The second method includes retrieving information from the memory of the first NRF node or from a second network node. The second network node is either a second NF node or a first security edge protected proxy (SEPP) node. The home network of the first NF node comprises the second network node and the first NRF node. The information indicates whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node.

[0014] In another aspect of this disclosure, a first NRF node is also provided, comprising a processing circuit configured to operate according to one or both of the first and second methods. In some embodiments, the first NRF node may include at least one memory for storing instructions that, when executed by the processing circuit, cause the first NRF node to operate according to one or both of the first and second methods.

[0015] According to another aspect of this disclosure, a third method is provided for managing the transmission and reception of information between networks. The third method is performed by a second NRF node. The third method includes obtaining information from a first NRF node. The home network of the first NF node comprises the first NRF node, and the visited network of the first NF node comprises the second NRF node. The information indicates whether the home network is capable of performing a task delegated to the home network from the visited network.

[0016] According to another aspect of this disclosure, a fourth method is provided for managing the transmission and reception of information between networks. The fourth method is performed by a second NRF node. The fourth method includes providing information to a first network node, which is a first NF node or a first service communications proxy (SCP) node configured to act as an SCP between the first NF node and the second NRF node. The visited network of the first NF node comprises a second NRF node and the first network node. The information indicates whether the home network of the first NF node is capable of performing tasks delegated from the visited network to the home network.

[0017] In another aspect of this disclosure, a second NRF node is also provided, comprising a processing circuit configured to operate according to one or both of the third and fourth methods. In some embodiments, the second NRF node may include at least one memory for storing instructions that, when executed by the processing circuit, cause the second NRF node to operate according to one or both of the third and fourth methods.

[0018] According to another aspect of this disclosure, a fifth method is provided for managing the transmission and reception of information between networks. The fifth method is performed by a first network node. The fifth method includes obtaining information from a second NRF node. The first network node is a first NF node, or a first SCP node configured to act as an SCP between the first NF node and the second NRF node. The visited network of the first NF node comprises a second NRF node and the first network node. The information indicates whether the home network of the first NF node is capable of performing a task delegated from the visited network to the home network.

[0019] Another aspect of this disclosure also provides a first network node comprising a processing circuit configured to operate according to the fifth method. In some embodiments, the first network node may include at least one memory for storing instructions that, when executed by the processing circuit, cause the first network node to operate according to the fifth method.

[0020] According to another aspect of this disclosure, a sixth method is provided for managing the transmission and reception of information between networks. The sixth method is performed by a second network node. The sixth method includes providing information to a first NRF node. The second network node is a second NF node or a first security edge protected proxy (SEPP) node. The home network of the first NF node comprises the second network node and the first NRF node. The information indicates whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node.

[0021] Another aspect of this disclosure also provides a second network node comprising a processing circuit configured to operate according to the sixth method. In some embodiments, the second network node may include at least one memory for storing instructions that, when executed by the processing circuit, cause the second network node to operate according to the sixth method.

[0022] According to another aspect of this disclosure, a method is provided that is performed by the system. This method includes any two or more of the first, second, third, fourth, fifth, and sixth methods.

[0023] According to another aspect of this disclosure, a system is provided comprising any two or more of the first NRF node, the second NRF node, the first network node, and the second network node described above.

[0024] According to another aspect of this disclosure, a computer program is provided which, when executed by a processing circuit, provides instructions that cause the processing circuit to perform one or more of the first, second, third, fourth, fifth, and sixth methods.

[0025] Another aspect of this disclosure provides a computer program product embodied on a non-temporary machine-readable medium, which is executable by a processing circuit and comprises instructions causing the processing circuit to perform one or more of the first, second, third, fourth, fifth, and sixth methods.

[0026] Thus, in the described embodiments, an advantageous information sharing is adopted that provides the nodes of the network with the knowledge necessary to avoid unnecessary signaling and processing. The nodes of the network are provided with the knowledge by the home network as to whether the home network is capable of performing the tasks entrusted to it. More specifically, information sharing enables the first network node to be notified of the capabilities of the home network for performing tasks such as (re)selection of the NF. This information can be used by the visited network to delegate tasks in a way that avoids unnecessary signaling and processing. For example, the visited network can use this information to avoid delegating tasks to the home network when the home network is unable to process the tasks, or instead, can delegate the tasks to the SEPP node of the visited network or the SCP node at the border (or edge) of the visited network.

[0027] Thus, an improved technique for managing the transmission and reception of information between networks is provided.

Brief Description of the Drawings

[0028] To better understand the present technology and to show how it can be implemented, by way of example, the following accompanying drawings are referred to. [Figure 1] A to D are block diagrams showing different existing systems. [Figure 2] It is a block diagram showing a first NRF node according to an embodiment. [Figure 3] It is a block diagram showing a method executed by the first NRF node according to an embodiment. [Figure 4] It is a block diagram showing a method executed by the first NRF node according to an embodiment. [Figure 5] It is a block diagram showing a second NRF node according to an embodiment. [Figure 6]This is a block diagram showing a method performed by a second NRF node according to one embodiment. [Figure 7] This is a block diagram showing a method performed by a second NRF node according to one embodiment. [Figure 8] A block diagram showing a first network node according to one embodiment. [Figure 9] This is a block diagram showing a method performed by a first network node according to one embodiment. [Figure 10] A block diagram showing a second network node according to one embodiment. [Figure 11] This is a block diagram showing a method performed by a second network node according to one embodiment. [Figure 12] Block diagram showing an example system. [Figure 13A] This is a signaling diagram illustrating the transmission and reception of signals in an exemplary system. [Figure 13B] This is a signaling diagram illustrating the transmission and reception of signals in an exemplary system. [Figure 14A] This is a signaling diagram illustrating the transmission and reception of signals in an exemplary system. [Figure 14B] This is a signaling diagram illustrating the transmission and reception of signals in an exemplary system. [Figure 15] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 16] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 17] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 18] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 19] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 20]This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 21] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 22] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 23] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Figure 24] This is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. [Modes for carrying out the invention]

[0029] Some embodiments intended herein will be described in more detail with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited only to the embodiments described herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0030] This specification describes techniques for handling service requests in a network. A service request may also be called a request to a service. Generally, a service is software intended to be managed on behalf of a user. In this specification, a service can be any type of service, such as a communication service (e.g., a notification service or a callback service), a context management service (e.g., a user device context management (UECM) service), a data management (DM) service, or any other type of service. In this specification, a reference to providing a service may mean, for example, running or operating a service.

[0031] This specification also describes techniques for handling notification requests in a network. Notification requests may also be called requests for notifications. Generally, users can subscribe to receive notifications. In this specification, notifications can be any type of notification, such as event notifications (event occurrence notifications to report an event), update notifications (e.g., to report an update), monitoring cancellation notifications, integrated data repository (UDR)-driven data recovery notifications, N1 notifications, or any other type of notification. In this specification, reference to providing notifications may refer, for example, to sending notifications.

[0032] In this specification, the term “start” may mean, for example, to cause or establish. Therefore, any reference to a node “starting to transmit” is understood to mean that the node (e.g., the node’s processing circuitry) may be configured to transmit on its own (e.g., via the node’s communication interface) or to cause another node to transmit.

[0033] The techniques described herein may be used with respect to any communications or telecommunications network, such as any network like a cellular network. The network may be a fifth-generation (5G) network or any other generation of network. In some embodiments, the network may be a core network or a radio access network (RAN). The techniques refer to home networks and visited networks. The home network referred to herein may be, for example, a home public land mobile network (PLMN), i.e., an h-PLMN. Similarly, the visited network referred to herein may be, for example, a visited PLMN, i.e., a v-PLMN.

[0034] The technology described herein is implemented by a first network repository function (NRF) node, a second NRF node, a first network node, and a second network node. The first network node may be, for example, a first network function (NF) node or a first service communication proxy (SCP) node. The first SCP node is a node configured to act as an SCP between the first NF node and the second NRF node. The second network node may be, for example, a second NF node or a first security edge protected proxy (SEPP) node.

[0035] An NF is a network processing function adopted by or defined by the Third Generation Partnership Project (3GPP®), having defined functional behavior and 3GPP®-defined 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 an appropriate platform (e.g., cloud infrastructure). In this specification, the term “node” in relation to “NF node” is understood to cover each of these scenarios. In this specification, a reference to an NF node may refer to, for example, an instance of an NF node, and similarly, a reference to multiple NF nodes may refer to instances of NF nodes (e.g., functionally equivalent). Thus, the terms “NF” and “NF instance” may be used interchangeably.

[0036] Figure 2 shows a first NRF node 50 in the home network of a first NF node according to one embodiment. The first NRF node 50 is for managing the transmission and reception of information between networks. In some embodiments, the first NRF node 50 referred to herein may refer to a device that is configured, positioned, and / or operable in such a way that it can communicate directly or indirectly with a second NRF node, a second network node, and / or other nodes or devices referred to herein in order to enable and / or perform the functions described herein. In some embodiments, the first NRF node 50 referred to herein may be, for example, a physical node (e.g., a physical machine or server) or a virtual node (e.g., a virtual machine, VM).

[0037] As shown in Figure 2, the first NRF node 50 comprises a processing circuit (or logic) 52. The processing circuit 52 controls the operation of the first NRF node 50 and can implement the methods described herein with respect to the first NRF node 50. The processing circuit 52 may be configured or programmed to control the first NRF node 50 in the manner described herein. The processing circuit 52 may comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multicore processors, and / or one or more modules. In a particular implementation, each of the one or more hardware components may be configured to perform, or be intended to perform, individual or multiple steps of the methods described herein with respect to the first NRF node 50. In some embodiments, the processing circuit 52 may be configured to run software to implement the methods described herein with respect to the first NRF node 50. The software may be containerized according to some embodiments. Thus, in some embodiments, the processing circuit 52 may be configured to run a container to implement the methods described herein with respect to the first NRF node 50.

[0038] In short, the processing circuit 52 of the first NRF node 50 is configured to provide information to the second NRF node. The visited network of the first NF node includes the second NRF node, and the home network of the first NF node includes the first NRF node 50. This information indicates whether the home network is capable of performing the task delegated to it from the visited network.

[0039] Alternatively, or in addition, the processing circuit 52 of the first NRF node 50 is configured to retrieve information from the memory of the first NRF node 50 or from a second network node. The second network node is either a second NF node or a first security edge protection proxy (SEPP) node. The home network of the first NF node comprises the second network node and the first NRF node 50. The information indicates whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node.

[0040] As shown in Figure 2, in some embodiments, the first NRF node 50 may optionally include memory 54. The memory 54 of the first NRF node 50 may include volatile memory or non-volatile memory. In some embodiments, the memory 54 of the first NRF node 50 may include non-temporary media. Examples of the memory 54 of the first NRF node 50 include, but are not limited to, random access memory (RAM), read-only memory (ROM), mass storage media such as hard disks, removable storage media such as compact discs (CDs) or digital general-purpose discs (DVDs), and / or any other arbitrary memory.

[0041] The processing circuit 52 of the first NRF node 50 may be communicatively coupled (e.g., connected) to the memory 54 of the first NRF node 50. In some embodiments, the memory 54 of the first NRF node 50 may be for storing program code or instructions that, when executed by the processing circuit 52 of the first NRF node 50, cause the first NRF node 50 to operate in the manner relating to the first NRF node 50 as described herein. For example, in some embodiments, the memory 54 of the first NRF node 50 may be configured to store program code or instructions that, when executed by the processing circuit 52 of the first NRF node 50, cause the first NRF node 50 to operate in the manner relating to the first NRF node 50 as described herein. Alternatively, or in addition, the memory 54 of the first NRF node 50 may be configured to store any information, data, messages, requests, responses, displays, notices, signals, or the like as described herein. The processing circuit 52 of the first NRF node 50 may be configured to control the memory 54 of the first NRF node 50 to store any of the information, data, messages, requests, responses, indications, notifications, signals, or the like as described herein.

[0042] In some embodiments, as shown in Figure 2, the first NRF node 50 may optionally include a communication interface 56. The communication interface 56 of the first NRF node 50 may be communicatively coupled (e.g., connected) to the processing circuitry 52 of the first NRF node 50 and / or the memory 54 of the first NRF node 50. The communication interface 56 of the first NRF node 50 may be operable to enable the processing circuitry 52 of the first NRF node 50 to communicate with the memory 54 of the first NRF node 50, and vice versa. Similarly, the communication interface 56 of the first NRF node 50 may be operable to enable the processing circuitry 52 of the first NRF node 50 to communicate with any one or more nodes (e.g., a second NRF node as referred herein, and / or a second network node as referred herein) and / or any other node. The communication interface 56 of the first NRF node 50 may be configured to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. In some embodiments, the processing circuit 52 of the first NRF node 50 may be configured to control the communication interface 56 of the first NRF node 50 to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0043] Although the first NRF node 50 is shown in Figure 2 as comprising a single memory 54, it will be understood that the first NRF node 50 may comprise at least one memory (i.e., one or more memories) 54 operating in the manner described herein. Similarly, although the first NRF node 50 is shown in Figure 2 as comprising a single communication interface 56, it will be understood that the first NRF node 50 may comprise at least one communication interface (i.e., one or more communication interfaces) 56 operating in the manner described herein. Furthermore, Figure 2 shows only the components necessary to illustrate an embodiment of the first NRF node 50, and it will be understood that in actual implementations, the first NRF node 50 may comprise components in addition to or alternative to those shown.

[0044] Figure 3 shows a first method, according to one embodiment, performed by a first NRF node 50 of a home network of a first NF node. The first method is for managing the transmission and reception of information between networks. The first NRF node 50, previously described with reference to Figure 2, may be configured to operate according to the first method of Figure 3. The first method may, according to some embodiments, be performed by or under the control of a processing circuit 52 of the first NRF node 50.

[0045] Referring to Figure 3, as shown in block 102, information is provided to the second NRF node. The visited network of the first NF node includes the second NRF node, and the home network of the first NF node includes the first NRF node 50. This information indicates whether the home network is capable of performing the task delegated to it from the visited network.

[0046] In some embodiments, information may be provided in response to receiving a first message from a second NRF node. In some embodiments, the first message may comprise a first request, which is a request for information, and / or a second request, which is a request to discover one or more second NF nodes in the home network. In some embodiments, the first message may comprise an identifier (e.g., plmn-id) that identifies the visited network. In some embodiments, providing information to a second NRF node may include initiating the transmission of a second message to the second NRF node, where the second message comprises information. In some embodiments, the information may be provided in a profile of the second NF node in the home network or in a profile of the first SEPP node in the home network.

[0047] In some embodiments, the first method may include storing information (for example, in memory 54) at the first NRF node 50.

[0048] In some embodiments, the first NF node may be a consumer NF node, or the first NF node may be a producer NF node. In some embodiments, the task may be to select one or more second NF nodes of the home network. In some embodiments, the first NF node may be a consumer NF node, and the task may be to select one or more second NF nodes of the producer to provide a service requested by the first NF node. In other embodiments, the first NF node may be a producer NF node, and the task may be to select one or more second NF nodes of the consumer to provide a notification requested by the first NF node.

[0049] Figure 4 shows a second method, according to one embodiment, performed by the first NRF node 50 of the home network of the first NF node. The second method is for managing the transmission and reception of information between networks. The first NRF node 50, as previously described with reference to Figure 2, may be configured to operate according to the second method of Figure 4. The second method may, according to some embodiments, be performed by or under the control of the processing circuit 52 of the first NRF node 50.

[0050] Referring to Figure 4, as shown in block 104, the information is obtained from the memory of the first NRF node 50 or from the second network node. The second network node is either the second NF node or the first SEPP node. The home network of the first NF comprises the second network node and the first NRF node 50. This information indicates whether the home network is capable of performing tasks delegated to it from the visited network of the first NF node.

[0051] In some embodiments, acquiring information may include receiving information. In some embodiments, the information may be acquired in the profile of a second network node. In some embodiments, the information may be acquired from the second network node along with a request to register the profile with the first NRF node 50.

[0052] In some embodiments, the second method may include storing the information (for example, in memory 54) at the first NRF node 50.

[0053] Figure 5 shows a second NRF node 30 in the network visited by the first NF node, according to one embodiment. The second NRF node 30 is for managing the transmission and reception of information between networks. In some embodiments, the second NRF node 30 referred to herein may refer to a device that is configured, positioned, and / or operable in such a way that it can communicate directly or indirectly with the first NRF node 50 referred to herein, the first network node referred to herein, and / or other nodes or devices in order to enable and / or perform the functions described herein. In some embodiments, the second NRF node 30 referred to herein may be, for example, a physical node (e.g., a physical machine or server) or a virtual node (e.g., a virtual machine, VM).

[0054] As shown in Figure 5, the second NRF node 30 comprises a processing circuit (or logic) 32. The processing circuit 32 can control the operation of the second NRF node 30 and implement the methods described herein with respect to the second NRF node 30. The processing circuit 32 may be configured or programmed to control the second NRF node 30 in the manner described herein. The processing circuit 32 may comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multicore processors, and / or one or more modules. In a particular embodiment, each of the one or more hardware components may be configured to perform, or be for performing, individual or multiple steps of the methods described herein with respect to the second NRF node 30. In some embodiments, the processing circuit 32 may be configured to run software to perform the methods described herein with respect to the second NRF node 30. The software may be containerized according to some embodiments. Thus, in some embodiments, the processing circuit 32 may be configured to run a container to perform the methods described herein with respect to the second NRF node 30.

[0055] In short, the processing circuit 32 of the second NRF node 30 is configured to acquire information from the first NRF node 50. The home network of the first NF node includes the first NRF node 50, and the visited network of the first NF node includes the second NRF node 30. This information indicates whether the home network is capable of performing tasks delegated to it from the visited network.

[0056] Alternatively, or in addition, the processing circuit 32 of the second NRF node 30 is configured to provide information to the first network node. The first network node is either the first NF node, or the first SCP node configured to act as an SCP between the first NF node and the second NRF node 30. The visited network of the first NF node comprises the second NRF node 30 and the first network node. The information indicates whether the home network of the first NF node is capable of performing tasks delegated from the visited network to the home network.

[0057] As shown in Figure 5, in some embodiments, the second NRF node 30 may optionally include memory 34. The memory 34 of the second NRF node 30 may include volatile memory or non-volatile memory. In some embodiments, the memory 34 of the second NRF node 30 may include non-temporary media. Examples of the memory 34 of the second NRF node 30 include, but are not limited to, random access memory (RAM), read-only memory (ROM), mass storage media such as hard disks, removable storage media such as compact discs (CDs) or digital general-purpose discs (DVDs), and / or any other arbitrary memory.

[0058] The processing circuit 32 of the second NRF node 30 may be communicatively coupled (e.g., connected) to the memory 34 of the second NRF node 30. In some embodiments, the memory 34 of the second NRF node 30 may be for storing program code or instructions that, when executed by the processing circuit 32 of the second NRF node 30, cause the second NRF node 30 to operate in the manner relating to the second NRF node 30 as described herein. For example, in some embodiments, the memory 34 of the second NRF node 30 may be configured to store program code or instructions that, when executed by the processing circuit 32 of the second NRF node 30, cause the second NRF node 30 to operate in the manner relating to the second NRF node 30 as described herein. Alternatively, or in addition, the memory 34 of the second NRF node 30 may be configured to store any information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. The processing circuit 32 of the second NRF node 30 may be configured to control the memory 34 of the second NRF node 30 to store any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0059] In some embodiments, as shown in Figure 5, the second NRF node 30 may optionally include a communication interface 36. The communication interface 36 of the second NRF node 30 may be communicatively coupled (e.g., connected) to the processing circuit 32 of the second NRF node 30 and / or the memory 34 of the second NRF node 30. The communication interface 36 of the second NRF node 30 may be operable to enable the processing circuit 32 of the second NRF node 30 to communicate with the memory 34 of the second NRF node 30, and vice versa. Similarly, the communication interface 36 of the second NRF node 30 may be operable to enable the processing circuit 32 of the second NRF node 30 to communicate with any one or more nodes (e.g., the first NRF node 50 as referred herein, and / or the first network node as referred herein) and / or any other arbitrary nodes. The communication interface 36 of the second NRF node 30 may be configured to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. In some embodiments, the processing circuit 32 of the second NRF node 30 may be configured to control the communication interface 36 of the second NRF node 30 to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0060] Although the second NRF node 30 is shown in Figure 5 as comprising a single memory 34, it will be understood that the second NRF node 30 may comprise at least one memory (i.e., one or more memories) 34 operating in the manner described herein. Similarly, although the second NRF node 30 is shown in Figure 5 as comprising a single communication interface 36, it will be understood that the second NRF node 30 may comprise at least one communication interface (i.e., one or more communication interfaces) 36 operating in the manner described herein. Furthermore, Figure 5 shows only the components necessary to illustrate an embodiment of the second NRF node 30, and it will be understood that in actual implementations, the second NRF node 30 may comprise components in addition to or alternative to those shown.

[0061] Figure 6 shows a third method, according to one embodiment, performed by a second NRF node 30 in the network visited by the first NF node. The third method is for managing the transmission and reception of information between networks. The second NRF node 30, as previously described with reference to Figure 5, may be configured to operate according to the third method of Figure 6. The third method may, according to some embodiments, be performed by or under the control of the processing circuit 32 of the second NRF node 30.

[0062] Referring to Figure 6, as shown in block 106, the information is obtained from the first NRF node 50. The home network of the first NF node includes the first NRF node 50, and the visited network of the first NF node includes the second NRF node 30. This information indicates whether the home network is capable of performing tasks delegated to it from the visited network.

[0063] In some embodiments, information may be obtained in response to sending a first message to the first NRF node 50. In some embodiments, the first message may comprise a first request, which is a request for information, and / or a second request, which is a request to discover one or more second NF nodes in the home network. In some embodiments, the first message may comprise an identifier that identifies the visited network.

[0064] In some embodiments, obtaining information from the first NRF node 50 may include receiving a second message from the first NRF node 50, where the second message contains information. In some embodiments, the information may be obtained in the profile of the second NF node of the home network or in the profile of the first SEPP node of the home network.

[0065] Figure 7 shows a fourth method, according to one embodiment, performed by a second NRF node 30 in the network visited by the first NF node. The fourth method is for managing the transmission and reception of information between networks. The second NRF node 30, as previously described with reference to Figure 5, may be configured to operate according to the fourth method in Figure 7. The fourth method may, according to some embodiments, be performed by or under the control of the processing circuit 32 of the second NRF node 30.

[0066] Referring to Figure 7, as shown in block 108, information is provided to the first network node. The first network node is either the first NF node or the first SCP node configured to act as an SCP between the first NF node and the second NRF node 30. The visited network of the first NF node comprises the second NRF node 30 and the first network node. This information indicates whether the home network of the first NF node is capable of performing the task delegated from the visited network to the home network.

[0067] In some embodiments, the information may be provided in response to receiving a second message from the first NRF node 50, where the second message includes the information. In some embodiments, providing the information to the first network node may include initiating the transmission of a third message to the first network node, where the third message includes the information. In some embodiments, the information may be provided in the profile of the second NF node of the home network or in the profile of the first SEPP node of the home network.

[0068] Figure 8 shows the first network nodes 10 and 20 of the destination network of the first NF node according to one embodiment. The first network nodes 10 and 20 are for managing the transmission and reception of information between networks.

[0069] As previously stated, in some embodiments, the first network nodes 10, 20 may be the first NF node 10 or the first SCP node 20. The first SCP node 20 may be a node configured to act as an SCP between the first NF node 10 and the second NRF node 30. In some embodiments, the first NF node 10 as referred herein may be a wireless device, e.g., a user device (UE). In some embodiments, the first network nodes 10, 20 as referred herein may refer to equipment that is configured, positioned, and / or operable in such a way that it can communicate directly or indirectly with the second NRF node 30, the first NF node 10 (in one embodiment, the first network node is the first SCP node 20), the first SCP node 20 (in one embodiment, the first network node is the first NF node 10), and / or other nodes or equipment, in order to enable and / or perform the functions described herein. In some embodiments, the first network nodes 10, 20 referred to herein may be, for example, physical nodes (e.g., physical machines or servers) or virtual nodes (e.g., virtual machines, VMs).

[0070] As shown in Figure 8, the first network nodes 10, 20 include a processing circuit (or logic) 12. The processing circuit 12 can control the operation of the first network nodes 10, 20 and implement the methods described herein with respect to the first network nodes 10, 20. The processing circuit 12 may be configured or programmed to control the first network nodes 10, 20 in the manner described herein. The processing circuit 12 may include one or more hardware components, such as one or more processors, one or more processing units, one or more multicore processors, and / or one or more modules. In a particular implementation, each of the one or more hardware components may be configured to perform, or be intended to perform, individual or multiple steps of the methods described herein with respect to the first network nodes 10, 20. In some embodiments, the processing circuit 12 may be configured to run software to perform the methods described herein with respect to the first network nodes 10, 20. The software may be containerized according to some embodiments. Therefore, in some embodiments, the processing circuit 12 may be configured to run a container to perform the methods described herein with respect to the first network nodes 10, 20.

[0071] In short, the processing circuits 12 of the first network nodes 10 and 20 are configured to acquire information from the second NRF node 30. The first network nodes 10 and 20 are either the first NF node 10 or the first SCP node 20 configured to act as an SCP between the first NF node 10 and the second NRF node 30. The visited network of the first NF node 10 comprises the second NRF node 30 and the first network nodes 10 and 20. This information indicates whether the home network of the first NF node 10 is capable of performing tasks delegated from the visited network to the home network.

[0072] As shown in Figure 8, in some embodiments, the first network nodes 10, 20 may optionally include memory 14. The memory 14 of the first network nodes 10, 20 may include volatile memory or non-volatile memory. In some embodiments, the memory 14 of the first network nodes 10, 20 may include non-temporary media. Examples of the memory 14 of the first network nodes 10, 20 include, but are not limited to, random access memory (RAM), read-only memory (ROM), mass storage media such as hard disks, removable storage media such as compact discs (CDs) or digital general-purpose discs (DVDs), and / or any other arbitrary memory.

[0073] The processing circuits 12 of the first network nodes 10, 20 may be communicatively coupled (e.g., connected) to the memory 14 of the first network nodes 10, 20. In some embodiments, the memory 14 of the first network nodes 10, 20 may be for storing program code or instructions that, when executed by the processing circuits 12 of the first network nodes 10, 20, cause the first network nodes 10, 20 to operate in the manner relating to the first network nodes 10, 20 as described herein. For example, in some embodiments, the memory 14 of the first network nodes 10, 20 may be configured to store program code or instructions that, when executed by the processing circuits 12 of the first network nodes 10, 20, cause the first network nodes 10, 20 to operate according to the method relating to the first network nodes 10, 20 as described herein. Alternatively, or in addition, the memory 14 of the first network nodes 10, 20 may be configured to store any information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. The processing circuit 12 of the first network nodes 10, 20 may be configured to control the memory 14 of the first network nodes 10, 20 to store any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0074] In some embodiments, as shown in Figure 8, the first network nodes 10, 20 may optionally be provided with a communication interface 16. The communication interface 16 of the first network nodes 10, 20 may be communicatively coupled (e.g., connected) to the processing circuits 12 and / or the memory 14 of the first network nodes 10, 20. The communication interface 16 of the first network nodes 10, 20 may be operable to enable the processing circuits 12 of the first network nodes 10, 20 to communicate with the memory 14 of the first network nodes 10, 20, or vice versa. Similarly, the communication interface 16 of the first network nodes 10, 20 may be operable to enable the processing circuit 12 of the first network nodes 10, 20 to communicate with any one or more nodes (e.g., a second NRF node as referred herein, a first NF node 10 as referred herein in one embodiment where the first network node is a first SCP node 20, and / or a first SCP node 20 as referred herein in one embodiment where the first network node is a first NF node 10) and / or any other node. The communication interface 16 of the first network nodes 10, 20 may be configured to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. In some embodiments, the processing circuit 12 of the first network nodes 10, 20 may be configured to control the communication interface 16 of the first network nodes 10, 20 to transmit and / or receive any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0075] Although the first network nodes 10 and 20 are shown in Figure 8 as having a single memory 14, it will be understood that the first network nodes 10 and 20 may have at least one memory (i.e., one or more memories) 14 operating in the manner described herein. Similarly, although the first network nodes 10 and 20 are shown in Figure 8 as having a single communication interface 16, it will be understood that the first network nodes 10 and 20 may have at least one communication interface (i.e., one or more communication interfaces) 16 operating in the manner described herein. Furthermore, Figure 8 shows only the components necessary to illustrate embodiments of the first network nodes 10 and 20, and it will be understood that in actual implementations, the first network nodes 10 and 20 may have components in addition to or alternative to those shown.

[0076] Figure 9 shows a fifth method, according to one embodiment, performed by the first network nodes 10 and 20. The fifth method is for managing the transmission and reception of information between networks. The first network nodes 10 and 20, as previously described with reference to Figure 8, can be configured to operate according to the fifth method of Figure 9. The fifth method can be performed by or under the control of the processing circuit 12 of the first network nodes 10 and 20, according to some embodiments.

[0077] Referring to Figure 9, as shown in block 110, the information is obtained from the second NRF node 30. The first network nodes 10, 20 are the first NF node 10, or the first SCP node 20 configured to act as an SCP between the first NF node 10 and the second NRF node 30. The visited network of the first NF node 10 comprises the second NRF node 30 and the first network nodes 10, 20. This information indicates whether the home network of the first NF node 10 is capable of performing tasks delegated from the visited network to the home network.

[0078] In some embodiments, the information may be obtained in response to sending a third message to a second NRF node 30. In some embodiments, the third message may comprise a first request, which is a request for information, and / or a second request, which is a request to discover one or more second NF nodes in the home network. In some embodiments, the third message may comprise an identifier that identifies the visited network.

[0079] In some embodiments, obtaining information from the second NRF node 30 may include receiving a third message from the second NRF node 30, where the third message contains information. In some embodiments, the information may be obtained in the profile of the second NF node of the home network or in the profile of the first SEPP node of the home network.

[0080] In some embodiments, the fifth method may include determining, based on the information, whether the home network is capable of performing the task.

[0081] In some embodiments, if the home network is unable to perform the task, the fifth method may include performing the task or delegating the task to a second SEPP node or a second SCP node in the visited network. The second SCP node may be configured to act as an SCP between the first network nodes 10, 20 and the second SEPP node. In some embodiments, the second SCP node may be the SCP node of the visited network closest to the second SEPP node.

[0082] Figure 10 shows second network nodes 42, 70, and 80 of the home network of the first NF node 10 according to one embodiment. The second network nodes 42, 70, and 80 are for managing the transmission and reception of information between networks. In some embodiments, the second network nodes 42, 70, and 80 referred to herein may refer to equipment that is configured, positioned, and / or operable, and capable of communicating directly or indirectly with the first NRF node 50, the second network nodes, the second SCP nodes, any second NF nodes, and / or other nodes or equipment referred to herein, in order to enable and / or perform the functions described herein. In some embodiments, the second network nodes 42, 70, and 80 referred to herein may be, for example, physical nodes (e.g., physical machines or servers) or virtual nodes (e.g., virtual machines, VMs).

[0083] As shown in Figure 10, the second network nodes 42, 70, and 80 each include a processing circuit (or logic) 72. The processing circuit 72 can control the operation of the second network nodes 42, 70, and 80 and implement the methods described herein with respect to the second network nodes 42, 70, and 80. The processing circuit 72 may be configured or programmed to control the second network nodes 42, 70, and 80 in the manner described herein. The processing circuit 72 may include one or more hardware components, such as one or more processors, one or more processing units, one or more multicore processors, and / or one or more modules. In a particular implementation, each of the one or more hardware components may be configured to perform, or be intended to perform, individual or multiple steps of the methods described herein with respect to the second network nodes 42, 70, and 80. In some embodiments, the processing circuit 72 may be configured to run software to perform the methods described herein with respect to the second network nodes 42, 70, and 80. The software may be containerized according to some embodiments. Therefore, in some embodiments, the processing circuit 72 may be configured to run a container to perform the methods described herein with respect to the second network nodes 42, 70, and 80.

[0084] In short, the processing circuit 72 of the second network nodes 42, 70, and 80 is configured to provide information to the first NRF node 50. The second network node is either the second NF nodes 70, 80, or the first SEPP node 42, and the home network of the first NF node 10 comprises the second network nodes 42, 70, and 80 and the first NRF node 50. This information indicates whether the home network is capable of performing tasks delegated to it from the visited network of the first NF node.

[0085] Alternatively, or in addition, the processing circuit 72 of the second network nodes 42, 70, and 80 is configured to initiate the transmission of a request to the second network node of the home network in response to the receipt of the request. The request is received with a dummy address of the second NF node, which signals that the request should be sent to the second network node without the address of the second NF node. The request is sent to the second network node without an address.

[0086] As shown in Figure 10, in some embodiments, the second network nodes 42, 70, and 80 may optionally include memory 74. The memory 74 of the second network nodes 42, 70, and 80 may comprise volatile memory or non-volatile memory. In some embodiments, the memory 74 of the second network nodes 42, 70, and 80 may comprise non-temporary media. Examples of the memory 74 of the second network nodes 42, 70, and 80 include, but are not limited to, random access memory (RAM), read-only memory (ROM), mass storage media such as hard disks, removable storage media such as compact discs (CDs) or digital general-purpose discs (DVDs), and / or any other arbitrary memory.

[0087] The processing circuit 72 of the second network nodes 42, 70, 80 may be communicatively coupled (e.g., connected) to the memory 74 of the second network nodes 42, 70, 80. In some embodiments, the memory 74 of the second network nodes 42, 70, 80 may be for storing program code or instructions that, when executed by the processing circuit 72 of the second network nodes 42, 70, 80, cause the second network nodes 42, 70, 80 to operate in the manner relating to the second network nodes 42, 70, 80 as described herein. For example, in some embodiments, the memory 74 of the second network nodes 42, 70, 80 may be configured to store program code or instructions that, when executed by the processing circuit 72 of the second network nodes 42, 70, 80, cause the second network nodes 42, 70, 80 to operate according to the method relating to the second network nodes 42, 70, 80 as described herein. Alternatively, or in addition, the memory 74 of the second network nodes 42, 70, 80 may be configured to store any information, data, messages, requests, responses, indications, notices, signals, or the like as described herein. The processing circuit 72 of the second network nodes 42, 70, 80 may be configured to control the memory 74 of the second network nodes 42, 70, 80 to store any of the information, data, messages, requests, responses, indications, notices, signals, or the like as described herein.

[0088] In some embodiments, as shown in Figure 10, the second network nodes 42, 70, 80 may optionally be provided with a communication interface 76. The communication interface 76 of the second network nodes 42, 70, 80 may be communicatively coupled (e.g., connected) to the processing circuits 72 of the second network nodes 42, 70, 80 and / or the memory 74 of the second network nodes 42, 70, 80. The communication interface 76 of the second network nodes 42, 70, 80 may be operable to enable the processing circuits 72 of the second network nodes 42, 70, 80 to communicate with the memory 74 of the second network nodes 42, 70, 80 and vice versa. Similarly, the communication interface 76 of the second network nodes 42, 70, 80 may be operable to enable the processing circuits 72 of the second network nodes 42, 70, 80 to communicate with any one or more nodes (e.g., the first NRF node 50 as referred herein) and / or any other arbitrary nodes. The communication interface 76 of the second network nodes 42, 70, 80 may be configured to transmit and / or receive any of the information, data, messages, requests, responses, displays, notifications, signals, or the like as described herein. In some embodiments, the processing circuit 72 of the second network nodes 42, 70, 80 may be configured to control the communication interface 76 of the second network nodes 42, 70, 80 to transmit and / or receive any of the information, data, messages, requests, responses, displays, notifications, signals, or the like as described herein.

[0089] Although the second network nodes 42, 70, and 80 are shown in Figure 10 as having a single memory 74, it will be understood that the second network nodes 42, 70, and 80 may have at least one memory (i.e., one or more memories) 74 operating in the manner described herein. Similarly, although the second network nodes 42, 70, and 80 are shown in Figure 10 as having a single communication interface 76, it will be understood that the second network nodes 42, 70, and 80 may have at least one communication interface (i.e., one or more communication interfaces) 76 operating in the manner described herein. Furthermore, Figure 10 shows only the components necessary to illustrate embodiments of the second network nodes 42, 70, and 80, and it will be understood that in actual implementations, the second network nodes 42, 70, and 80 may have components in addition to or alternative to those shown.

[0090] Figure 11 shows a sixth method, according to one embodiment, performed by the second network nodes 42, 70, and 80 of the home network of the first NF node 10. The sixth method is for managing the transmission and reception of information between networks. The second network nodes 42, 70, and 80, as previously described with reference to Figure 10, can be configured to operate according to the sixth method of Figure 11. According to some embodiments, the sixth method can be performed by or under the control of the processing circuit 72 of the second network nodes 42, 70, and 80.

[0091] Referring to Figure 11, as shown in block 112, information is provided to the first NRF node 50. The second network node is either the second NF nodes 70, 80 or the first SEPP node 42, and the home network of the first NF node 10 comprises the second network nodes 42, 70, 80 and the first NRF node 50. This information indicates whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node.

[0092] In some embodiments, providing information to the first NRF node 50 may include initiating the transmission of information to the first NRF node 50. In some embodiments, the information may be provided in the profiles of the second network nodes 42, 70, and 80. In some embodiments, the information may be provided along with a request to register the profile with the first NRF node 50.

[0093] In some embodiments, the first NF node 10 referred to herein may be a consumer NF node 10. In other embodiments, the first NF node 10 referred to herein may be a producer NF node. In some embodiments, the task referred to herein may be to select one or more second NF nodes 70, 80 of the home network. In some embodiments, the first NF node 10 referred to herein may be a consumer NF node, and the task referred to herein may be to select one or more second NF nodes 70, 80 of the producer to provide a service requested by the first NF node 10. In other embodiments, the first NF node 10 referred to herein may be a producer NF node, and the task referred to herein may be to select one or more second NF nodes 70, 80 of the consumer to provide a notice requested by the first NF node 10.

[0094] In embodiments described herein, the first NF node 10 and / or the first SCP node 20 may be informed in the data returned by the first NRF node 50 of the home network's ability to perform a task (e.g., re-selection of a second NF node). Mechanisms are described for the home network to notify the visited network whether the home network supports the delegation of the task (e.g., re-selection of a second NF node), such as in indirect communication. The new data may provide capability to the visited network. In some embodiments, this new data may be inserted (by different means) into the data returned from the first NRF node 50.

[0095] Several embodiments will be described with reference to different variations for providing the capability information mentioned herein.

[0096] Variation 1 (Modification 1)) Information provided in the NRF discovery response (at time of registration): It is possible to use data that is appropriate to be returned in the discovery results, i.e., to include it as new data in one or more NF profiles (Variation 1-A) or as new data in a SEPP profile (Variation 1-B). In such embodiments, the second NF node or first SEPP node 42 of the home network registers the new data (at NRF registration). In existing techniques, since discovery is already routed from the first NRF node of the home network to the second NRF node of the visited network via the SEPP nodes (i.e., the second SEPP node 44 of the visited network and the first SEPP node 42 of the home network), the visited network does not discover the profile of the first SEPP node 42 of the home network. Therefore, SEPP profiles are intended to be used only within the network (e.g., within the PLMN). Embodiments according to Variation 1 require the registration of new SEPP information at the first NRF node 50 of the home network.

[0097] • Variation 2) Information provided in the NRF discovery response (inserted by the NRF): As an alternative, to avoid affecting NF registration, new data can be inserted by the first NRF node 50 itself (e.g., based on configuration). The new data can be inserted into the NF profile of one or more second NF nodes (Variation 2-A), or the new data can be inserted into the SEPP profile (Variation 2-B).

[0098] • Variation 3) Information provided in the NRF discovery response (inserted by SEPP): As yet another alternative, new data can be inserted in the discovery response by the SEPP node itself (e.g., based on configuration). The new data can be inserted into the NF profile of one or more second NF nodes (Variation 3-A), or the new data can be inserted into the SEPP profile (Variation 3-B).

[0099] • Variation 4) Information provided in the new NRF service: As yet another alternative, a new service could be provided by the first NRF node 50 to specifically offer home network capabilities. In this way, it would no longer be necessary to transmit information as part of an existing profile (as returned in discovery responses). Instead, the new data could be included in a new service response. Specifically, a new data structure, such as PLMN data, could be defined.

[0100] In embodiments described herein, the visited network has the advantage of knowing whether the home network can handle a request involving the delegation of a task (e.g., the (re)selection of a second NF node). According to some embodiments, based on this knowledge, the visited network may only delegate logic that the home network would be able to perform (e.g., appropriately).

[0101] If the home network is unable to perform the task (for example, if the home network is Model B or Model C (target)), the home network may perform one of the following three options:

[0102] a) Do not delegate the task (and optionally follow the behavior of the legacy technology instead) b) Delegate the task to the visited network (for example, a second SEPP node 44 in the visited network could take on the role of SCP and be able to perform the task), or c) Delegate the task to a specific SCP in the visited network. This SCP may be defined as a kind of "boundary" SCP, i.e., the last SCP before the second SEPP node 44 in the visited network. The intention is to place this "boundary SCP" as close as possible to the second SEPP node 44 in the visited network in order to minimize the signaling path (e.g., if re-selection is required).

[0103] A system is also provided comprising any two or more of the first NRF node 50, the second NRF node 30, the first network nodes 10, 20, and the second network nodes 42, 70, 80 as described herein. Methods performed by the system include methods described herein with respect to any two or more of the first NRF node 50, the second NRF node 30, the first network nodes 10, 20, and the second network nodes 42, 70, 80.

[0104] Figure 12 shows a system according to one embodiment. The system comprises a visited network (vPLMN) of a first NF node and a home network (hPLMN) of the first NF node. The first NF node may be, for example, a consumer NF node (NFc). In the embodiment shown in Figure 12, the visited network comprises at least one first NF node (NFc), a first SCP node (SCPx), and a first SEPP node (vSEPP), and the home network comprises at least one second NF node (NFp), a second SCP node (SCPy), and a second SEPP node (hSEPP). The at least one second NF node may be, for example, at least one producer NF node (NFp).

[0105] Currently, the 3GPP® definition of indirect communication does not specifically address delegation during roaming from vPLMN to hPLMN, and is therefore assumed to be limited to within a PLMN. In other words, delegation of NFp(re)selection logic is not currently standardized. This can be summarized by referring to Figure 12.

[0106] Currently, within the PLMN (vPLMN in the example shown in Figure 12), it is possible to delegate some (re)selection logic (from NFc to SCP) with the help of various information fragments transferred from NFc to SCP. In the example shown in Figure 12, circles 1, 2, and 3 represent different information fragments. The first circle 1 represents information about the selection of a candidate service producer instance. The second circle 2 represents information about the initial selection of one service producer instance. The third circle 3 represents information about the re-selection of an alternative service producer instance. There are three different options (alternatives) for delegating the (re)selection of NF instances to the PLMN. The first option is not to delegate the (re)selection. The second option is to have delegation of non-functional (re)selection (information represented by circles 2 and 3). The third option is to have delegation of functional and non-functional (re)selection (information represented by circles 1, 2, and 3).

[0107] If the information represented by circles 1, 2, and 3 is delegated to SCPx, it is not currently explained whether this delegation can extend further across PLMNs. In fact, one SCP within vPLMN is expected to provide the target destination (3gpp-Sbi-Target-apiRoot). This means that SCPx (or another SCP, if any exists within vPLMN) is expected to perform the initial selection, and this single SCP is also expected to perform re-selection (e.g., in case of failure). Different options for logic delegation are illustrated in Figure 12, but since 3GPP® does not consider anything else, currently only the first option is considered for inter-PLMN communication.

[0108] However, delegating the (re)selection logic has several advantages and may be requested by some customers in the near future. In Stage 2, there is a problem in that no requirements for Model C indirect communication across PLMNs are considered. If the initial selection logic is delegated to the hPLMN, this means that the hPLMN selects the NF target (NFp). If the NF target (NFp) has already been selected in the vPLMN, this selection is meaningless. Different cases are possible depending on the indirect communication model deployed in the vPLMN.

[0109] Several exemplary systems are described with reference to the signaling diagrams in Figures 13 (Figures 13A and 13B) through 24. As is evident from the description with reference to Figures 13 and 14 (Figures 14A and 14B), existing technologies have problems, and as is evident from the description with reference to Figures 15 through 24, these problems can be addressed using the technologies described herein.

[0110] Figure 13 is a signaling diagram showing the transmission and reception of signals in an exemplary system. This illustrates a problem with existing technologies where networks are incompatible.

[0111] The system shown in Figure 13 comprises a first NF node 10, a first SCP node 20 in the visited network of the first NF node (e.g., a visited PLMN), a second NRF node 30 in the visited network, a SEPP node 40, a first NRF node 50 in the home network of the first NF node 10 (e.g., a home PLMN), and several second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to act as an SCP between the first NF node 10 and the second NRF node 30 (and also as an SCP between the first NF node 10 and the second SEPP node 44).

[0112] In the example shown in Figure 13, multiple second NF nodes 70, 80 comprise two second NF nodes. However, it will be understood that the system shown in Figure 13 can have one or more (i.e., any number) second NF nodes. In the example shown in Figure 13, a set of second NF nodes ("NF (Set X)") includes multiple second NF nodes 70, 80.

[0113] The signal transmission and reception between nodes in the system shown in Figure 13 will be described in terms of service requests. Therefore, the multiple second NF nodes 70, 80 may each be configured to provide services 300, 302. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be multiple NF nodes of a (service) producer (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 13 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be multiple NF nodes of a (service) consumer (NFc).

[0114] As shown in block 200 of Figure 13, multiple second NF nodes 70, 80 are registered with the first NRF node 50. For example, the NF profiles of multiple second NF nodes 70, 80 may be stored in the first NRF node 50 (for example, in its memory). The NF profile of a second NF node may include one or more pieces of information indicating the identity of the second NF node, information indicating the set to which the second NF node is included, and information indicating one or more services configured to be provided by the second NF node.

[0115] As shown by arrow 202 in Figure 13, the first NF node 10 sends a service request to the first SCP node 20. The first SCP node 20 then receives the service request from the first NF node 10. The service request is for the service requested by the first NF node 10. The first NF node 10 may also send a request that conforms to indirect communication in Model D (for example, including parameters that allow the first SCP node 20 to perform initial selection and re-selection).

[0116] According to the indirect communication model with delegated discovery (for example, as previously described with reference to Figure 1D), the first NF node 10 transmits one or more discovery parameters (or factors) necessary to find one or more suitable second NF nodes, and the first SCP node 20 can discover one or more second NF nodes via the second NRF node 30 by using the one or more discovery parameters received.

[0117] Therefore, in the embodiment shown in Figure 13, a service request may comprise one or more discovery parameters ("sbi-discovery-*") that form the basis for the first SCP node 20 to discover one or more second NF nodes. The discovery parameters may include information for initial functional selection.

[0118] As shown by arrows 204 to 210 in Figure 13, NF selection is performed in the visited network. More specifically, as shown by arrow 204 in Figure 13, the first SCP node 20 sends a discovery request to the second NRF node 30. The second NRF node 30 then receives the discovery request from the first SCP node 20. As shown by arrow 206 in Figure 13, the second NRF node 30 sends a discovery request to the first NRF node 50 via SEPP node 40 (i.e., the second SEPP node 44 and the first SEPP node 42). The first NRF node 50 then receives the discovery request from the first SCP node 20. A discovery request is a request for information indicating one or more second NF nodes to provide services. A discovery request may consist of one or more discovery parameters (e.g., "sbi-discovery-*").

[0119] As shown by arrow 208 in Figure 13, the first NRF node 50 sends a discovery response to the second NRF node 30 via the SEPP node 40 (i.e., the first SEPP node 42 and the second SEPP node 44). The second NRF node 30 then receives the discovery response from the first NRF node 50. As shown by arrow 210 in Figure 13, the second NRF node 30 sends a discovery response to the first SCP node 20. The first SCP node 20 then receives the discovery response from the second NRF node 30. The discovery response includes information indicating multiple second NF nodes 70, 80 to provide the service. The discovery response may include, for example, profiles of multiple second NF nodes 70, 80. Therefore, steps 204 to 210 may involve the discovery of an NF profile. This requires inter-network (e.g., PLMN) communication to retrieve profiles registered in a home network (e.g., home PLMN).

[0120] As shown in block 212 of Figure 13, one or more second NF nodes are selected from the results. More specifically, the first SCP node 20 selects one or more second NF nodes from among several second NF nodes 70, 80 to which the service request received from the first NF node 10 should be sent. The selection may be based on any existing technique, and those skilled in the art will be aware of various techniques in this regard, such as any of those described above. Thus, it is the SCP nodes in the home network that perform the initial selection. In the example shown in Figure 13, the first SCP node 20 selects second NF node 70. Alternatively, the first SCP node 20 may select second NF nodes based on cached results, instead of performing NRF discovery (as shown by arrows 204-210 in Figure 13).

[0121] As shown in block 214 of Figure 13, the first SCP node 20 determines whether the selected second NF node 70 is in another network. That is, the first SCP node 20 determines whether the selected second NF node 70 is reachable via the SEPP node 40. In the embodiment shown in Figure 13, the first SCP node 20 determines that the selected second NF node 70 is reachable via the SEPP node 40. The first SCP node 20 is in the destination network of the first NF node 10, while the selected second NF node 70 is in the home network of the first NF node 10.

[0122] As shown in block 216 of Figure 13, the first SCP node 20 delegates the (re)selection logic to the home network. For example, if it is determined that a service request needs to reach another network (via SEPP node 40), the destination network (or more specifically, the second SEPP node 44) may decide to delegate the (re)selection to the home network. Thus, the destination network (or more specifically, the second SEPP node 44) may provide the home network with the information necessary for the (re)selection of the second NF node, namely, discovery parameters (e.g., sbi-discovery-*).

[0123] As shown by arrow 218 in Figure 13, the first SCP node 20 sends a service request to SEPP node 40 (or more specifically, the second SEPP node 44 of the visited network). The second SEPP node 44 receives the service request from the first SCP node 20. This request is sent to SEPP node 40 (or more specifically, the second SEPP node 44) to reach the corresponding home network of the first NF node 10. In the service request, according to the current 3GPP® standard, the selected target second NF node 70 is included in the target destination (3gpp-Sbi-Target-apiRoot) header. The target destination referred to herein may be the application programming interface (API) root of a uniform resource identifier (URI) for the selected second NF node 70. The API root of a URI may also be called "3gpp-Sbi-Target-apiRoot".

[0124] In step 218 of Figure 13, the target destination is used for the second SEPP node 44. For example, the target destination is included in the service request to the second SEPP node 44. To enable delegation of initial selection, parameters are provided that are used to discover possible destination second NF nodes. For example, sbi-discovery-* is provided. The discovery parameters (e.g., sbi-discovery-*) are included in the service request sent to SEPP node 40 to provide information to the home network.

[0125] As shown in block 220 of Figure 13, the second SEPP node 44 of the visited network establishes an interface (i.e., an N32 interface) to the first SEPP node 42 of the home network. That is, an interface is established between the second SEPP node 44 and the first SEPP node 42. As shown in block 222 of Figure 13, the first SEPP node 42 may decide to forward the received discovery parameter (e.g., sbi-discovery-*) header. For example, the first SEPP node 42 may forward all received headers, or, if not specified, according to some implementations, the sbi-discovery-* header used for indirect communication may be removed by the first SEPP node 42.

[0126] As shown by arrow 224 in Figure 13, the first SEPP node 42 sends a service request to the selected second NF node 70. The selected second NF node 70 then receives the service request from the first SEPP node 42. The service request sent to the selected second NF node 70 may include discovery parameters (e.g., sbi-discovery-*), but this information is irrelevant to the second NF node 70.

[0127] As shown by the cross "X" in Figure 13, an error may occur that means the service request cannot be executed. When an error occurs, the home network has no means to find an alternative second NF node. Therefore, it is impossible to perform (re)selection in the home network, but the visited network has delegated this task.

[0128] As shown by arrow 226 in Figure 13, the selected second NF node 70 sends a response to the service request to the SEPP node 40, and the SEPP node 40 (or more specifically, the first SEPP node 42) may receive the response from the selected second NF node 70. The response may indicate that the service request was unsuccessful, for example, that the selected second NF node 70 failed to perform the service request, or that an error occurred. Alternatively, there may be no response or the response may be missing due to an error. As shown by arrow 228 in Figure 13, if the SEPP node 40 receives the response, the SEPP node 40 (or more specifically, the second SEPP node 44) may send the response to the first SCP node 20, and the first SCP node 20 may receive the response from the SEPP node 40. As shown by arrow 230 in Figure 13, the first SCP node 20 may send the response to the first NF node 10, and the first NF node 10 may receive the response from the first SCP node 20. In this way, the error is propagated to the visited network via steps 226 to 230 in Figure 13.

[0129] Therefore, as shown in Figure 13, the delegation of (re)selection is not achieved, and an error occurs.

[0130] Figure 14 is a signaling diagram showing the transmission and reception of signals in another exemplary system. This illustrates a problem with existing technologies where there are inconsistencies (lack of compatibility) between networks.

[0131] The system shown in Figure 14 comprises a first NF node 10, a first SCP node 20 in the visited network of the first NF node (e.g., a visited PLMN), a second NRF node 30 in the visited network, a SEPP node 40, a first NRF node 50 in the home network of the first NF node 10 (e.g., a home PLMN), a second SCP node 90 in the home network, and several second NF nodes 70, 80 within the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to act as an SCP between the first NF node 10 and the second NRF node 30 (and also as an SCP between the first NF node 10 and the second SEPP node 44). The second SCP node 90 is configured to act as an SCP between the first NRF node 50 and several second NF nodes 70, 80 (and also as an SCP between the first SEPP node 42 and several second NF nodes 70, 80).

[0132] In the example shown in Figure 14, multiple second NF nodes 70, 80 comprise two second NF nodes. However, it will be understood that the system shown in Figure 14 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 14, a set of second NF nodes ("NF (Set X)") includes multiple second NF nodes 70, 80.

[0133] The signal transmission and reception between nodes in the system shown in Figure 14 will be described in terms of service requests. Therefore, the multiple second NF nodes 70, 80 may each be configured to provide services 300, 302. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be multiple NF nodes of a (service) producer (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 14 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be multiple NF nodes of a (service) consumer (NFc).

[0134] Steps 304 to 324 in Figure 14 are as previously explained with reference to steps 200 to 220 in Figure 13.

[0135] As shown in block 326 of Figure 14, SEPP node 40 (or more specifically, the first SEPP node 42) identifies that the home network has a second SCP node 90 configured for the traffic in question. That is, SEPP node 40 (or more specifically, the first SEPP node 42) can identify that at least indirect communication is deployed for inbound roamer traffic (e.g., traffic from the first NF node 10). Therefore, in some embodiments, the first SEPP node 42 may identify that the service request received in step 322 of Figure 14 should be sent to the second SCP node 90 rather than a selected second NF node 70 in the home network.

[0136] Step 328 in Figure 14 is as previously explained with reference to Step 222 in Figure 13.

[0137] As shown by arrow 330 in Figure 14, the first SEPP node 42 sends a service request to the second SCP node 90, rather than to the selected second NF node 70. As a result, the selected second SCP node 90 receives the service request from the first SEPP node 42. The service request sent to the second SCP node 90 may include a target destination (e.g., 3gpp-Sbi-Target-apiRoot) and / or discovery parameters (e.g., sbi-discovery-*). The target destination is the selected second NF node 70.

[0138] As shown by arrow 332 in Figure 14, the second SCP node 90 sends a service request to the selected second NF node 70. The selected second NF node 70 then receives the service request from the second SCP node 90. An error may occur, as indicated by the cross "X" in Figure 14, meaning the service request cannot be performed.

[0139] As shown by arrow 334 in Figure 14, the selected second NF node 70 sends a response to the service request to the second SCP node 90. The second SCP node 90 then receives the response. The response may indicate that the service request was unsuccessful, for example, that the selected second NF node 70 failed to perform the service request, or that an error occurred. Alternatively, there may be no response or the response may be missing due to an error.

[0140] As shown in block 336 of Figure 14, if an error occurs and the second SCP node 90 only supports Model C, even if the second SCP node 90 receives discovery parameters from the first SEPP node 42 in step 330 of Figure 14, the second SCP node 90 cannot use the discovery parameters (Model D with functional information, e.g., sbi-discovery-*) to find an alternative second NF node within the home network. The home network has no means to find an alternative second NF node. Therefore, it is impossible to perform (re)selection within the home network, but the visited network has delegated this task.

[0141] As shown by arrow 338 in Figure 14, the second SCP node 90 may send a response to the SEPP node 40, and the SEPP node 40 (or more specifically, the first SEPP node 42) may receive a response from the selected second NF node 70.

[0142] Steps 340 and 342 in Figure 14 are as previously described with reference to steps 228 and 230 in Figure 13, respectively.

[0143] Therefore, as shown in Figure 14, the delegation of (re)selection is not achieved, and an error occurs.

[0144] The problems described with reference to Figures 13 and 14 can be solved by the techniques described herein, as shown in Figures 15 to 24. Figures 15 to 24 consider the different cases described above that support indirect communication in a visited network.

[0145] Figure 15 is a signaling diagram showing signal transmission and reception in a system according to one embodiment. This embodiment is an example of Variation 1, more specifically Variation 1-A.

[0146] The system shown in Figure 15 comprises a first SCP node 20 in the visited network (e.g., visited PLMN) of the first NF node 10, a second NRF node 30 and SEPP node 40 in the visited network, a first NRF node 50 in the home network (e.g., home PLMN) of the first NF node 10, and several second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to act as an SCP between the first NF node 10 and the second NRF node 30 (and also as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the several second NF nodes 70, 80 may be as previously described with reference to Figures 2 to 11.

[0147] The system shown in Figure 15 may further include a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to act as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and also as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0148] In the example shown in Figure 15, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 15 can have one or more (i.e., any number) second NF nodes. In the example shown in Figure 15, a set of second NF nodes ("NF (Set X)") includes multiple second NF nodes 70, 80.

[0149] The signal transmission and reception between nodes in the system shown in Figure 15 is described in terms of service requests. Therefore, the multiple second NF nodes 70, 80 may each be configured to provide services 300, 302. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be multiple NF nodes of a (service) producer (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 15 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be multiple NF nodes of a (service) consumer (NFc).

[0150] As shown in block 400 of Figure 15, the second NF nodes 70 and 80 provide information to the first NRF node 50, which then obtains this information. This information indicates whether the home network is capable of performing tasks delegated to it from the visited network. Therefore, in this specification, this information may also be referred to as capability information.

[0151] In some embodiments, capability information may be provided to the first NRF node 50 by registering NF (e.g., NFp) and SEPP profiles with the first NRF node 50. In these embodiments, capability information may be included in the profiles of one or more second NF nodes 70, 80 and / or the first SEPP node 42. For example, information regarding the home network's support for (re)selection of NF capabilities may be included in such profiles.

[0152] Steps 402 to 406 in Figure 15 are as previously explained with reference to steps 202 to 206 in Figure 13.

[0153] In the embodiment shown in Figure 15, in step 402, the first NF node 10 is configured to use indirect communication by Model D. Therefore, the discovery parameters (e.g., sbi-discovery-*) may include information for initial functional selection. If the first NF node 10 is configured to use indirect communication by Model C instead (a variation where the first NF node 10 provides only sets), the discovery parameters (e.g., sbi-discovery-*) may include NF sets. An NF set is a set of second NF nodes from which one or more second NF nodes should be selected.

[0154] In the embodiment shown in Figure 15, in steps 404 and 406, the first SCP node 20 performs the initial selection of one or more second NF nodes. Thus, the first SCP node 20 can obtain the corresponding NF profile. Since the first NF node 10 is in a different network (which can be determined based on the information provided in the service request received in step 402), the second NRF node 30 obtains their NF profile from the corresponding home network. Therefore, the NRF discovery request is sent to the corresponding first NRF node 50 via the SEPP node 40.

[0155] As shown by arrow 408 in Figure 15, the first NRF node 50 provides capability information to the second NRF node 30, thereby allowing the second NRF node 30 to acquire the capability information. More specifically, the first NRF node 50 transmits capability information to the second NRF node 30, thereby allowing the second NRF node 30 to receive the capability information.

[0156] As shown by arrow 410 in Figure 15, the second NRF node 30 provides capability information to the first SCP node 20, thereby allowing the first SCP node 20 to acquire the capability information. More specifically, the second NRF node 30 transmits capability information to the first SCP node 20, thereby allowing the first SCP node 20 to receive the capability information.

[0157] In steps 408 and 410 of Figure 15, capability information may be transmitted in the discovery response. The discovery response may also include the acquired NF profile. For example, in some embodiments, the discovery result may include an NF profile, and these NF profiles may include capability information.

[0158] Therefore, as shown in Figure 15, according to some embodiments, new capabilities can be included in the profile at registration. As shown in block 412 of Figure 15, the capabilities of the home network are favorably recognized by the first SCP node 20.

[0159] Figure 16 is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. This embodiment is an example of Variation 1, more specifically Variation 1-A.

[0160] The system shown in Figure 16 comprises a first SCP node 20 in the visited network (e.g., visited PLMN) of the first NF node 10, a second NRF node 30 and SEPP node 40 in the visited network, a first NRF node 50 in the home network (e.g., home PLMN) of the first NF node 10, and several second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to act as an SCP between the first NF node 10 and the second NRF node 30 (and also as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the several second NF nodes 70, 80 may be as previously described with reference to Figures 2 to 11.

[0161] The system shown in Figure 16 may further include a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to act as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and also as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0162] In the example shown in Figure 16, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 16 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 16, a set of second NF nodes ("NF (Set X)") includes multiple second NF nodes 70, 80.

[0163] The signal transmission and reception between nodes in the system shown in Figure 16 is described in terms of service requests. Therefore, the multiple second NF nodes 70, 80 may each be configured to provide services 300, 302. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be multiple NF nodes of a (service) producer (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 16 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be multiple NF nodes of a (service) consumer (NFc).

[0164] Figure 16 is similar to Figure 15, but differs in that Figure 16 corresponds to embodiments in which indirect communication in the visited network follows Model C (with target) or Model C (with target + set). In Model C (with target), the first NF node 10 includes the target destination (e.g., 3gpp-Sbi-Target-apiRoot) in the request, while in Model C (with target + set), the first NF node 10 includes both the target destination (e.g., 3gpp-Sbi-Target-apiRoot) and the NF set in the request. This request is sent from the first NF node 10 to the first SCP node 20 after step 510 in Figure 16. Before that, the first NF node 10 needs to know whether the task (e.g., (re)selection) can be delegated to the home network. That is, the first NF node 10 needs to know the capabilities of the home network related to that task.

[0165] Steps 500 and 502 to 508 in Figure 16 are as previously described with reference to steps 400 and 404 to 410 in Figure 15, respectively. However, in the embodiment shown in Figure 16, it is the first NF node 10 that sends a discovery request (in step 502 of Figure 16) and receives capability information, for example (in step 508 of Figure 16), in a discovery response.

[0166] Therefore, as shown in Figure 16, according to some embodiments, new capabilities can be included in the profile at registration. As shown in block 510 of Figure 16, the capabilities of the home network are favorably recognized by the first NF node 10.

[0167] Figure 17 is a signaling diagram showing the transmission and reception of signals in a system according to one embodiment. This embodiment is an example of Variation 1, more specifically Variation 1-B.

[0168] The system shown in Figure 17 comprises a first SCP node 20 in the visited network (e.g., visited PLMN) of the first NF node 10, a second NRF node 30 and a SEPP node 40 in the visited network, a first NRF node 50 in the home network (e.g., home PLMN) of the first NF node 10, and several second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to act as an SCP between the first NF node 10 and the second NRF node 30 (and also as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the several second NF nodes 70, 80 may be as previously described with reference to Figures 2 to 11.

[0169] The system shown in Figure 17 may further include a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to act as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and also as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0170] In the example shown in Figure 17, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 17 can have one or more (i.e., any number) second NF nodes. In the example shown in Figure 17, a set of second NF nodes ("NF (Set X)") includes multiple second NF nodes 70, 80.

[0171] The signal transmission and reception between nodes in the system shown in Figure 17 will be described in terms of service requests. Therefore, the multiple second NF nodes 70, 80 may each be configured to provide services 300, 302. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be multiple NF nodes of a (service) producer (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 17 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be multiple NF nodes of a (service) consumer (NFc).

[0172] As shown in block 600 of Figure 17, the first SEPP node 42 provides information to the first NRF node 50, which then obtains this information. This information indicates whether the home network is capable of performing tasks delegated to the home network from the visited network. Therefore, in this specification, this information may also be referred to as capability information.

[0173] In some embodiments, capability information may be provided to the first NRF node 50 by registering a SEPP profile with the first NRF node 50. In these embodiments, capability information may be included in the profile of the first SEPP node 42. For example, information regarding the home network's support for (re)selection of NF capabilities may be included in such a profile.

[0174] Steps 602 to 606 in Figure 17 are as previously explained with reference to steps 202 to 206 in Figure 13.

[0175] In the embodiment shown in Figure 17, in step 602, the first NF node 10 is configured to use indirect communication by Model D. Therefore, the discovery parameters (e.g., sbi-discovery-*) may include information for initial functional selection. If the first NF node 10 is instead configured to use indirect communication by Model C (a variation in which the first NF node 10 provides only sets), the discovery parameters (e.g., sbi-discovery-*) may include NF sets. An NF set is a set of second NF nodes, one or more of which should be selected.

[0176] In the embodiment shown in Figure 17, in steps 604 and 606, in order to determine whether the first SCP node 20 needs to delegate the (re)selection of one or more second NF nodes to the home network, the first SCP node 20 uses the NRF discovery service to obtain capability information to get new data (for example, named plmn-capabilities) to be included in the SEPP profile.

[0177] Steps 608 and 610 in Figure 17 are the same as those described above with reference to steps 408 and 410 in Figure 15, respectively, except that the discovery response may include an acquired SEPP profile instead of an acquired NF profile. For example, in some embodiments, the discovery result may include a SEPP profile, which may include capability information.

[0178] Therefore, as shown in Figure 17, according to some embodiments, new capabilities can be included in the SEPP profile at registration. As shown by block 612 in Figure 17, the capabilities of the home network are favorably known by the first SCP node 20.

[0179] Figure 18 is a signaling diagram showing the transmission and reception of signals in a system according to an embodiment. This embodiment is an example of Variant 1, or more specifically, Variant 1-B.

[0180] The system shown in Figure 18 comprises a first SCP node 20, a second NRF node 30, and a SEPP node 40 in the visited network (e.g., a visited PLMN) of the first NF node 10, a first NRF node 50 in the home network (e.g., a home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 through 11.

[0181] The system shown in Figure 18 may further include a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0182] In the example shown in Figure 18, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 18 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 18, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0183] The transmission and reception of signals between nodes in the system shown in Figure 18 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 18 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0184] Figure 18 is similar to Figure 17, except that it corresponds to an embodiment in which indirect communication in the visited network follows "Model C with Target" or "Model C with Target + Set". "Model C with Target" is when the first NF node 10 includes a target destination (e.g., 3gpp-Sbi-Target-apiRoot) in the request, while "Model C with Target + Set" is when the first NF node 10 includes both a target destination (e.g., 3gpp-Sbi-Target-apiRoot) and an NF set in the request. This request is sent from the first NF node 10 to the first SCP node 20 after step 710 in Figure 18. Before that, the first NF node 10 needs to know whether the task (e.g., (re)selection) can be delegated to the home network. That is, the first NF node 10 needs to know the capabilities of the home network related to that task.

[0185] Step 700 in Figure 18 is as described above with reference to step 600 in Figure 17. Steps 702 to 708 in Figure 18 are as described above with reference to steps 604 to 610 in Figure 17, respectively, except that the first NF node 10 sends a discovery request (in step 702 in Figure 18) and receives capability information, for example, in the discovery response (in step 708 in Figure 18). The discovery response may include a discovered SEPP profile rather than a discovered NF profile. For example, in some embodiments, the discovery result may include a SEPP profile, which may include capability information.

[0186] Therefore, as shown in Figure 18, according to some embodiments, new capabilities can be included in the SEPP profile at registration. As shown by block 710 in Figure 18, the capabilities of the home network are favorably known by the first SCP node 20.

[0187] Figure 19 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 2.

[0188] The system shown in Figure 19 comprises a first SCP node 20, a second NRF node 30, and a SEPP node 40 in the visited network (e.g., a visited PLMN) of the first NF node 10, a first NRF node 50 in the home network (e.g., a home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 to 11.

[0189] The system shown in Figure 19 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0190] In the example shown in Figure 19, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 19 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 19, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0191] The transmission and reception of signals between nodes in the system shown in Figure 19 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 19 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0192] Step 800 in Figure 19 is as described above with reference to step 400 in Figure 15. Steps 802 to 806 in Figure 19 are as described above with reference to steps 402 to 406 in Figure 15 and steps 602 to 606 in Figure 17, respectively. As shown by block 808 in Figure 19, the first NRF node 50 can insert capability information into the discovery response. For example, capability information may be included in the NF profile and / or SEPP profile within the discovery response.

[0193] Steps 810 and 812 in Figure 19 are the same as those described above with reference to steps 408 and 410 in Figure 15 and steps 608 and 610 in Figure 17, respectively, except that the discovery response may include the acquired NF profile and / or SEPP profile. For example, in some embodiments, the discovery result may include the NF profile and / or SEPP profile, which may include capability information. Thus, the first NRF node 50 can insert new capabilities into the discovery response.

[0194] Therefore, as shown in Figure 19, according to some embodiments, new capabilities can be included in one or more NF profiles and / or SEPP profiles at registration. As shown by block 814 in Figure 19, the capabilities of the home network are favorably known by the first SCP node 20.

[0195] Figure 20 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 2.

[0196] The system shown in Figure 20 comprises a first SCP node 20 in the visited network (e.g., visited PLMN) of the first NF node 10, a second NRF node 30 and SEPP node 40 in the visited network, a first NRF node 50 in the home network (e.g., home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 to 11.

[0197] The system shown in Figure 20 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0198] In the example shown in Figure 20, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 20 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 20, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0199] The transmission and reception of signals between nodes in the system shown in Figure 20 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 20 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0200] Figure 20 is similar to Figure 19, except that it corresponds to an embodiment in which indirect communication in the visited network follows "Model C with Target" or "Model C with Target + Set". "Model C with Target" is when the first NF node 10 includes a target destination (e.g., 3gpp-Sbi-Target-apiRoot) in the request, while "Model C with Target + Set" is when the first NF node 10 includes both a target destination (e.g., 3gpp-Sbi-Target-apiRoot) and an NF set in the request. This request is sent from the first NF node 10 to the first SCP node 20 after step 912 in Figure 20. Before that, the first NF node 10 needs to know whether the task (e.g., (re)selection) can be delegated to the home network. That is, the first NF node 10 needs to know the capabilities of the home network related to that task.

[0201] Step 900 in Figure 20 is as described above with reference to step 800 in Figure 19. Steps 902, 904, 908, and 910 in Figure 20 are as described above with reference to steps 702, 704, 706, and 708 in Figure 18, respectively, except that the discovery response may include the acquired NF profile and / or SEPP profile. For example, in some embodiments, the discovery result may include the NF profile and / or SEPP profile, which may include capability information. Step 906 in Figure 20 is as described above with reference to step 808 in Figure 19.

[0202] Therefore, as shown in Figure 20, according to some embodiments, new capabilities can be included in one or more NF profiles and SEPP profiles at registration. As shown by block 912 in Figure 20, the capabilities of the home network are favorably known by the first SCP node 20.

[0203] Figure 21 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 3.

[0204] The system shown in Figure 21 comprises a first SCP node 20 in the visited network (e.g., visited PLMN) of the first NF node 10, a second NRF node 30 and SEPP node 40 in the visited network, a first NRF node 50 in the home network (e.g., home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 through 11.

[0205] The system shown in Figure 21 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0206] In the example shown in Figure 21, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 21 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 21, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0207] The transmission and reception of signals between nodes in the system shown in Figure 21 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 21 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0208] Step 1000 in Figure 21 is as described above with reference to step 800 in Figure 19. Steps 1002 to 1006 and 1010 to 1012 in Figure 21 are as described above with reference to steps 802 to 806 and 810 to 812 in Figure 19, respectively. Step 1008 in Figure 21 is as described above with reference to step 808 in Figure 19, except that step 1008 in Figure 21 (i.e., the step of inserting new capability information into the discovery response) is performed by the first SEPP node 42.

[0209] Therefore, as shown in Figure 21, according to some embodiments, new capabilities can be included in one or more NF profiles and SEPP profiles at registration. As shown by block 1014 in Figure 21, the capabilities of the home network are favorably known by the first SCP node 20.

[0210] Figure 22 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 3.

[0211] The system shown in Figure 22 comprises a first SCP node 20, a second NRF node 30, and a SEPP node 40 in the visited network (e.g., a visited PLMN) of the first NF node 10, a first NRF node 50 in the home network (e.g., a home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 through 11.

[0212] The system shown in Figure 22 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0213] In the example shown in Figure 22, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 22 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 22, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0214] The transmission and reception of signals between nodes in the system shown in Figure 22 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 22 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0215] Step 1100 in Figure 22 is as described above with reference to step 900 in Figure 20. Steps 1102 to 1104 and 1108 to 1110 in Figure 22 are as described above with reference to steps 902 to 904 and 908 to 910 in Figure 20, respectively. Step 1106 in Figure 22 is as described above with reference to step 906 in Figure 20, except that step 1106 in Figure 22 (i.e., the step of inserting new capability information into the discovery response) is performed by the first SEPP node 42.

[0216] Therefore, as shown in Figure 22, according to some embodiments, new capabilities can be included in one or more NF profiles and SEPP profiles at registration. As shown by block 1112 in Figure 22, the capabilities of the home network are favorably known by the first NF node 10.

[0217] Figure 23 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 4.

[0218] The system shown in Figure 23 comprises a first SCP node 20, a second NRF node 30, and a SEPP node 40 in the visited network (e.g., a visited PLMN) of the first NF node 10, a first NRF node 50 in the home network (e.g., a home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 through 11.

[0219] The system shown in Figure 23 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0220] In the example shown in Figure 23, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 23 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 23, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0221] The transmission and reception of signals between nodes in the system shown in Figure 23 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 23 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0222] As shown by block 1200 in Figure 23, capability information is new data in the first NRF node 50. For example, capability information may be stored in the memory of the first NRF node 50. Thus, the first NRF node 50 can retrieve capability information from its memory.

[0223] Step 1202 in Figure 23 is as described above with reference to step 402 in Figure 15.

[0224] As indicated by arrow 1204 in Figure 23, the first SCP node 20 sends a request for capability information to the second NRF node 30. Thus, the second NRF node 30 receives the request from the first SCP node 20. As indicated by arrow 1206 in Figure 23, the second NRF node 30 sends the request to the first NRF node 50 via SEPP node 40 (i.e., via the second SEPP node 44 and the first SEPP node 42). Thus, the first NRF node 50 receives the request from the first SCP node 20.

[0225] As indicated by arrow 1208 in Figure 23, the first NRF node 50 sends a response to the second NRF node 30 via the SEPP node 40 (i.e., via the first SEPP node 42 and the second SEPP node 44). Thus, the second NRF node 30 receives a response from the first NRF node 50. As indicated by arrow 1210 in Figure 23, the second NRF node 30 sends a response to the first SCP node 20. Thus, the first SCP node 20 receives a response from the second NRF node 30. The response includes capability information. A new service at the first NRF node 50 provides new capability information. In some embodiments, the new capability information may be provided with a specific network identifier, e.g., (plmn-id).

[0226] Therefore, as shown in Figure 23, according to some embodiments, new capabilities can be provided by the new NRF service. As shown by block 1212 in Figure 23, the capabilities of the home network are favorably known by the first SCP node 20.

[0227] Figure 24 is a signaling diagram showing the transmission and reception of signals in the system according to this embodiment. This embodiment is an example of variant 4.

[0228] The system shown in Figure 24 comprises a first SCP node 20, a second NRF node 30, and a SEPP node 40 in the visited network (e.g., a visited PLMN) of the first NF node 10, a first NRF node 50 in the home network (e.g., a home PLMN) of the first NF node 10, and a number of second NF nodes 70, 80 in the home network. The SEPP node 40 comprises a first SEPP node 42 in the home network and a second SEPP node 44 in the visited network. The first SCP node 20 is configured to operate as an SCP between the first NF node 10 and the second NRF node 30 (and as an SCP between the first NF node 10 and the second SEPP node 44). The first SCP node 20, the second NRF node 30, the first SEPP node 42, the first NRF node 50, and the number of second NF nodes 70, 80 may be as described above with reference to Figures 2 to 11.

[0229] The system shown in Figure 24 may further comprise a first NF node 10 and a second SCP node 90 of the home network. The second SCP node 90 may be configured to operate as an SCP between the first NRF node 50 and a plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and a plurality of second NF nodes 70, 80).

[0230] In the example shown in Figure 24, multiple second NF nodes 70, 80 comprise two second NF nodes (i.e., "NF1" and "NF2"). However, it will be understood that the system shown in Figure 24 may have one or more (i.e., any number) second NF nodes. In the example shown in Figure 24, a set of second NF nodes ("NF (Set X)") comprises multiple second NF nodes 70, 80.

[0231] The transmission and reception of signals between nodes in the system shown in Figure 24 is described in relation to service requests. Therefore, multiple second NF nodes 70, 80 may be configured to provide services 300, 302, respectively. Also, the first NF node 10 may be an NF node of a (service) consumer (NFc), and the multiple second NF nodes may be NF nodes of multiple (service) producers (NFp). However, it will be understood that other requests are also possible. For example, the service requests in Figure 24 may be replaced with notification requests. In some such examples, the first NF node 10 may be an NF node of a (service) producer (NFp), and the multiple second NF nodes may be NF nodes of multiple (service) consumers (NFc).

[0232] Figure 24 is similar to Figure 23, except that it corresponds to an embodiment in which indirect communication in the visited network follows "Model C with Target" or "Model C with Target + Set". "Model C with Target" is when the first NF node 10 includes a target destination (e.g., 3gpp-Sbi-Target-apiRoot) in the request, while "Model C with Target + Set" is when the first NF node 10 includes both a target destination (e.g., 3gpp-Sbi-Target-apiRoot) and an NF set in the request.

[0233] Step 1300 in Figure 24 is as described above with reference to step 1200 in Figure 23. Steps 1302 to 1308 in Figure 24 are as described above with reference to steps 1204 to 1210 in Figure 23, respectively. However, in the embodiment shown in Figure 24, it is the first NF node 10 that sends the request (in step 1302 in Figure 24) and receives capability information in the response, for example (in step 1308 in Figure 24).

[0234] Therefore, as shown in Figure 24, according to some embodiments, new capabilities can be provided by the new NRF service. As shown by block 1310 in Figure 24, the capabilities of the home network are favorably known by the first NF node 10.

[0235] The wireless devices referred to herein may be any type of wireless device. Examples of the types of wireless devices referred to herein include, but are not limited to, smartphones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop-based equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), and user equipment (UE) such as in-vehicle wireless terminal devices. The wireless devices referred to herein may support device-to-device (D2D) communication by implementing, for example, the Third Generation Partnership Project (3GPP®) standards for side-link communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), in which case they may be called D2D communication devices.

[0236] As yet another specific example, in an Internet of Things (IoT) scenario, the wireless devices referred to herein may represent machines or other devices that perform monitoring and / or measurements and transmit the results of such monitoring and / or measurements to other wireless devices and / or network nodes. In this case, the wireless devices referred to herein may also be machine-to-machine (M2M) devices, which may be referred to as machine-type communication (MTC) devices in the context of 3GPP®.

[0237] As one specific example, a wireless device referred to herein may be, for example, a user equipment (UE) implementing the 3GPP® Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices include sensors, measuring devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a wireless device referred to herein may represent a vehicle or other equipment capable of monitoring and / or reporting its operating status or other functions related to its operation. A wireless device referred to herein may also represent an endpoint of a wireless connection, in which case a wireless device referred to herein may be called a wireless terminal. Furthermore, a wireless device referred to herein may be mobile, in which case it may be called a mobile device or mobile terminal.

[0238] Also provided are computer programs that, when executed by processing circuits (such as the processing circuit 52 of the first NRF node 50 described above, the processing circuit 32 of the second NRF node 30 described above, the processing circuit 12 of the first network nodes 10 and 20 described above, and / or the processing circuit 72 of the second network nodes 42, 70, and 80 described above), cause the processing circuits to perform at least a portion of the methods described herein. Also provided are computer program products embodied on a non-temporary, machine-readable medium, which include instructions executable by processing circuits (such as the processing circuit 52 of the first NRF node 50 described above, the processing circuit 32 of the second NRF node 30 described above, the processing circuit 12 of the first network nodes 10 and 20 described above, and / or the processing circuit 72 of the second network nodes 42, 70, and 80 described above) to cause the processing circuits to perform at least a portion of the methods described herein. A computer program product is provided which includes a carrier comprising instructions for causing processing circuits (such as the processing circuit 52 of the first NRF node 50 described earlier, the processing circuit 32 of the second NRF node 30 described earlier, the processing circuit 12 of the first network nodes 10 and 20 described earlier, and / or the processing circuit 72 of the second network nodes 42, 70, and 80 described earlier) to perform at least a portion of the methods described herein. In some embodiments, the carrier may be one of the following: an electronic signal, an optical signal, an electromagnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0239] In some embodiments, the node functions described herein may be performed by hardware. Thus, in some embodiments, one or more of the first NRF node 50, the second NRF node 30, the first network nodes 10, 20, and / or the second network nodes 42, 70, 80 described herein may be hardware nodes. However, it will also be understood that, at an optional choice, at least some or all of the node functions described herein may be virtualized. For example, functions performed by one or more of the first NRF node 50, the second NRF node 30, the first network nodes 10, 20, and / or the second network nodes 42, 70, 80 may be implemented in software running on general-purpose hardware configured to orchestrate the node functions. Accordingly, in some embodiments, one or more of the first NRF node 50, the second NRF node 30, the first network nodes 10, 20, and / or the second network nodes 42, 70, 80 described herein may be virtual nodes.

[0240] In some embodiments, at least some or all of the node functions described herein may run in a network-enabled cloud. All of the node functions described herein may be located in the same location, or at least some of the node functions may be distributed.

[0241] It will be understood that in some embodiments, at least some or all of the method steps described herein can be automated. That is, in some embodiments, at least some or all of the method steps described herein can be performed automatically. The methods described herein may be computer implementation methods.

[0242] Accordingly, the embodiments described herein offer an advantage in providing improved techniques for managing the transmission and reception of information between networks. In particular, the techniques described herein can provide network nodes with knowledge of network capabilities. For example, capability information can be exchanged so that a visited network of an NF node can obtain information about the capabilities of the home network of that NF node. This enables effective task delegation from the visited network to the home network. That is, the visited network is aware of the home network's ability to perform the task delegated to it, and therefore errors related to the inability to perform the task on the home network are avoided. This is particularly useful in inter-network communication (from the visited network to the home network), such as when an NF node is roaming.

[0243] The embodiments described above are illustrative and not limiting to the concept, and it should be noted 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 preclude the presence of elements or steps other than those enumerated in the claims, and “a” or “an” does not preclude plural, and a single processor or other unit may perform the functions of several units described in the claims. No reference numeral in the claims should be construed as limiting its scope.

Claims

1. A method for managing the transmission and reception of information between networks, wherein the method is performed by a first network repository function (NRF) node (50), and the method is This includes providing information to the second NRF node (30) (102, 408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306), The visited network of the first network function (NF) node (10) includes the second NRF node (30), and the home network of the first NF node (10) includes the first NRF node (50). The information relates to a method indicating whether the home network is capable of performing tasks delegated to the home network from the visited network.

2. The method according to claim 1, The information is provided in response to the receipt of a first message from the second NRF node (30) (406, 504, 606, 704, 806, 904, 1006, 1104, 1206, 1304) (408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306), by the method.

3. The method according to claim 2, The first message mentioned above is, The first request is a request for the aforementioned information, and / or A second request, which is a request to discover one or more second NF nodes (70, 80) of the aforementioned home network. A method that includes [a certain feature].

4. A method according to claim 2 or 3, A method wherein the first message comprises an identifier that identifies the destination network.

5. A method according to any one of claims 1 to 4, Providing the information to the second NRF node (30) (408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306) is, A method comprising initiating the transmission of a second message to the second NRF node (30), wherein the second message comprises the information.

6. A method according to any one of claims 1 to 5, The information is provided in the profile of the second NF node (70, 80) of the home network, or in the profile of the first security edge protected proxy (SEPP) node (42) of the home network.

7. A method according to any one of claims 1 to 6, A method comprising storing the information in the first NRF node (50).

8. A method according to any one of claims 1 to 7, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

9. A method according to any one of claims 1 to 8, The task is to select one or more second NF nodes (70, 80) of the home network, method.

10. The method according to claim 9, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

11. A method for managing the transmission and reception of information between networks, wherein the method is performed by a second network repository function (NRF) node (30), and the method is This includes obtaining information from the first NRF node (50) (106, 408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306), The home network of the first network function (NF) node (10) includes the first NRF node (50), and the visited network of the first NF node (10) includes the second NRF node (30). The information relates to a method indicating whether the home network is capable of performing tasks delegated to the home network from the visited network.

12. The method according to claim 11, The information is obtained in response to sending a first message to the first NRF node (50) (406, 504, 606, 704, 806, 904, 1006, 1104, 1206, 1304) (408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306), by the method.

13. The method according to claim 12, The first message mentioned above is, The first request is a request for the aforementioned information, and / or A second request is a request to discover one or more second NF nodes (70, 80) of the aforementioned home network. Methods that include...

14. A method according to claim 12 or 13, A method wherein the first message comprises an identifier that identifies the destination network.

15. A method according to any one of claims 11 to 14, Obtaining the information from the first NRF node (50) (408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306) is, A method comprising receiving a second message from the first NRF node (50), wherein the second message comprises the information.

16. A method according to any one of claims 11 to 15, The information is obtained in the profile of the second NF node (70, 80) of the home network, or in the profile of the first security edge protected proxy (SEPP) node (42) of the home network, by the method.

17. A method according to any one of claims 11 to 16, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

18. A method according to any one of claims 11 to 17, The task is to select one or more second NF nodes (70, 80) of the home network, method.

19. The method according to claim 18, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

20. A method for managing the transmission and reception of information between networks, wherein the method is performed by a second network repository function (NRF) node (30), and the method is This includes providing information to the first network nodes (10, 20) (108, 410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308), The first network nodes (10, 20) are a first network function (NF) node (10) or a first service communication proxy (SCP) node (20) configured to operate as an SCP between the first NF node (10) and a second NRF node (30), and the destination network of the first NF node (10) comprises the second NRF node (30) and the first network nodes (10, 20). The information relates to a method indicating whether the home network of the first NF node (10) is capable of performing tasks delegated to the home network from the visited network.

21. The method according to claim 20, The information is provided in response to the reception of a second message from a first NRF node (50) (408, 506, 608, 706, 810, 908, 1010, 1108, 1208, 1306) (410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308), and the second message comprises the information, method.

22. A method according to claim 20 or 21, Providing the information to the first network nodes (10, 20) (410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308) is, A method comprising initiating the transmission of a third message to the first network nodes (10, 20), wherein the third message comprises the information.

23. A method according to any one of claims 20 to 22, The information is provided in the profile of the second NF node (70, 80) of the home network, or in the profile of the first security edge protected proxy (SEPP) node (42) of the home network.

24. A method according to any one of claims 20 to 23, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

25. A method according to any one of claims 20 to 24, The task is to select one or more second NF nodes (70, 80) of the home network, method.

26. The method according to claim 25, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

27. A method for managing the transmission and reception of information between networks, wherein the method is performed by a first network node (10, 20), and the method is This includes obtaining information from a second network repository function (NRF) node (30) (110, 410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308), wherein the first network nodes (10, 20) are a first network function (NF) node (10) or a first service communication proxy (SCP) node (20) configured to act as an SCP between the first NF node (10) and the second NRF node (30), and the destination network of the first NF node (10) comprises the second NRF node (30) and the first network nodes (10, 20). The information relates to a method indicating whether the home network of the first NF node (10) is capable of performing tasks delegated to the home network from the visited network.

28. The method according to claim 27, The information is obtained in response to sending a third message to the second NRF node (30) (404, 504, 604, 702, 804, 902, 1004, 1102, 1204, 1302) (410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308), by the method.

29. The method according to claim 28, The third message is, The first request is a request for the aforementioned information, and / or, A second request, which is a request to discover one or more second NF nodes (70, 80) of the aforementioned home network. A method that includes [a certain feature].

30. The method according to claim 28 or 29, The method wherein the third message comprises an identifier that identifies the visited network.

31. A method according to any one of claims 27 to 30, Obtaining the information from the second NRF node (30) (410, 508, 610, 708, 812, 910, 1012, 1110, 1210, 1308) is, A method comprising receiving a third message from the second NRF node (30), wherein the third message comprises the information.

32. A method according to any one of claims 27 to 31, The information is obtained in the profile of the second NF node (70, 80) of the home network, or in the profile of the first security edge protected proxy (SEPP) node (42) of the home network, by the method.

33. A method according to any one of claims 27 to 32, wherein the method is A method comprising determining, based on the aforementioned information, whether the home network is capable of performing the task.

34. A method according to any one of claims 27 to 33, If the home network is unable to perform the task, the method Performing the aforementioned task, or Delegating the task to a second security edge protection proxy (SEPP) node (44) or a second SCP node of the visited network. A method comprising the following, wherein the second SCP node is configured to operate as an SCP between the first network nodes (10, 20) and the second SEPP node (44).

35. The method according to claim 34, The method wherein the second SCP node is the SCP node in the visited network that is closest to the second SEPP node (44).

36. A method according to any one of claims 27 to 35, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

37. A method according to any one of claims 27 to 36, The task is to select one or more second NF nodes (70, 80) of the home network, method.

38. The method according to claim 37, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

39. A method for managing the transmission and reception of information between networks, wherein the method is performed by a second network node (42, 70, 80), and the method is This includes providing information to the first network repository function (NRF) node (50) (112, 400, 500, 600, 700, 808, 906, 1008, 1106), The second network node is a second network function (NF) node (70, 80) or a first security edge protection proxy (SEPP) node (42), and the home network of the first network function (NF) node (10) comprises the second network node (42, 70, 80) and the first NRF node (50). The information relates to a method indicating whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node (10).

40. The method according to claim 39, Providing the information to the first NRF node (50) (400, 500, 600, 700, 808, 906, 1008, 1106) is, A method comprising initiating the transmission of the information toward the first NRF node (50).

41. The method according to claim 39 or 40, The information is provided in the profile of the second network nodes (42, 70, 80) by method.

42. The method according to claim 41, The information is provided along with a request to register the profile with the first NRF node (50).

43. A method according to any one of claims 39 to 42, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

44. A method according to any one of claims 39 to 43, The task is to select one or more second NF nodes (70, 80) of the home network, method.

45. The method according to claim 44, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

46. A method for managing the transmission and reception of information between networks, wherein the method is performed by a first network repository function (NRF) node (50), and the method is This includes obtaining information from the memory of the first NRF node (50) or from the second network nodes (42, 70, 80) (104, 400, 500, 600, 700, 808, 906, 1008, 1106, 1200, 1300), The second network node is a second network function (NF) node (70, 80) or a first security edge protection proxy (SEPP) node (42), and the home network of the first network function (NF) node (10) comprises the second network node (42, 70, 80) and the first NRF node (50). The information relates to a method indicating whether the home network is capable of performing tasks delegated to the home network from the visited network of the first NF node (10).

47. The method according to claim 46, A method comprising obtaining the aforementioned information (400, 500, 600, 700, 808, 906, 1008, 1106, 1200, 1300) and receiving the aforementioned information.

48. The method according to claim 46 or 47, The information is obtained in the profile of the second network nodes (42, 70, 80) by the method.

49. The method according to claim 48, The information is obtained from the second network nodes (42, 70, 80) along with a request to register the profile with the first NRF node (50).

50. A method according to any one of claims 46 to 49, wherein the method is A method comprising storing the information in the first NRF node (50).

51. A method according to any one of claims 46 to 50, The first NF node (10) is a consumer NF node, or The first NF node (10) is the NF node of the producer, in this method.

52. A method according to any one of claims 46 to 51, The task is to select one or more second NF nodes (70, 80) of the home network, method.

53. The method according to claim 52, The first NF node (10) is a consumer NF node, and the task is to select one or more second NF nodes (70, 80) of the producer to provide the services (300, 302) requested by the first NF node (10), or The method wherein the first NF node (10) is a producer's NF node, and the task is to select one or more second NF nodes (70, 80) of a consumer to provide notifications requested by the first NF node (10).

54. A method performed by a system, wherein the method is The method according to any one of claims 1 to 10, The method according to any one of claims 11 to 19, The method according to any one of claims 20 to 26, The method according to any one of claims 27 to 38, The method according to any one of claims 39 to 45, and / or A method comprising the method according to any one of claims 46 to 53.

55. A first network repository function (NRF) node (50), A first NRF node (50) comprising a processing circuit (52) configured to operate according to any one of claims 1 to 10 and / or any one of claims 46 to 53.

56. The first NRF node (50) according to claim 55, The first NRF node (50) is A first NRF node (50) comprising at least one memory (54) for storing instructions that, when executed by the processing circuit (52), cause the first NRF node (50) to operate according to any one of claims 1 to 10 and / or any one of claims 46 to 53.

57. A second network repository function (NRF) node (30), A second NRF node (30) comprising a processing circuit (32) configured to operate according to any one of claims 11 to 19 and / or any one of claims 20 to 26.

58. A second NRF node (30) according to claim 57, The second NRF node (30) is A second NRF node (30) comprising at least one memory (34) for storing instructions that, when executed by the processing circuit (32), cause the second NRF node (30) to operate according to any one of claims 11 to 19 and / or any one of claims 20 to 26.

59. The first network nodes (10, 20) A first network node (10, 20) comprising a processing circuit (12) configured to operate according to any one of claims 27 to 38.

60. The first network node (10, 20) according to claim 59, The first network nodes (10, 20) are: A first network node (10, 20) 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 in accordance with any one of claims 27 to 38.

61. The second network nodes (42, 70, 80) A second network node comprising a processing circuit (72) configured to operate according to any one of claims 39 to 45.

62. The second network node (42, 70, 80) according to claim 61, The second network nodes (42, 70, 80) are: A second network node (42, 70, 80) comprising at least one memory (74) for storing instructions that, when executed by the processing circuit (72), cause the second network node (42, 70, 80) to operate in accordance with any one of claims 39 to 45.

63. It is a system, The first NRF node (50) according to claim 55 or 56, A second NRF node (30) according to claim 57 or 58, A first network node (10, 20) according to claim 59 or 60, A system comprising two or more of the second network nodes (42, 70, 80) described in claim 61 or 62.

64. A computer program comprising instructions, when executed by a processing circuit, causing the processing circuit to perform a method according to any one of claims 1 to 10, any one of claims 11 to 19, any one of claims 20 to 26, any one of claims 27 to 38, any one of claims 39 to 45, and / or any one of claims 46 to 53.

65. A computer program product embodied on a non-temporary, machine-readable medium, comprising instructions executable by a processing circuit to cause the processing circuit to perform a method according to any one of claims 1 to 10, any one of claims 11 to 19, any one of claims 20 to 26, any one of claims 27 to 38, any one of claims 39 to 45, and / or any one of claims 46 to 53.

Images