A SEPP addressing method, apparatus, device, storage medium, and product

Abstract

This application discloses a SEPP addressing method, apparatus, device, storage medium, and product. The second SEPP obtains the IP address of the service provider corresponding to the service provider's external access domain name by at least one of the following methods: initiating a second service discovery request to a second NRF, initiating a DNS query request to a DNS, and using a second mapping relationship between the external access domain name and IP address based on the locally cached data. Using the embodiments of this application, it is possible to eliminate the need to configure FQDN mapping information for NFs with roaming interfaces across the entire network, greatly reducing the amount and complexity of SEPP configuration.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a SEPP addressing method, apparatus, device, storage medium and product. Background Technology

[0002] SEPP (Security Edge Protection Proxy) is used for signaling security protection across PLMN (Public Land Mobile Network). It is usually deployed centrally at the operator's network boundary and needs to interoperate with the entire network's 5GC (5th Generation Core Network).

[0003] Currently, when SEPP searches for the IP address of a Network Function (NF) within the network, SEPP needs to pre-configure the FQDN (Fully Qualified Domain Name) mapping information of all NFs with roaming interfaces across the entire network, resulting in a huge amount of SEPP configuration and increasing the complexity of SEPP configuration. Summary of the Invention

[0004] This application provides a SEPP addressing method, apparatus, device, storage medium, and product to solve the problem that in the prior art, SEPP requires pre-configuration of FQDN mapping information of NFs with roaming and interconnection interfaces across the entire network, resulting in a huge amount of SEPP configuration and increased SEPP configuration complexity.

[0005] To achieve the above objectives, embodiments of this application provide a SEPP addressing method applied to a second SEPP, the SEPP addressing method comprising:

[0006] Receive a service request sent by the first SEPP; the service request includes topology hiding information of the service provider;

[0007] The topology hiding information is restored to obtain the external access domain name of the service provider;

[0008] Based on the external access domain name of the service provider, query whether the IP address of the service provider exists in the second mapping relationship between the external access domain name and the IP address cached locally;

[0009] If so, then the IP address of the service provider is obtained;

[0010] If not, a second service discovery request is initiated to the second NRF, or a DNS query request is initiated to the DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider.

[0011] The first SEPP belongs to a first PLMN; and the second SEPP, the second NRF, the DNS and the service provider belong to a second PLMN.

[0012] As an improvement of the above scheme, the second mapping relationship is cached by at least one of the following manners:

[0013] A service discovery response sent by the second NRF is received, and original service provider information in the service discovery response is cached;

[0014] A second service discovery response returned by the second NRF based on the second service discovery request is cached;

[0015] A DNS query response returned by the DNS based on the DNS query request is cached.

[0016] As an improvement of the above scheme, before the receiving of the service request sent by the first SEPP, the SEPP addressing method further comprises:

[0017] A first service discovery request sent by the first SEPP is received; the first service discovery request comprises a fully qualified domain name of an international NRF in the second NRF, a network element type of the service provider and a network element type of a service user; wherein the first service discovery request is initiated by the service user, and the service user belongs to the first PLMN;

[0018] A third mapping relationship between a preset fully qualified domain name and IP addresses of different roaming scenarios is obtained;

[0019] According to the network element type of the service provider, a current roaming scenario in which the international NRF in the second NRF is located is confirmed; or, according to the network element type of the service provider and the network element type of the service user, the current roaming scenario in which the international NRF in the second NRF is located is confirmed;

[0020] According to the third mapping relationship, the fully qualified domain name of the international NRF in the second NRF and the current roaming scenario, an IP address of the international NRF in the second NRF is obtained.

[0021] As an improvement of the above scheme, the initiating of the second service discovery request to the second NRF comprises:

[0022] initiating a second service discovery request to an international NRF in the second NRF, the second service discovery request being configured to instruct the international NRF to query an IP address of the service provider from an NRF in the second NRF according to an external access domain name of the service provider.

[0023] To achieve the above object, the embodiment of the present application further provides an SEPP addressing method, applied to a second NRF, comprising:

[0024] receiving a second service discovery request initiated by a second SEPP; the second service discovery request comprising an external access domain name of a service provider;

[0025] querying an IP address of the service provider according to the external access domain name of the service provider;

[0026] sending a second service discovery response to the second SEPP, the second service discovery response comprising the IP address of the service provider.

[0027] To achieve the above object, the embodiment of the present application further provides an SEPP addressing method, applied to a second NRF, comprising:

[0028] receiving a service discovery request sent by a second SEPP;

[0029] in response to the service discovery request, sending a service discovery response to the second SEPP, so that the second SEPP acquires an IP address of a service provider corresponding to an external access domain name of the service provider according to a second mapping relationship between the external access domain name and the IP address cached locally;

[0030] wherein the service discovery response comprises original service provider information, and the second SEPP caches the second mapping relationship according to the original service provider information.

[0031] To achieve the above object, the embodiment of the present application further provides an SEPP addressing method, applied to a DNS, comprising:

[0032] receiving a DNS query request initiated by a second SEPP; the DNS query request comprising an external access domain name of a service provider;

[0033] acquiring a first mapping relationship between a preset external access domain name and an IP address;

[0034] acquiring an IP address of the service provider according to the first mapping relationship and the external access domain name of the service provider;

[0035] sending a DNS query response to the second SEPP, the DNS query response comprising the IP address of the service provider.

[0036] To achieve the above object, the embodiment of the present application further provides a SEPP addressing device, comprising:

