Internetwork address providing method and device, electronic equipment, storage medium and product

Abstract

The invention relates to the technical field of communication, and particularly provides an inter-network address providing method and device, electronic equipment, a storage medium and a product. In a cross-network access scene, aiming at the problems of signaling processing efficiency and service delay caused by the fact that NF instance IDs often involved in mobility management and service registration processes of a 5G network cannot be directly used for service request routing, NF service must be carried out or NF discovery needs to be carried out, a first inter-network address is carried in a service registration request, and the service registration request carries a second inter-network address. The second internetwork address is carried in the cross-network service calling request initiated when the service user is used, so that the service process of cross-network access based on the NF instance ID can be optimized, the situation that the internetwork address is acquired through multiple signaling processes is avoided, the cross-network access is realized through the internetwork address to ensure the security of the cross-network access, and the network access efficiency is improved. The cross-network access signaling processing efficiency is further improved, and the service time delay is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and device for providing an inter-network address, an electronic device, a storage medium, and a product. Background Art

[0002] The registration and addressing of NF instance IDs are often involved in the mobility management and service registration processes of 5G networks. Since NF instance IDs cannot be used directly for service request routing, NF services or NF discovery must be performed based on NF instance IDs first. In the scenarios of user authentication, service authentication, and cross-network access of international roaming services in non-contracted NPNs (non-public networks), considering inter-network access security, it is necessary to first perform an inter-network NF service discovery or NF discovery based on the instance ID of the target network function to obtain the inter-network address of the NF. The inter-network signaling process involves not only the multi-level cascading of service network elements, but also the inter-network interconnection network elements deployed between different networks, which makes the cross-network access signaling processing efficiency and service latency issues more prominent. In addition, under the NPN architecture, the topology hiding requirements between the non-contracted NPN accessed by NPN users and the NPN / PLMN contracted by users also need to consider the effective acquisition of the inter-network address of the NF in the NPN service process. Summary of the invention

[0003] In view of the above problems, the present disclosure is proposed. The present disclosure provides a method and device for providing an inter-network address, an electronic device, a storage medium and a product.

[0004] According to one aspect of the present disclosure, a method for providing an inter-network address is provided, which is applied to a first network function NF of a first network, and the method includes:

[0005] Sending a service registration request to the network storage function NRF, wherein the service registration request carries the first network address;

[0006] As a service user, a cross-network service call request is initiated, wherein the service call request carries a second network address.

[0007] According to another aspect of the present disclosure, there is provided an inter-network address providing device, comprising:

[0008] A registration unit, sending a service registration request to the network storage function NRF, wherein the service registration request carries the first network address;

[0009] The calling unit is used to initiate a cross-network service calling request as a service user, wherein the service calling request carries a second network address.

[0010] According to another aspect of the present disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the method described in any one of the above embodiments.

[0011] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, the method described in any of the above embodiments is implemented.

[0012] According to another aspect of the present disclosure, a computer program product is provided, including a computer program / instruction, which implements the method described in any of the above embodiments when the computer program / instruction is executed by a processor.

[0013] As described in detail below, according to an embodiment of the present disclosure, a method and device for providing an internet address, an electronic device, a storage medium and a product are provided. In the present disclosure, on the one hand, in the NF service registration process, by carrying its own related internet address (i.e., the first internet address) in its service registration request, the NRF can obtain the internet address of each network function in the first network. In this way, in the cross-network access process, there is no need to perform additional internet service discovery or NF discovery based on the NF instance ID, and only a simple interaction with the NRF is required to obtain the internet address of each NF in the network to which it belongs; on the other hand, in a specific cross-network access scenario, when a service user (e.g., the first NF) initiates a service call request, it will carry its own internet address (i.e., the second internet address) in it. In this way, the opposite network can obtain the internet address of the service user, and then in some possible reverse cross-network scenarios, the second internet address can be directly applied to achieve reverse cross-network access to the first NF. In this process, the inter-network address of the NF is carried in the service registration request and the service call request, which can be used to notify the recipient of its own inter-network address status, and the other side can reversely access or call accordingly. That is, the inter-network address interaction and synchronization of NFs between different networks are realized through the service call process. Therefore, in the actual cross-network access scenario, the technical solution provided by the present disclosure can optimize the business process of cross-network access based on NF instance ID, avoid the acquisition of inter-network addresses through multiple signaling processes, and realize cross-network access through inter-network addresses to ensure the security of cross-network access, thereby further improving the signaling processing efficiency of cross-network access and reducing business latency.

[0014] It is to be understood that both the foregoing general description and the following detailed description are exemplary, and are intended to provide further explanation of the technology as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and other purposes, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0016] Figure 1 A flowchart of a method for providing an inter-network address provided in an embodiment of the present disclosure.

[0017] Figure 2 A flowchart of another method for providing an inter-network address provided in an embodiment of the present disclosure.

[0018] Figure 3 A flowchart of another method for providing an inter-network address provided in an embodiment of the present disclosure.

[0019] Figure 4 A flowchart of another method for providing an inter-network address provided in an embodiment of the present disclosure.

[0020] Figure 5 A schematic diagram of a CH architecture of an NPN provided in an embodiment of the present disclosure.

[0021] Figure 6 A flowchart of another method for providing an inter-network address provided in an embodiment of the present disclosure.

[0022] Figure 7 A structural block diagram of an inter-network address providing device provided in an embodiment of the present disclosure.

[0023] Figure 8 A hardware block diagram of an electronic device provided in an embodiment of the present disclosure.

[0024] Fig. 9 A schematic diagram of a computer program product provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present disclosure more obvious, the exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described here.

[0026] The present disclosure is applicable to any cross-network access scenario, specifically, to a cross-network service call or NF call scenario, which will be described in detail below in conjunction with an embodiment.

[0027] The mobility management and service registration processes of 5G networks often involve the registration and addressing of NF instance IDs, and service invocation and discovery need to be based on NF instance IDs.

