[go: up one dir, main page]

WO2024235664A1 - Gestion d'échange d'informations - Google Patents

Gestion d'échange d'informations Download PDF

Info

Publication number
WO2024235664A1
WO2024235664A1 PCT/EP2024/062164 EP2024062164W WO2024235664A1 WO 2024235664 A1 WO2024235664 A1 WO 2024235664A1 EP 2024062164 W EP2024062164 W EP 2024062164W WO 2024235664 A1 WO2024235664 A1 WO 2024235664A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
network
nrf
information
nodes
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2024/062164
Other languages
English (en)
Inventor
Maria Cruz Bartolome Rodrigo
Volker KLEINFELD
Mary Amarisa ROBISON PIETSCH
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2024235664A1 publication Critical patent/WO2024235664A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers

Definitions

  • the disclosure relates to methods for managing information exchange between networks and nodes configured to operate in accordance with those methods.
  • a service request is generally from a consumer of the service (“service consumer”) to a producer of the service (“service producer”).
  • 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. This is referred to as direct communication and indirect communication respectively.
  • the NF node of the service consumer and the NF node of the service producer may communicate via a service communication proxy (SCP) node.
  • SCP service communication proxy
  • Figure 1A-D illustrates different existing systems for handling service requests, as set out in the Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 Version (V) 17.3.0.
  • 3GPP Third Generation Partnership Project
  • TS Technical Specification
  • V Version
  • Figures 1A and 1 B illustrate systems that use direct communication
  • Figures 10 and 1 D illustrate systems that use indirect communication
  • Figures 1A, 1 B, 10 and 1 D can be said to represent Models A, B, C and D respectively, which may be referenced herein.
  • a service request is sent directly from the NF node of the service consumer to the NF node of the service producer.
  • a response to the service request is sent directly from the N F node of the service producer to the N F node of the service consumer.
  • any subsequent service requests are sent directly from the N F node of the service consumer to the N F node of the service producer.
  • the system illustrated in Figure 1 B also comprises a network repository function (NRF) node.
  • NRF network repository function
  • the NF node of the service consumer can receive an NF profile for one or more NF nodes of the service producer and, based on the received NF profile(s), can select an NF node of the service producer to which to send the service request.
  • the NRF node is not used and instead the NF node of the service consumer may be configured with the NF profile(s) of the NF node(s) of the service producer.
  • a service request is sent indirectly from the NF node of the service consumer to the NF node of the service producer via a service communication proxy (SCP) node.
  • a response to the service request is sent indirectly from the NF node of the service producer to the NF node of the service consumer via the SCP node.
  • any subsequent service requests are sent indirectly from the NF node of the service consumer to the NF node of the service producer via the SCP node.
  • the systems illustrated in Figures 1C and 1 D also comprise an NRF node.
  • the NF node of the service consumer can query the NRF node to discover suitable NF nodes of the service producer to which to send the service request.
  • the NF node of the service consumer can receive an NF profile for one or more NF nodes of the service producer and, based on the received NF profile(s), can select an NF node of the service producer to which to send the service request.
  • the service request sent from the NF node of the service consumer to the SCP node comprises the address of the selected NF node of the service producer.
  • the NF node of the service consumer can forward the service request without performing any further discovery or selection.
  • the selected NF node of the service producer may be up to the NF node of the service consumer to find an alternative.
  • the SCP node may communicate with the NRF node to acquire selection parameters (e.g. location, capacity, etc.) and the SCP node may select an NF node of the service producer to which to send the service request.
  • the NF node of the service consumer does not carry out the discovery or selection process. Instead, the NF node of the service consumer adds any necessary discovery and selection parameters (required to find a suitable N F node of the service producer) to the service request that it sends via the SCP node.
  • the SCP node uses the request address and the discovery and selection parameters in the service request to route the service request to a suitable NF node of the service producer.
  • the NF node of the service consumer sends the service request to the SCP node and provides, within the service request to the SCP node, the discovery and selection parameters necessary to discover and select an NF node of a service producer.
  • the SCP node can perform discovery with the NRF node to discover a target NF node of the service producer to which to route the service request.
  • the SCP node can discover a target NF node of the service producer in the manner indicated in 3GPP TS 23.502 V17.3.0.
  • indirect communication from a first NF (e.g. NF consumer, NFc) node to a second NF (e.g. NF producer, NFp) node via a first SCP node is defined in 3GPP at Stage 2 level.
  • Indirect communication provides the means for a first NF node to be able to delegate all, or part, of the logic required for initial selection of the required second NF node and/or for reselection of an alternative second NF node (e.g. in case of failure of the initially selection second NF node) to the SCP.
  • Stage 2 does not consider any requirements for indirect communication (e.g. the model illustrated in Figure 1C) across public land mobile networks (PLMNs).
  • PLMNs public land mobile networks
  • delegation of (re)selection of NF logic 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 required for (re)selection of NF(s) is provided from the visited network to the home network.
  • the home network may not be able to support the required delegation of logic and this will cause an error.
  • a first NRF node comprising processing circuitry configured to operate in accordance with one or both of the first method and the second method.
  • the first NRF node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the first NRF node to operate in accordance with one or both of the first method and the second method.
  • a fourth method for managing information exchange between networks is performed by a second NRF node.
  • the fourth method comprises providing information to a first network node.
  • the first network node is a first NF node or a first service communication proxy (SCP) node that is configured to operate as an SCP between the first NF node and the second NRF node.
  • a visited network of the first NF node comprises the second NRF node and the first network node.
  • the information is indicative of whether a home network of the first NF node is capable of performing a task delegated to the home network from the visited network.
  • a second NRF node comprising processing circuitry configured to operate in accordance with one or both of the third method and the fourth method.
  • the second NRF node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the second NRF node to operate in accordance with one or both of the third method and the fourth method.
  • a fifth method for managing information exchange between networks is performed by a first network node.
  • the fifth method comprises acquiring information from a second NRF node.
  • the first network node is a first NF node or a first SCP node that is configured to operate as an SCP between the first NF node and the second NRF node.
  • a visited network of the first NF node comprises the second NRF node and the first network node.
  • the information is indicative of whether a home network of the first NF node is capable of performing a task delegated to the home network from the visited network.
  • a first network node comprising processing circuitry configured to operate in accordance with the fifth method.
  • the first network node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the first network node to operate in accordance with the fifth method.
  • a second network node comprising processing circuitry configured to operate in accordance with the sixth method.
  • the second network node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the second network node to operate in accordance with the sixth method.
  • a method performed by a system comprises any two or more of the first, second, third, fourth, fifth and sixth methods.
  • a system comprising any two or more of a first NRF node as described earlier, a second NRF node as described earlier, a first network node as described earlier, and a second network node as described earlier.
  • a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform any one or more of the first, second, third, fourth, fifth and sixth methods.
  • a computer program product embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform any one or more of the first, second, third, fourth, fifth and sixth methods.
  • advantageous information sharing is employed that provides the nodes of the network with knowledge needed to avoid useless signalling and processing.
  • the nodes of the network are provided with the knowledge of whether or not the home network is capable of performing a task delegated to the home network. More specifically, the information sharing enables the first network node to be informed about the home network capabilities to perform a task, such as a (re)selection of NFs. This information can be used by the visited network to delegate a task in such a way that useless signalling and processing can be avoided.
  • the visited network can make use of the information to avoid delegating the task to the home network when the home network is not able to process it, or alternatively delegate the task to the SEPP node of the visited network or an SCP node at the border (or edge) of the visited network.
  • Figure 1A-D is a block diagram illustrating different existing systems
  • Figure 2 is a block diagram illustrating a first NRF node according to an embodiment
  • Figures 3 and 4 are block diagrams illustrating methods performed by a first NRF node according to an embodiment
  • Figure 5 is a block diagram illustrating a second NRF node according to an embodiment
  • Figures 6 and 7 are block diagrams illustrating methods performed by a second NRF node according to an embodiment
  • Figure 8 is a block diagram illustrating a first network node according to an embodiment
  • Figure 9 is a block diagram illustrating a method performed by a first network node according to an embodiment
  • Figure 10 is a block diagram illustrating a second network node according to an embodiment
  • Figure 12 is a block diagram illustrating a system according to an example
  • Figures 13 and 14 are signalling diagrams illustrating an exchange of signals in an example system.
  • Figures 15 to 24 are signalling diagrams illustrating an exchange of signals in a system according to an embodiment.
  • a notification request can also be referred to as a request for a notification.
  • users can subscribe to receive a notification.
  • a notification can be any type of notification, such as an event notification (such as an event occurrence notification, e.g. to report an event), an update notification (e.g. to report an update), a monitoring revocation notification, a unified data repository (UDR)-initiated data restoration notification, an N1 notification, or any other type of notification.
  • an event notification such as an event occurrence notification, e.g. to report an event
  • an update notification e.g. to report an update
  • a monitoring revocation notification e.g. to report an update
  • UDR unified data repository
  • any reference to a node “initiating transmission” will be understood to mean that the node (e.g. processing circuitry of the node) can be configured to itself transmit (e.g. via a communications interface of the node) or can be configured to cause another node to transmit.
  • the techniques described herein can be used in respect of any network, such as any communications or telecommunications network, e.g. cellular network.
  • the network may be a fifth generation (5G) network or any other generation network.
  • the network may be a core network or a radio access network (RAN).
  • the techniques refer to a home network and a visited network.
  • the home network referred to herein can, for example, be a home public land mobile network (PLMN), i.e. a h-PLMN.
  • the visited network referred to herein can, for example, be a visited PLMN, i.e. a v-PLMN.
  • the techniques described herein are 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 can, for example, be a first network function (NF) node or a first service communication proxy (SCP) node.
  • the first SCP node is a node that is configured to operate as an SCP between the first NF node and the second NRF node.
  • the second network node can, for example, be a second NF node or a first security edge protection proxy (SEPP) node.
  • SEPP security edge protection proxy
  • An NF is a third generation partnership project (3GPP) adopted, or 3GPP defined, processing function in a network, which has defined functional behaviour and 3GPP defined interfaces.
  • An NF can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the term “node” in relation to an “NF node” will be understood to cover each of these scenarios.
  • references to an NF node may refer to, for example, an instance of an NF node and, similarly, references to a plurality of NF nodes may refer to (for example, functionally equivalent) instances of NF nodes.
  • the terms “NF” and “NF instance” may be used interchangeably.
  • Figure 2 illustrates a first NRF node 50 of a home network of a first NF node in accordance with an embodiment.
  • the first NRF node 50 is for managing information exchange between networks.
  • the first NRF node 50 referred to herein can refer to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with the second NRF node referred to herein, the second network node referred to herein, and/or with other nodes or equipment to enable and/or to perform the functionality described herein.
  • the first NRF node 50 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM).
  • the first NRF node 50 comprises processing circuitry (or logic) 52.
  • the processing circuitry 52 controls the operation of the first NRF node 50 and can implement the method described herein in respect of the first NRF node 50.
  • the processing circuitry 52 can be configured or programmed to control the first NRF node 50 in the manner described herein.
  • the processing circuitry 52 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules.
  • each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the first NRF node 50.
  • the processing circuitry 52 can be configured to run software to perform the method described herein in respect of the first NRF node 50.
  • the software may be containerised according to some embodiments.
  • the processing circuitry 52 may be configured to run a container to perform the method described herein in respect of the first NRF node 50.
  • the processing circuitry 52 of the first NRF node 50 is configured to provide information to a second NRF node.
  • a visited network of a first NF node comprises the second NRF node and a home network of the first NF node comprises the first NRF node 50. The information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the processing circuitry 52 of the first NRF node 50 is configured to acquire information from a memory of the first NRF node 50 or from a second network node.
  • the second network node is a second NF node or a first security edge protection proxy (SEPP) node.
  • SEPP security edge protection proxy
  • a home network of a first NF node comprises the second network node and the first NRF node 50. The information is indicative of whether the home network is capable of performing a task delegated to the home network from a visited network of the first NF node.
  • the first NRF node 50 may optionally comprise a memory 54.
  • the memory 54 of the first NRF node 50 can comprise a volatile memory or a non-volatile memory.
  • the memory 54 of the first NRF node 50 may comprise a non-transitory media. Examples of the memory 54 of the first NRF node 50 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and/or any other memory.
  • RAM random access memory
  • ROM read only memory
  • CD compact disk
  • DVD digital versatile disk
  • the processing circuitry 52 of the first NRF node 50 can be communicatively coupled (e.g. connected) to the memory 54 of the first NRF node 50.
  • the memory 54 of the first NRF node 50 may be for storing program code or instructions which, when executed by the processing circuitry 52 of the first NRF node 50, cause the first NRF node 50 to operate in the manner described herein in respect of the first NRF node 50.
  • the memory 54 of the first NRF node 50 may be configured to store program code or instructions that can be executed by the processing circuitry 52 of the first NRF node 50 to cause the first NRF node 50 to operate in accordance with the method described herein in respect of the first NRF node 50.
  • the memory 54 of the first NRF node 50 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 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 similar, that are described herein.
  • the first NRF node 50 may optionally comprise a communications interface 56.
  • the communications interface 56 of the first NRF node 50 can 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 communications interface 56 of the first NRF node 50 may be operable to allow the processing circuitry 52 of the first NRF node 50 to communicate with the memory 54 of the first NRF node 50 and/or vice versa. Similarly, the communications interface 56 of the first NRF node 50 may be operable to allow the processing circuitry 52 of the first NRF node 50 to communicate with any one or more nodes (e.g. the second NRF node referred to herein, and/or the second network node referred to herein) and/or any other node.
  • the communications interface 56 of the first NRF node 50 can be configured to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 52 of the first NRF node 50 may be configured to control the communications interface 56 of the first NRF node 50 to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • first NRF node 50 is illustrated in Figure 2 as comprising a single memory 54, it will be appreciated that the first NRF node 50 may comprise at least one memory (i.e. a single memory or a plurality of memories) 54 that operate in the manner described herein.
  • first NRF node 50 is illustrated in Figure 2 as comprising a single communications interface 56, it will be appreciated that the first NRF node 50 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 56 that operate in the manner described herein.
  • Figure 2 only shows the components required to illustrate an embodiment of the first NRF node 50 and, in practical implementations, the first NRF node 50 may comprise additional or alternative components to those shown.
  • Figure 3 illustrates a first method performed by a first NRF node 50 of a home network of a first NF node in accordance with an embodiment.
  • the first method is for managing information exchange between networks.
  • the first NRF node 50 described earlier with reference to Figure 2 can be configured to operate in accordance with the first method of Figure 3.
  • the first method can be performed by or under the control of the processing circuitry 52 of the first NRF node 50 according to some embodiments.
  • a visited network of a first NF node comprises the second NRF node and a home network of the first NF node comprises the first NRF node 50.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the information may be provided in response to receiving a first message from the second NRF node.
  • the first message may comprise a first request that is a request for the information and/or a second request that is a request to discover one or more second NF nodes of the home network.
  • the first message may comprise an identifier (e.g. plmn-id) that identifies the visited network.
  • providing the information to the second NRF node may comprises initiating transmission of a second message towards the second NRF node, wherein the second message comprises the information.
  • the information may be provided in a profile of a second NF node of the home network or a profile of a first SEPP node of the home network.
  • the first method may comprise storing the information (e.g. in a memory 54) at the first NRF node 50.
  • the first NF node may be an NF node of a consumer or the first NF node may be an NF node of a producer.
  • the task may be to select one or more second NF nodes of the home network.
  • the first NF node may be an NF node of a consumer and the task may be to select one or more second NF nodes of a producer to provide a service requested by the first NF node.
  • the first NF node may be an NF node of a producer and the task may be to select one or more second NF nodes of a consumer to provide a notification requested by the first NF node.
  • Figure 4 illustrates a second method performed by a first NRF node 50 of a home network of a first NF node in accordance with an embodiment.
  • the second method is for managing information exchange between networks.
  • the first NRF node 50 described earlier with reference to Figure 2 can be configured to operate in accordance with the second method of Figure 4.
  • the second method can be performed by or under the control of the processing circuitry 52 of the first NRF node 50 according to some embodiments.
  • information is acquired from a memory of the first NRF node 50 or from a second network node.
  • the second network node is a second NF node or a first SEPP node.
  • a home network of a first NF comprises the second network node and the first NRF node 50.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from a visited network of the first NF node.
  • acquiring the information may comprise receiving the information.
  • the information may be acquired in a profile of the second network node.
  • the information may be acquired from the second network node with a request to register the profile at the first NRF node 50.
  • the second method may comprise storing the information (e.g. in a memory 54) at the first NRF node 50.
  • Figure 5 illustrates a second NRF node 30 of a visited network of a first NF node in accordance with an embodiment.
  • the second NRF node 30 is for managing information exchange between networks.
  • the second NRF node 30 referred to herein can refer to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with the first NRF node 50 referred to herein, the first network node referred to herein, and/or with other nodes or equipment to enable and/or to perform the functionality described herein.
  • the second NRF node 30 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM).
  • the second NRF node 30 comprises processing circuitry (or logic) 32.
  • the processing circuitry 32 controls the operation of the second NRF node 30 and can implement the method described herein in respect of the second NRF node 30.
  • the processing circuitry 32 can be configured or programmed to control the second NRF node 30 in the manner described herein.
  • the processing circuitry 32 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules.
  • each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the second NRF node 30.
  • the processing circuitry 32 can be configured to run software to perform the method described herein in respect of the second NRF node 30.
  • the software may be containerised according to some embodiments.
  • the processing circuitry 32 may be configured to run a container to perform the method described herein in respect of the second NRF node 30.
  • the processing circuitry 32 of the second NRF node 30 is configured to acquire information from a first NRF node 50.
  • a home network of a first NF node comprises the first NRF node 50 and a visited network of the first NF node comprises the second NRF node 30.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the second NRF node 30 may optionally comprise a memory 34.
  • the memory 34 of the second NRF node 30 can comprise a volatile memory or a non-volatile memory.
  • the memory 34 of the second NRF node 30 may comprise a non-transitory media. Examples of the memory 34 of the second NRF node 30 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and/or any other memory.
  • the processing circuitry 32 of the second NRF node 30 can be communicatively coupled (e.g.
  • the memory 34 of the second NRF node 30 may be for storing program code or instructions which, when executed by the processing circuitry 32 of the second NRF node 30, cause the second NRF node 30 to operate in the manner described herein in respect of the second NRF node 30.
  • the memory 34 of the second NRF node 30 may be configured to store program code or instructions that can be executed by the processing circuitry 32 of the second NRF node 30 to cause the second NRF node 30 to operate in accordance with the method described herein in respect of the second NRF node 30.
  • the memory 34 of the second NRF node 30 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 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, notifications, signals, or similar, that are described herein.
  • the second NRF node 30 may optionally comprise a communications interface 36.
  • the communications interface 36 of the second NRF node 30 can be communicatively coupled (e.g. connected) to the processing circuitry 32 of the second NRF node 30 and/or the memory 34 of the second NRF node 30.
  • the communications interface 36 of the second NRF node 30 may be operable to allow the processing circuitry 32 of the second NRF node 30 to communicate with the memory 34 of the second NRF node 30 and/or vice versa.
  • the communications interface 36 of the second NRF node 30 may be operable to allow the processing circuitry 32 of the second NRF node 30 to communicate with any one or more nodes (e.g.
  • the communications interface 36 of the second NRF node 30 can be configured to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 32 of the second NRF node 30 may be configured to control the communications interface 36 of the second NRF node 30 to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the second NRF node 30 is illustrated in Figure 5 as comprising a single memory 34, it will be appreciated that the second NRF node 30 may comprise at least one memory (i.e. a single memory or a plurality of memories) 34 that operate in the manner described herein.
  • the second NRF node 30 is illustrated in Figure 5 as comprising a single communications interface 36, it will be appreciated that the second NRF node 30 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 36 that operate in the manner described herein.
  • Figure 5 only shows the components required to illustrate an embodiment of the second NRF node 30 and, in practical implementations, the second NRF node 30 may comprise additional or alternative components to those shown.
  • Figure 6 illustrates a third method performed by a second NRF node 30 of a visited network of a first NF node in accordance with an embodiment.
  • the third method is for managing information exchange between networks.
  • the second NRF node 30 described earlier with reference to Figure 5 can be configured to operate in accordance with the third method of Figure 6.
  • the third method can be performed by or under the control of the processing circuitry 32 of the second NRF node 30 according to some embodiments.
  • a home network of a first NF node comprises the first NRF node 50 and a visited network of the first NF node comprises the second NRF node 30.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the information may be acquired in response to transmitting a first message towards the first NRF node 50.
  • the first message may comprise a first request that is a request for the information and/or a second request that is a request to discover one or more second NF nodes of the home network.
  • the first message may comprise an identifier that identifies the visited network.
  • acquiring the information from the first NRF node 50 may comprise receiving a second message from the first NRF node 50, wherein the second message comprises the information.
  • the information may be acquired in a profile of a second NF node of the home network or a profile of a first SEPP node of the home network.
  • Figure 7 illustrates a fourth method performed by a second NRF node 30 of a visited network of a first NF node in accordance with an embodiment.
  • the fourth method is for managing information exchange between networks.
  • the second NRF node 30 described earlier with reference to Figure 5 can be configured to operate in accordance with the fourth method of Figure 7.
  • the fourth method can be performed by or under the control of the processing circuitry 32 of the second NRF node 30 according to some embodiments.
  • the first network node is a first NF node or a first SCP node that is configured to operate as an SCP between the first NF node and the second NRF node 30.
  • a visited network of the first NF node comprises the second NRF node 30 and the first network node.
  • the information is indicative of whether a home network of the first NF node is capable of performing a task delegated to the home network from the visited network.
  • the information may be provided in response to receiving a second message from a first NRF node 50, wherein the second message comprises the information.
  • providing the information to the first network node may comprise initiating transmission of a third message towards the first network node, wherein the third message comprises the information.
  • the information may be provided in a profile of a second NF node of the home network or a profile of a first SEPP node of the home network.
  • Figure 8 illustrates a first network node 10, 20 of a visited network of a first NF node in accordance with an embodiment.
  • the first network node 10, 20 is for managing information exchange between networks.
  • the first network node 10, 20 may be the first NF node 10 or a first SCP node 20.
  • the first SCP node 20 can be a node that is configured to operate as an SCP between the first NF node 10 and the second NRF node 30.
  • the first NF node 10 referred to herein can be a wireless device, e.g. a user equipment (UE).
  • UE user equipment
  • the first network node 10, 20 referred to herein can refer to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with the second NRF node 30 referred to herein, the first NF node 10 referred to herein (in embodiments where the first network node is the first SCP node 20), the first SCP node 20 referred to herein (in embodiments where the first network node is the first NF node 10) and/or with other nodes or equipment to enable and/or to perform the functionality described herein.
  • the first network node 10, 20 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM).
  • the first network node 10, 20 comprises processing circuitry (or logic) 12.
  • the processing circuitry 12 controls the operation of the first network node 10, 20 and can implement the method described herein in respect of the first network node 10, 20.
  • the processing circuitry 12 can be configured or programmed to control the first network node 10, 20 in the manner described herein.
  • the processing circuitry 12 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules.
  • each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the first network node 10, 20.
  • the processing circuitry 12 can be configured to run software to perform the method described herein in respect of the first network node 10, 20.
  • the software may be containerised according to some embodiments.
  • the processing circuitry 12 may be configured to run a container to perform the method described herein in respect of the first network node 10, 20.
  • the processing circuitry 12 of the first network node 10, 20 is configured to acquire information from a second NRF node 30.
  • the first network node 10, 20 is a first NF node 10 or a first SCP node 20 that is configured to operate as an SCP between the first NF node 10 and the second NRF node 30.
  • a visited network of the first NF node 10 comprises the second NRF node 30 and the first network node 10, 20.
  • the information is indicative of whether a home network of the first NF node 10 is capable of performing a task delegated to the home network from the visited network.
  • the first network node 10, 20 may optionally comprise a memory 14.
  • the memory 14 of the first network node 10, 20 can comprise a volatile memory or a non-volatile memory.
  • the memory 14 of the first network node 10, 20 may comprise a non-transitory media. Examples of the memory 14 of the first network node 10, 20 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and/or any other memory.
  • RAM random access memory
  • ROM read only memory
  • CD compact disk
  • DVD digital versatile disk
  • the processing circuitry 12 of the first network node 10, 20 can be communicatively coupled (e.g. connected) to the memory 14 of the first network node 10, 20.
  • the memory 14 of the first network node 10, 20 may be for storing program code or instructions which, when executed by the processing circuitry 12 of the first network node 10, 20, cause the first network node 10, 20 to operate in the manner described herein in respect of the first network node 10, 20.
  • the memory 14 of the first network node 10, 20 may be configured to store program code or instructions that can be executed by the processing circuitry 12 of the first network node 10, 20 to cause the first network node 10, 20 to operate in accordance with the method described herein in respect of the first network node 10, 20.
  • the memory 14 of the first network node 10, 20 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 12 of the first network node 10, 20 may be configured to control the memory 14 of the first network node 10, 20 to store any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the first network node 10, 20 may optionally comprise a communications interface 16.
  • the communications interface 16 of the first network node 10, 20 can be communicatively coupled (e.g. connected) to the processing circuitry 12 of the first network node 10, 20 and/or the memory 14 of the first network node 10, 20.
  • the communications interface 16 of the first network node 10, 20 may be operable to allow the processing circuitry 12 of the first network node 10, 20 to communicate with the memory 14 of the first network node 10, 20 and/or vice versa.
  • the communications interface 16 of the first network node 10, 20 may be operable to allow the processing circuitry 12 of the first network node 10, 20 to communicate with any one or more nodes (e.g.
  • the first NF node 10 in embodiments where the first network node is the first SCP node 20, and/or the first SCP node 20 referred to herein in embodiments where the first network node is the first NF node 10) and/or any other node.
  • the communications interface 16 of the first network node 10, 20 can be configured to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 12 of the first network node 10, 20 may be configured to control the communications interface 16 of the first network node 10, 20 to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • first network node 10, 20 is illustrated in Figure 8 as comprising a single memory 14, it will be appreciated that the first network node 10, 20 may comprise at least one memory (i.e. a single memory or a plurality of memories) 14 that operate in the manner described herein.
  • first network node 10, 20 is illustrated in Figure 8 as comprising a single communications interface 16
  • first network node 10, 20 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 16 that operate in the manner described herein.
  • Figure 8 only shows the components required to illustrate an embodiment of the first network node 10, 20 and, in practical implementations, the first network node 10, 20 may comprise additional or alternative components to those shown.
  • Figure 9 illustrates a fifth method performed by the first network node 10, 20 in accordance with an embodiment.
  • the fifth method is for managing information exchange between networks.
  • the first network node 10, 20 described earlier with reference to Figure 8 can be configured to operate in accordance with the fifth method of Figure 9.
  • the fifth method can be performed by or under the control of the processing circuitry 12 of the first network node 10, 20 according to some embodiments.
  • information is acquired from a second NRF node 30.
  • the first network node 10, 20 is a first NF node 10 or a first SCP node 20 that is configured to operate as an SCP between the first NF node 10 and the second NRF node 30.
  • a visited network of the first NF node 10 comprises the second NRF node 30 and the first network node 10, 20.
  • the information is indicative of whether a home network of the first NF node 10 is capable of performing a task delegated to the home network from the visited network.
  • the information may be acquired in response to transmitting a third message towards the second NRF node 30.
  • the third message may comprise a first request that is a request for the information and/or a second request that is a request to discover one or more second NF nodes of the home network.
  • the third message may comprise an identifier that identifies the visited network.
  • acquiring the information from the second NRF node 30 may comprise receiving a third message from the second NRF node 30, wherein the third message comprises the information.
  • the information may be acquired in a profile of a second NF node of the home network or a profile of a first SEPP node of the home network.
  • the fifth method may comprise determining, based on the information, whether the home network is capable of performing the task.
  • the fifth method may comprise performing the task or delegating the task to a second SEPP node of the visited network or a second SCP node of the visited network.
  • the second SCP node can be configured to operate as an SCP between the first network node 10, 20 and the second SEPP node.
  • the second SCP node may be the closest SCP node of the visited network to the second SEPP node.
  • Figure 10 illustrates a second network node 42, 70, 80 of a home network of a first NF node 10 in accordance with an embodiment.
  • the second network node 42, 70, 80 is for managing information exchange between networks.
  • the second network node 42, 70, 80 referred to herein can refer to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with the first NRF node 50 referred to herein, the second network node referred to herein, the second SCP node referred to herein, any second NF node referred to herein, and/or with other nodes or equipment to enable and/or to perform the functionality described herein.
  • the second network node 42, 70, 80 referred to herein can, for example, be a physical node (e.g. a physical machine or server) or a virtual node (e.g. a virtual machine, VM).
  • the second network node 42, 70, 80 comprises processing circuitry (or logic) 72.
  • the processing circuitry 72 controls the operation of the second network node 42, 70, 80 and can implement the method described herein in respect of the second network node 42, 70, 80.
  • the processing circuitry 72 can be configured or programmed to control the second network node 42, 70, 80 in the manner described herein.
  • the processing circuitry 72 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules.
  • each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the second network node 42, 70, 80.
  • the processing circuitry 72 can be configured to run software to perform the method described herein in respect of the second network node 42, 70, 80.
  • the software may be containerised according to some embodiments.
  • the processing circuitry 72 may be configured to run a container to perform the method described herein in respect of the second network node 42, 70, 80.
  • the processing circuitry 72 of the second network node 42, 70, 80 is configured to provide information to a first NRF node 50.
  • the second network node is a second NF node 70, 80 or a first SEPP node 42 and a home network of a first N F node 10 comprises the second network node 42, 70, 80 and the first NRF node 50.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from a visited network of the first NF node.
  • the processing circuitry 72 of the second network node 42, 70, 80 is configured to initiate transmission of a request towards a second network node of the home network in response to receiving the request.
  • the request is received with a dummy address of a second NF node that signals that the request is to be transmitted towards the second network node without an address of the second NF node.
  • the request is transmitted towards the second network node without the address.
  • the second network node 42, 70, 80 may optionally comprise a memory 74.
  • the memory 74 of the second network node 42, 70, 80 can comprise a volatile memory or a non-volatile memory.
  • the memory 74 of the second network node 42, 70, 80 may comprise a non-transitory media. Examples of the memory 74 of the second network node 42, 70, 80 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital versatile disk (DVD), and/or any other memory.
  • RAM random access memory
  • ROM read only memory
  • CD compact disk
  • DVD digital versatile disk
  • the processing circuitry 72 of the second network node 42, 70, 80 can be communicatively coupled (e.g. connected) to the memory 74 of the second network node 42, 70, 80.
  • the memory 74 of the second network node 42, 70, 80 may be for storing program code or instructions which, when executed by the processing circuitry 72 of the second network node 42, 70, 80, cause the second network node 42, 70, 80 to operate in the manner described herein in respect of the second network node 42, 70, 80.
  • the memory 74 of the second network node 42, 70, 80 may be configured to store program code or instructions that can be executed by the processing circuitry 72 of the second network node 42, 70, 80 to cause the second network node 42, 70, 80 to operate in accordance with the method described herein in respect of the second network node 42, 70, 80.
  • the memory 74 of the second network node 42, 70, 80 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 72 of the second network node 42, 70, 80 may be configured to control the memory 74 of the second network node 42, 70, 80 to store any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the second network node 42, 70, 80 may optionally comprise a communications interface 76.
  • the communications interface 76 of the second network node 42, 70, 80 can be communicatively coupled (e.g. connected) to the processing circuitry 72 of the second network node 42, 70, 80 and/or the memory 74 of the second network node 42, 70, 80.
  • the communications interface 76 of the second network node 42, 70, 80 may be operable to allow the processing circuitry 72 of the second network node 42, 70, 80 to communicate with the memory 74 of the second network node 42, 70, 80 and/or vice versa.
  • the communications interface 76 of the second network node 42, 70, 80 may be operable to allow the processing circuitry 72 of the second network node 42, 70, 80 to communicate with any one or more nodes (e.g. the first NRF node 50 referred to herein) and/or any other node.
  • the communications interface 76 of the second network node 42, 70, 80 can be configured to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the processing circuitry 72 of the second network node 42, 70, 80 may be configured to control the communications interface 76 of the second network node 42, 70, 80 to transmit and/or receive any of the information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
  • the second network node 42, 70, 80 is illustrated in Figure 10 as comprising a single memory 74, it will be appreciated that the second network node 42, 70, 80 may comprise at least one memory (i.e. a single memory or a plurality of memories) 74 that operate in the manner described herein.
  • the second network node 42, 70, 80 is illustrated in Figure 10 as comprising a single communications interface 76, it will be appreciated that the second network node 42, 70, 80 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 76 that operate in the manner described herein.
  • Figure 10 only shows the components required to illustrate an embodiment of the second network node 42, 70, 80 and, in practical implementations, the second network node 42, 70, 80 may comprise additional or alternative components to those shown.
  • Figure 11 illustrates a sixth method performed by a second network node 42, 70, 80 of a home network of a first NF node 10 in accordance with an embodiment.
  • the sixth method is for managing information exchange between networks.
  • the second network node 42, 70, 80 described earlier with reference to Figure 10 can be configured to operate in accordance with the sixth method of Figure 11.
  • the sixth method can be performed by or under the control of the processing circuitry 72 of the second network node 42, 70, 80 according to some embodiments.
  • the second network node is a second NF node 70, 80 or a first SEPP node 42 and a home network of a first NF node 10 comprises the second network node 42, 70, 80 and the first NRF node 50.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from a visited network of the first NF node.
  • providing the information to the first NRF node 50 may comprise initiating transmission of the information towards the first NRF node 50.
  • the information may be provided in a profile of the second network node 42, 70, 80.
  • the information may be provided with a request to register the profile at the first NRF node 50.
  • the first NF node 10 referred to herein may be an NF node 10 of a consumer. In other embodiments, the first NF node 10 referred to herein may be an NF node of a producer. 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 an NF node of a consumer and the task referred to herein may be to select one or more second NF nodes 70, 80 of a producer to provide a service requested by the first NF node 10.
  • the first NF node 10 referred to herein may be an NF node of a producer and the task referred to herein may be to select one or more second NF nodes 70, 80 of a consumer to provide a notification requested by the first NF node 10.
  • the first NF node 10 and/or the first SCP node 20 can be informed of the home network capabilities to perform a task (e.g. a (re)selection of second NF nodes) in data returned by the first NRF node 50.
  • a task e.g. a (re)selection of second NF nodes
  • the visited network from the home network, about whether the home network supports delegation of a task (e.g. a (re)selection of second NF nodes), such as in case of indirect communication.
  • New data may provide the visited network capabilities. In some embodiments, this new data can be inserted (by different means) in the data returned by the first NRF node 50.
  • the second NF node(s) or first SEPP node 42 of the home network registers the new data (at NRF registration).
  • the visited network does not discover the profile of the first SEPP node 42 of the home network, since the discovery is routed from the first NRF node of the home network to second NRF node of the visited network via the SEPP node (i.e. the second SEPP node 44 of the visited network and the first SEPP node 42 of the home network) already.
  • the SEPP profile is expected to be used intra-network (e.g. intra- PLMN) only.
  • the embodiment according to Variant 1 requires new SEPP information to be registered in the first NRF node 50 of the home network.
  • the new data can be inserted by the first NRF node 50 itself (e.g. based on configuration).
  • the new data can be inserted in the NF profile of one or more second NF nodes (Variant 2-A), or the new data can be inserted in an SEPP profile (Variant 2-B).
  • the new data can be inserted by the SEPP node itself (e.g. based on configuration) in the discovery response.
  • the new data can be inserted in the NF profile of one or more second NF nodes (Variant 3-A) or the new data can be inserted in an SEPP profile (Variant 3-B).
  • a new service can be provided by the first NRF node 50 to specifically provide the home network capabilities. In this way, information does not need to be conveyed as part of the existing profiles (returned in the discovery response). Instead, the new data can be included in a new service response. Specifically, a new data structure may be defined, e.g. PLMN data.
  • the visited network advantageously knows whether the home network is able to process a request with delegation of a task (e.g. (re)selection of second NF nodes). According to some embodiments, based on this knowledge, the visited network may only perform delegation of the logic that the home network will be able to (e.g. properly) execute.
  • the home network may perform one of the following three options: a) not delegate the task (and optionally instead follow state of the art behaviour); b) delegate the task to the visited network (e.g. the second SEPP node 44 of the visited network can take the role of an SCP, being able to perform the task); or c) delegate the task to a specific SCP of the visited network that may be defined as a kind of “border” SCP, i.e. it acts as the last SCP before the second SEPP node 44 of the visited network.
  • This “border SCP” is placed as close as possible to the second SEPP node 44 of the visited network, in order to minimise signalling paths (e.g. if reselection is required).
  • a method performed by the system comprises the method described herein in respect of any two or more of the first NRF node 50, the second NRF node 30, the first network node 10, 20, and the second network node 42, 70, 80.
  • FIG 12 illustrates a system according to an 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 can, for example, be an NF node of a consumer (NFc).
  • the visited network comprises at least one first NF node (NFc), a first SCP node (SCPx), and a first SEPP node (vSEPP)
  • 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 can, for example, be at least one NF node of a producer (NFp).
  • the circles 1 , 2, 3 represent the different pieces of information.
  • the first circle 1 represents information about a selection of service producer instance candidates.
  • the second circle 2 represents information about an initial selection of one service producer instance.
  • the third circle 3 represents information about a reselection of an alternative service producer instance.
  • Three different alternatives of delegation of the (re)selection of an NF instance to PLMN are possible.
  • the first alternative is that there is no delegation of (re)selection.
  • the second alternative is that there is delegation of non-functional (re)selection (the information represented by circles 2 and 3).
  • the third alternative is that there is delegation of functional and nonfunctional (re)selection (the information represented by circles 1 , 2 and 3).
  • delegating (re)selection logic has some advantages and it may be requested by some customers in the near future.
  • Figure 13 is a signalling diagram illustrating an exchange of signals in an example system. It illustrates an issue with existing techniques whereby there is an incompatibility between networks.
  • the system illustrated in Figure 13 comprises a first NF node 10, a first SCP node 20 of a visited network (e.g. a visited PLMN) of the first NF node, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 in the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second NF nodes 70, 80 comprise two second NF nodes.
  • the system illustrated in Figure 13 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 13 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 13 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • the plurality of second NF nodes 70, 80 are registered in the first NRF node 50.
  • NF profiles of the plurality of second NF nodes 70, 80 may be stored in (e.g. a memory of) the first NRF node 50.
  • An NF profile of a second NF node can comprise one or more of information indicative of the identity of a second NF node, information indicative of the set in which the second NF node is comprised, and information indicative of one or more services that the second NF node is configured to provide.
  • the first NF node 10 transmits a service request towards the first SCP node 20.
  • the first SCP node 20 thus receives the service request from the first NF node 10.
  • the service request is for a service requested by the first NF node 10.
  • the first NF node 10 may transmit a request that is adapted to indirect communication in Model D (e.g. including parameters to allow the first SCP node 20 to perform initial selection and reselection).
  • the first NF node 10 sends one or more discovery parameters (or factors) required 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 received one or more discovery parameters.
  • the service request can comprise one or more discovery parameters (“sbi-discovery-*”) on the basis of which the first SCP node 20 is to discover one or more second NF nodes.
  • the discovery parameters can contain information for initial functional selection.
  • an NF selection is performed in the visited network.
  • the first SCP node 20 transmits a discovery request towards the second NRF node 30.
  • the second NRF node 30 thus receives the discovery request from the first SCP node 20.
  • the second NRF node 30 transmits the discovery request towards the first NRF node 50 via the SEPP node 40 (i.e. via the second SEPP node 44 and the first SEPP node 42).
  • the first NRF node 50 thus receives the discovery request from the first SCP node 20.
  • the discovery request is a request for information indicative of one or more second NF nodes for providing the service.
  • the discovery request can comprise the one or more discovery parameters (e.g. “sbi-discovery-*”).
  • the first NRF node 50 transmits a discovery response towards the second NRF node 30 via the SEPP node 40 (i.e. via the first SEPP node 42 and the second SEPP node 44).
  • the second NRF node 30 thus receives the discovery response from the first NRF node 50.
  • the second NRF node 30 transmits the discovery response towards the first SCP node 20.
  • the first SCP node 20 thus receives the discovery response from the second NRF node 30.
  • the discovery response comprises information indicative of the plurality of second NF nodes 70, 80 for providing the service.
  • the discovery response can, for example, comprise profiles of the plurality of second NF nodes 70, 80.
  • steps 204 to 210 can involve the discovery of NF profiles. This requires inter-network (e.g. PLMN) communication to acquire the profiles registered in the home network (e.g. home PLMN).
  • inter-network e.g. PLMN
  • the first SCP node 20 selects one or more second NF nodes of the plurality of second NF nodes 70, 80 to which to transmit the service request received from the first NF node 10.
  • the selection can be based on any existing technique and a person skilled in the art will be aware of various techniques in this regard, such as any of those mentioned earlier.
  • it is an SCP node in the home network that performs the initial selection.
  • the first SCP node 20 selects the second NF node 70.
  • the first SCP node 20 may select a second NF node based on cached results.
  • the first SCP node 20 identifies whether the selected second NF node 70 is in another network. That is, the first SCP node 20 identifies whether the selected second NF node 70 is reached via the SEPP node 40. In the embodiment illustrated in Figure 13, the first SCP node 20 identifies that the selected second NF node 70 is reached via the SEPP node 40. The selected second NF node 70 is in the home network of the first NF node 10, whereas the first SCP node 20 is in the visited network of the first NF node 10.
  • the first SCP node 20 delegates (re)selection logic to the home network. For example, once it is known that the service request needs to reach another network (via the SEPP node 40), then the visited network (or, more specifically, the second SEPP node 44) may decide to delegated (re)selection to the home network. The visited network (or, more specifically, the second SEPP node 44) may therefore provide the information required for (re)selection of a second NF node to the home network. That is, it provides the discovery parameters (e.g. sbi-discovery-*).
  • discovery parameters e.g. sbi-discovery-*
  • the first SCP node 20 transmits the service request towards the 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.
  • the request is sent to the SEPP node 40 (or, more specifically, the second SEPP node 44) to reach the corresponding home network of the first NF node 10.
  • the selected target second NF node 70 is included in the target destination (3gpp-Sbi-Target-apiRoot) header.
  • the target destination referred to herein can be the application programming interface (API) root of a uniform resource identifier (URI) for the selected second NF node 70.
  • API application programming interface
  • URI uniform resource identifier
  • the API root of the URI can also be referred to as a “3gpp-Sbi-Target-apiRoot”.
  • the target destination is used in step 218 of Figure 13 towards the second SEPP node 44.
  • the target destination is included in the service request to the second SEPP node 44.
  • the parameters used to discover the possible destination second NF nodes are provided.
  • sbi- discovery-* is provided.
  • the discovery parameters (e.g. sbi-discovery-*) are included in the service request transmitted towards the SEPP node 40 in order to provide information to the home network.
  • the second SEPP node 44 of the visited network establishes an interface (namely, 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.
  • the first SEPP node 42 may decide to forward the discovery parameters (e.g. sbi-discovery-*) headers received. For example, the first SEPP node 42 may forward all received headers or, if it is not specified, the sbi-discovery-* header used for indirect communication may be removed by the first SEPP node 42 according to some implementations.
  • the first SEPP node 42 transmits the service request towards the selected second NF node 70.
  • the selected second NF node 70 thus receives the service request from the first SEPP node 42.
  • the service request transmitted towards the selected second NF node 70 may include the discovery parameters (e.g. sbi-discovery-*), but this information is irrelevant for the second NF node 70.
  • the selected second NF node 70 transmits a response to the service request towards the SEPP node 40 and the SEPP node 40 (or, more specifically, the first SEPP node 42) may thus receive the response from the selected second NF node 70.
  • the response can indicate that the service request is unsuccessful, e.g. that the selected second NF node 70 has failed to successfully execute the service request, or that there has been an error. Alternatively, the error may result in no response or a lack of response.
  • the SEPP node 40 may transmit the response to the first SCP node 20 and the first SCP node 20 may thus receive the response from the SEPP node 40.
  • the first SCP node 20 may transmit the response to the first NF node 10 and the first NF node 10 may thus receive the response from the first SCP node 20.
  • the error is thus propagated to the visited network by way of steps 226 to 230 of Figure 13. Therefore, as illustrated in Figure 13, the delegation of (re)selection is not achieved and an error occurs.
  • Figure 14 is a signalling diagram illustrating an exchange of signals in another example system. It illustrates an issue with existing techniques whereby there is an incompatibility between networks.
  • the system illustrated in Figure 14 comprises a first NF node 10, a first SCP node 20 of a visited network (e.g. a visited PLMN) of the first NF node, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, a second SCP node 90 of the home network, and a plurality of second NF nodes 70, 80 in the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 second SCP node 90 is configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes.
  • the system illustrated in Figure 14 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 14 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • NFc NF node of a (service) consumer
  • NFps NF nodes of a (service) producer
  • the service request of Figure 14 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Steps 304 to 324 of Figure 14 are as described earlier with reference to steps 200 to 220 of Figure 13 respectively.
  • the SEPP node 40 (or, more specifically, the first SEPP node 42) identifies that the home network has a configured second SCP node 90 for the traffic. That is, the SEPP node 40 (or, more specifically, the first SEPP node 42) can identify that indirect communication is at least deployed for inbound roamer traffic (e.g. traffic from the first NF node 10). As such, in some embodiments, the first SEPP node 42 may identify that the service request received at step 322 of Figure 14 is to be sent to the second SCP node 90 instead of the selected second NF node 70 in the home network.
  • Step 328 of Figure 14 is as described earlier with reference to step 222 of Figure 13.
  • the first SEPP node 42 transmits the service request towards the second SCP node 90 instead of towards the selected second NF node 70.
  • the selected second SCP node 90 thus receives the service request from the first SEPP node 42.
  • the service request transmitted towards the second SCP node 90 may include the target destination (e.g. 3gpp-Sbi-Target-apiRoot) and/or the discovery parameters (e.g. sbi-discovery-*).
  • the target destination is the selected second NF node 70.
  • the second SCP node 90 transmits the service request towards the selected second NF node 70.
  • the selected second NF node 70 thus receives the service request from the second SCP node 90.
  • the selected second NF node 70 transmits a response to the service request towards the second SCP node 90.
  • the second SCP node 90 thus receives the response.
  • the response can indicate that the service request is unsuccessful, e.g. that the selected second NF node 70 has failed to successfully execute the service request, or that there has been an error. Alternatively, the error may result in no response or a lack of response.
  • Block 336 of Figure 14 if an error is produced and the second SCP node 90 only supports Model C, the second SCP node 90 is unable to use the discovery parameters (Model D, with functional information, e.g.
  • the home network does not have any means by which it can find an alternative second NF node. Therefore, it is not possible for (re)selection to be performed in the home network, but the visited network has delegated this task.
  • the second SCP node 90 may transmit the response to the SEPP node 40 and the SEPP node 40 (or, more specifically, the first SEPP node 42) may thus receive the response from the selected second NF node 70.
  • Steps 340 and 342 of Figure 14 are as described earlier with reference to steps 228 and 230 of Figure 13 respectively.
  • Figure 15 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 1 or, more specifically, Variant 1-A.
  • the system illustrated in Figure 15 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second NF nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 15 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 15 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 15 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 15 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • the second NF nodes 70, 80 provide information to the first NRF node 50 and thus the first NRF node 50 acquires the information.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the information may also be referred to herein as capability information.
  • the capability information may be provided to the first NRF node
  • the capability information can be included in the profile of one or more second NF nodes 70, 80 and/or the first SEPP node 42.
  • information about the support of the home network of (re)selection of NF capabilities may be included in such profiles.
  • Steps 402 to 406 of Figure 15 are as described earlier with reference to steps 202 to 206 of Figure 13 respectively.
  • the first NF node 10 is configured to use indirect communication with Model D.
  • discovery parameters e.g. sbi- discovery-*
  • the discovery parameters can comprise the NF Set.
  • the NF Set is a set of second NF nodes from which one or more second NF nodes are to be selected.
  • the first SCP node 20 is to perform an initial selection of one or more second NF nodes.
  • the first SCP node 20 may acquire the corresponding NF profile(s). Since the first NF node 10 is in another network (which may be known based on information provided in the service request received at step 402), then the second NRF node 30 acquires those NF profile(s) from the corresponding home network. As such, the NRF discovery request is sent via the SEPP node 40 towards the corresponding first NFR node 50.
  • the first NRF node 50 provides the capability information to the second NRF node 30 and the second NRF node 30 thus acquires the capability information. More specifically, the first NRF node 50 transmits the capability information to the second NRF node 30 and the second NRF node 30 thus receives the capability information.
  • the second NRF node 30 provides the capability information to the first SCP node 20 and the first SCP node 20 thus acquires the capability information. More specifically, the second NRF node 30 transmits the capability information to the first SCP node 20 and the first SCP node 20 thus receives the capability information.
  • the capability information can be transmitted in the discovery response.
  • the discovery response can also comprise the acquired NF profile(s).
  • the discovery results can comprise NF profile(s) and those NF profile(s) may comprise the capability information.
  • new capabilities can be included in a profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 16 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 1 or, more specifically, Variant 1-A.
  • the system illustrated in Figure 16 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 16 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 16 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 16 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 16 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Figure 16 is similar to Figure 15, except that Figure 16 corresponds to an embodiment where indirect communication in the visited network follows Model C with target or Model C with target + Set.
  • Model C with target is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target-apiRoot) in a request
  • Model C with target + Set is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target- apiRoot) and an NF Set in a request.
  • This request will be sent after step 510 of Figure 16, from the first NF node 10 to the first SCP node 20.
  • the first NF node 10 Prior to that, the first NF node 10 needs to know whether a task (e.g. (re)selection) may be delegated to the home network. That is, the first NF node 10 needs to know the home network capabilities related to that task.
  • a task e.g. (re)selection
  • Steps 500 and 502 to 508 of Figure 16 are as described earlier with reference to steps 400 and 404 to 410 of Figure 15 respectively. However, in the embodiment illustrated in Figure 16, it is the first NF node 10 that transmits the discovery request (at step 502 of Figure 16) and receives the capability information, e.g. in the discovery response (at step 508 of Figure 16).
  • FIG 16 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 1 or, more specifically, Variant 1-B.
  • the system illustrated in Figure 17 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 17 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 17 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 17 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 17 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • the first SEPP node 42 provides information to the first NRF node 50 and thus the first NRF node 50 acquires the information.
  • the information is indicative of whether the home network is capable of performing a task delegated to the home network from the visited network.
  • the information may also be referred to herein as capability information.
  • the capability information may be provided to the first NRF node 50 by registering an SEPP profile in the first NRF node 50.
  • the capability information can be included in the profile of the first SEPP node 42. For example, information about the support of the home network of (re)selection of NF capabilities may be included in such a profile.
  • Steps 602 to 606 of Figure 17 are as described earlier with reference to steps 202 to 206 of Figure 13 respectively.
  • the first NF node 10 is configured to use indirect communication with Model D.
  • discovery parameters e.g. sbi- discovery-*
  • the discovery parameters can comprise the NF Set.
  • the NF Set is a set of second NF nodes from which one or more second NF nodes are to be selected.
  • the first SCP node 20 acquires the capability information using the NRF discovery service to obtain new data (e.g. named plmn- capabilities) included in the SEPP profile.
  • new data e.g. named plmn- capabilities
  • Steps 608 and 610 of Figure 17 are as described earlier with reference to steps 408 and 410 of Figure 15 respectively, except that the discovery response can comprise the acquired SEPP profile, rather than acquired NF profile(s).
  • the discovery results can comprise an SEPP profile and that SEPP profile may comprise the capability information.
  • new capabilities can be included in an SEPP profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 18 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 1 or, more specifically, Variant 1-B.
  • the system illustrated in Figure 18 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 18 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 18 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 18 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • NFc service consumer
  • NFps service producer
  • the service request of Figure 18 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Figure 18 is similar to Figure 17, except that Figure 18 corresponds to an embodiment where indirect communication in the visited network follows Model C with target or Model C with target + Set.
  • Model C with target is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target-apiRoot) in a request
  • Model C with target + Set is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target- apiRoot) and an NF Set in a request.
  • This request will be sent after step 710 of Figure 18, from the first NF node 10 to the first SCP node 20.
  • the first NF node 10 Prior to that, the first NF node 10 needs to know whether a task (e.g. (re)selection) may be delegated to the home network. That is, the first NF node 10 needs to know the home network capabilities related to that task.
  • a task e.g. (re)selection
  • Step 700 of Figure 18 is as described earlier with reference to step 600 of Figure 17.
  • Steps 702 to 708 of Figure 18 are as described earlier with reference to steps 604 to 610 of Figure 17 respectively, except that it is the first NF node 10 that transmits the discovery request (at step 702 of Figure 18) and receives the capability information, e.g. in the discovery response (at step 708 of Figure 18).
  • the discovery response can comprise the acquired SEPP profile, rather than acquired NF profile(s).
  • the discovery results can comprise an SEPP profile and that SEPP profile may comprise the capability information.
  • FIG 18 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 2.
  • the system illustrated in Figure 19 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 19 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 19 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 19 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • NFc NF node of a (service) consumer
  • NFps NF nodes of a (service) producer
  • the service request of Figure 19 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Step 800 of Figure 800 of Figure 19 is as described earlier with reference to step 400 of Figure 15.
  • Steps 802 to 806 of Figure 19 are as described earlier with reference to steps 402 to 406 of Figure 15 respectively and steps 602 to 606 of Figure 17 respectively.
  • the first NRF node 50 can insert the capability information into the discovery response.
  • the capability information may be included in NF profile(s) and/or an SEPP profile in the discovery response.
  • Steps 810 and 812 of Figure 19 are as described earlier with reference to steps 408 and 410 of Figure 15 respectively and steps 608 and 610 of Figure 17 respectively, except that the discovery response can comprise the acquired NF profile(s) and/or the SEPP profile.
  • the discovery results can comprise NF profile(s) and/or an SEPP profile, which may comprise the capability information.
  • the first NRF node 50 can insert new capabilities in the discovery response.
  • new capabilities can be included in one or more NF profiles and/or an SEPP profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 20 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 2.
  • the system illustrated in Figure 20 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 20 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 20 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 20 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 20 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Figure 20 is similar to Figure 19, except that Figure 20 corresponds to an embodiment where indirect communication in the visited network follows Model C with target or Model C with target + Set.
  • Model C with target is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target-apiRoot) in a request
  • Model C with target + Set is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target- apiRoot) and an NF Set in a request.
  • This request will be sent after step 912 of Figure 20, from the first NF node 10 to the first SCP node 20.
  • the first NF node 10 Prior to that, the first NF node 10 needs to know whether a task (e.g. (re)selection) may be delegated to the home network. That is, the first NF node 10 needs to know the home network capabilities related to that task.
  • a task e.g. (re)selection
  • Step 900 of Figure 20 is as described earlier with reference to step 800 of Figure 19.
  • Steps 902, 904, 908 and 910 of Figure 20 are as described earlier with reference to steps 702, 704, 706 and 708 of Figure 18 respectively, except that the discovery response can comprise the acquired NF profile(s) and/or SEPP profile.
  • the discovery results can comprise NF profile(s) and/or an SEPP profile, which may comprise the capability information.
  • Step 906 of Figure 20 is as described earlier with reference to step 808 of Figure 19.
  • new capabilities can be included in one or more NF profiles and an SEPP profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 21 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 3.
  • the system illustrated in Figure 21 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 21 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 21 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 21 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 21 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Step 1000 of Figure 21 is as described earlier with reference to step 800 of Figure 19.
  • Steps 1002 to 1006 and 1010 to 1012 of Figure 21 are as described earlierwith reference to steps 802 to 806 and 810 to 812 of Figure 19 respectively.
  • Step 1008 of Figure 21 is as described earlier with reference to step 808 of Figure 19, except that step 1008 of Figure 21 (i.e. the step of inserting the new capability information into the discovery response) is performed by the first SEPP node 42.
  • new capabilities can be included in one or more NF profiles and an SEPP profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 22 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 3.
  • the system illustrated in Figure 22 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 22 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 22 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 22 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 22 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Step 1100 of Figure 22 is as described earlier with reference to step 900 of Figure 20.
  • Steps 1102 to 1104 and 1108 to 1110 of Figure 22 are as described earlier with reference to steps 902 to 904 and 908 to 910 of Figure 20 respectively.
  • Step 1106 of Figure 22 is as described earlier with reference to step 906 of Figure 20, except that step 1106 of Figure 22 (i.e. the step of inserting the new capability information into the discovery response) is performed by the first SEPP node 42.
  • new capabilities can be included in one or more NF profiles and an SEPP profile at registration according to some embodiments.
  • the capabilities of the home network are advantageously known by the first NF node 10.
  • Figure 23 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 4.
  • the system illustrated in Figure 23 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 23 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 23 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 23 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 23 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • the capability information is new data in the first NRF node 50.
  • the capability information may be stored in a memory of the first NRF node 50.
  • the first NRF node 50 may acquire the capability information from its memory.
  • Step 1202 of Figure 23 is as described earlier with reference to step 402 of Figure 15.
  • the first SCP node 20 transmits a request for the capabilities information towards the second NRF node 30.
  • the second NRF node 30 thus receives the request from the first SCP node 20.
  • the second NRF node 30 transmits the request towards the first NRF node 50 via the SEPP node 40 (i.e. via the second SEPP node 44 and the first SEPP node 42).
  • the first NRF node 50 thus receives the request from the first SCP node 20.
  • the first NRF node 50 transmits a response towards the second NRF node 30 via the SEPP node 40 (i.e. via the first SEPP node 42 and the second SEPP node 44).
  • the second NRF node 30 thus receives the response from the first NRF node 50.
  • the second NRF node 30 transmits the response towards the first SCP node 20.
  • the first SCP node 20 thus receives the response from the second NRF node 30.
  • the response comprises the capability information.
  • the new service in the first NRF node 50 provides the new capability information.
  • the new capability information may be provided with a specific network identifier e.g. (plmn-id).
  • new capabilities can be provided by a new NRF service according to some embodiments.
  • the capabilities of the home network are advantageously known by the first SCP node 20.
  • Figure 24 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment. This embodiment is an example of Variant 4.
  • the system illustrated in Figure 24 comprises a first SCP node 20 of a visited network (e.g. a visited PLMN) of a first NF node 10, a second NRF node 30 of the visited network, an SEPP node 40, a first NRF node 50 of a home network (e.g. a home PLMN) of the first NF node 10, and a plurality of second NF nodes 70, 80 of the home network.
  • the SEPP node 40 comprises a first SEPP node 42 of the home network and a second SEPP node 44 of 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 plurality of second N F nodes 70, 80 can be as described earlier with reference to Figures 2 to 11.
  • the system illustrated in Figure 24 can also comprise the first NF node 10 and a second SCP node 90 of the home network.
  • the second SCP node 90 can be configured to operate as an SCP between the first NRF node 50 and the plurality of second NF nodes 70, 80 (and as an SCP between the first SEPP node 42 and the plurality of second NF nodes 70, 80).
  • the plurality of second NF nodes 70, 80 comprise two second NF nodes (i.e. “NF1” and “NF2”). However, it will be understood that the system illustrated in Figure 24 can comprise one or more (i.e. any number of) second NF nodes.
  • a set of second NF nodes (“NF (Set X)”) comprises the plurality of second NF nodes 70, 80.
  • the exchange of signals between the nodes of the system illustrated in Figure 24 will be described in terms of a service request.
  • the plurality of second NF nodes 70, 80 can thus each be configured to provide a service 300, 302.
  • the first NF node 10 can be an NF node of a (service) consumer (NFc) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) producer (NFps).
  • the service request of Figure 24 may be replaced with a notification request.
  • the first NF node 10 can be an NF node of a (service) producer (NFp) and the plurality of second NF nodes can be a plurality of NF nodes of a (service) consumer (NFcs).
  • Figure 24 is similar to Figure 23, except that Figure 24 corresponds to an embodiment where indirect communication in the visited network follows Model C with target or Model C with target + Set.
  • Model C with target is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target-apiRoot) in a request
  • Model C with target + Set is where the first NF node 10 includes a target destination (e.g. 3gpp-Sbi-Target- apiRoot) and an NF Set in a request.
  • Step 1300 of Figure 24 is as described earlier with reference to step 1200 of Figure 23.
  • Steps 1302 to 1308 of Figure 24 are as described earlier with reference to steps 1204 to 1210 of Figure 23 respectively.
  • it is the first NF node 10 that transmits the request (at step 1302 of Figure 24) and receives the capability information, e.g. in the response (at step 1308 of Figure 24).
  • new capabilities can be provided by a new NRF service according to some embodiments.
  • the capabilities of the home network are advantageously known by the first NF node 10.
  • the wireless device referred to herein can be any type of wireless device.
  • Examples of a type of wireless device as referred to herein include, but are not limited to, a user equipment (UE), such as a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehiclemounted wireless terminal device, etc.
  • UE user equipment
  • the wireless device as referred to herein may support device-to-device (D2D) communication, for example, by implementing a third generation partnership project (3GPP) standard for sidelink communication, vehicle-to- vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • 3GPP third generation partnership project
  • V2V vehicle-to- vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • the wireless device as referred to herein may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node.
  • the wireless device as referred to herein may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine type communication
  • the wireless device as referred to herein may be a user equipment (UE), e.g. implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • UE user equipment
  • NB-loT narrow band internet of things
  • the wireless device as referred to herein may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • the wireless device as referred to herein may represent the endpoint of a wireless connection, in which case the wireless device as referred to herein may be referred to as a wireless terminal.
  • the wireless device as referred to herein may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • a computer program comprising instructions which, when executed by processing circuitry (such as the processing circuitry 52 of the first NRF node 50 described earlier, the processing circuitry 32 of the second NRF node 30 described earlier, the processing circuitry 12 of the first network node 10, 20 described earlier, and/or the processing circuitry 72 of the second network node 42, 70, 80 described earlier), cause the processing circuitry to perform at least part of the method described herein.
  • processing circuitry such as the processing circuitry 52 of the first NRF node 50 described earlier, the processing circuitry 32 of the second NRF node 30 described earlier, the processing circuitry 12 of the first network node 10, 20 described earlier, and/or the processing circuitry 72 of the second network node 42, 70, 80 described earlier
  • a computer program product embodied on a non- transitory machine-readable medium, comprising instructions which are executable by processing circuitry (such as the processing circuitry 52 of the first NRF node 50 described earlier, the processing circuitry 32 of the second NRF node 30 described earlier, the processing circuitry 12 of the first network node 10, 20 described earlier, and/or the processing circuitry 72 of the second network node 42, 70, 80 described earlier) to cause the processing circuitry to perform at least part of the method described herein.
  • processing circuitry such as the processing circuitry 52 of the first NRF node 50 described earlier, the processing circuitry 32 of the second NRF node 30 described earlier, the processing circuitry 12 of the first network node 10, 20 described earlier, and/or the processing circuitry 72 of the second network node 42, 70, 80 described earlier
  • a computer program product comprising a carrier containing instructions for causing processing circuitry (such as the processing circuitry 52 of the first NRF node 50 described earlier, the processing circuitry 32 of the second NRF node 30 described earlier, the processing circuitry 12 of the first network node 10, 20 described earlier, and/or the processing circuitry 72 of the second network node 42, 70, 80 described earlier) to perform at least part of the method described herein.
  • the carrier can be any one of an electronic signal, an optical signal, an electromagnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the node functionality described herein can be performed by hardware.
  • any one or more of the first NRF node 50 described herein, the second NRF node 30 described herein, the first network node 10, 20 described herein, and/or the second network node 42, 70, 80 described herein can be a hardware node.
  • optionally at least part or all of the node functionality described herein can be virtualized.
  • the functions performed by any one or more of the first NRF node 50 described herein, the second NRF node 30 described herein, the first network node 10, 20 described herein, and/or the second network node 42, 70, 80 described herein can be implemented in software running on generic hardware that is configured to orchestrate the node functionality.
  • any one or more of the first NRF node 50 described herein, the second NRF node 30 described herein, the first network node 10, 20 described herein, and/or the second network node 42, 70, 80 described herein can be a virtual node.
  • at least part or all of the node functionality described herein may be performed in a network enabled cloud.
  • the node functionality described herein may all be at the same location or at least some of the node functionality may be distributed.
  • the technique described herein can provide the nodes of the network with knowledge of network capabilities. For example, capability information can be exchanged to allow a visited network of an NF node to acquire information about the capabilities of a home network of the NF node.
  • capability information can be exchanged to allow a visited network of an NF node to acquire information about the capabilities of a home network of the NF node.
  • This enables effective delegation of a task from the visited network to the home network. That is, the visited network is aware of the ability of the home network to perform a task delegated to the home network and thus errors associated with an inability to perform tasks in the home network are avoided. This is particularly useful in inter-network (from a visited network to a home network) communication, such as when an NF node is roaming.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de gestion d'échange d'informations entre des réseaux. Le procédé est effectué par un nœud de fonction de référentiel réseau (NRF). Le procédé consiste à fournir (102) des informations à un second nœud NRF. Un réseau visité d'un premier nœud de fonction de réseau (NF) comprend le second nœud NRF et un réseau domestique du premier nœud NF comprend le premier nœud NRF. Les informations indiquent si le réseau domestique est apte ou non à effectuer une tâche déléguée au réseau domestique par le réseau visité.