[0037] a first receiving module, configured to receive a service request sent by a first SEPP; the service request comprising topology hiding information of a service provider;

[0038] a restoring module, configured to restore the topology hiding information to obtain an external access domain name of the service provider;

[0039] an addressing module, configured to query whether the IP address of the service provider exists in a second mapping relationship between the external access domain name and the IP address in a local cache according to the external access domain name of the service provider;

[0040] if yes, obtaining the IP address of the service provider;

[0041] if no, initiating a second service discovery request to a second NRF or initiating a DNS query request to a DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider;

[0042] wherein the first SEPP belongs to a first PLMN; and the second SEPP, the second NRF, the DNS and the service provider belong to a second PLMN.

[0043] To achieve the above object, the embodiment of the present application further provides a SEPP addressing device, comprising:

[0044] a second receiving module, configured to receive a service discovery request sent by a second SEPP;

[0045] a responding module, configured to send a service discovery response to the second SEPP in response to the service discovery request, so that the second SEPP queries the IP address of the service provider corresponding to the external access domain name of the service provider according to a second mapping relationship between the external access domain name and the IP address in a local cache;

[0046] wherein the service discovery response comprises original service provider information, and the second SEPP caches the second mapping relationship according to the original service provider information.

[0047] To achieve the above object, the embodiment of the present application further provides a SEPP addressing device, comprising:

[0048] a third receiving module, configured to receive a second service discovery request initiated by a second SEPP; the second service discovery request comprising an external access domain name of a service provider;

[0049] a querying module, configured to query an IP address of the service provider according to the external access domain name of the service provider;

[0050] a first sending module, configured to send a second service discovery response to the second SEPP, the second service discovery response comprising the IP address of the service provider.

[0051] To achieve the above object, the embodiment of the present application further provides a SEPP addressing device, comprising:

[0052] a fourth receiving module, configured to receive a DNS query request initiated by a second SEPP; the DNS query request comprising an external access domain name of a service provider;

[0053] a first obtaining module, configured to obtain a first mapping relationship between a preset external access domain name and an IP address;

[0054] a second obtaining module, configured to obtain the IP address of the service provider according to the first mapping relationship and the external access domain name of the service provider;

[0055] a second sending module, configured to send a DNS query response to the second SEPP, the DNS query response comprising the IP address of the service provider.

[0056] To achieve the above object, the embodiment of the present application further provides a SEPP addressing device, comprising a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the SEPP addressing method as described above.

[0057] To achieve the above object, the embodiment of the present application further provides a computer readable storage medium, comprising a stored computer program; wherein the computer program, when running, controls a device where the computer readable storage medium is located to execute the SEPP addressing method as described above.

[0058] To achieve the above object, the embodiment of the present application further provides a computer program product, comprising computer programs / instructions, which, when executed by a processor, implement the SEPP addressing method as described above.

[0059] Compared with the prior art, the SEPP addressing method, apparatus, device, storage medium and product provided in this application embodiment obtains the IP address of the service provider corresponding to the external access domain name of the service provider by the second SEPP through at least one of the following methods: initiating a second service discovery request to the second NRF, initiating a DNS query request to the DNS, and a second mapping relationship between the external access domain name and IP address based on local caching. This changes the static configuration method in the prior art to a dynamic query / dynamic storage method, eliminating the need to configure the FQDN mapping information of NFs with roaming interfaces across the entire network, greatly reducing the amount of SEPP configuration, thereby reducing SEPP configuration cost and complexity. It also avoids the phenomenon that once the IP address of an NF in the network changes, the FQDN mapping information in the SEPP needs to be updated synchronously, which can easily lead to problems in inter-network roaming signaling interaction due to information asynchrony. This greatly reduces maintenance costs and improves the SEPP addressing accuracy. Attached Figure Description

[0060] Figure 1 This is a flowchart of an existing SEPP addressing method provided by the internetwork.

[0061] Figure 2 This is a flowchart of a SEPP addressing method provided in an embodiment of this application;

[0062] Figure 3 This is a flowchart illustrating how SEPP discovers NF IP addresses via NRF, as provided in an embodiment of this application.

[0063] Figure 4 This is another flowchart of a SEPP addressing method provided in an embodiment of this application;

[0064] Figure 5 This is another flowchart of a SEPP addressing method provided in an embodiment of this application;

[0065] Figure 6 This is another flowchart of a SEPP addressing method provided in an embodiment of this application;

[0066] Figure 7 This is a structural block diagram of a SEPP addressing device provided in an embodiment of this application;

[0067] Figure 8 This is another structural block diagram of a SEPP addressing device provided in an embodiment of this application;

[0068] Figure 9 This is another structural block diagram of a SEPP addressing device provided in the embodiments of this application;

[0069] Figure 10This is another structural block diagram of a SEPP addressing device provided in the embodiments of this application;

[0070] Figure 11 This is a structural block diagram of a SEPP addressing device provided in an embodiment of this application. Detailed Implementation

[0071] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0072] It is worth noting that, taking the following example: TLS (Transport Layer Security) is not enabled within the intranet, the 3gpp-Sbi-Target-apiRoot header field is not used between SEPPs, and the first PLMN contains a service consumer (NF), a first NRF (c-NRF), and a first SEPP (c-SEPP), while the second PLMN contains a second SEPP (p-SEPP), a second NRF (p-NRF), and a service producer (NF), the existing inter-network service discovery process and service invocation (i.e., service request) process are as follows: Figure 1 :