[0028] The NF instance ID, also known as the network element instance ID, adopts the Universally Unique Identifier (UUID) format, that is, UUID = time-low"-"time-mid"-"time-high-and-version"-"clock-seq-and-reserved clock-seq-low"-"node. The NF instance ID cannot be used directly for service request routing, and NF service or NF discovery must be performed.

[0029] For ease of understanding, the Access and Mobility Management Function (AMF) and Short Message Service Function (SMSF) are used as examples for specific explanation. In the processes of mobility management and SMS service registration, AMF and SMSF will register their instance IDs with the Unified Data Management (UDM).

[0030] In this way, when UDM calls AMF's service to subscribe to UE's reachability status, location and other events, the instance ID cannot be directly used for routing service request messages, and the AMF instance ID must be used for service discovery / NF discovery first. Similarly, when the SMS system goes to UDM to query the SMSF address, it will obtain the SMSF's NF instance ID. When the SMS system calls SMSF's service to forward MT SMS through the service-based interface, it must first use the SMSF instance ID for service discovery / NF discovery.

[0031] When using NF instance ID for service discovery / NF discovery, the service user carries the NF instance ID as a service discovery parameter and sends it to NRF, and NRF returns the NFprofile of the matched NF to the service user. In this way, the service user can truly obtain the inter-network address of AMF or SMSF and perform subsequent inter-network access. The inter-network signaling process not only involves the multi-level cascading of service network elements, but also involves the inter-network interconnection network elements deployed between different networks, which makes the cross-network access signaling processing efficiency and service latency issues more prominent.

[0032] In summary, the process of obtaining inter-network addresses is complicated and cumbersome, and the efficiency of cross-network access is low. In view of this situation, the present disclosure provides a new design concept: when NF, as a service user, initiates an inter-network service call, it carries its own inter-network address in its request, so that the opposite network can know the inter-network address of the NF of this network. In this way, the inter-network address interaction and synchronization of NFs between different networks are realized through the service call process. The following is a detailed description.

[0033] The present disclosure provides a method for providing an inter-network address, which is applied to a first network function NF of a first network. In the present disclosure, the first network can be any network in a cross-network scenario. For the sake of distinction, the present disclosure takes the cross-network access of two networks as an example for specific description, and one of the networks is referred to as the first network, and the other is recorded as the second network. The present disclosure has no special restrictions on the network types of the first network and the second network, and the two can be the same or different. Its possible application scenarios are described in detail later in conjunction with the embodiments, and are not repeated here for the time being. The first NF in the present disclosure can be any NF in the first network that has the ability to request cross-network services, which will be described in detail later.

[0034] Please refer to Figure 1 , Figure 1 The following is a flow chart of a method for providing an inter-network address according to an embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0035] S102, the first NF sends a service registration request to the NRF, where the service registration request carries the first internet address.

[0036] like Figure 1 As shown, NRF and the first NF belong to the same first network, that is, S102 means that when NF sends a service registration request to the NRF of this network, it can carry its own related inter-network service address. As a network function used to implement the network storage function (or network warehousing function) in the first network, NRF can store the first inter-network address of each network function in the first network. In addition, in some embodiments, NRF can also support service discovery or NF discovery function. Therefore, when cross-network access is required, if NRF receives an NF discovery or NF service discovery request, it can directly feedback the inter-network address of NF or NF service to the other side, without the need for additional NF discovery processing based on NF instance ID, saving resources and improving access efficiency.

[0037] In an actual implementation scenario, any NF can register an NF with the NRF or register an NF service. Therefore, the first Internet address carried here can specifically be: the Internet address of the first NF or the Internet address of the first NF service.

[0038] S104, the first NF, as a service user, initiates a cross-network service call request, and the service call request carries the second inter-network address.

[0039] like Figure 1 As shown, the specific scenario targeted by the present disclosure is a cross-network access scenario. Any NF in any network in the scenario can act as a service user to request a service call from a service provider in another network, or can act as a service provider to provide services to service users in another network. In addition, Figure 1 The service provider shown can be any network function in the second network that can have cross-network service capabilities, for example, NRF, AMF, SMSF, UDM, authentication server function (Authentication Server Function, AUSF) in the second network, etc., without exhausting them.

[0040] Based on this, Figure 1 S104 shows the situation where the first NF, as a service user (or service initiator), initiates a cross-network service call request. It should be understood that Figure 1 S102 and S104 in the figure show two different processes. The present disclosure has no special restrictions on the logical relationship between the two processes. However, in general scenarios, NF generally registers first and then requests other NFs to provide cross-network services. However, it is inevitable that in some possible special scenarios, NF may first initiate a cross-network service request and then initiate (or initiate simultaneously) a service registration request.

[0041] It should be noted that in the present disclosure, in addition to conventional information (not described here, and reference may be made to relevant technologies or standards), the cross-network service call request initiated by the NF as a service user also carries a second inter-network address. The second inter-network address may specifically be the inter-network address of the first NF.

[0042] In an exemplary embodiment, please refer to Figure 2 , Figure 2 A flowchart of another method for providing an inter-network address provided by an embodiment of the present disclosure. Figure 2 As shown, AMF can act as the first NF to initiate a service registration request to NRF, and can also initiate a service call request (or also referred to as a service request) to the UDM (or other network element) of the second network. Figure 2 As shown, when AMF initiates a service registration request to NRF, the inter-network address of AMF or the inter-network address of AMF service (i.e., the first inter-network address mentioned above) can be carried in the NF profile of AMF. In addition, when AMF needs to call NF or NF service of other networks, for example Figure 2When calling the UDM service of the second network in the scenario, Nudm_UECM_Registration (i.e., a service call request for UDM) can be sent to the UDM of the second network, and the inter-network address of AMF (i.e., the second inter-network address) can be carried in the service call request. Figure 2 The illustrated embodiment provides two possible implementations of carrying the AMF network address in the service call request:

[0043] Amf3GppAccessRegistration and AmfNon3GppAccessRegistration carry the inter-network address of AMF or the service request header field extension carries the inter-network address of AMF. Both implementation methods can carry the second inter-network address in the cross-network service call request, which will be explained in detail later and will not be expanded here.