PCT/EP2024/062164 2023-05-12 2024-05-02 Gestion d'échange d'informations Pending WO2024235664A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP23382448.1 2023-05-12
EP23382448 2023-05-12

Publications (1)

Publication Number Publication Date
WO2024235664A1 true WO2024235664A1 (fr) 2024-11-21

Family

ID=86387402

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/062164 Pending WO2024235664A1 (fr) 2023-05-12 2024-05-02 Gestion d'échange d'informations

Country Status (1)

Country Link
WO (1) WO2024235664A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230110286A1 (en) * 2021-10-08 2023-04-13 Oracle International Corporation Methods, systems, and computer readable media for routing inter-public land mobile network (inter-plmn) messages related to existing subscriptions with network function (nf) repository function (nrf) using security edge protection proxy (sepp)

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230110286A1 (en) * 2021-10-08 2023-04-13 Oracle International Corporation Methods, systems, and computer readable media for routing inter-public land mobile network (inter-plmn) messages related to existing subscriptions with network function (nf) repository function (nrf) using security edge protection proxy (sepp)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security Aspects; Study on security aspects of the 5G Service Based Architecture (SBA) (Release 16)", no. V16.1.0, 25 September 2020 (2020-09-25), pages 1 - 103, XP051961171, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/33_series/33.855/33855-g10.zip 33855-g10.doc> [retrieved on 20200925] *
DEUTSCHE TELEKOM AG ET AL: "Introduction of indirect communication between NF services, and implicit discovery", vol. TSG SA, no. Shenzhen, China; 20190320 - 20190322, 15 March 2019 (2019-03-15), XP051697317, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/TSG%5FSA/TSGS%5F83/Docs/SP%2D190215%2Ezip> [retrieved on 20190315] *
KELLER RALPH ET AL: "The 5G System Roaming Architecture", 17 June 2021 (2021-06-17), pages 1 - 12, XP093177390, Retrieved from the Internet <URL:https://www.ericsson.com/4981f6/assets/local/reports-papers/ericsson-technology-review/docs/2021/roaming-in-the-5g-system.pdf> *