[0073] The service user first initiates a cross-PLMN service discovery request (Nnrf_NF Discovery Request). The first NRF is configured to send Nnrf_NF Discovery Requests to the first SEPP in all cross-PLMN scenarios and constructs the FQDN for the second NRF. The first SEPP, based on the received FQDN (including the PLMN ID) from the second NRF, forwards the Nnrf_NF Discovery Request to the corresponding second SEPP. The second SEPP obtains the Nnrf_NF Discovery Response from the second NRF, where the service provider's FQDN is the external access domain name (InterPLMNFQDN). After performing topology hiding, it returns the response to the first SEPP. The first SEPP forwards the Nnrf_NF Discovery Response to the first NRF, which then forwards the Nnrf_NF Discovery Response to the service user.

[0074] The service user initiates a service invocation request (business request) HTTP / 2Service Request based on the received service discovery response. By default, the service user is configured to send the HTTP / 2Service Request to the first SEPP for cross-border scenarios. The first SEPP forwards the HTTP / 2Service Request to the second SEPP. The second SEPP performs topology reconstruction to obtain the service provider's InterPLMNFQDN and forwards the HTTP / 2Service Request to the service provider using the FQDN routing policy. Upon receiving the HTTP / 2Service Response, the second SEPP forwards it to the first SEPP, which then forwards the HTTP / 2Service Response to the service user.

[0075] In view of this, the embodiments of this application optimize steps 9-11 above, changing the static configuration method in the prior art to a dynamic query / dynamic storage method. It eliminates the need to configure the FQDN mapping information of NFs with roaming interoperability interfaces across the entire network, greatly reducing the amount of SEPP configuration, thereby reducing SEPP configuration costs and complexity. It also avoids the phenomenon that once the IP address of an NF in the network changes, the FQDN mapping information in SEPP needs to be updated synchronously, which can easily lead to problems in inter-network roaming signaling interaction due to information asynchrony. This greatly reduces maintenance costs and improves SEPP addressing accuracy.

[0076] See Figure 2 , Figure 2 This is a flowchart of a SEPP addressing method provided in an embodiment of this application. The SEPP addressing method is applied to a second SEPP and includes:

[0077] S11. Receive a service request sent by the first SEPP; the service request includes topology hiding information of the service provider;

[0078] S12. Restore the topology hiding information to obtain the external access domain name of the service provider;

[0079] S13. Based on the external access domain name of the service provider, query whether the IP address of the service provider exists in the second mapping relationship between the external access domain name and the IP address cached locally;

[0080] S14. If yes, then obtain the IP address of the service provider;

[0081] S15. If not, initiate a second service discovery request to the second NRF, or initiate a DNS query request to the DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider.

[0082] Wherein, the first SEPP belongs to the first PLMN; the second SEPP, the second NRF, the DNS and the service provider belong to the second PLMN.

[0083] In this embodiment, a service user initiates a service request to a first SEPP, which then sends the request to a second SEPP. The second SEPP receives the service request (which is a cross-PLMN service call request) and restores the topology hiding information of the service provider included in the request to obtain the external access domain name of the service provider. Specifically, the second SEPP restores the FQDN of the service provider based on the destination URI in the topology hiding information (or based on the 3gpp-Sbi-Target-apiRoot header field if it is carried) to obtain the external access domain name interplmnFqdn of the service provider.

[0084] Based on the external access domain name of the service provider, query whether the IP address of the service provider exists in the second mapping relationship between the external access domain name and the IP address cached locally;

[0085] If so, then the IP address of the service provider is obtained;

[0086] If not, a second service discovery request is initiated to the second NRF, or a DNS query request is initiated to the DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider.

[0087] In other words, this application provides three methods for obtaining the service provider's IP address:

[0088] Method 1 for obtaining IP address: SEPP obtains the IP address of the service provider by capturing and caching the second mapping relationship.

[0089] Based on the external access domain name of the service provider, query whether the IP address of the service provider exists in the second mapping relationship between the external access domain name and the IP address cached locally. If so, the IP address of the service provider is obtained.

[0090] In this embodiment of the application, the IP address of the service provider corresponding to the external access domain name can be obtained based on the second mapping relationship between the external access domain name and the IP address cached by the second SEPP. For example, after the second SEPP receives a service request sent by the first SEPP, it can query the IP address of the service provider corresponding to the external access domain name of the service provider through the second mapping relationship between the external access domain name and the IP address cached by the second SEPP.

[0091] Method 2 for obtaining IP address: SEPP discovers the IP address of the service provider through NRF.

[0092] A second service discovery request is initiated to the second NRF, which instructs the second NRF to query the IP address of the service provider.

[0093] Specifically, the second service discovery request is used to instruct the second NRF to query the IP address of the service provider based on the service provider's external access domain name. In the second service discovery request, the external access domain name of the service provider, interplmnFqdn, is carried in the target-nf-fqdn field. Furthermore, a new SEPP value is added to the requester-nf-type field, indicating that the second service discovery request is initiated by a second SEPP.

[0094] In this embodiment of the application, the second SEPP may initiate a second service discovery request to the second NRF. The second service discovery request includes the external access domain name of the service provider. For example, after the second SEPP receives a service request sent by the first SEPP, if the IP address of the service provider cannot be found through the second mapping relationship, the second SEPP constructs a second service discovery request and sends the second service discovery request to the second NRF.