[0044] Based on this, the opposite network can obtain the inter-network address of the service user, and then in some possible reverse cross-network scenarios, the second inter-network address can be directly applied to achieve reverse cross-network access to the first NF. In other words, if the opposite network needs to reversely initiate a cross-network service call request to the first NF, there is no need to perform an additional inter-network address acquisition process, and the service call request can be directly initiated based on this. In this way, after multiple cross-network service calls, the first network and the second network can each obtain the inter-network address of at least part of the NF in the opposite network, and then directly perform inter-network service calls without the need for additional inter-network address discovery based on the NF instance ID. In other words, by carrying the second inter-network address in the cross-network service call request, the synchronization and exchange of the inter-network addresses of the NFs between different networks can be achieved based on multiple cross-network service call interactions between different networks.

[0045] In this process, the inter-network address of the NF is carried in the service registration request and the service call request, which can be used to notify the recipient of its own inter-network address status, and the other side can reversely access or call accordingly. That is, the inter-network address interaction and synchronization of NFs between different networks are realized through the service call process. Therefore, in the actual cross-network access scenario, the technical solution provided by the present disclosure can optimize the business process of cross-network access based on NF instance ID, avoid the acquisition of inter-network addresses through multiple signaling processes, and realize cross-network access through inter-network addresses to ensure the security of cross-network access, thereby further improving the signaling processing efficiency of cross-network access and reducing business latency.

[0046] In addition, as mentioned above, any NF can be used as both a service user and a service provider. In this case, the first NF can act as a service provider and receive a cross-network service call request initiated by the second NF of the second network, the service call request carries a third inter-network address, and uses the third inter-network address as the inter-network address of the second NF.

[0047] It should be noted that the second NF involved in this embodiment is Figure 1 The service providers in the illustrated embodiment may be the same or different, depending on the calling requirements in the actual cross-network access calling scenario.

[0048] In the present disclosure, any NF in the first network and the second network that has the ability to call cross-network services can initiate a cross-network service call request to the NF of the opposite network and carry its own Internet address. Taking the first NF as an example, the first NF, as a service user, can carry the Internet address of the first NF (i.e., the second Internet address) in the cross-network service call request initiated by itself; and the first NF, as a service provider, can also determine that the third Internet address is the Internet address of the second NF on the opposite side based on the third Internet address carried in the received cross-network service call request. In this way, if the first NF subsequently needs to initiate a cross-network service call to the second NF on the opposite side, it can directly use the third Internet address without going through additional NF discovery or NF service discovery.

[0049] In addition, in a cross-network service call request, in addition to the service user's own Internet address, the service provider's Internet address can also be carried.

[0050] In an exemplary embodiment, Figure 1 The S104 shown can be specifically implemented as follows: the first NF, as a service user, initiates a cross-network service call request to the second NF of the second network; wherein, when the Internet address of the second NF is received, the Internet address of the second NF is carried in the service call request.

[0051] In this embodiment, the inter-network address of the second NF carried in the service call request can be used as the destination address of the service call request. That is, after receiving the service call request, the second network can directly send the service call request to the second NF without performing NF discovery or NF service discovery in the second network, thereby improving the access efficiency between networks.

[0052] For example, please refer to Figure 3 , Figure 3 A flowchart of another method for providing an inter-network address provided by an embodiment of the present disclosure. Figure 3As shown, two possible situations are shown in which the first NF (ie, UDM) acts as a service provider and a service user respectively.

[0053] On the one hand, UDM can act as a service provider and receive service call requests initiated by the service user AMF (i.e., the second NF of the second network). For AMF, AMF initiates a service call request to UDM and carries the Internet address of AMF in it. In this scenario, for the service provider UDM, when it receives the service call request, it can use the Internet address carried in it as the Internet address of AMF. Furthermore, if UDM subsequently needs to call the AMF or AMF service across networks, it can directly use the Internet address of AMF. For example Figure 3 The second half deals with the situation where AMF acts as a service provider.

[0054] On the other hand, UDM can act as a service user and initiate a service call request, namely Namf_EventExposure_Subscribe, to the AMF of the second network; at this time, AMF, as a service provider, receives the service call request initiated by UDM. In this embodiment, since UDM has already received the inter-network address of AMF, it can directly use the inter-network address of AMF, that is, the inter-network address of AMF as the service request address. No additional NF discovery is required in this process.

[0055] It should be noted that in the present disclosure, the first network and the second network are only used to distinguish different networks in the cross-network scenario, so any network can be used as the first network, and the NF in any network can be used as the first NF of this solution to implement this solution. No further details will be given.

[0056] In addition, in the present disclosure, some NFs may have relevant capabilities for data storage or maintenance, such as NRF, UDM, etc. Based on this, these NFs (as the first NF) may also maintain the internet address-related data of themselves or the network to which they belong.

[0057] For example, for NRF, UDM or other first NFs with data storage or maintenance capabilities, when it receives a cross-network service call request as a service provider, it can maintain the second NF and the third Internet address accordingly (for ease of explanation, the corresponding relationship between the NF and its Internet address will be recorded as Internet address related data in the following. It should be understood that there may be other names in actual scenarios, such as Internet routing data, Internet address relationship, etc., which are not exhaustive or limited), so as to be applied by itself or provided to other NFs in the future. In this embodiment, the method may also include: when a cross-network service call request is received, the second NF and the third Internet address carried therein are stored accordingly.

[0058] For another example, for NRF, UDM or other first NFs with data storage or maintenance capabilities, in addition to maintaining the internet address related data received by itself according to the aforementioned embodiment, it can also maintain the internet address related data of other networks received by other NFs in the first network to which it belongs. For example, a specific NF (which can be any one of the first NFs mentioned above or any one of the first network) can be customized and specified, and the internet address related data of other networks can be maintained by the specific NF, and when other first NFs receive a cross-network service call request, they can send the internet address related data received by themselves to the specific NF. Therefore, in this embodiment, the method can also include the following steps: when receiving a cross-network service call request, the first NF sends the second NF and the third internet address carried in the service call request to the specific NF. For a specific NF, the method can also include: the specific NF receives the second NF and the third internet address from the first NF, and stores the second NF and the third internet address accordingly.