Similar Documents

Publication Publication Date Title
US11265808B2 (en) Adaptive network slice selection
WO2020200268A1 (fr) Procédé et appareil pour la découverte de services
JP2022544488A (ja) ネットワーク機能サービスディスカバリのための方法および装置
JP2024521821A (ja) コアネットワークにおいてネットワーク機能（ｎｆ）高可用性（ｈａ）トポロジ情報を配布するための方法、システム、およびコンピュータ可読媒体
JP7635255B2 (ja) Ｐｄｕセッションの確立のための方法および装置
US20230388776A1 (en) Methods, network function nodes and computer readable media for event subscription management
CN112533177A (zh) 一种提供、发现移动边缘计算的方法及设备、装置、介质
EP4189864B1 (fr) Fourniture de services tenant compte de la fonctionnalité du réseau (nf) basée sur le proxy de communication de services (scp)
WO2023148124A1 (fr) Gestion de session pour sessions pdu redondantes
US11924294B2 (en) Service request handling
US12206746B2 (en) Bound service request handling
US20250184402A1 (en) Service request handling
US20230188625A1 (en) Service request handling
JP2025087748A (ja) 第５世代ネットワークにおけるメッセージ処理
WO2024235664A1 (fr) Gestion d&#39;échange d&#39;informations
WO2024235663A1 (fr) Gestion d&#39;échange d&#39;informations
WO2022238910A1 (fr) Cadriciel pour une gestion dynamique de ressources dans une tranche partagée
US20250141776A1 (en) Message Handling in a Network
WO2022161685A1 (fr) Demande de service et gestion de réponse
WO2022022842A1 (fr) Gestion de demande de service
WO2021233646A1 (fr) Gestion de demande de service
US12452341B2 (en) Methods, systems, and computer readable media for improved network function (NF) discovery between forwarded and forwarding NF repository functions (NRFs) to avoid preemption of NF profiles of producer NFs local to forwarding NRF
WO2024145730A1 (fr) Procédé et appareil pour des applications périphériques
US20250119712A1 (en) Methods, systems, and computer readable media for service aggregation for alternate routing of callback messages
WO2025181298A1 (fr) Gestion d&#39;événements de changement de données

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24722293

Country of ref document: EP

Kind code of ref document: A1