[0095] The second NRF receives the second service discovery request, queries the IP address corresponding to the service provider's external access domain name interplmnFqdn, and returns a second service discovery response to the second SEPP. The second service discovery response includes the service provider's IP address, such as... Figure 3 This application's embodiment changes the original static configuration method to a dynamic query method, eliminating the need to configure FQDN mapping information for NFs with roaming interoperability interfaces across the entire network. This significantly reduces the amount of SEPP configuration, thereby reducing SEPP configuration costs and complexity. It also avoids the situation where every change in the IP address of an NF within the network requires synchronous updates of FQDN mapping information in SEPP, which can easily lead to problems in inter-network roaming signaling interaction due to information asynchrony. This greatly reduces maintenance costs and improves SEPP addressing accuracy.

[0096] Method 3 for obtaining IP address: SEPP queries the service provider's IP address through DNS.

[0097] A DNS query request is initiated to the DNS, which instructs the DNS to query the IP address of the service provider.

[0098] It is understood that the DNS (Domain Name System) is configured with a first mapping relationship between external access domain names and IP addresses, and the DNS query request is specifically used to instruct the DNS to query the IP address of the service provider corresponding to the external access domain name of the service provider according to the first mapping relationship.

[0099] In this embodiment of the application, the second SEPP can initiate a DNS query request to the DNS, and the DNS query request includes the external access domain name of the service provider; for example, after the second SEPP receives a service request sent by the first SEPP, if the IP address of the service provider cannot be found through the second mapping relationship, the second SEPP constructs a DNS query request, which carries the external access domain name interplmnFqdn of the service provider, and sends the DNS query request to the DNS based on the trusted DNS IP address;

[0100] The DNS receives the DNS query request, queries the IP address corresponding to the external access domain name interplmnFqdn of the service provider, and returns a DNS query response to the second SEPP, which includes the IP address of the service provider.

[0101] In this embodiment of the application, the DNS needs to configure a first mapping relationship between the external access domain name and IP address of the NF with roaming and interconnection interface across the entire network; the second SEPP pre-configures a trusted DNS IP address.

[0102] This application's embodiment changes the original static configuration method to a dynamic query method, eliminating the need to configure FQDN mapping information for NFs with roaming interoperability interfaces across the entire network. This significantly reduces the amount of SEPP configuration, thereby reducing SEPP configuration costs and complexity. It also avoids the situation where every time the IP address of an NF within the network changes, the FQDN mapping information in SEPP needs to be updated synchronously, which can easily lead to problems in inter-network roaming signaling interaction due to information asynchrony. This greatly reduces maintenance costs and improves SEPP addressing accuracy.

[0103] In this embodiment, SEPP first checks locally whether the second mapping relationship has a corresponding IP address. If it does not exist, it then constructs a second service discovery request or DNS query request, which can improve the efficiency of service request forwarding and at the same time reduce the performance overhead of NRF and DNS as much as possible.

[0104] This application provides three methods for caching the second mapping relationship:

[0105] Caching method 1: Receive the service discovery response sent by the second NRF, and cache it according to the original service provider information in the service discovery response.

[0106] In this embodiment of the application, the second NRF responds to the received service discovery request by sending a service discovery response to the second SEPP; the service discovery response includes original service provider information, and the second SEPP caches the second mapping relationship based on the original service provider information (e.g., external access domain name and IP address) in the service discovery response;

[0107] The service discovery request is used to request services from the service provider; wherein, the service discovery request may be a first service discovery request initiated by a service user (this first service discovery request can be sent to the second SEPP through a normal process). Figure 1 In steps 1-3), the service discovery request can also be sent to the second SEPP according to the process provided below. The service discovery request can also be a second service discovery request initiated by the second SEPP (the second service discovery request provided by IP address acquisition method 1). For ease of description, we will use the term service discovery request here, and the response corresponding to the service discovery request will be referred to as the service discovery response.

[0108] Specifically, if the service discovery request is a first service discovery request initiated by a service user, and this first service discovery request is sent to the second SEPP through a normal process, then the service discovery response for this first service discovery request needs to be optimized in steps 5-6 above. Specifically:

[0109] Step 5: In the prior art, when the second NRF returns the service discovery response, it returns the external access domain name of the service provider and deletes and hides sensitive information such as IP addresses in the NF profile (Network Function Profile); therefore, the returned service discovery response does not include the service provider's IP.

[0110] This application optimizes it as follows: when the second NRF (e.g., the NRF of the second NRF) returns the service discovery response, it returns the external access domain name of the service provider, and does not delete or hide sensitive information such as IP address in NF profile. The returned service discovery response includes: the external access domain name of the service provider and the IP address of the service provider.

[0111] Step 6: In the prior art, before the second SEPP sends the service discovery response to the first SEPP, it transforms, modifies, or replaces important information in the service discovery response, such as CallbackURI, FQDN in the Location header field, IP address, and other sensitive information, through topology hiding.

[0112] This application optimizes the process as follows: Before the second SEPP sends the service discovery response to the first SEPP, the second SEPP caches the second mapping relationship based on the original service provider information (including its external access domain name and IP address) in the service discovery response result. Then, sensitive information such as IP address in NFprofile is deleted and hidden, and the external access domain name is hidden before the service discovery response is sent to the first SEPP.

[0113] Caching method 2: Cache the second service discovery response returned by the second NRF based on the second service discovery request.

[0114] In this embodiment of the application, the second mapping relationship of the service provider's IP address cache is obtained according to the IP address acquisition method 2.

[0115] Caching method 3: Cache the DNS query response returned by the DNS based on the DNS query request.

[0116] In this embodiment of the application, the second mapping relationship of the service provider's IP address cache is obtained according to the IP address acquisition method 3.