[0059] In the two embodiments described above, the first NF (or specific NF) can record and obtain the inter-network routing information of NFs in other networks, and subsequently, convenient cross-network service calls can be implemented directly based on these data without the need for a complex NF instance-based NF discovery process.

[0060] In addition, in the above two embodiments, the first NF (or specific NF) can realize its own use based on the maintained inter-network routing related information (that is, it can directly initiate cross-network service calls as a service user), and can also provide it to other NFs to facilitate their cross-network service access.

[0061] In an exemplary embodiment, when other NFs need to initiate a cross-network service call to the second NF, they can send an address query request for the second NF to the first NF. At this time, the inter-network address provision method that can be executed by the first NF can also include the following steps:

[0062] The first NF may receive an address query request for the second NF; thus, when the address query request is used in a cross-network service call process and the internet address of the second NF has been received, the internet address of the second NF is returned for the address query request.

[0063] For example, the first NF may be a UDM, which maintains information related to the inter-network address carried in the cross-network service call request received by each NF in the first network. Therefore, when the AMF (or any other network element such as the SMSF) needs to initiate a cross-network service call to the second NF, the AMF may send an address query request for the second NF to the UDM. The UDM may receive the address query request and determine whether the inter-network address of the second NF has been received through its own maintenance data; if it has been received, the inter-network address of the second NF may be fed back to the AMF, so that the second NF may initiate a cross-network service call request accordingly; on the contrary, if it has not been received, the UDM does not maintain the inter-network address of the second NF, at which point the UDM may feed back to the AMF as empty or perform NF discovery through other methods (such as NF service / NF discovery methods in some prior art, in this embodiment, these NF service / NF discovery methods may be used as a supplementary solution to the technical solution provided by the present disclosure), for example, NF discovery through the NF instance ID.

[0064] also, Figure 4 A possible implementation example of this scenario is given as an example. Figure 4 A flowchart of another method for providing an inter-network address provided in an embodiment of the present disclosure. Figure 4 The scenario shown is still described in detail by taking the UDM of the first network as the first NF as an example.

[0065] like Figure 4 As shown, UDM can receive a service call request initiated by SMSF (i.e., the second NF of the second network), namely Nudm_UECM_Registration, which can carry the network address of SMSF. Specifically, the network address of SMSF can be carried in SmsfRegistration or the network address of SMSF can be carried in the service request header field extension, which will be explained in detail later and will not be expanded here. Based on this, for UDM, UDM can maintain the network address of SMSF.

[0066] On this basis, UDM can also receive address query requests for the second NF from other network elements (recorded as the third NF). The third NF here can belong to any network. When the third NF belongs to the same network as the second NF requested for query, for example, when the third NF is any NF that belongs to the second network together with the SMSF, the Internet address of the second NF can actually be determined by addressing or querying within the network. To this end, the Internet address of the second NF can be determined by the method of this solution, or it can be determined by the method within the network. The present disclosure has no special restrictions on this. In addition, the third NF can be any other network except the second network, which can include but is not limited to the first network. In other words, the first NF of the first network can receive address query requests (or called called route query requests) from other NFs of the same network for the second NF, and can also receive address query requests for the second NF from any NF of any network other than its own network. Exemplarily, Figure 4 This situation is shown, Figure 4 The "other network different from the second network" in the above may specifically be the first network, Figure 4 The third NF in the example may specifically be an SMS center or an IP-SM-GW, etc., without exhausting the list.

[0067] like Figure 4 As shown, for UDM, UDM can receive a user roaming SMS service called route query request initiated by a third NF in a network different from the second network (i.e., the address query request for the second NF in the previous text). Based on this, since UDM has previously received the inter-network address of SMSF, and the address query request is used for the cross-network service call process, at this time, UDM can send the inter-network address of SMSF (i.e., the inter-network address of the second NF) to the third NF. Thus, Figure 4 As shown, based on the inter-network address of SMSF, the third NF can initiate a cross-network service call to SMSF.

[0068] In addition, the inter-network address can have many forms. In the present disclosure, the inter-network address of any NF is different from the actual address of the NF. In other words, the inter-network address is a hidden address used by the NF in the cross-network communication scenario. The inter-network address is known by other networks but does not expose the real address of the NF and the real topology of the network to which it belongs.

[0069] The present disclosure has no particular restrictions on the actual design of the inter-network address. In actual scenarios, the inter-network address of the NF can be determined by at least one of the following methods, but not limited to: encryption algorithm, mapping relationship, custom indication or setting program or algorithm. The inter-network address of the NF can be related to its actual address (for example, obtained by encryption or other algorithm processing based on the actual address), or it can be unrelated (for example, a custom setting of the mapping relationship).

[0070] In an exemplary embodiment, the internet address of the NF or NF service involved in the present disclosure may include, but is not limited to: a fully qualified domain name (FQDN).

[0071] Based on this, the NF's inter-network address can be distinguished from its real address, and its own network address and topological structure can be hidden during the cross-network service call process, ensuring the security of the cross-network service call process.

[0072] In addition, in the embodiments provided by the present disclosure, both the service registration request and the cross-network service call request can carry the Internet address. For example, the service registration request carries the Internet address related to the registrant (i.e., the first NF in S102); for another example, the service call request can carry the Internet address of the service user (such as S104 above), and can further carry the Internet address of the service provider (for example, in one embodiment above, the service call request for the second NF can carry the third Internet address of the second NF).

[0073] Based on this, in actual scenarios, the service call request carries the second internet address, which may include but is not limited to at least one of the following:

[0074] Mode 1: Carrying the second Internet address in the resource attribute of the resource related to the service call request.

