Methods, systems, and computer readable media for providing configurable producer NF internet protocol (IP) address mapping for network function (NF) library function (NRF)
By implementing configurable producer NF IP address mapping rules in the NF library function, the problems of producer NF multi-IP address selection and network address conversion in 5G network are solved, improving network flexibility and maintainability, and reducing the Operational challenges.
Patent Information
- Application Number
- CN202380027474.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-15
- Filing Date
- 2023-02-15
- Publication Date
- 2024-11-05
AI Technical Summary
In 5G networks, the NF profile of the producer NF may contain multiple IP addresses, causing the consumer NF to choose a routable IP address, and there are scalability issues with network address translation and DNS support, resulting in operational challenges and overload.
By implementing configurable producer NF IP address mapping rules in NF library function (NRF), locating producer NF IP address mapping rules using consumer NF parameters, selecting the appropriate IP address or network address translation from the NF profile IP address, provided to consumers NF, supports region-based DNS resolution and load balancing.
It solves the scalability problem of IP address selection and network address translation, reduces the custom logic needs of consumers NF, improves the flexibility and maintainability of the network, and avoids the operational challenges of DNS record updates.
Smart Images

Figure CN118901231A_ABST
Abstract
Description
[0001] Priority declaration
[0002] This application claims the benefit of priority to U.S. Patent Application No. 17 / 672,646, filed on February 15, 2022, the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] The subject matter described herein relates to facilitating efficient communications in 5G and other networks supporting service discovery and Domain Name System (DNS) translation. More specifically, the subject matter described herein relates to providing configurable producer NF IP address mapping for an NRF, including support for selecting from multiple IP addresses configured for the same producer NF and selecting a Network Address Translated (NATed) IP address. Background Art
[0004] In a 5G telecommunications network, a network function that provides a service is referred to as a producer NF or NF service producer. A network function that consumes a service is referred to as a consumer NF or NF service consumer. A network function can be a producer NF, a consumer NF, or both, depending on whether the network function is consuming a service, producing a service, or consuming and producing a service. The terms "producer NF" and "NF service producer" are used interchangeably herein. Similarly, the terms "consumer NF" and "NF service consumer" are used interchangeably herein.
[0005] A given producer NF may have many service endpoints, where a service endpoint is a point of contact for one or more NF instances hosted by the producer NF. A service endpoint is identified by a combination of an Internet Protocol (IP) address and a port number, or a fully qualified domain name (FQDN) that resolves to an IP address and a port number on a network node hosting the producer NF. An NF instance is an instance of a producer NF that provides a service. A given producer NF may include more than one NF instance. It should also be noted that multiple NF instances may share the same service endpoint.
[0006] NF registers with the Network Function Repository Function (NRF). NRF maintains profiles of available NF instances that identify the services supported by each NF instance. The profile of an NF instance is referred to as an NF profile in 3GPP TS29.510. An NF instance can obtain information about other NF instances that have been registered with the NRF through an NF discovery service operation. According to the NF discovery service operation, the consumer NF sends an NF discovery request to the NRF. The NF discovery request includes query parameters, which the NRF uses to locate the NF profile of the producer NF that can provide the service identified by the query parameters. The NF profile is a data structure that defines the type of service provided by the NF instance and the contact and capability information about the NF instance. Therefore, it is desirable that the consumer NF can formulate an NF discovery request with query parameters that are optimized for locating the producer NF that can and is most suitable for providing the service requested by the consumer NF.
[0007] The Service Communication Proxy (SCP) can also call the NF Discovery service operation to learn about the available producer NF instances. The situation where the SCP uses the NF service discovery process on behalf of the consumer NF to obtain information about the producer NF instance is called delegated discovery. The consumer NF connects to the SCP, which load balances the traffic between the producer NF service instances that provide the required service, or directly routes the traffic to the destination producer NF instance. The communication model in which the consumer NF communicates with the producer NF via the SCP is called the indirect communication model.
[0008] In addition to SCP, another example of an intermediate proxy that forwards traffic between producer NF and consumer NF is the Security Edge Protection Proxy (SEPP). SEPP is a network function for protecting control plane traffic exchanged between different 5G Public Land Mobile Networks (PLMNs). As such, SEPP performs message filtering, policing, and topology hiding on all Application Programming Interface (API) messages transmitted between PLMNs.
[0009] One problem that may arise in 5G and other communication networks is that the NF profile of a producer NF may include multiple IP addresses, and a consumer NF may need to select one of the IP addresses for reaching the producer NF. One possible solution to this problem is to have the consumer NF receive a NF profile that includes multiple IP addresses and implement custom logic that selects a routable IP address from the multiple IP addresses in the NF profile. This solution is undesirable because it requires custom logic on each consumer NF, and consumer NFs running the same custom logic may end up selecting the same IP address, which may cause bottlenecks in the network.
[0010] Another problem associated with the IP address of the NF profile is the need for Network Address Translation (NAT). The network operator may need to configure Network Address Translation so that the producer NF can return different Network Address Translated IP addresses to the consumer NF located in different sites or localities. Possible solutions to this problem include placing a Network Address Translator in each separate locality or network, having the consumer NF perform Network Address Translation when connecting to the producer NF in each subnet, or having the producer NF provide multiple Network Address Translated IP addresses in the NF profile. None of these solutions are scalable.
[0011] Yet another issue related to producer NF IP addressing is how to provide localized DNS support in different sites or regions. Multiple IP address and / or network address translation issues can be addressed by providing region-based DNS support in each site or region. In such a case, the producer NF can publish a fully qualified domain name (FQDN) in its NF profile, and the localized DNS server can translate the FQDN based on the requester's region. However, this solution may result in operational challenges, such as keeping DNS records up to date.
[0012] Therefore, in view of these and other difficulties, there is a need for an NRF with configurable producer NF IP address mapping support. Summary of the invention
[0013] A method for supporting configurable producer network function (NF) Internet protocol (IP) address mapping includes receiving, at a NF repository function (NRF), a request message for a network address and / or service information of a producer NF from a requesting node. The method further includes determining at least one consumer NF parameter from the request message. The method further includes locating a producer NF IP address mapping rule using the at least one consumer NF parameter. The method further includes, in response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule. The method further includes generating a response message including the IP address and transmitting the response message to the requesting node.
[0014] According to another aspect of the subject matter described herein, receiving a request message includes receiving an NF discovery request message, and determining an IP address to be returned to the requesting node includes using at least one query parameter from the NF discovery request message to locate a NF profile of a producer NF and using a producer NF IP address mapping rule to select an IP address from the NF profile.
[0015] According to another aspect of the subject matter described herein, selecting an IP address using a producer NF IP address mapping rule includes selecting the IP address from a plurality of IP addresses included in a NF profile.
[0016] According to another aspect of the subject matter described herein, selecting the IP address using the producer NF IP address mapping rule includes selecting a network address translated IP address as the IP address to be returned to the requesting node using the producer NF IP address mapping rule.
[0017] According to another aspect of the subject matter described herein, locating the IP address mapping rule using at least one consumer NF attribute includes locating the IP address mapping rule using at least one attribute obtained from a NF profile of the consumer NF or a source address of the request message.
[0018] According to another aspect of the subject matter described herein, the requesting node comprises a consumer NF or a service communication proxy (SCP).
[0019] According to another aspect of the subject matter described herein, receiving the request message includes receiving a Domain Name System (DNS) resolution request message, and determining an IP address to be returned to the requesting node includes locating a NF profile of a producer NF using a NF instance identifier mapped to a fully qualified domain name (FQDN) in the DNS resolution request message and selecting an IP address from the NF profile using a producer NF IP address mapping rule.
[0020] According to another aspect of the subject matter described herein, using the consumer NF parameter to locate the IP address mapping rule includes using a source IP address of a DNS resolution request message to locate the IP address mapping rule.
[0021] According to another aspect of the subject matter described herein, receiving a DNS resolution request message from a requesting node includes receiving a DNS resolution request message from a consumer NF, and an SCP, or a DNS server.
[0022] According to another aspect of the subject matter described herein, determining the IP address includes selecting an IP address from a plurality of IP addresses included in the NF profile, or selecting a network address translated IP address from the NF profile.
[0023] According to another aspect of the subject matter described herein, a system for supporting configurable producer network function (NF) Internet Protocol (IP) address mapping. The system includes an NF repository function (NRF), the NRF including at least one processor and memory, for receiving a request message for a network address and / or service information of a producer NF from a requesting node. The system includes a producer NF IP address mapper for: determining at least one consumer NF parameter from the request message, locating a producer NF IP address mapping rule using the at least one consumer NF parameter, and in response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule. The system further includes a response generator implemented by the at least one processor for generating a response message including an IP address and transmitting the response message to the requesting node.
[0024] According to another aspect of the subject matter described herein, the request message includes an NF discovery request message, and the producer NF IP address mapper is configured to determine an IP address to be returned to the requesting node by locating a NF profile of the producer NF using at least one query parameter from the NF discovery request message and selecting an IP address from the NF profile using a producer NF IP address mapping rule.
[0025] According to another aspect of the subject matter described herein, a producer NF IP address mapper is configured to select an IP address from a plurality of IP addresses included in a NF profile using a producer NF IP address mapping rule.
[0026] According to another aspect of the subject matter described herein, the producer NF IP address mapper is configured to use producer NF IP address mapping rules to select a network address translated IP address as the IP address to be returned to the requesting node.
[0027] According to another aspect of the subject matter described herein, the producer NF IP address mapper is configured to locate an IP address mapping rule using at least one attribute obtained from a NF profile of a consumer NF or a source address of a request message.
[0028] According to another aspect of the subject matter described herein, the request message includes a Domain Name System (DNS) resolution request message, and the producer NF IP address mapper is configured to determine an IP address to be returned to the requesting node by locating a NF profile of the producer NF using a NF instance identifier mapped to a fully qualified domain name (FQDN) in the DNS resolution request message and selecting an IP address from the NF profile using a producer NF IP address mapping rule.
[0029] According to another aspect of the subject matter described herein, the producer NF IP address mapper is configured to locate an IP address mapping rule using a source IP address of a DNS resolution request message.
[0030] According to another aspect of the subject matter described herein, the requesting node comprises a consumer NF, a Service Communication Proxy (SCP), or a DNS server.
[0031] According to another aspect of the subject matter described herein, the IP address includes selecting an IP address from a plurality of IP addresses included in the NF profile, or selecting a network address translated IP address from the NF profile.
[0032] According to another aspect of the subject matter described herein, a non-transitory computer-readable medium having executable instructions stored thereon, the executable instructions, when executed by a processor of a computer, controls the computer to perform steps at a network function (NF) library function (NRF). The steps include receiving a request message for a network address and / or service information of a producer NF from a requesting node. The steps further include determining at least one consumer NF parameter from the request message. The steps further include using the at least one consumer NF parameter to locate a producer NF IP address mapping rule. The steps further include, in response to locating the producer NF IP address mapping rule, using the producer NF IP address mapping rule to determine an IP address to be returned to the requesting node. The steps further include generating a response message including an IP address. The steps further include transmitting the response message to the requesting node.
[0033] The subject matter described herein may be implemented in software in combination with hardware and / or firmware. For example, the subject matter described herein may be implemented in software executed by a processor. In an exemplary implementation, the subject matter described herein may be implemented using a non-transitory computer-readable medium having computer-executable instructions stored thereon, which controls the computer to perform steps when executed by the processor of the computer. Exemplary computer-readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application-specific integrated circuits. In addition, the computer-readable medium implementing the subject matter described herein may be located on a single device or computing platform, or may be distributed between multiple devices or computing platforms. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Exemplary implementations of the subject matter described herein will now be described with reference to the accompanying drawings, in which:
[0035] Figure 1 is a network diagram illustrating an exemplary 5G system network architecture;
[0036] Figure 2 is a network diagram illustrating a problem that occurs when an NF profile includes multiple IP addresses;
[0037] Figure 3 is a network diagram illustrating the problem that occurs when the IP address of a producer NF requires network address translation;
[0038] Figure 4 is a network diagram illustrating problems associated with providing localized DNS support when a NF profile returns an FQDN that requires localized DNS translation;
[0039] Figure 5 is a network diagram illustrating an NRF having configurable IP address mapping rules for selecting an IP address to be returned to a consumer NF when a NF profile contains multiple IP addresses;
[0040] Figure 6 is a network diagram illustrating an NRF with an integrated DNS server providing localized DNS support and selection between multiple IP addresses (including NATed IP addresses);
[0041] Figure 7 is a block diagram illustrating exemplary producer NF IP address mapping rules that may be configured at an NRF;
[0042] Figure 8 is a flow chart illustrating an exemplary process that may be implemented by an NRF when processing a NF discovery request using producer NF IP address mapping rules;
[0043] Fig. 9 is a flow chart illustrating an exemplary process that may be performed by an NRF to update NF (and its associated services) profile parameters in an NF discovery response using producer NF IP address mapping rules;
[0044] Fig.10 is a flow chart illustrating an exemplary process that may be performed by an NRF capable of providing localized DNS support;
[0045] Fig.11 is a flow chart illustrating an exemplary process that an NRF may perform when processing a DNS query using producer NF IP address mapping rules;
[0046] Fig.12 is a flow chart illustrating an exemplary process that may be performed when selecting an IP address to be included in a NF profile to be sent in an NF discovery response using a producer NF IP address mapping rule;
[0047] Fig.13is a message flow diagram illustrating exemplary messages exchanged when an NRF provides support for selecting one of a plurality of IP addresses for load balancing;
[0048] Fig.14 is a message flow diagram illustrating exemplary messages exchanged when an NRF provides support for using producer NF IP address mapping rules to select between multiple IP addresses for consumers in different regions;
[0049] Fig.15 is a message flow diagram illustrating exemplary messages exchanged when an NRF provides localized DNS support for NF discovery services;
[0050] Fig.16 is a message flow diagram illustrating exemplary messages exchanged when an NRF provides localized DNS support, including support for DNS forwarding to the nearest NRF for DNS resolution;
[0051] Fig.17 is a block diagram illustrating an exemplary architecture of an NRF with configurable IP address mapping rules for producer NFs; and
[0052] Fig.18 is a flow chart illustrating an exemplary process that an NRF may perform in supporting configurable IP address mapping rules for a producer NF. DETAILED DESCRIPTION
[0053] Figure 1 is a block diagram illustrating an exemplary 5G system network architecture. Figure 1 The architecture in includes NRF 100 and SCP 101 which may be located in the same domestic public land mobile network (HPLMN). As described above, NRF 100 may maintain profiles of available NF instances and the services they support, and allow consumer NFs or SCPs to subscribe to and be notified of registrations of new / updated NF instances. SCP 101 may also support service discovery and selection of NF instances. SCP 101 may perform load balancing of connections between consumer NFs and producer NFs.
[0054] NRF 100 is a repository for profiles of NF instances. In order to communicate with a producer NF instance, a consumer NF or SCP must obtain the NF profile of the producer NF from NRF 100. NF profile is a JavaScript Object Notation (JSON) data structure defined in 3GPP TS29.510. NF profile includes attributes indicating the type of service provided, the capabilities of the NF instance, and for contacting the NF instance.
[0055] exist Figure 1In the example, any network function can be a consumer NF, a producer NF, or both, depending on whether they are requesting services, providing services, or requesting and providing services. In the illustrated example, the NF includes a policy control function (PCF) 102, a unified management (UDM) function 104, and an application function (AF) 106. The PCF 102 performs policy-related operations in the network, the UDM function 104 manages user data, and the AF 106 provides application services.
[0056] Figure 1 The NF shown in FIG. 1 further includes a session management function (SMF) 108, which manages sessions between an access and mobility management function (AMF) 110 and PCF 102. AMF 110 performs management operations similar to those performed by a mobility management entity (MME) in a 4G network. Authentication server function (AUSF) 112 performs authentication services for user equipment (UE), such as user equipment (UE) 114, seeking access to the network.
[0057] The Network Slice Selection Function (NSSF) 116 provides network slicing services for devices seeking to access specific network capabilities and features associated with network slices. The Network Exposure Function (NEF) 118 provides an Application Programming Interface (API) for application functions seeking to obtain information about Internet of Things (IoT) devices and other UEs attached to the network. The NEF 118 performs functions similar to the Service Capability Exposure Function (SCEF) in 4G networks.
[0058] Radio access network (RAN) 120 connects user equipment (UE) 114 to the network via wireless links. Radio access network 120 can use g-Node B (gNB) (in Figure 1 The UE 114 may be configured to access the wireless network by using a wireless access point (not shown) or other wireless access point. The user plane function (UPF) 122 may support various proxy functionalities for user plane services. An example of such proxy functionality is multipath transmission control protocol (MPTCP) proxy functionality. The UPF 122 may also support performance measurement functionality that may be used by the UE 114 to obtain network performance measurements. Figure 1 Also illustrated in FIG. 1 is a data network (DN) 124 through which the UE accesses data network services, such as Internet services.
[0059] The SEPP 126 filters incoming traffic from another PLMN and performs topology hiding for traffic exiting the home PLMN. The SEPP 126 can communicate with a SEPP in a foreign PLMN that manages security for the foreign PLMN. Thus, traffic between NFs in different PLMNs can span two SEPP functions, one for the home PLMN and the other for the foreign PLMN.
[0060] As described above, issues that may arise in 5G and other networks that support service discovery and DNS include selecting a producer NF IP address when the producer NF supports multiple IP addresses, performing network address translation on the producer NF IP address, and performing DNS resolution in a manner that solves either or both of the first two issues. 3GPP TS29.510 allows a producer NF to register an NF profile or service profile that includes an FQDN and / or multiple IPv4 or IPv6 addresses. Tables 1 and 2 illustrate portions of an NF profile and a service profile that include FQDN and IP address related attributes, respectively. Table 3 defines the IpEndPoint attribute of a service profile.
[0061]
[0062] Table 1: NF profile attributes related to IP addressing
[0063]
[0064] Table 2: IP address related attributes of service profile
[0065]
[0066] Table 3: Definition of the IpEndPoint attribute of the service profile
[0067] Note 1 for NF profile and Note 7 for service profile illustrated in Table 1 emphasize the following aspects:
[0068] NOTE 1: At least one of the addressing parameters (fqdn, ipv4address or ipv6address) shall be included in the NF profile. If the NF supports NF services with "https" URI scheme (i.e., usage of TLS is mandatory), the FQDN shall be provided in the NF profile or NF service profile (see clause 6.1.6.2.3). See NOTE 1 of Table 6.1.6.2.3-1 regarding the usage of these parameters. If multiple ipv4 addresses and / or ipv6 addresses are included in the NF profile, then the NF service consumer discovering the service shall randomly select one of these addresses, unless the operator has defined a local policy for IP address selection, in order to avoid overloading for a specific ipv4 address and / or ipv6 address.
[0069] NOTE 7: If multiple IPv4 addresses and / or IPv6 addresses are included in the NF service, then unless the operator has defined a local policy for IP address selection, the NF service consumer that discovers the service SHOULD randomly select one of these addresses in order to avoid overloading a specific IPv4 address and / or IPv6 address.
[0070] The bold part of the above paragraph indicates that when a NF or service profile supports multiple IP addresses, the consumer should randomly select one of the addresses unless the operator has defined a specific policy. Relying on the consumer to select among multiple IP addresses in a NF or service profile may be problematic because such a solution is not scalable and may result in different consumer NFs over-selecting the same IP address.
[0071] Figure 2 is a network diagram illustrating problems that may occur when a producer NF profile registers multiple IP addresses in its NF or service profile. Figure 2 , the producer NF 200 located at site / region A registers IP addresses IP1 and IP2 with NRFs 100A and 100B. The purpose of registering two IP addresses is to enable the consumer NF1 300 located at site / region A to contact the producer NF 200 using IP address IP1, and the consumer NF2 302 located at site / region B to contact the producer NF 200 using IP address IP2.
[0072] When multiple IP addresses are registered for the same producer NF, the consumer NF needs logic to select a routable IP address to reach the producer NF. Figure 2 As shown, it is possible that the producer NF has published multiple IP addresses so that the producer NF can be reached from different locations separated by different subnets. For example, the producer NF 200 publishes different IP addresses in its NF or service profile so that the producer NF 200 can be reached from region A and region B. Figure 2 In the example in FIG. 1 , an NRF instance 100A or 100B exclusive to each region is shown. However, a network operator may choose to have a shared NRF instance with multiple reachable addresses so that the NRF can be reached from different subnets / regions.
[0073] When one of the consumer NFs 300 and 302 sends a NF Discovery Request to its local NRF instance 100A or 100B, the consumer NF 300 or 302 obtains the NF profile with two IP addresses of the producer NF 200 via the NF Discovery Response message. The consumer NF 300 or 302 can run custom logic to find the routable IP address that will be used to set up the connection between the consumer NF and the producer NF, as indicated by the arrow between the consumer NF 300 and 302 and the producer NF 200. This logic is required for each consumer NF in a different subnet that is trying to connect with the producer NF 200.
[0074] In some cases, a producer NF may publish multiple IP addresses to load balance network traffic on multiple network interfaces. In this case, 3GPP TS29.510 recommends that the consumer NF randomly select one of the IP addresses to avoid overloading a specific IPv4 address and / or IPv6 address. Because each consumer NF has its independent selection logic to select an IP address from the NF or service profile of the producer NF, it is possible that all consumer NFs will select the same IP address at the same time, which may lead to overloading of the interface associated with the over-selected IP address.
[0075] In another example, a producer NF may desire to use network address translation to provide different NATed IP addresses to different networks. Figure 3 FIG. 1 is a network diagram illustrating a case where a producer NF provides different network address translated IP addresses to consumer NFs located in different sites or regions. Figure 3 In the example, the producer NF 200 may desire to have the consumer NF 300 contact the producer NF 200 from region / site A using the NATed IP address IP1, and contact the producer NF 200 from region / site B using the NATed IP address IP2.
[0076] To achieve Figure 3 , a network operator can set up a routing module in the operator's network to automatically perform network address translation. In another example, a consumer NF can enable custom logic to perform NAT when connected to a producer NF in an isolated subnet. When a new isolated subnet is hosted by a network operator, the producer NF can add a new NATed IP address to the NF profile of the producer NF. Requiring the producer NF and / or independent network address translators to perform NAT for different subnets may cause operational challenges and maintainability challenges within the operator's network.
[0077] Figure 4This is an example of using DNS to partially resolve Figure 2 and Figure 3 A network diagram describing the problem. Figure 4 In the example, DNS servers 400 and 402 are located in sites / regions A and B, respectively. DNS server 400 performs a DNS lookup on the FQDN requested by consumer NF 300 and returns an IP address routable in site / region A. Similarly, DNS server 402 performs a DNS lookup on consumer NF 302 and returns an IP address routable in site / region B.
[0078] It is assumed that the producer NF 200 publishes the FQDN in its NF profile. The functionality for providing a region-based DNS is described at the following URL:
[0079] https: / / docs.microsoft.com / en-us / windowsserve / networking / dns / deploy / primary-geo-location
[0080] In this model, the operator can set up DNS so that a public DNS server is provided for each producer NF, which can respond based on the region of the requester. In another example, a DNS server can be provided in each region, which has information about all producer NFs in the network and can provide region-based DNS translation results. In either case, maintaining up-to-date DNS records is difficult, especially in a cloud network environment where NFs are dynamically triggered based on analytical data registered or unregistered at the NRF for a given slice or location.
[0081] In view of the above Figures 2 to 4 The described problem requires facilitating the management of FQDN to IP address mappings via DNS in 5G networks. It is also required to enable NATed IP based routing between isolated networks. Furthermore, it is required to avoid requiring consumer NF logic to select an IP address for routing when the producer NF advertises multiple IP addresses.
[0082] To address the above difficulties, the NRF described herein may be configured with an IP address mapper and configurable producer NF IP address mapping rules that allow the NRF to intelligently select between / among multiple IP addresses published in a NF or service profile, and to select different NATed IP addresses to be returned to different consumer NFs based on consumer NF attributes such as regions. The IP address mapper may be used to select among the IP addresses in the NF profile for return in response to a DNS query processed by the NRF.
[0083] Figure 5 is a network diagram illustrating an NRF with configurable IP address mapping rules and an IP address mapper that uses these rules to select an IP address to be returned to consumer NFs and SCPs. Figure 5 , NRFs 100A and 100B each include an IP address mapper 500 and configurable IP address mapping rules 502 to allow selection between or among multiple IP addresses (including NATed IP addresses).
[0084] In the first example, the producer NF publishes (one or more) IP endpoints in its NF or service profile. As described in the previous paragraph, the NRF 100A and 100B can be configured with operator-defined rules, which are referred to as producer NF IP address mapping rules in this article, and enable the NRF to map the IP address in the NF or service profile of the producer NF to information about the consumer NF (such as region, source IP address, etc.). In response to receiving the NF discovery request, the NRF 100A or 100B can locate the NF or service profile that matches the query parameters in the NF discovery request. The NRF 100A or 100B can then determine whether any producer NF IP address mapping rules are configured for the NF or service profile. If the NRF 100A or 100B determines that the producer NF IP address mapping rules are configured for the NF or service profile, the NRF 100A or 100B can use the mapping rules and the input about the consumer NF to update the IP address returned to the consumer NF or SCP in the NF discovery response with the specific IP address that will be used to contact the producer NF. The producer NF IP address mapping rules may be based on the operator network deployment model. For example, if the network operator implements network isolation and the producer NF only publishes a single IP address based on the subnet of the producer NF, the NRF may generate a NATed IP address and provide the address to each consumer NF in the NF discovery response, where different NATed IP addresses may be provided to consumer NFs in different regions, and the NATed IP address provided to each consumer NF is an IP address routable from the region or site of the consumer NF.
[0085] To determine the NATed IP address for a particular consumer NF, the NRF may utilize information about the consumer NF. For example, if the consumer NF provides a requester-nf-instance-id in the NF Discovery Request, the NRF may use the requester-nf-instance-id to locate the NF or service profile of the consumer NF and use one or more of the following attributes from the consumer NF profile to select a producer NF IP address mapping rule that may be used to determine the IP address of the producer NF to be returned to the consumer NF in the NF Discovery Response: NF instance ID, FQDN, IP endpoint information, region, network slice, etc. In another example, the NRF may use the source IP subnet of the TCP datagram carrying the NF Discovery Request or other (one or more) source identification parameters from the NF Discovery Request to select a producer NF IP address mapping rule for generating or selecting an IP address to be returned to the consumer NF in the NF or service profile.
[0086] If the network operator implements network isolation, and the producer NF advertises multiple IP addresses for different subnets, the NRF can use any of the IP endpoint information, region, slice, etc. from the NF profile of the consumer NF to locate the matching producer NF IP address mapping rule and select one of the IP addresses to return to the consumer NF. Otherwise, the NRF can utilize the source IP subnet of the TCP datagram carrying the NF discovery request or other (one or more) source identification parameters from the NF discovery request. If the producer NF advertises multiple IP addresses for load balancing, the producer NF IP address mapping rule can be used to select one or more IP addresses that are routable from the site or region of the consumer NF, and if there are numerous such addresses after applying the rules, a load balancing algorithm can be used.
[0087] Figure 6 is a network diagram illustrating an exemplary solution for producer NF IP address mapping at an NRF when the producer NF publishes an FQDN and one or more IP endpoints in its NF or service profile. Figure 6 In the example in , the producer NF 200 publishes the FQDN and IP endpoint addresses IP1 and IP2 in its NF or service profile registered with the NRFs 100A and 100B. In addition, each NRF 100A and 100B includes a DNS server 600, which receives DNS queries or resolution requests from consumer NFs and returns routable IP addresses in response to the DNS queries. The NRFs 100A and 100B may include a producer NF IP address mapper 500 and a producer NF IP address mapping rule 502 as described above to select among multiple IP addresses to provide in the DNS response message.
[0088] As indicated above, the producer NF 200 publishes the FQDN and (one or more) IP endpoints in its NF or service profile. The producer NF 200 may choose to publish one or more IP addresses based on the deployment model of the network operator. Co-hosting the DNS server 600 with the NRFs 100A and 100B allows the NRFs 100A and 100B to manage DNS entries based on registration, deregistration, and updates of NF profiles. If the network includes a local DNS server, such as the DNS server 604, the local DNS server 604 may be configured to forward the DNS query to the DNS server 600 co-hosted with the NRF 100A or 100B closest to the DNS server that received the DNS query.
[0089] The producer NF IP address mapper 500 may use the producer NF IP address mapping rules 502 to select the IP address that the DNS server 600 will return. For example, if the network operator implements network isolation, the DNS server 600 may return the IP address selected by the IP address mapper 500 based on the source IP address of the TCP datagram carrying the DNS query. The IP address returned to the consumer NF in the DNS response may be either one of the IP addresses published by the producer NF in the NF or service profile, or a NATed IP address selected by the IP address mapper 500 associated with the DNF server 600 based on the operator configuration and information available in the profile of the producer NF. If the producer NF 200 publishes multiple IP addresses of the same subnet, and the NRF 100A or 100B determines that all IP addresses published by the producer NF 200 are applicable to the consumer NF 300 or 302, the NRF 100A or 100B selects one of the IP addresses (based on the operator policy) and returns the IP address as part of the DNS query response.
[0090] Therefore, based on the operator network / deployment and configuration, the NRF as described herein selects among multiple IP addresses in the NF profile for load balancing or other criteria in a manner that provides a routable IP address to the consumer NF. The NRF as described herein also selects a NATed IP address that is routable from the consumer NF's network and returns it to the consumer NF. The NRF further performs a DNS lookup and returns the routable IP address to the consumer NF while operating based on NF registration, deregistration, and update services. In one example, a local DNS server separate from the NRF can forward the DNS query to the NRF so that the NRF can perform DNS resolution.
[0091] The NRF may include producer NF IP address mapping rules for determining the IP address returned to the consumer NF or SCP in the NF or service profile. Figure 7 An exemplary producer NF IP address mapping rule is illustrated. Figure 7 , the producer NF IP address mapping rules 502 are divided into ConsumerCriteria 700 and ProducerConfigList 702. ConsumerCriteria 700 includes criteria from or related to the consumer NF that can be used to select rules from ProducerConfigList 702. In the example, ConsumerCriteria 700 includes a Priority attribute, which has a value ranging between 0 and 255, and the lower the priority value, the higher the priority indicated. ConsumerCriteria further includes a Type attribute, which has a value that can be any one of [instance id, fqdn, IP endpoint, region, IP subnet]. If the consumer NF provides requester-nf-instance-id in the discovery request, the instance id, fqdn, IP endpoint, region, etc. can be extracted from the consumer NF profile registered with the NRF. The Value field in ConsumerCriteria stores the value of the attribute specified by the Type attribute. If "IP Subnet" is set, the rules for the producer NF will be applied to the consumer NF in a way that matches the "IP Subnet" in any IP endpoint advertised by the consumer NF in its profile. IP Subnet should be set when DNS support is enabled at the NRF.
[0092] The Value specified in the consumer criteria is compared with the criteria in the ProducerConfigList to locate one or more matching rules. If multiple rules in a given ConsumerCriteria match the incoming request parameters or the IP address in the TCP datagram, the rule with the highest priority (i.e., closer to 0) wins and is used to select a ProducerConfigList object to evaluate the IP address to be returned to the consumer NF or SCP. ConsumerCriteria can match multiple rows, i.e., for some ProducerConfigLists, ConsumerCriteria is based on regional settings. For some ProducerConfigLists, ConsumerCriteria can be set to IPSet. When an incoming request from a consumer NF matches multiple ConsumerCriteria, the priority acts as a tiebreaker. Based on the priority, a given rule that will have a ProducerConfigList list is selected. Within the ProducerConfigList, NfType and NfInstance act as keywords for selecting mapping rules. Therefore, priority is not required for selecting mapping rules within the ProducerConfigList.
[0093] ProducerConfigList is a list of configuration rules for producers with multiple IP addresses published in their NF or service profiles, or for which NATed IP addresses should be generated. These rules can be used to provide IP information in NF profiles or as part of DNS resolution. If a producer NF does not match NfType and NfInstance, its profile will be provided as is (i.e., without modification) in the response to the NF discovery request. NfType is the type of producer NF to which the rules are applied. If the producer NF profile matches NfType and NfInstance, the NRF will use the matching rules from ProducerConfigList to determine the IP address to be returned to the consumer NF or SCP in the NF discovery response. ProducerConfigList can have multiple records for the same NfType, which allows unique configuration for different producer instances.
[0094] NfInstance is an optional parameter used to specify a list of NfInstances to which a given rule will be applied. If missing, the rule will be assumed to be for the given NfType by default, and will be applied to all NfInstances not explicitly specified. When specified, the entry for NfInstance must be unique among the various entries in the ProducerConfigList. For a given NfType, a configuration with an empty NfInstance list should be allowed within the ProducerConfigList.
[0095] The ProfileEndpointData attribute is used to specify the following values: [FQDN,IP,BOTH]. When ProfileEndpointData is set to FQDN, only the FQDN information will be provided in the NF profile returned to the consumer NF or SCP, even when the FQDN and one or more IP addresses are present in the NF profile. The value FQDN should only be set if the operator has an external DNS or the NRF can perform a DNS lookup. When the ProfileEndpointData attribute is set to IP, only the IP information will be provided in the NF profile returned to the consumer NF or SCP, even when the FQDN and one or more IP addresses are present in the NF profile. When the ProfileEndpointData attribute is set to BOTH, when the FQDN and one or more IP addresses are present in the NF profile, the FQDN information and the associated (one or more) IP addresses will be provided in the NF profile returned to the consumer NF or SCP.
[0096] The ipSubnet attribute in the ProducerConfigList is used to specify the IP subnet address that matches the given subnet from the producer NF profile. If the consumer NF sends an NF discovery request, the ProducerConfigList is selected based on the ConsumerCriteria. Based on the matching NfType and NfInstance, the matching producer configuration is found. Based on the IPset, an IP address is selected from the producer NF profile and returned as part of the NF discovery response. If the request being processed by the NRF is a DNS resolution request rather than an NF discovery request, the ConsumerCriteria will match the IP address in the TCP datagram carrying the DSN resolution request. Based on the requested FQDN (in the DNS resolution request), the matching NF instance ID is found from the DNS mapping table (see Table 4). Then, based on the NfType and instanceId, the corresponding ProducerConfig rule will be applied, that is, based on the IPSet configuration in the ProducerConfig rule, the NRF will return the corresponding IP address from the producer NF profile as a DNS query response. If none of the IP addresses in the NR profile matches the given subnet, all IP addresses (provided by the producer NF) will be returned in the NF profile included in the NF Discovery Response message.
[0097] The NATset attribute is used to specify List[<producerPublishedIP,NatedIP> ]. List of NATed IP sets. If a producer NF or service profile contains an IP address specified in the list as producerPublishedIP, then that IP address will be replaced with the corresponding NATedIP address in the NF or service profile (for discovery responses), or in the DNS response. If the NATed IP address matches the value of the ipSubnet parameter, then the NATed IP address(es) will be selected and returned in the NF profile or DNS response.
[0098] The loadBalancingIP attribute is applicable only when ProfileEndpointData is set to IP or Both. There can be multiple IP addresses matching a given ipSubnet in the producer NF profile. The loadBalancingIP parameter allows the NRF to decide whether all or one IP address will be returned in the NF profile. The loadBalancingIP parameter is set to TRUE by default when ProfileEndpointData is set to FQDN or "DNS support" is enabled at the NRF. When the loadBalancingIP attribute is set to TRUE, alternating IP addresses (determined by processing the IP addresses in the NF profile using ipSubnet and NATset) will be returned for each discovery request. Otherwise, all relevant IP addresses will be returned.
[0099] Figure 8 is a flowchart illustrating an exemplary process that an NRF may perform when processing an NF discovery request. Figure 8 In step 800, the NRF receives a NF discovery request from a consumer NF. In the case of delegated discovery, the NF discovery request may come from an SCP that is performing discovery on behalf of the consumer NF. In step 802, the NRF runs default logic that selects a set of producer NF profiles to be included in the discovery response. Step 802 may include comparing query parameters in the NF discovery request with corresponding attributes in the NF profiles registered with the NRF to locate a matching NF profile.
[0100] In step 804, the NRF determines whether the consumer NF provided a requester-nf-instance-id in the NF discovery request. If the consumer NF provided a requester-nf-instance-id, control proceeds to step 806, in which the NRF looks up the consumer NF profile corresponding to the requester-nf-instance-id. The NRF then extracts parameters from the consumer NF profile and compares the parameters with the value of the Type attribute specified in the ConsumerCriteria of the consumer NF IP address mapping rule 502. If the parameters from the consumer NF profile match the value of the Type attribute of the ConsumerCriteria of any of the producer NF IP address mapping rules, control proceeds to step 808, in which the NRF selects the rule with the highest priority in the Priority attribute of the rule. Control then proceeds to step 810, in which the NRF performs a lookup in the ProducerConfigList to find a ProducerConfig object with an NF type and a target NF type that match the corresponding attributes from the discovery request. In step 812, it is determined whether a match is found for the comparison in step 810. If a match is found, control passes to step 814 where the NRF begins the process of iterating through all producer NF profiles selected for discovery responses to perform the step of updating the IP address.
[0101] Iterating through the NF profiles begins at step 816, where the NRF selects the next profile from the profiles selected for the discovery response. In step 818, the NRF finds the ProducerConfig object of the NF instance with the instance ID of the profile, otherwise selects the ProducerConfig object with the NF instance set to null. Control then proceeds to step 820, where the NRF determines whether any profile with a matching producer configuration object is found. If a matching object is found, control proceeds to step 822, where the NRF runs the logic to update the NF profile based on the parameters selected in the ProducerConfig object. In step 820, if there are no matching parameters, or after updating the parameters in step 822, control returns to step 816, where the next profile is selected. Steps 816 to 822 are repeated until all profiles have been processed. Control then proceeds to step 824, where the modified NF profile is returned to the consumer NF in the NF discovery response.
[0102] Returning to step 804, if the consumer NF does not provide a requester-nf-instance-id, control proceeds to step 826, where the IP subnet of the TCP datagram carrying the NF discovery request is compared with the IP subnet attribute of the ConsumerCriteria having a type of "IPsubnet". Control then proceeds to step 808, where the highest priority matching rule is selected. Steps 810 to 824 are then executed to process the NF profile to be returned in the NF discovery response.
[0103] Returning to step 812, if there is no match in the ProducerConfigList with the NF type from the discovery request or the target NF type, control proceeds to step 828, where it is determined that no producer NF profile change is required. Control then returns to step 824, where the unprocessed NF profile is returned in the NF discovery response.
[0104] Fig. 9 is an example of an NRF executed to update Figure 8 Flowchart of exemplary steps for specifying NF (and its associated service) profile parameters in step 822 of FIG. Fig. 9 , in step 900, the logic to update the NF and its service profile based on the parameters in the selected ProducerConfig object begins. In step 902, the NRF iterates through the NF profile and the service instances in the profile to update the parameters. The first step in the iteration is step 904, in which the NRF determines whether the ProducerConfig.ProfileEndpointData attribute is set to the FQDN. If the ProducerConfig.ProfileEndpointData attribute is set to the FQDN, control proceeds to step 906, in which the NRF removes the ipEndPoints from the NF profile. Control then proceeds to step 908 and then to step 902, in which processing of the next NF profile begins.
[0105] Returning to step 904, if the NRF determines that the ProducerConfig.ProfileEndpointData property is not set to the FQDN, control proceeds to step 910, in which it is determined whether the ProducerConfig.ProfileEndpointData property is set to the IP. If the ProducerConfig.ProfileEndpointData property is set to the IP, control proceeds to step 912, in which the NRF updates the profile to remove the FQDN. Control then proceeds to step 914, in which the NRF determines whether any of the ipEndPoints specified in the NF profile matches any of the IP addresses in the producerPublishedIP property in the ProducerConfig.NATset. If any of the ipEndPoints in the profile matches any of the IP addresses specified in the producerPublishedIP property in the ProducerConfig.NATset, control proceeds to step 916, in which the matching IpEndPoint is replaced with the NATed IP address specified in the ProducerConfig.NATset. Control then proceeds to step 918, in which it is determined whether any IpEndPoint matches ProducerConfig.IPsubnet. If the answer in step 918 is "yes", control proceeds to step 920, in which the NRF removes the unmatched ipEndPoint from the NF profile. Control then proceeds to step 922, in which the NRF determines whether ProducerConfig.LoadBalancingIP is set to TRUE. If ProducerConfig.LoadBalancingIP is set to TRUE, control proceeds to step 924, in which the NRF uses a round-robin selection or other load balancing algorithm to select a single IP address to be retained in the NF profile to be returned or sent to the consumer NF. Control then returns to step 902, in which it continues to iterate through the remaining NF profiles or service profiles (within NfProfile) to be returned in the NF Discovery Response. Steps 904 to 918 are repeated for each NF profile to be included in the NF Discovery Response.
[0106] Returning to step 910, if ProducerConfig.ProfileEndpointData is not set to an IP (or FQDN), control passes to step 914, where it is determined whether any IpEndPoint in the profile matches the producer-advertised IP address in ProducerConfig.NATset. Steps 914 to 924 are then used to update the IP address to be included in the NF or service profile returned to the consumer NF.
[0107] Returning to step 914, if none of the ipEndPoints in the NF profile matches the producerPublishedIP in ProducerConfig.NATset, control returns to steps 918 to 924, where the IP addresses in the ipEndPoints attribute in the NF or service profile are processed without replacing any of the IP addresses with the NATed IP address.
[0108] Fig.10 is a flow chart illustrating an exemplary process performed by an NRF in generating local DNS data that can be used to obtain responses to DNS requests in response to NF registration, NF update, and NF deregistration service operations. Fig.10 In step 1000, the NF sends a NF profile registration, update or deregistration service request to the NRF. Step 1000 may also include the NRF failing to receive a response to the NF heartbeat request within the NF heartbeat interval defined for the producer NF instance.
[0109] In step 1002, it is determined whether the NF registration, update or deregistration request is valid. If the request is not valid, control passes to step 1004, in which the NRF responds to the request but does not generate any local DNS data.
[0110] If it is determined that the request in step 1002 is valid, control passes to step 1004, in which the NRF runs its default logic to process the request. Step 1004 may include generating an Nnrf management response to the request. In step 1006, the NRF determines whether DNS support is enabled. If DNS support is not enabled, control passes to step 1008, in which the NRF generates a response to the request message, but does not generate any local DNS data.
[0111] If DNS support is enabled, control proceeds to step 1010, in which the NRF determines whether the NF or service profile has FQDN and IpEndPoint information. If the NF profile has FQDN and IpEndPoint information, control proceeds to step 1012, in which the NRF adds or updates local DNS data to store FQDN to NF profile / service profile instance ID mappings. Step 1012 also applies to the case when the NF restarts heartbeat. The NRF adds all FQDNs (in the NF profile or service profile of the restarted instance) to the DNS data store. Control then proceeds to step 1014, in which the NRF removes the FQDN to NF profile / service profile instance ID mappings that are no longer part of the NF service / profile from the local DNS data. Step 1014 also applies to the case where the NF heartbeat is lost, causing the NF profile to be marked as suspended. The NRF removes all FQDNs (in the NF profile or service profile of the suspended instance) from the DNS data store.
[0112] Returning to step 1010, if the NF or service profile does not have FQDN and IpEndPoint information, control proceeds to step 1014, where the NRF removes the FQDN to NF Profile / Service Profile Instance ID mapping that is no longer part of the NF service / profile from the local DNS data. After step 1014, control returns to step 1004, where the NRF responds to the request for Nnrf service operations.
[0113] Table 4 illustrates an example of local DNS data that the NRF may maintain.
[0114] FQDN NF Profile ID Source FQDN InstanceID Abc.com Profile-instance-id1 Nf Profile-Instance-id1 Xyz.com Profile-instance-id2 Serve Service-InstanceID
[0115] Table 4: Local DNS data
[0116] As will be described in detail below, the local DNS data in Table 4 obtained from NF Registration Request, NF Deregistration Request and NF Update Request may be used to locate a NF profile that is used to provide an IP address in response to a DNS query.
[0117] Fig.11 is a flow chart illustrating exemplary steps that may be performed by an NRF when processing a DNS query using an IP address obtained from a NF or service profile. Fig.11In step 1100, the NRF receives a DNS query. In step 1102, the NRF determines whether the FQDN in the DNS query is in the local DNS table (see Table 4). If the FQDN is not in the local DNS table, control proceeds to step 1104, and then to step 1106, in which the NRF determines that no FQDN to IP address mapping is found, and in step 1106, the NRF returns a DNS response indicating that no IP address mapping is found.
[0118] In step 1102, if the FQDN in the DNS query is found in the local DNS table, control passes to step 1108, in which the NRF determines whether there are any matching ConsumerCriteria based on the DNS query. If there are no matching ConsumerCriteria, control passes to steps 1104 and 1106, in which the NRF determines that no FQDN to IP address mapping is found, and sends a DNS response without an IP address to the requester.
[0119] In step 1108, if a matching ConsumerCriteria based on the source IP address of the DNS query is found, control proceeds to step 1110, in which the producer NF IP address mapping rule with the highest priority and matching ConsumerCriteria is selected. Control then proceeds to step 1112, in which the NRF finds the ProducerConfig object with the NF instance containing the NF Profile ID (corresponding to the FQDN in the local DNS table). Otherwise, the NRF selects the ProducerConfig object with the NF Instance attribute set to null.
[0120] In step 1114, the NRF determines whether any matching ProducerConfig objects are located. If no matching ProducerConfig objects are located, control returns to steps 1104 and 1106, where it is determined that no FQDN to IP address mapping is found, and a DNS response is sent.
[0121] In step 1114, if a matching ProducerConfig object is found, control proceeds to step 1116, in which the NRF obtains the matching NF Profile corresponding to the NF Profile ID of the FQDN in the DNS table and creates a local copy. Control then proceeds to step 1118, in which the NRF runs logic to obtain an IP address from the NF Profile based on the FQDN from the DNS request and the parameters in the selected ProducerConfig object.
[0122] Fig.12 is a flow chart illustrating an exemplary process performed by an NRF to find an IP address to be returned in a DNS response from a NF profile. Fig.12 , in step 1200, the logic to obtain an IP address from the NF or service profile based on the DNS request and the parameters in the selected ProducerConfig object is initiated. In step 1202, the NRF begins the process of iterating through the NF profiles and service instances in the NF profile to select an IP address. In step 1204, the NRF determines whether there is a matching FQDN in the profile. If there is a matching FQDN in the profile, control proceeds to step 1206, in which the NRF determines whether any IP endpoint in the NF profile matches the producerPublishedIP in ProducerConfig.NATset. If there is any matching IP address, control proceeds to step 1208, in which the NRF updates the matching IP address in ipEndPoint with the corresponding NATed IP address in the NF profile. After step 1208, or if there is no matching ipEndPoint in step 1206, control passes to step 1210, in which the NRF determines if there is any IpEndPoint match to ProducerConfig.IPsubnet. If there is any IpEndPoint match, control passes to step 1212, in which the NRF removes any unmatched IP endpoints from the profile. Control then passes to step 1214, in which the NRF uses a round-robin selection or other selection algorithm to select a single IP address from the profile. Control then passes to step 1216, in which the NRF returns the IP address from the NF or service profile to include in the DNS response.
[0123] Fig.13 is a message flow diagram illustrating exemplary messages exchanged for selecting a routable IP address among multiple IP addresses in a NF profile using load balancing using configurable producer NF IP address mapping rules at an NRF. Fig.13 , in line 1, the producer NF 200 sends a NF registration request to the NRF 100. The NF registration request includes multiple IP addresses and FQDNs in the NF profile. The NRF 100 is also configured with configurable IP address mapping rules to select a routable IP address specific to the site of the consumer NF. In line 2 of the message flow diagram, the NRF 100 responds to the producer NF 200 with a success response indicating a successful registration of the NF profile.
[0124] In line 3, the consumer NF 300 sends a NF Discovery Request to the NRF 100. The NRF 100 locates the NF profile that matches the query parameters in the NF Discovery Request, and uses the producer NF IP address mapping rule to select the IP address IP1 from the ipEndPoint in the NF profile of the producer NF 200. The NRF 100 modifies the NF profile to include the IP address IP1, and in line 4, sends an NF Discovery Response with the modified NF profile to the consumer NF 300.
[0125] In line 5 of the message flow diagram, the consumer NF 302 sends a NF Discovery Request to the NRF 100. The NRF 100 selects the NF profile corresponding to the query parameters in the NF Discovery Request and applies the producer NF IP address mapping rule to select the IP address IP2 from the ipEndPoints attribute of the NF profile to return to the consumer NF 302. In line 6, the NRF 100 sends a NF Discovery Response with the modified NF profile to the consumer NF 302.
[0126] In line 7, consumer NF 300 sends an SBI service request using the routable IP address IP1 to producer NF 200. In line 8, producer NF 200 responds with a success response. In line 9, consumer NF 302 sends a service request to producer NF 200 using the IP address IP2. In line 10, producer NF 200 responds with a success response.
[0127] Fig.14 is a message flow diagram illustrating exemplary messages exchanged when using configurable IP address mapping rules at an NRF to provide different IP addresses to consumer NFs located in different networks. Fig.14 In the message flow diagram, it is assumed that both NRFs 100A and 100B are configured with producer NF IP address mapping rules to select among the IP addresses in the NF profile to return to the consumer NF in a different network. In line 1, the producer NF 200 sends a NF registration request to NRF 100B. The NF registration request includes multiple IP addresses and FQDNs in the NF profile. In line 2 of the message flow diagram, NRF 100B responds to the producer NF 200 with a success response indicating that the NF profile was successfully registered. NRF 100B replicates the NF profile to the geographically redundant partner NRF 100A.
[0128] In line 3, the consumer NF 300 sends a NF Discovery Request to the NRF 100. The NRF 100A locates a NF profile that matches the query parameters in the NF Discovery Request and uses the producer NF IP address mapping rules to select a routable IP address from the ipEndPoint in the NF profile of the producer NF 200 based on the region or other source identification parameters. The NRF 100A modifies the NF profile to include the selected IP address and, in line 4, sends a NF Discovery Response with the modified NF profile to the consumer NF 300.
[0129] In line 5 of the message flow diagram, the consumer NF 302 sends a NF Discovery Request to the NRF 100B. The NRF 100B selects the NF profile corresponding to the query parameters in the NF Discovery Request and applies the producer NF IP address mapping rule to select a routable IP address from the ipEndPoints attribute of the NF Discovery Request of the NF profile to return to the consumer NF 302. In line 6, the NRF 100B sends a NF Discovery Response with the modified NF profile to the consumer NF 302.
[0130] In line 7, the consumer NF 302 sends the SBI service request to the producer NF 200 using the routable IP address that the consumer NF 302 receives from the NRF 100B. In line 8, the producer NF 200 responds with a success response. In line 9, the consumer NF 300 sends the service request to the producer NF 200 using the IP address IP2. In line 10, the producer NF 200 responds with a success response.
[0131] Fig.15 is a message flow diagram illustrating exemplary messages exchanged when the NRF provides localized DNS support for NF discovery services. Fig.15In the example, both NRF 100A and 100B include an NRF SBI interface 1500 and an NRF DNS server 600, the NRF SBI interface 1500 is used to receive and respond to SBI service requests, and the NRF DNS server 600 is used to receive and respond to DNS requests. In the first row of the message flow chart, the producer NF 200 sends the NF registration request to the SBI interface 1500 of the NRF 100B. In the second row, the NRF SBI interface 1500 of the NRF 100B responds with a successful response. In this example, it is assumed that the NF profile registered by the producer NF 200 includes multiple reachable IP addresses and FQDNs. In the third row of the message flow chart, the NRF SBI interface 1500 updates the DNS record with the IP address and FQDN received in the NF registration request in the first row. It should be understood that the DNS source record can be updated directly, or the local DNS mapping data can be updated as described above with respect to Table 4.
[0132] In line 4 of the message flow diagram, the NRF DNS server 600 responds to the NRF SBI interface 1500 with a success response confirming the successful update of the DNS data. The NRF 100B replicates the NF profile registered in line 1 to the geographically redundant partner NRF 100A. The NRF 100A stores the NF profile in its NF profile database and updates its DNS data.
[0133] In line 5 of the message flow diagram, the consumer NF 302 sends a NF Discovery Request to the SBI interface 1500 of the NRF 100B. In line 6 of the message flow diagram, the NRF 100B responds with a Success Response including the NF Profile of the Producer NF 200. According to the rules applied by the NRF 100B, the NF Profile may include the FQDN of the Producer NF 200. In line 7 of the message flow diagram, the consumer NF 302 sends a DNS query to the NRF DNS server 600. In line 8, the NRF DNS server 600 of the NRF 100B responds to the consumer NF 302 with a routable IP address using the DNS mapping data received in the Registration Request in line 1.
[0134] In line 9 of the message flow diagram, the consumer NF 300 sends a NF discovery request to the NRF SBI interface 1500 of the NRF 100A. In line 10, the NRF SBI interface 1500 of the NRF 100A responds with a success response including the NF profile of the producer NF 200. In line 11, the consumer NF 300 sends a DNS query to the NRF DNS server 600 of the NRF 100A. In line 12, the NRF DNS server 600 of the NRF 100A responds to the consumer NF 300 with a routable IP address.
[0135] Fig.16 is a message flow diagram illustrating exemplary messages exchanged when a DNS server supports forwarding DNS queries to a local DNS server for DNS resolution. Fig.16 , in line 1 of the message flow diagram, the producer NF 200 sends a NF registration request to the SBI interface 1500 of the NRF 100B. In line 2, the NRF SBI interface 1500 of the NRF 100B responds with a success response. In this example, it is assumed that the NF profile registered by the producer NF 200 includes multiple reachable IP addresses and FQDNs. In line 3 of the message flow diagram, the NRF SBI interface 1500 updates the DNS record with the IP address and FQDN received in the NF registration request in line 1. It should be understood that the DNS source record can be updated directly, or the local DNS mapping data can be updated as described above with respect to Table 4.
[0136] In line 4 of the message flow diagram, the NRF DNS server 600 responds to the NRF SBI interface 1500 with a success response confirming the successful update of the DNS data. The NRF 100B replicates the NF profile registered in line 1 to the geographically redundant partner NRF 100A. The NRF 100A stores the NF profile in its NF profile and updates its DNS data.
[0137] In line 5 of the message flow diagram, the consumer NF 300 sends a NF discovery request to the SBI interface 1500 of the NRF 100B. In line 6 of the message flow diagram, the NRF 100A responds with a success response including the NF profile of the producer NF 200. According to the rules applied by the NRF 100A, the NF profile may include the FQDN of the producer NF 200. In line 7 of the message flow diagram, the consumer NF 300 sends a DNS query to a local DNS server 1600 external to the NRF 100A. In line 8, if the local DNS server 1600 cannot resolve the DNS query, the local DNS server 1600 implements DNS forwarding by sending the corresponding DNS query to the NRF DNS server 600 of the NRF 100A. In line 9, the NRF DNS server 600 of the NRF 100A responds to the local DNS server 1600 with a routable IP address using the DNS mapping data received in the registration request in line 1. In line 10 , the local DNS server 1600 responds to the consumer NF 300 with the routable IP address of the producer NF 200 .
[0138] Fig.17 is a block diagram illustrating an exemplary architecture for an NRF 100 as described herein. Fig.17 , the NRF 100 includes at least one processor 1700 and a memory 1702. The NRF 100 further includes the above-mentioned producer NF IP address mapper 500 and producer NF IP address mapping rules 502. The NRF 100 also includes a NF profile database 1702 and DNS data or DNS mapping data 1706. The NRF 100 further includes a response generator 1708, which includes an NRF SBI interface 1500 and an NRF DNS server 600.
[0139] In operation, when the NRF 100 receives a NF discovery request via the SBI interface 1500, the NRF 100 responds to the NF discovery request using the NF profile in the NF profile database 1704, together with the producer NF IP address mapper 500 and the mapping rule 502 to select an IP address to be returned to the requesting node. Similarly, when responding to a DNS query received via the DNS server 600, the producer NF IP address mapper 500 may use the IP address mapping rule 502, together with the DNS data or the DNS mapping data 1706, to select an IP address stored in the NF profile database 1704 to provide to the DNS server 600, so that the DNS server 600 may respond to the DNS query with an IP address routable to the consumer NF.
[0140] Fig.18 is a flow chart illustrating an exemplary process for supporting configurable producer NF IP address mapping. Fig.18 In step 1800, the process includes receiving a request message for a network address and / or server of a producer NF from a requesting node at a NF repository function (NRF). For example, the NRF 100 may receive an NF discovery request message from a consumer NF or SCP or a DNS resolution request message from a consumer NF, SCP, or DNS server.
[0141] In step 1802, the process includes determining at least one consumer NF parameter from the request message. For example, if the request is an NF Discovery Request message including a requestor NF Instance ID, the NRF 100 may use the requestor NF Instance ID to locate the NF profile of the consumer NF and obtain the FQDN, (one or more) IP endpoint addresses and / or regions from the NF profile. If the request message is a DNS resolution request message or an NF Discovery Request message without a requestor NF Instance ID, the NRF 100 may use the source IP address of the message as the consumer NF parameter.
[0142] In step 1804, the process includes locating a producer NF IP address mapping rule using the at least one consumer NF parameter. For example, the NRF 100 may use the NF instance ID, FQDN, (one or more) IP endpoint addresses and / or source IP address as ConsumerCriteria to locate a matching rule in the ProducerConfigList.
[0143] In step 1806, the process includes, in response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule. For example, the matching rule may specify that an IP address from among a plurality of IP addresses in the NF profile should be selected based on region or other consumer NF attributes. In another example, the matching rule may indicate that a network address translated address should be returned.
[0144] In step 1808, the process includes generating a response message including the IP address. For example, if the request message is an NF discovery request, the NRF 100 may generate an NF discovery response message including the NF profile of the producer NF, wherein the selected IP address is returned as the only IP address in the ipEndPoints attribute of the NF profile, replacing one or more IP addresses previously included in the NF profile. If the request message is a DNS resolution request, the response message may include a DNS resolution response message including the selected IP address.
[0145] In step 1810, the process includes transmitting a response message to the requesting node. For example, the NRF 100 may transmit the response message to a consumer NF, an SCP, or a DNS server that generated the NF discovery or DNS resolution request.
[0146] The disclosures of each of the following references are incorporated herein by reference in their entirety.
[0147] References
[0148] 1. 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Phase 3 (Release 17) 3GPP TS29.510 V17.3.0 (2021-09)
[0149] It will be understood that various details of the subject matter described herein can be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only and not for the purpose of limitation, as the subject matter described herein is defined by the claims recited below.
Claims
1. A method for supporting configurable producer network function (NF) Internet protocol (IP) address mapping, the method include: At NF Repository Function (NRF): Receive a request message for the network address and / or service information of the producer NF from the requesting node; determining at least one consumer NF parameter from the request message; locating a producer NF IP address mapping rule using the at least one consumer NF parameter; In response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule; generating a response message including the IP address; as well as The response message is transmitted to the requesting node.
2. The method according to claim 1, in: Receiving the request message includes receiving an NF discovery request message; and Determining the IP address to be returned to the requesting node includes: using at least one query parameter from the NF discovery request message to locate a NF profile of the producer NF, and using the producer NF IP address mapping rule to select the IP address from the NF profile.
3. The method of claim 2, wherein selecting the IP address using the producer NF IP address mapping rule comprises selecting the IP address from a plurality of IP addresses included in the NF profile.
4. The method of claim 2, wherein using the producer NF IP address mapping rule to select the IP address comprises using the producer NF IP address mapping rule to select a network address translated IP address as the IP address to be returned to the requesting node.
5. The method of any one of claims 2 to 4, wherein using the at least one consumer NF attribute to locate the IP address mapping rule comprises using at least one attribute obtained from the NF profile of the consumer NF or the source address of the request message to locate the IP address mapping rule.
6. The method according to any one of claims 2 to 5, wherein the requesting node comprises a consumer NF or a service communication proxy (SCP).
7. A method as claimed in any one of the preceding claims, in: Receiving the request message includes receiving a domain name system (DNS) resolution request message; and Determining the IP address to be returned to the requesting node includes: using the NF instance identifier mapped to the fully qualified domain name (FQDN) in the DNS resolution request message to locate the NF profile of the producer NF, and using the producer NF IP address mapping rule to select the IP address from the NF profile.
8. The method of claim 7, wherein using a consumer NF parameter to locate the IP address mapping rule comprises using a source IP address of the DNS resolution request message to locate the IP address mapping rule.
9. The method of claim 7 or claim 8, wherein receiving the DNS resolution request message from the requesting node comprises receiving the DNS resolution request message from a consumer NF and an SCP or a DNS server.
10. The method according to any one of claims 7 to 9, wherein determining the IP address comprises selecting the IP address from a plurality of IP addresses included in the NF profile, or selecting a network address translated IP address from the NF profile.
11. A system for supporting configurable producer network function (NF) Internet protocol (IP) address mapping, the system include: an NF Repository Function (NRF) comprising at least one processor and a memory, for receiving a request message for a network address and / or service information of a producer NF from a requesting node; a producer NF IP address mapper for determining at least one consumer NF parameter from the request message, locating a producer NF IP address mapping rule using the at least one consumer NF parameter, and in response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule; as well as A response generator implemented by the at least one processor is configured to generate a response message including the IP address and transmit the response message to the requesting node.
12. The system according to claim 11, in: The request message includes a NF discovery request message; and The producer NF IP address mapper is configured to determine the IP address to be returned to the requesting node by locating a NF profile of the producer NF using at least one query parameter from the NF discovery request message and selecting the IP address from the NF profile using the producer NF IP address mapping rule.
13. The system of claim 12, wherein the producer NF IP address mapper is configured to use the producer NF IP address mapping rule to select the IP address from a plurality of IP addresses included in the NF profile.
14. The system of claim 12, wherein the producer NF IP address mapper is configured to use the producer NF IP address mapping rule to select a network address translated IP address as the IP address to be returned to the requesting node.
15. The system of any one of claims 12 to 14, wherein the producer NF IP address mapper is configured to locate the IP address mapping rule using at least one attribute obtained from the NF profile of the consumer NF or the source address of the request message.
16. The system according to any one of claims 11 to 15, in: The request message includes a Domain Name System (DNS) resolution request message; and The producer NF IP address mapper is configured to determine the IP address to be returned to the requesting node by locating the NF profile of the producer NF using the NF instance identifier mapped to the fully qualified domain name (FQDN) in the DNS resolution request message and selecting the IP address from the NF profile using the producer NF IP address mapping rule.
17. The system of claim 16, wherein the producer NF IP address mapper is configured to locate an IP address mapping rule using a source IP address of the DNS resolution request message.
18. The system of claim 16 or claim 17, wherein the requesting node comprises a consumer NF, a service communication proxy (SCP), or a DNS server.
19. The system of any one of claims 16 to 18, wherein determining the IP address comprises selecting the IP address from a plurality of IP addresses included in the NF profile, or selecting a network address translated IP address from the NF profile.
20. A non-transitory computer readable medium storing executable instructions, wherein when the executable instructions are executed by a processor of a computer, the computer is controlled to perform the following steps: At the Network Function (NF) Library Function (NRF): Receive a request message for the network address and / or service information of the producer NF from the requesting node; determining at least one consumer NF parameter from the request message; locating a producer NF IP address mapping rule using the at least one consumer NF parameter; In response to locating the producer NF IP address mapping rule, determining an IP address to be returned to the requesting node using the producer NF IP address mapping rule; generating a response message including the IP address; as well as The response message is sent to the requesting node.
Citation Information
Cited By
Communication method and apparatus
WO2026153178A1