[0117] This application embodiment changes the original static configuration method to a dynamic configuration method, eliminating the need to configure the FQDN mapping information of NFs with roaming interoperability interfaces across the entire network. This greatly reduces the amount of SEPP configuration, thereby reducing SEPP configuration costs and complexity. It also avoids the phenomenon that once the IP address of an NF within the network changes, the FQDN mapping information in SEPP needs to be updated synchronously, which can easily lead to problems in inter-network roaming signaling interaction due to information asynchrony. This greatly reduces maintenance costs and improves SEPP addressing accuracy.

[0118] In this embodiment, the second SEPP can locally cache query results based on the external access domain name interplmnFqdn. Subsequently, IP address mapping can be performed directly based on the locally cached second mapping relationship using the external access domain name interplmnFqdn. This can improve the efficiency of business request forwarding while minimizing the performance overhead of NRF and DNS.

[0119] In this embodiment, the second SEPP can statically configure the aging time of the second mapping relationship, or age the cache result according to the validityPeriod time returned by the second NRF, which can ensure the accuracy of intra-network routing.

[0120] In an optional embodiment, the SEPP addressing method further includes:

[0121] The service request is sent to the service provider based on the service provider's IP address.

[0122] In this embodiment of the application, the IP address of the service provider is obtained through at least one of the above methods, and the service request is sent to the service provider through the IP address so that the service provider can provide services.

[0123] In an optional embodiment, before receiving the service request sent by the first SEPP, the SEPP addressing method further includes:

[0124] Receive a first service discovery request sent by the first SEPP; the first service discovery request includes the fully qualified domain name of the international NRF in the second NRF, the network element type of the service provider and the network element type of the service user; wherein, the first service discovery request is initiated by the service user, and the service user belongs to the first PLMN;

[0125] Obtain the third-party mapping relationship between the preset fully qualified domain name and the IP address in different roaming scenarios;

[0126] Based on the network element type of the service provider, determine the current roaming scenario of the international NRF in the second NRF; or, based on the network element type of the service provider and the network element type of the service user, determine the current roaming scenario of the international NRF in the second NRF.

[0127] Based on the third mapping relationship, the fully qualified domain name of the international NRF in the second NRF, and the current roaming scenario, the IP address of the international NRF in the second NRF is obtained.

[0128] This application embodiment considers the scenario where existing inter-network roaming and international roaming coexist. For the scenario where inbound I-NRFs (international-NRFs) and outbound I-NRFs are separately configured in inter-network roaming, the peer I-NRF can only be configured with one pair of local I-NRFs (mutually disaster-tolerant) FQDNs. This makes it impossible to distinguish between outbound and inbound scenarios, and cannot achieve correct routing for multiple I-NRFs (non-disaster-tolerant relationships). Therefore, differentiated identification and forwarding of local SEPPs needs to be implemented. Specifically:

[0129] SEPP pre-configures a third-party mapping relationship between fully qualified domain names and IP addresses in different roaming scenarios, exposing only one fully qualified domain name to the outside world; for example, one fully qualified domain name corresponds to one IP address in the roaming-in scenario and one IP address in the roaming-out scenario.

[0130] The service user initiates a first service discovery request and sends the first service discovery request to the first NRF. The first NRF sends the first service discovery request to the first SEPP, and the first SEPP sends the first service discovery request to the second SEPP.

[0131] The second SEPP receives the first service discovery request; then, based on the network element type of the service provider, it confirms the current roaming scenario of the international NRF in the second NRF; or, based on the network element type of the service provider and the network element type of the service user, it confirms the current roaming scenario of the international NRF in the second NRF; finally, based on the third mapping relationship, the fully qualified domain name of the international NRF in the second NRF, and the current roaming scenario, it obtains the IP address of the international NRF in the second NRF.

[0132] Understandably, for scenarios where the N14 interface is not enabled between networks, the current roaming scenario of the international NRF in the second NRF is determined based on the network element type of the service provider. For example, if the network element type of the service provider is AMF (Access and Mobility Management Function), it is determined to be a roaming-in scenario, and the IP address of the roaming-in scenario can be obtained; if the network element type of the service provider is UDM (Unified Data Management), it is determined to be a roaming-out scenario, and the IP address of the roaming-out scenario can be obtained.

[0133] In scenarios where the N14 interface is enabled between networks, the AMF (Application Provider Component) may be discovered as a network element in both roaming-out and roaming-in scenarios. In this case, SEPP needs to additionally consider the network element type of the service user to determine the current roaming scenario of the international NRF in the second NRF. For example, if both the service provider's and service user's network element types are AMF, it is determined to be a roaming-out scenario, and the IP address of the roaming-out scenario can be obtained. If both the service provider's and service user's network element types are AMF and UDM, it is determined to be a roaming-in scenario, and the IP address of the roaming-in scenario can be obtained.

[0134] In one optional embodiment, initiating the second service discovery request to the second NRF includes:

[0135] A second service discovery request is initiated to the international NRF in the second NRF. The second service discovery request is used to instruct the international NRF to query the IP address of the service provider from the NRF in the second NRF based on the external access domain name of the service provider.

[0136] In this embodiment, the second SEPP initiates a second service discovery request to the international NRF within the second NRF. The international NRF then sends this second service discovery request to the NRF within the second NRF, enabling the NRF to query the IP address of the service provider. Specifically, the NRF needs to match the SEPP service discovery scenario, and based on the value of `target-nf-fqdn`, queries the `interplmnFqdn` field information during network element registration to return the service provider's IP address.