[0075] Exemplarily, the resources related to the service call request can be customized, and the present disclosure has no particular restrictions on this. Exemplarily, the resources related to the service call request can be specifically its original resources, that is, a new resource attribute can be added to the original resources related to the service call request, and the newly added resource attribute can be specifically used to carry the inter-network routing address. For example, in the cross-network service call scenario of international roaming, the resource definition extension can support the new attribute part to carry the inter-network address, such as the international roaming network element address identifier. For another example, in the special cross-network service call scenario of the non-public network (NPN) certificate holder (CH) architecture, new attributes can also be defined in the service call request to hide the topology between the NPN and CH networks, wherein the new attributes can be used to represent at least one of the CH network, NPN, and NF type (i.e., NF type).

[0076] Mode 2: Carrying the second Internet address in the header field of the service call request.

[0077] In this embodiment, the internet routing address can be carried in the header field of the service call request. The present disclosure has no special restrictions on the header field structure of the request. For example, it can be Figure 1 As shown in the header field structure, in this case, the internet address can be carried by identifying the service user identity (NF type) and feature support capability header field extension.

[0078] It should be understood that both the above-mentioned method 1 and method 2 can carry the second internet address in the service call request. In actual scenarios, one or the other can be used, or they can be used in combination. The present disclosure has no particular restrictions on this.

[0079] In addition, the above-mentioned methods 1 and 2 actually provide how to carry the Internet address in the request message, which can be carried in the resource attributes of the resource related to the request (i.e., method 1), or carried in the header field of the request (method 2). It should be understood that the above only takes the second Internet address carried in the service call request as an example to illustrate the process. In actual scenarios, other situations involving carrying the Internet address in the request can adopt at least one of these two methods. For example, the present disclosure also involves carrying the first Internet address in the service registration request, which can also adopt at least one of the above-mentioned methods 1 and 2, and will not be repeated.

[0080] As mentioned above, the inter-network address providing method provided by the present disclosure can be applied to any cross-network access scenario, as exemplified below.

[0081] The first NF involved in the present disclosure may be any NF with cross-network access capability, and the present disclosure does not provide an exhaustive list of such NFs. For ease of understanding, the first NF may include, but is not limited to, at least one of the following: access and mobility management function AMF, SMSF, unified data management UDM or authentication server function AUSF, NF with cross-network service-oriented interface in roaming architecture or NPN deployment.

[0082] It should be understood that in actual scenarios, the first NF may also be other NFs with cross-network access capabilities, which are not exhaustive. In addition, based on different types of the first NF, its cross-network service call process may also be different.

[0083] Exemplarily, when the first NF is AMF, the cross-network service call process may be an AMF registration process; when the first NF is SMSF, the cross-network service call process may be an SMSF registration process; when the first NF is UDM, the cross-network service call process may be a capability open subscription process, etc. Of course, other possible cross-network service call processes may also be possible in actual scenarios, and this is only an exemplary description.

[0084] In addition, as mentioned above, the first NF can be a service user or a service provider, and the second NF mentioned above can also be a service user or a service provider; for any NF with cross-network access capability, it can be a service user or a service provider; and for service providers, there are no special restrictions. For example, when the service provider does not have cross-network communication capabilities, it can provide services to service users through other NFs in the network that have cross-network communication capabilities. Therefore, the service provider can be any NF in the network.

[0085] In addition, the first network and the second network involved in the present disclosure may be any network, and the present disclosure has no special restrictions on this, and they can be determined based on actual scenarios.

[0086] Exemplarily, the first network in the present disclosure may include but is not limited to at least one of the following: a public land mobile network PLMN, an independent non-public network (Stand-alone NPN, SNPN), a certificate holder CH network of a non-public network NPN, a satellite operator network, and a land mobile network. This list is not exhaustive. Similarly, the second network may also include but is not limited to at least one of the following: a public land mobile network PLMN, an independent non-public network SNPN, a certificate holder CH network of a non-public network NPN, a satellite operator network, and a land mobile network.

[0087] In addition, based on the different networks to which each NF belongs, in order to facilitate network communication, for any NF / NF service, the inter-network address of the NF / NF service may also carry relevant information for indicating the network to which the NF belongs.

[0088] Exemplarily, the internet address of the NF / NF service may carry the network identifier of the network to which the NF belongs.

[0089] In one embodiment, when the first network is a public land mobile network PLMN, the network address of the NF or NF service carries a PLMN identifier.

[0090] In another embodiment, when the first network is an independent non-public network SNPN, the internet address of the NF or NF service carries a SNPN identifier.

[0091] In another embodiment, when the first network is a certificate holder CH network of a non-public network NPN, the service registration request also carries CH related information, and the CH related information is used to indicate that the first NF is a NF in the CH network or the first network is a CH network.

[0092] That is, under the Credentials Holder architecture of NPN, the first network can be SNPN or PLMN. In addition to carrying the first inter-network address in the NF registration request or NF service registration request, the first inter-network address can also carry relevant information of the Credentials Holder (such as the network identifier of the CH network), which is used to identify itself as a NF of a Credentials Holder. The present disclosure has no special restrictions on the specific method of network identification, which can be specifically at least one of the network name, network number or other custom identifiers, and the present disclosure has no special restrictions on this.

[0093] The following takes the international roaming scenario and the NPN CH scenario as examples to illustrate possible implementation examples of the present solution.

[0094] In the international roaming scenario, when AMF performs cross-PLMN mobility management registration and SMSF performs short message service registration, the topology-hidden inter-network routing service address used for inter-network service requests can be carried in the service registration request, that is, the inter-network address mentioned in the previous text of this disclosure. In this way, UDM can save the inter-network routing service addresses of AMF and SMSF serving roaming UEs in the above-mentioned business process, so that the SMS system can obtain the inter-network service address of SMSF by querying UDM. In addition, the inter-network routing service address can be carried by extending the resource definition in the service call request for mobility management and short message service registration to support new attributes (such as the international roaming network element address identifier), or it can be carried by extending the header field that identifies the service user identity (NF type) and feature support capabilities.

[0095] In the specific implementation, first in the UE registration and SMS service registration process, AMF and SMSF determine that the UE is a roaming user. When calling Nudm_UEContextManagement Service, the service registration request carries the hidden network address, and UDM saves the mapping relationship between the instance ID of AMF and SMSF and its network routing service address in the above process.

[0096] For example. In the interactive process of AMF registering inter-network service with UDM, the inter-network address can be carried in its service registration request. That is, the optional attribute inter-network routing service address can be added to Amf3GppAccessRegistration and AmfNon3GppAccessRegistration, and its data format can be specifically FQDN; or, the format can be extended in the header field of the above service registration request to support it carrying the inter-network routing service address. Among them, roaming communication can be carried out between AMF and UDM through the N8 interface.

[0097] In addition, UDM can send response information to AMF based on the service registration request. The content and method of the response information are not limited. For example, the response information may include but is not limited to: no content, established, forbidden, general failure error code, etc. Among them, no content means No Content; established means Created, that is, establishing the registration of AMF; forbidden means Forbidden; general failure error code means general failure error codes. The present disclosure has no special restrictions on how UDM responds to service registration requests, which can be determined based on relevant technologies or standards.

[0098] In the above service registration process, UDM can also save the mapping relationship between the AMF instance ID and its inter-network address (i.e., inter-network routing service address). Therefore, when UDM needs to call AMF services across networks, it can check the mapping relationship it maintains; further, if the mapping relationship contains the inter-network address of the AMF, service discovery can be omitted, and the inter-network routing service address of the AMF can be used directly in the service call request (for example, in its Uniform Resource Identifier (URI)).

[0099] For AMF, in the prior art, when UDM calls AMF's service to subscribe to UE's accessible status, location and other events, the instance ID cannot be directly used for routing service request messages, and the AMF instance ID must be used for service discovery / NF discovery first; compared to this, AMF carries its own Internet address when registering with UDM. If UDM calls AMF's service subsequently, there is no need to perform service discovery, but the service call function can be directly implemented based on the Internet address of AMF, which greatly simplifies the steps and methods for obtaining the Internet address, and is conducive to improving cross-network access efficiency.

[0100] For another example, in the process of SMSF registering internet service with UDM, the internet address can be carried in its service registration request. That is, the optional attribute internet routing service address can be added to SmsfRegistration (i.e. SMSF registration request), and its data format can be specifically FQDN; or, the format can be extended in the header field of the above service request (i.e. SmsfRegistration) to support it carrying the internet routing service address.

[0101] Similarly, in the SMSF registration scenario, UDM can respond to SMSF based on relevant technologies or standards, which may include but not limited to two situations: establishment and prohibition. The establishment is Created (SmsfRegistration), which means to establish SMSF registration; Forbidden means to be prohibited. No further details are given.

[0102] In addition, UDM can also save the mapping relationship between SMSF instance ID and its inter-network address (i.e., inter-network routing service address). Therefore, on the one hand, in the called routing query process of the user's roaming SMS service, SMS-GMSC, SMSRouter, IP-SM-GW, etc. can obtain the inter-network routing service address of SMSF from UDM; in specific implementation, it can be implemented by sending an address query request to UDM as described above, and SMSF can provide services to the outside as a service provider. On the other hand, when SMS-GMSC, SMS Router, IP-SM-GW, etc. need to call the MtForwardSm service of SMSF, if there is an inter-network routing service address, the inter-network routing service address can be used directly in the service call request URI without performing NF service discovery. Among them, SMSF can communicate with any one of SMS-GMSC, SMS Router, and IP-SM-GW through the Nsmsf interface.

[0103] For SMSF, in the prior art, when the SMS system goes to UDM to query the SMSF address, it will obtain the NF instance ID of SMSF. When the SMS system calls the service of SMSF and forwards the MT SMS through the service-based interface, it will first use the SMSF instance ID for service discovery / NF discovery. Compared with this, SMSF carries its own inter-network address when registering with UDM. If the subsequent SMS system or SMS-GMSC, SMS Router, IP-SM-GW, etc., can directly obtain the inter-network address of SMSF by interacting with UDM, there is no need to perform service discovery based on the NF instance ID of SMSF. This greatly simplifies the steps and methods for obtaining the inter-network address, which is conducive to improving the efficiency of cross-network access.

[0104] In summary, in the PLMN deployment architecture involved in Guoman, both SMF and AMSF can support carrying the inter-network routing service address in the service call request in the scenario of UDM service call for roaming users. This can optimize the cross-network service call addressing and avoid the service discovery process based on NF instance ID.

[0105] In addition, it should be noted that the technical solution provided by the present disclosure can be applied not only to ordinary international roaming scenarios, but also to inter-network roaming scenarios of non-terrestrial networks accessed by satellites, such as inter-network roaming scenarios between satellite and ground. Specifically, in scenarios where a mobile user roams under the coverage of a satellite operator network and uses a mobile phone to directly route from the satellite operator network to the user's mobile network to implement inter-network roaming services between satellite and ground, this solution can also be used to implement inter-network roaming between satellite and ground. In this scenario, the first network can be specifically a satellite operator network, or it can also be a terrestrial mobile network.

[0106] In the CH scenario of NPN, this solution can also be used to achieve cross-network communication between the NPN network and the CH network.

[0107] Please refer to Figure 5 , Figure 5 A schematic diagram of a CH architecture of an NPN provided in an embodiment of the present disclosure. Figure 5 As shown, in the CH architecture of NPN, a SNPN network and a CH network are included, and the networks therebetween are isolated.

[0108] Specifically, the CH architecture of NPN can be used for Non subscribed NPN access. In related technologies, such as TS23.501, the CH network can use AUSF and UDM for primary identity authentication and authorization. For a non-roaming UE, such as Figure 5 In the architecture shown, for example, the AMF and SMF in the SNPN register with the UDM of the CH network and retrieve subscription data from it. In the above architecture, there is also topology hiding between the Non subscribed NPN and the subscribed NPN or the network (NPN or PLMN) where the CH is located.