[0137] See Figure 4 , Figure 4 This is another flowchart of a SEPP addressing method provided in an embodiment of this application. The SEPP addressing method is applied to a second NRF, and the SEPP addressing method includes:

[0138] S21. Receive the service discovery request sent by the second SEPP;

[0139] S22. In response to the service discovery request, a service discovery response is sent to the second SEPP, so that the second SEPP queries the IP address of the service provider corresponding to the external access domain name of the service provider according to the second mapping relationship between the external access domain name and the IP address cached locally.

[0140] The service discovery response includes original service provider information, and the second SEPP caches the second mapping relationship based on the original service provider information.

[0141] It should be noted that this embodiment is an implementation of the second NRF corresponding to the above method embodiment. Therefore, the relevant descriptions in the above method embodiment can be referred to, and the same beneficial effects can be achieved. To avoid repetition, further details will not be provided here.

[0142] See Figure 5 , Figure 5 This is another flowchart of a SEPP addressing method provided in an embodiment of this application. The SEPP addressing method is applied to a second NRF, and the SEPP addressing method includes:

[0143] S31. Receive a second service discovery request initiated by the second SEPP; the second service discovery request includes the external access domain name of the service provider;

[0144] S32. Query the IP address of the service provider based on the external access domain name of the service provider;

[0145] S33. Send a second service discovery response to the second SEPP, the second service discovery response including the IP address of the service provider.

[0146] It should be noted that this embodiment is an implementation of the second NRF corresponding to the above method embodiment. Therefore, the relevant descriptions in the above method embodiment can be referred to, and the same beneficial effects can be achieved. To avoid repetition, further details will not be provided here.

[0147] See Figure 6 , Figure 6 This is another flowchart of a SEPP addressing method provided in an embodiment of this application. The SEPP addressing method is applied to DNS, and the SEPP addressing method includes:

[0148] S41. Receive a DNS query request initiated by the second SEPP; the DNS query request includes the external access domain name of the service provider;

[0149] S42. Obtain the first mapping relationship between the preset external access domain name and IP address;

[0150] S43. Obtain the IP address of the service provider based on the first mapping relationship and the external access domain name of the service provider;

[0151] S44. Send a DNS query response to the second SEPP, the DNS query response including the IP address of the service provider.

[0152] It should be noted that this embodiment is an implementation of DNS corresponding to the above method embodiment. Therefore, the relevant descriptions in the above method embodiment can be referred to, and the same beneficial effects can be achieved. To avoid repetition, further details will not be provided here.

[0153] See Figure 7 , Figure 7 This is a structural block diagram of a SEPP addressing device provided in an embodiment of this application. The SEPP addressing device includes:

[0154] The first receiving module 11 is used to receive a service request sent by the first SEPP; the service request includes topology hiding information of the service provider;

[0155] The restoration module 12 is used to restore the topology hiding information to obtain the external access domain name of the service provider;

[0156] Addressing module 13 is used to query whether the IP address of the service provider exists in the second mapping relationship between the external access domain name and the IP address cached locally, based on the external access domain name of the service provider.

[0157] If so, then the IP address of the service provider is obtained;

[0158] If not, a second service discovery request is initiated to the second NRF, or a DNS query request is initiated to the DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider;

[0159] Wherein, the first SEPP belongs to the first PLMN; the second SEPP, the second NRF, the DNS and the service provider belong to the second PLMN.

[0160] Optionally, the SEPP addressing device further includes:

[0161] The first caching module is used to receive the service discovery response sent by the second NRF and cache it according to the original service provider information in the service discovery response.

[0162] The second caching module is used to cache the second service discovery response returned by the second NRF based on the second service discovery request.

[0163] The third caching module is used to cache the DNS query response returned by the DNS based on the DNS query request.

[0164] Optionally, the SEPP addressing device further includes:

[0165] The fifth receiving module is used to receive a first service discovery request sent by the first SEPP; the first service discovery request includes the fully qualified domain name of the international NRF in the second NRF, the network element type of the service provider and the network element type of the service user; wherein, the first service discovery request is initiated by the service user, and the service user belongs to the first PLMN;

[0166] The third acquisition module is used to obtain the third mapping relationship between the preset fully qualified domain name and the IP address of different roaming scenarios;

[0167] The confirmation module is used to confirm the current roaming scenario of the international NRF in the second NRF based on the network element type of the service provider; or, based on the network element type of the service provider and the network element type of the service user, to confirm the current roaming scenario of the international NRF in the second NRF.

[0168] The fourth acquisition module is used to obtain the IP address of the international NRF in the second NRF based on the third mapping relationship, the fully qualified domain name of the international NRF in the second NRF, and the current roaming scenario.

[0169] Optionally, initiating a second service discovery request to the second NRF includes:

[0170] A second service discovery request is initiated to the international NRF in the second NRF. The second service discovery request is used to instruct the international NRF to query the IP address of the service provider from the NRF in the second NRF based on the external access domain name of the service provider.

[0171] It should be noted that the SEPP addressing device described above in this embodiment can implement any step in the SEPP addressing method embodiment applied to the second SEPP in this application and achieve the same beneficial effect, which will not be elaborated here.

[0172] See Figure 8 , Figure 8 This is another structural block diagram of a SEPP addressing device provided in the embodiments of this application. The SEPP addressing device includes:

[0173] The second receiving module 21 is used to receive the service discovery request sent by the second SEPP;

[0174] The response module 22 is used to send a service discovery response to the second SEPP in response to the service discovery request, so that the second SEPP can obtain the IP address of the service provider corresponding to the external access domain name of the service provider according to the second mapping relationship between the external access domain name and the IP address cached locally;

[0175] The service discovery response includes original service provider information, and the second SEPP caches the second mapping relationship based on the original service provider information.

[0176] It should be noted that the SEPP addressing device described above in this embodiment can implement any step in the SEPP addressing method embodiment applied to the second NRF in this application and achieve the same beneficial effect, which will not be elaborated here.

[0177] See Figure 9 , Figure 9 This is another structural block diagram of a SEPP addressing device provided in an embodiment of this application. The SEPP addressing device includes:

[0178] The third receiving module 31 is used to receive a second service discovery request initiated by the second SEPP; the second service discovery request includes the external access domain name of the service provider;

[0179] The query module 32 is used to query the IP address of the service provider based on the external access domain name of the service provider;

[0180] The first sending module 33 is used to send a second service discovery response to the second SEPP, the second service discovery response including the IP address of the service provider.

[0181] It should be noted that the SEPP addressing device described above in this embodiment can implement any step in the SEPP addressing method embodiment applied to the second SEPP in this application and achieve the same beneficial effect, which will not be elaborated here.

[0182] See Figure 10 , Figure 10 This is another structural block diagram of a SEPP addressing device provided in the embodiments of this application. The SEPP addressing device includes:

[0183] The fourth receiving module 41 is used to receive a DNS query request initiated by the second SEPP; the DNS query request includes the external access domain name of the service provider;

[0184] The first acquisition module 42 is used to acquire the first mapping relationship between the preset external access domain name and IP address;

[0185] The second acquisition module 43 is used to acquire the IP address of the service provider based on the first mapping relationship and the external access domain name of the service provider;

[0186] The second sending module 44 is used to send a DNS query response to the second SEPP, the DNS query response including the IP address of the service provider.

[0187] It should be noted that the SEPP addressing device described above in this embodiment can implement any step in the SEPP addressing method embodiment applied to the second DNS in this application and achieve the same beneficial effect, which will not be elaborated here.

[0188] Furthermore, this application also provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the SEPP addressing method as described in any of the above embodiments.

[0189] Furthermore, this application also provides a computer program product, including a computer program / instruction that, when executed by a processor, implements the SEPP addressing method as described in any of the above embodiments.

[0190] See Figure 11 , Figure 11 This is a structural block diagram of a SEPP addressing device provided in an embodiment of this application. The SEPP addressing device includes: a processor 51, a memory 52, and a computer program stored in the memory 52 and executable on the processor 51. When the processor 51 executes the computer program, it implements the steps in the above-described SEPP addressing method embodiments. Alternatively, when the processor 51 executes the computer program, it implements the functions of each module / unit in the above-described device embodiments.

[0191] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 52 and executed by the processor 51 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the SEPP addressing device.

[0192] The SEPP addressing device may include, but is not limited to, processor 51 and memory 52. ​​Those skilled in the art will understand that the schematic diagram is merely an example of a SEPP addressing device and does not constitute a limitation on the SEPP addressing device. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the SEPP addressing device may also include input / output devices, network access devices, buses, etc.

[0193] The processor 51 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 51 is the control center of the SEPP addressing device, connecting all parts of the SEPP addressing device via various interfaces and lines.

[0194] The memory 52 can be used to store the computer program and / or modules. The processor 51 implements various functions of the SEPP addressing device by running or executing the computer program and / or modules stored in the memory 52 and calling the data stored in the memory 52. ​​The memory 52 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 52 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital card (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0195] Wherein, if the modules / units integrated in the SEPP addressing device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 51, it can implement the steps of the various method embodiments described above. Wherein, the computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying at least the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0196] It should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided in this application, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.

[0197] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications are also considered to be within the scope of protection of this application.

Claims

1. A method of SEPP addressing, characterized in that, The SEPP addressing method is applied to a second SEPP, and the SEPP addressing method comprises: receiving a service request sent by a first SEPP; the service request comprises topology hidden information of a service provider; restoring the topology hidden information to obtain an external access domain name of the service provider; querying whether an IP address of the service provider exists in a second mapping relationship between external access domain names and IP addresses cached locally according to the external access domain name of the service provider; if yes, obtaining the IP address of the service provider; if no, initiating a second service discovery request to a second NRF or initiating a DNS query request to a DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider; wherein the first SEPP belongs to a first PLMN; the second SEPP, the second NRF, the DNS and the service provider belong to a second PLMN.

2. The SEPP addressing method of claim 1, wherein, The second mapping relationship is cached by at least one of the following manners: receiving a service discovery response sent by the second NRF, and caching according to original service provider information in the service discovery response; caching according to a second service discovery response returned by the second NRF based on the second service discovery request; caching according to a DNS query response returned by the DNS based on the DNS query request.

3. The SEPP addressing method of claim 1, wherein, Before the receiving of the service request sent by the first SEPP, the SEPP addressing method further comprises: receiving a first service discovery request sent by the first SEPP; the first service discovery request comprises a fully qualified domain name of an international NRF in the second NRF, a network element type of the service provider and a network element type of a service user; wherein the first service discovery request is initiated by the service user, and the service user belongs to the first PLMN; obtaining a third mapping relationship between a preset fully qualified domain name and IP addresses of different roaming scenarios; confirming a current roaming scenario in which the international NRF in the second NRF is located according to the network element type of the service provider, or confirming the current roaming scenario in which the international NRF in the second NRF is located according to the network element type of the service provider and the network element type of the service user; obtaining an IP address of the international NRF in the second NRF according to the third mapping relationship, the fully qualified domain name of the international NRF in the second NRF and the current roaming scenario.