[0109] Based on this, the SNPN network and the CH network can be used as the first network in the present disclosure in different scenarios, and the inter-network address provision method provided by the present disclosure can be used to implement cross-network service registration and access. For example, the service registration of the AMF and SMF in the SNPN to the UDM in the CH network can be implemented through the method of the present disclosure.

[0110] In the NPN CH architecture, new attributes can be defined in the service registration / NF registration request, and the new attributes can be used to hide the topology between the NPN and CH networks. Among them, the new attributes can be used to identify information such as the CH network, NPN, and NF type.

[0111] Specifically, the UDM registration of the network where the CH is located can use its own internet routing service address. The new attribute can identify the CH network and NPN, and the data format can also be FQDN. For UDM service discovery / NF discovery of non-contracted NPNs, the NRF in the SNPN can return the internet routing service address of the UDM. Among them, the internet address of the UDM can identify the CH network and NPN, and the data format can also be FQDN. When the AMF of the non-contracted NPN determines that it needs to access the UDM of the CH network, it can carry its own internet routing service address when registering the user context. The internet routing service address can be used to identify the CH network and NPN, and the data format can also be FQDN.

[0112] For the UDM of the CH network, the UDM can save the mapping relationship between the instance ID of the AMF and the internetwork routing service address. When the UDM of the CH network calls the service of the AMF, it does not need to perform service discovery and can directly use the internetwork routing service address of the AMF.

[0113] For example, please refer to Figure 6 , Figure 6 A flowchart of another method for providing an inter-network address provided by an embodiment of the present disclosure. Figure 6 In the illustrated scenario, the first network is a CH network of an NPN, and the second network is a SNPN network. Detailed description is given below.

[0114] like Figure 6 As shown, in the CH network of NPN, NFs such as UDM can initiate a service registration request to NRF. In the service registration request, in addition to the inter-network address of UDM or the inter-network address of UDM service as described above, CH related information is also carried. These CH related information can be used to indicate that UDM is a network function in the CH network or that the first network is a CH network.

[0115] In addition, if Figure 6 As shown in the figure, in the CH network architecture of NPN, network elements in the SNPN network (i.e., the second network), such as AMF, SMF, etc., can initiate NF discovery or service discovery for UDM to NRF. It should be understood that the communication between the second NF in the SNPN network, such as AMF, and the NRF in the CH network, is essentially still a cross-network service discovery or service call, so the communication or access between the two needs to be forwarded through multiple intermediate network elements; in this regard, Figure 6Some of the intermediate network elements that the two need to communicate through are shown, but this disclosure does not limit or elaborate on this. The following description will focus on the communication interaction process between AMF and NRF to explain this solution.

[0116] like Figure 6 As shown, AMF can initiate UDM discovery or UDM service discovery for UDM to NRF based on CH related information. In this regard, NRF can receive the request as the first NF mentioned above. In addition, since NRF has received the service registration request of UDM, NRF can feedback UDM related information to AMF, such as Figure 6 In the response message, NRF initiates a response message to AMF and carries the NF profile of UDM (including the internet address of UDM). Based on this, after receiving the response message, AMF can initiate a service call request to UDM based on the internet address of UDM (that is, using it as the service address of the service request). As mentioned above, the service call request can carry the internet address of AMF, which can be carried in Amf3GppAccessRegistration, AmfNon3GppAccessRegistration, or in the service request header field extension, which will not be repeated.

[0117] In summary, in the CH architecture of NPN, for the AMF or other NF (such as NRF) deployed by NPN, when it accesses the UDM of the CH network, it carries its own internet address. For example, when AMF accesses, it carries the internet routing service address of AMF in its request. The internet address can be used to identify the CN network or NPN. The data format of the internet address can be, but is not limited to, FQDN. For the UDM of the CH network, the UDM can save the mapping relationship between the NF instance ID and the internet routing service address, and when it is necessary to call the NF (such as AMF) in the NPN network, there is no need to perform NF / NF service discovery, and the internet routing service address of the NF can be used directly. In this process, not only is the method of obtaining the internet address simplified, but also the topology hiding requirement in the CH architecture of NPN is further solved. The NPN and CH networks can achieve secure communication under the premise of topology hiding.

[0118] In summary, in cross-network access scenarios, the NF instance ID often involved in the mobility management and service registration process of 5G networks cannot be directly used for service request routing, and the signaling processing efficiency and service delay problems caused by the need for NF service or NF discovery must be performed. The present disclosure carries the first inter-network address in the service registration request, and carries the second inter-network address in the cross-network service call request initiated when acting as a service user. This can optimize the service process based on cross-network access based on NF instance ID, avoid the inter-network address from being obtained through multiple signaling processes, and realizes cross-network access through the inter-network address to ensure the security of cross-network access, thereby further improving the signaling processing efficiency of cross-network access and reducing service delay.

[0119] The present disclosure also provides an inter-network address providing device, which can be deployed in any NF in the first network. Figure 7 A structural block diagram of an inter-network address providing device provided in an embodiment of the present disclosure, such as Figure 7 As shown, the network address providing device 700 includes:

[0120] The registration unit 710 sends a service registration request to the network storage function NRF, wherein the service registration request carries the first network address;

[0121] The calling unit 720 is used to initiate a cross-network service calling request as a service user, wherein the service calling request carries a second network address.