4. The SEPP addressing method of claim 1, wherein, The initiating of the second service discovery request to the second NRF comprises: initiating a second service discovery request to the international NRF in the second NRF, and the second service discovery request is used to instruct the international NRF to query the IP address of the service provider according to the external access domain name of the service provider.

5. A method of SEPP addressing, characterized in that, The SEPP addressing method is applied to a second NRF, and the SEPP addressing method comprises: When the second SEPP cannot find the IP address of the service provider in the second mapping relationship according to the external access domain name of the service provider, a second service discovery request initiated by the second SEPP is received; wherein the external access domain name of the service provider is obtained by restoring the topology hiding information of the service provider, the topology hiding information of the service provider is in the service request of the first SEPP, the second mapping relationship is a mapping relationship between the external access domain name and the IP address cached locally by the second SEPP, and the second service discovery request includes the external access domain name of the service provider; the first SEPP belongs to a first PLMN, and the second SEPP, the second NRF and the service provider belong to a second PLMN; The IP address of the service provider is queried according to the external access domain name of the service provider; A second service discovery response including the IP address of the service provider is sent to the second SEPP.

6. A method of SEPP addressing, characterized in that, The SEPP addressing method is applied to DNS, and the SEPP addressing method includes: When the second SEPP cannot find the IP address of the service provider in the second mapping relationship according to the external access domain name of the service provider, a DNS query request initiated by the second SEPP is received; wherein the external access domain name of the service provider is obtained by restoring the topology hiding information of the service provider, the topology hiding information of the service provider is in the service request of the first SEPP, the second mapping relationship is a mapping relationship between the external access domain name and the IP address cached locally by the second SEPP, and the DNS query request includes the external access domain name of the service provider; the first SEPP belongs to a first PLMN, and the second SEPP, the DNS and the service provider belong to a second PLMN; A first mapping relationship between a preset external access domain name and an IP address is obtained; The IP address of the service provider is obtained according to the first mapping relationship and the external access domain name of the service provider; A DNS query response including the IP address of the service provider is sent to the second SEPP.

7. A SEPP addressing device, characterized in that, It includes: A first receiving module configured to receive a service request sent by a first SEPP; The service request includes topology hiding information of a service provider; A restoring module configured to restore the topology hiding information to obtain an external access domain name of the service provider; An addressing module configured to query whether the IP address of the service provider exists in a second mapping relationship between an external access domain name and an IP address cached locally according to the external access domain name of the service provider; If yes, the IP address of the service provider is obtained; If no, a second service discovery request is initiated to a second NRF, or a DNS query request is initiated to a DNS; the second service discovery request is used to instruct the second NRF to query the IP address of the service provider, and the DNS query request is used to instruct the DNS to query the IP address of the service provider; The first SEPP belongs to a first PLMN; The second SEPP, the second NRF, the DNS, and the service provider belong to a second PLMN.

8. A SEPP addressing device, characterized in that, The method comprises the following steps: The third receiving module is configured to receive a second service discovery request initiated by the second SEPP when the second SEPP cannot find the IP address of the service provider in the second mapping relationship according to the external access domain name of the service provider, wherein the external access domain name of the service provider is obtained by restoring the topology hiding information of the service provider, the topology hiding information of the service provider exists in the service request of the first SEPP, the second mapping relationship is a mapping relationship between the external access domain name and the IP address locally cached by the second SEPP, and the second service discovery request comprises the external access domain name of the service provider; the first SEPP belongs to a first PLMN, and the second SEPP, the second NRF, and the service provider belong to a second PLMN. The querying module is configured to query the IP address of the service provider according to the external access domain name of the service provider. The first sending module is configured to send a second service discovery response to the second SEPP, wherein the second service discovery response comprises the IP address of the service provider.

9. A SEPP addressing device, characterized in that, The method comprises the following steps: The fourth receiving module is configured to receive a DNS query request initiated by the second SEPP when the second SEPP cannot find the IP address of the service provider in the second mapping relationship according to the external access domain name of the service provider, wherein the external access domain name of the service provider is obtained by restoring the topology hiding information of the service provider, the topology hiding information of the service provider exists in the service request of the first SEPP, the second mapping relationship is a mapping relationship between the external access domain name and the IP address locally cached by the second SEPP, and the DNS query request comprises the external access domain name of the service provider; the first SEPP belongs to a first PLMN, and the second SEPP, the DNS, and the service provider belong to a second PLMN. The first obtaining module is configured to obtain a first mapping relationship between a preset external access domain name and an IP address. The second obtaining module is configured to obtain the IP address of the service provider according to the first mapping relationship and the external access domain name of the service provider. The second sending module is configured to send a DNS query response to the second SEPP, wherein the DNS query response comprises the IP address of the service provider.

10. A SEPP addressing device, characterized in that, The computer readable storage medium comprises a stored computer program; wherein the computer program controls the device where the computer readable storage medium is located to execute the SEPP addressing method according to any one of claims 1-6 when running.

11. A computer readable storage medium, characterized in that, The computer readable storage medium comprises a stored computer program; wherein the computer program controls the device where the computer readable storage medium is located to execute the SEPP addressing method according to any one of claims 1-6 when running.

12. A computer program product, characterised in that, Computer program / instructions for implementing the SEPP addressing method according to any of claims 1-6 when executed by a processor.

Images