[0122] In an exemplary embodiment, the device further includes a communication unit ( Figure 7 (not shown), the communication unit is specifically used to: as a service provider, receive a cross-network service call request initiated by the second NF of the second network, the service call request carries a third internet address, and uses the third internet address as the internet address of the second NF.

[0123] In an exemplary embodiment, the calling unit 720 is specifically used to: as a service user, initiate a cross-network service calling request to the second NF of the second network; wherein, when the Internet address of the second NF is received, the Internet address of the second NF is carried in the service calling request.

[0124] In an exemplary embodiment, the device further includes a communication unit ( Figure 7 (not shown), the communication unit is specifically used to: receive an address query request for the second NF; when the address query request is used for a cross-network service call process and the internet address of the second NF has been received, return the internet address of the second NF for the address query request.

[0125] In an exemplary embodiment, the first internet address is the internet address of the first NF or the internet address served by the first NF; the second internet address is the internet address of the first NF.

[0126] In an exemplary embodiment, the internet address of the NF or NF service includes: a fully qualified domain name (FQDN).

[0127] In an exemplary embodiment, when the first network is a public land mobile network PLMN, the network address of the NF or NF service carries a PLMN identifier; when the first network is an independent non-public network SNPN, the network address of the NF or NF service carries an SNPN identifier.

[0128] In an exemplary embodiment, when the first network is a certificate holder CH network of a non-public network NPN, the service registration request also carries CH related information, and the CH related information is used to indicate that the first NF is a NF in the CH network or the first network is a CH network.

[0129] In an exemplary embodiment, the service call request carries the second Internet address, including at least one of the following: carrying the second Internet address in a resource attribute of a resource related to the service call request; carrying the second Internet address in a header field of the service call request.

[0130] In an exemplary embodiment, the first network includes at least one of the following: a public land mobile network PLMN, an independent non-public network SNPN, a certificate holder CH network of a non-public network NPN, a satellite operator network, and a land mobile network.

[0131] In an exemplary embodiment, the first NF includes at least one of the following: access and mobility management function AMF, short message function SMSF, unified data management UDM or authentication server function AUSF, roaming architecture or NF with cross-network service interface in NPN deployment.

[0132] Figure 8 The electronic device 800 according to the embodiment of the present disclosure includes at least a memory, a processor and a computer program stored in the memory, and the processor executes the computer program to implement the inter-network address providing method described in any of the above embodiments.

[0133] Figure 8The electronic device 800 shown specifically includes: a central processing unit (CPU) 801, a graphics processing unit (GPU) 802 and a memory 803. These units are interconnected via a bus 804. The central processing unit (CPU) 801 and / or the graphics processing unit (GPU) 802 can be used as the above-mentioned processor, and the memory 803 can be used as the above-mentioned memory for storing computer-readable instructions. In addition, the electronic device 800 may also include a communication unit 805, a storage unit 806, an output unit 807, an input unit 808 and an external device 809, which are also connected to the bus 804.

[0134] Fig. 9 A schematic diagram of a computer-readable storage medium provided in an embodiment of the present disclosure. Fig. 9 As shown, a computer-readable storage medium 900 according to an embodiment of the present disclosure stores a computer program / instruction 901 thereon. When the computer program / instruction 901 is executed by a processor, the method for providing an address between networks described in any of the foregoing embodiments of the present disclosure is implemented. The computer-readable storage medium includes, but is not limited to, for example, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0135] The present disclosure further provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the method for providing an inter-network address as described in any of the foregoing embodiments of the present disclosure.

[0136] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0137] The block diagrams of the devices, apparatuses, equipment, and systems involved in this disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including," "comprising," "having," and the like are open words, referring to "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or," and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

[0138] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0139] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0140] Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

[0141] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0142] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A method for providing an inter-network address, characterized in that: A first network function NF applied to a first network, the method comprising: Sending a service registration request to the network storage function NRF, wherein the service registration request carries the first network address; As a service user, a cross-network service call request is initiated, wherein the service call request carries a second network address.

2. The method according to claim 1, characterized in that The method further comprises: As a service provider, receive a cross-network service call request initiated by a second NF of a second network, wherein the service call request carries a third internet address, and use the third internet address as the internet address of the second NF.

3. The method according to claim 2, characterized in that As a service user, initiating a cross-network service call request includes: As a service user, a cross-network service call request is initiated to the second NF of the second network; When the internet address of the second NF is received, the internet address of the second NF is carried in the service call request.

4. The method according to claim 2, characterized in that: The method further comprises: receiving an address query request for the second NF; When the address query request is used in a cross-network service call process and the internet address of the second NF has been received, the internet address of the second NF is returned in response to the address query request.

5. The method according to claim 1, characterized in that The first inter-network address is the inter-network address of the first NF or the inter-network address served by the first NF; The second internet address is the internet address of the first NF.

6. The method according to claim 1, characterized in that The internet address of the NF or NF service includes: a fully qualified domain name (FQDN).

7. The method according to claim 1, characterized in that When the first network is a public land mobile network PLMN, the inter-network address of the NF or NF service carries a PLMN identifier; When the first network is an independent non-public network SNPN, the internet address of the NF or NF service carries an SNPN identifier.

8. The method according to claim 1, characterized in that When the first network is a CH network of a certificate holder of a non-public network NPN, the service registration request further carries CH related information, where the CH related information is used to indicate that the first NF is a NF in the CH network or the first network is a CH network.

9. The method according to claim 1, characterized in that: The service call request carries a second internet address, including at least one of the following: Carrying the second internet address in the resource attribute of the resource related to the service call request; The second internet address is carried in the header field of the service invocation request.

10. The method according to any one of claims 1 to 9, characterized in that: The first network includes at least one of the following: a public land mobile network PLMN, an independent non-public network SNPN, a certificate holder CH network of a non-public network NPN, a satellite operator network, and a land mobile network.

11. The method according to any one of claims 1 to 10, characterized in that: The first NF includes at least one of the following: access and mobility management function AMF, short message function SMSF, unified data management UDM or authentication server function AUSF, roaming architecture or NF with cross-network service interface in NPN deployment.

12. An inter-network address providing device, characterized in that: include: A registration unit, sending a service registration request to the network storage function NRF, wherein the service registration request carries the first network address; The calling unit is used to initiate a cross-network service calling request as a service user, wherein the service calling request carries a second network address.

13. An electronic device, characterized in that: include: a memory for storing computer readable instructions; as well as A processor is used to run the computer-readable instructions so that the electronic device executes the method according to any one of claims 1 to 11.

14. A non-transitory computer-readable storage medium for storing computer-readable instructions, characterized in that: When the computer-readable instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The method comprises a computer program, which implements the method according to any one of claims 1 to 11 when being executed by a processor.

Images