CN110290161A - A topology hiding method, node, functional entity and computer storage medium - Google Patents

Abstract

The embodiment of the invention discloses a topology hiding method, a node, a functional entity and a computer storage medium. The method includes: an edge node receives an ingress service discovery request, and replaces a service provider network function identifier in a service discovery response corresponding to the ingress service discovery request with a service provider network function identifier after topology hiding; the edge node Forwarding the service discovery response corresponding to the ingress service discovery request carrying the service provider network function identifier after the topology hiding.

Description

A topology hiding method, node, functional entity and computer storage medium

technical field

The invention relates to wireless communication technology, in particular to a topology hiding method, a node, a functional entity and a computer storage medium.

Background technique

The topology hiding of roaming signaling intercommunication is to hide the topology of the local network without violating the protocol standard, replace the real network element identification, and hide the signaling route in the network. The source host name in the request message and response message sent by this network needs to be hidden. The signaling addressing after topology hiding is to translate and restore the replaced network element identifier in the subsequent received message, so as to realize the addressing in the local network. The destination host name (identification of the network element of the local network) in the request message sent by the external network is a hidden identification, which needs to be translated and restored.

In the 4th generation mobile communication technology (4G, the 4th Generation mobile communication technology) network, Diameter signaling hop-by-hop addressing for international roaming, topology hiding is realized through the International Routing Agent (I-DRA) node of the Diameter signaling network, and I -DRA maintains the topology hidden mapping table and performs routing. The problem to be solved is to hide the identity of the source network element in the service request message and the response message, that is, to hide the network topology of the operator where the source node is located.

The service discovery process is introduced into the fifth generation mobile communication technology (5G, the 5th Generation mobile communication technology) network, which is implemented by a service discovery node (NRF), and the destination NF needs to be discovered before service access. In the roaming scenario, the NF accesses the other network's NRF through the local network's NRF to obtain the other network's NF ID or address. If the returned NF ID is not topologically hidden, it will expose the network topology of the operator where the destination node is located. Obviously, the existing technology can only hide the network topology of the operator where the source node is located, and cannot meet the topology hiding requirements of the destination node in the 5G network cross-operator service discovery scenario.

Contents of the invention

In order to solve the existing technical problems, the embodiment of the present invention provides a topology hiding method, a node, a functional entity and a computer storage medium.

In order to achieve the above object, the technical solution of the embodiment of the present invention is achieved in this way:

An embodiment of the present invention provides a topology hiding method, the method comprising:

The edge node receives the ingress service discovery request, and replaces the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding;

The edge node forwards a service discovery response corresponding to the ingress service discovery request that carries the topology-hidden service provider network function identifier.

In the above solution, the replacement of the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding includes: the edge node queries the preset mapping table Obtain the service provider network function identifier corresponding to the service provider network function identifier after topology hiding, and replace the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider after topology hiding Provider network capability ID.

In the above solution, the replacement of the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding includes: the edge node replaces the service provider network function identifier with the service provider The network function identifier is transformed into a service provider network function identifier after topology hiding, and the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request is replaced with the service provider network function identifier after topology hiding.

In the above solution, the method further includes: the edge node storing the mapping relationship between the service provider network function identifier and the service provider network function identifier after the topology hiding.

In the above scheme, the method further includes: the edge node judges that the message is a service discovery request based on the uniform resource identifier carried in the received message, and based on the service discovery request, the network function entity is discovered by an external network service The service discovery network function entity sent to the local network determines that the service discovery request is an ingress service discovery request.

In the above solution, the method further includes: the edge node receives an ingress service request; the ingress service request carries the network function identifier of the service provider after topology hiding;

The edge node replaces the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier;

The edge node sends a service request carrying the network function identifier of the service provider to the network function entity of the service provider of the local network.

In the above solution, the edge node replaces the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier, including: the edge node queries the preset mapping Table or stored mapping relationship, to obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding;

The edge node replaces the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier.

In the above solution, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In the above solution, the ingress service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network.

The embodiment of the present invention also provides a topology hiding method, the method comprising:

The service discovery network functional entity receives the ingress service discovery request;

The service discovery network function entity determines the service provider network function entity corresponding to the ingress service discovery request, and performs topology hiding on the service provider network function entity identifier;

The service discovery network function entity returns a service discovery response corresponding to the ingress service discovery request that carries the topology-hidden service provider network function entity identifier.

In the above solution, the topology hiding of the network function entity identifier of the service provider includes:

The service discovery network function entity determines whether a mapping relationship including the service provider network function entity identifier and the service provider network function entity identifier after the topology hiding is stored;

When a mapping relationship including the service provider network function entity identifier and the service provider network function entity identifier after the topology is hidden is stored, the topology corresponding to the service provider network function entity identifier is obtained based on the mapping relationship The hidden service provider network function entity identifier;

When the mapping relationship including the service provider network function entity identifier is not stored, generate a topology-hidden service provider network function entity identifier for the service provider network function entity identifier, and store the service provider network function entity identifier The mapping relationship between the entity identifier and the service provider network function entity identifier after the topology is hidden.

In the above solution, the method further includes: the service discovery network function entity receives a service discovery request from a node of the local network; the service discovery request carries a service provider network function entity identifier after topology hiding;

The service discovery network function entity determines the service provider network function entity identifier corresponding to the service provider network function entity identifier after the topology hiding;

The service discovery network function entity returns a service discovery response carrying the service provider network function entity identifier to the local network node.

In the above solution, the service discovery network function entity determines the service provider network function entity identity corresponding to the service provider network function entity identity after the topology hiding, including:

The service discovery network function entity queries the stored mapping relationship, and obtains the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding.

In the above solution, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

The embodiment of the present invention also provides a topology hiding method, the method comprising:

The node receives the ingress service request, and extracts the topology-hidden service provider network function identifier from the ingress service request;

The node sends a service discovery request carrying the network function identifier of the service provider after the topology hiding to the service discovery network function entity of the local network;

The node receives the service discovery response returned by the service discovery network function entity and carries the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding;

The node replaces the topology-hidden service provider network function identifier in the ingress service request with the service provider corresponding to the topology-hidden service provider network function identifier carried in the service discovery response. or network function entity identifier.

An embodiment of the present invention also provides an edge node, where the edge node includes: a first receiving unit, a first replacement unit, and a first sending unit, wherein,

The first receiving unit is configured to receive an ingress service discovery request;

The first replacement unit is configured to replace the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request received by the first receiving unit with the service provider network function identifier after topology hiding;

The first sending unit is configured to forward a service discovery response corresponding to the ingress service discovery request and carrying the network function identifier of the service provider after topology hiding.

In the above solution, the first replacement unit is configured to query the preset mapping table to obtain the topology-hidden service provider network function identifier corresponding to the service provider network function identifier, and to search the entry service discovery request for the corresponding service The service provider network function identifier in the discovery response is replaced by the service provider network function identifier after the topology is hidden.

In the above solution, the first replacement unit is configured to transform the service provider network function identifier into a service provider network function identifier after topology hiding, and match the ingress service discovery request to the service provider in the service discovery response. The provider network function identifier replaces the service provider network function identifier after the topology hiding.

In the above solution, the edge node further includes a first storage unit configured to store the mapping relationship between the service provider network function identifier and the service provider network function identifier after the topology hiding.

In the above solution, the edge node further includes a first judging unit, configured to judge that the message is a service discovery request based on the uniform resource identifier carried in the message received by the first receiving unit, and based on the service discovery request It is determined that the service discovery request is an ingress service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In the above solution, the first receiving unit is further configured to receive an ingress service request; the ingress service request carries the network function identifier of the service provider after the topology hiding;

The first replacement unit is further configured to replace the topology-hidden service provider network function identifier in the ingress service request received by the first receiving unit with the service provider network function identifier;

The first sending unit is further configured to send a service request carrying the service provider network function identifier to the local network service provider network function entity.

In the above solution, the first replacement unit is configured to query a preset mapping table or a stored mapping relationship, and obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding; The service provider network function identifier after the topology hiding in the ingress service request is replaced by the service provider network function identifier.

In the above solution, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In the above solution, the ingress service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network.

The embodiment of the present invention also provides a service discovery network function entity, the service discovery network function entity includes a second receiving unit, a topology hiding unit and a second sending unit; wherein,

The second receiving unit is configured to receive an ingress service discovery request;

The topology hiding unit is configured to determine the service provider network function entity corresponding to the ingress service discovery request received by the second receiving unit, and perform topology hiding on the service provider network function entity identifier;

The second sending unit is configured to return a service discovery response corresponding to the ingress service discovery request that carries the topology-hidden service provider network function entity identifier.

In the above solution, the service discovery network function entity further includes a second storage unit, configured to store a mapping relationship including the identifier of the service provider network function entity;

The topology hiding unit is configured to determine whether the second storage unit stores a mapping relationship containing the service provider network function entity identifier; when the second storage unit stores a mapping relationship containing the service provider network function entity identifier When the mapping relationship is based on the mapping relationship, the topology-hidden service provider network function entity identifier corresponding to the service provider network function entity identifier is obtained based on the mapping relationship; when the second storage unit does not store the For the mapping relationship of the network function entity identifier, generate a topology-hidden service provider network function entity identifier for the service provider network function entity identifier.

In the above solution, the second receiving unit is further configured to receive a service discovery request from a node of the local network; the service discovery request carries a service provider network function entity identifier after topology hiding;

The topology hiding unit is further configured to determine the service provider network function entity identifier corresponding to the service provider network function entity identifier after the topology hiding;

The second sending unit is further configured to return a service discovery response carrying the service provider network function entity identifier to the local network node.

In the above solution, the topology hiding unit is configured to query the stored mapping relationship, and obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding.

In the above solution, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

The embodiment of the present invention also provides a node, and the node includes: a third receiving unit, an extracting unit, a third sending unit, and a second replacing unit; wherein,

The third receiving unit is configured to receive an ingress service request;

The extracting unit is configured to extract the topology-hidden service provider network function identifier from the ingress service request received by the third receiving unit;

The third sending unit is configured to send a service discovery request carrying the service provider network function identifier after topology hiding to the service discovery network function entity of the local network;

The third receiving unit is further configured to receive a service discovery response returned by the service discovery network function entity and carrying the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding;

The second replacement unit is configured to replace the topology-hidden service provider network function identifier in the ingress service request with the topology-hidden service provider network carried in the service discovery response The service provider network function entity identifier corresponding to the function identifier.

The embodiment of the present invention also provides a computer storage medium on which computer instructions are stored, wherein when the instructions are executed by a processor, the steps of the topology hiding method applied to edge nodes described in the embodiment of the present invention are implemented; or,

When the instruction is executed by the processor, implement the steps of the topology hiding method applied to the service discovery network functional entity described in the embodiment of the present invention; or,

When the instruction is executed by the processor, the steps of the topology hiding method applied to the node described in the embodiment of the present invention are implemented.

An embodiment of the present invention also provides an edge node, including a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the program, it implements the Steps of the topology hiding method applied to edge nodes.

The embodiment of the present invention also provides a service discovery network functional entity, including a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements the embodiment of the present invention when executing the program The steps of the topology hiding method applied to edge nodes.

The embodiment of the present invention also provides a node, including a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the program, the application described in the embodiment of the present invention is realized. The steps of the node-based topology hiding method.

The topology hiding method, node, functional entity, and computer storage medium provided by the embodiments of the present invention, one method includes: the edge node receives an ingress service discovery request, and corresponds the ingress service discovery request to the service provider network in the service discovery response The function identifier is replaced with the network function identifier of the service provider after topology hiding; the edge node forwards the service discovery response corresponding to the ingress service discovery request carrying the network function identifier of the service provider after topology hiding. Adopting the technical solution of the embodiment of the present invention realizes the hiding of the service provider network function identifier of the service discovery response corresponding to the ingress service discovery request through the edge node in the service discovery scenario.

Another method includes: the service discovery network function entity receives the ingress service discovery request; the service discovery network function entity determines the service provider network function entity corresponding to the ingress service discovery request, and performs the identification of the service provider network function entity Topology hiding: the service discovery network function entity returns a service discovery response corresponding to the ingress service discovery request carrying the service provider network function entity identifier after topology hiding. Adopting the technical solution of the embodiment of the present invention realizes the hiding of the service provider network function identifier of the service discovery response corresponding to the ingress service discovery request through the service discovery network function entity in the service discovery scenario.

Description of drawings

FIG. 1 is a schematic diagram of an application architecture of a topology hiding method according to an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a topology hiding method according to Embodiment 1 of the present invention;

FIG. 3 is a schematic flowchart of a topology hiding method according to Embodiment 2 of the present invention;

FIG. 4 is a schematic flowchart of a topology hiding method according to Embodiment 3 of the present invention;

FIG. 5 is a schematic diagram of a specific interaction flow of the topology hiding method according to the embodiment of the present invention;

FIG. 6 is a schematic diagram of another specific interaction flow of the topology hiding method according to the embodiment of the present invention;

FIG. 7 is a schematic diagram of a composition structure of an edge node according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of another composition structure of an edge node according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another composition structure of an edge node according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a composition structure of a service discovery network functional entity according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of another composition structure of a service discovery network functional entity according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of the composition and structure of a node in an embodiment of the present invention.

Detailed ways

Before the topology hiding method of the embodiment of the present invention is described in detail, the system architecture of the topology hiding method of the embodiment of the present invention is first described. FIG. 1 is a schematic diagram of an application architecture of a topology hiding method according to an embodiment of the present invention; as shown in FIG. 1 , it includes a service discovery network function entity (NRF) and a service provider network function entity (NF). The system architecture also includes edge nodes for forwarding data between NRFs. Wherein, an example of an edge node may be a Security Edge Protection Proxy (SEPP, Security Edge Protection Proxy) node, and the node is used to be responsible for interaction security between networks. A connection can be established between any two nodes of SEPP, NRF and NF through the network.

In each embodiment of the present invention, the destination node of topology hiding in the service discovery scenario is NF, that is, in the following embodiments of the present invention, the service provider network function entity identifier may specifically be an NF ID (NF ID).

The present invention will be described in further detail below in conjunction with the accompanying drawings and specific embodiments.

Embodiment one

An embodiment of the present invention provides a topology hiding method. Fig. 2 is a schematic flow chart of a topology hiding method according to Embodiment 1 of the present invention; as shown in Fig. 2 , the method includes:

Step 101: The edge node receives the ingress service discovery request, and replaces the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding.

Step 102: The edge node forwards a service discovery response corresponding to the ingress service discovery request and carrying the network function identifier of the service provider after topology hiding.

In this embodiment, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity. Referring to the example in FIG. 1, if the edge node is the SEPP of network 2, then the The ingress service discovery request is a service discovery request sent by the NRF of network 1 to the NRF of network 2.

In this embodiment, the method further includes: the edge node judges that the message is a service discovery request based on the uniform resource identifier carried in the received message, and based on that the service discovery request is a network function discovered by an external network service The entity sends the service discovery network function entity of the local network to determine that the service discovery request is an ingress service discovery request.

Specifically, the edge node judges that the received message is an ingress service discovery request by judging that the message is a service discovery request through the API name of the uniform resource identifier (URI, Uniform Resource Identifier) carried in the message; further according to the message In other words, the message is sent by the network service discovery network functional entity to the local network service discovery network functional entity to determine that the service discovery request is an ingress service discovery request.

In this embodiment, as an implementation manner, the replacement of the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding includes: the edge The node queries the preset mapping table to obtain the topology-hidden service provider network function identifier corresponding to the service provider network function identifier, and replaces the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with The network function identifier of the service provider after the topology is hidden.

Specifically, a mapping table is pre-configured and stored in the edge node, and the mapping table records the service provider network function identifier (ie, NF ID) belonging to the local network and the service provider network function identifier (denoted as topology ID) after topology hiding. hidden NF ID) mapping relationship. In this way, in the scenario where the NF is used as the destination node or the source node to perform topology hiding, the same topology-hiding NF ID can be used for replacement, thereby reducing the mapping table space.

Then the edge node looks up the stored mapping table through the information carried in the ingress service discovery request or the service discovery response corresponding to the ingress service discovery request (for example, NF ID), and obtains the service provider network function identifier after topology hiding corresponding to the NF ID ( NF ID after topology hiding), replace the NFID in the service discovery response corresponding to the ingress service discovery request with the NF ID after topology hiding, and the edge node forwards the NF ID carrying the NF ID after topology hiding, corresponding to the ingress service discovery request service discovery response.

As another implementation manner, the replacing the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding includes: the edge node converting the The service provider network function identifier is transformed into the service provider network function identifier after topology hiding, and the service provider network function identifier in the corresponding service discovery response of the ingress service discovery request is replaced by the service provider network function after topology hiding logo. And, the method may further include: the edge node storing the mapping relationship between the service provider network function identifier and the service provider network function identifier after the topology hiding.

Specifically, in this embodiment, the edge node adopts dynamic transformation to generate the service provider network function identifier (NF ID after topology hiding) corresponding to the service provider network function identifier (NFID) corresponding to the service provider network function identifier (NF ID after topology hiding). After hiding the NF ID, record the mapping relationship between the NF ID and the NF ID after topology hiding.

In an embodiment, the method further includes: the edge node receives an ingress service request; the ingress service request carries the network function identifier of the service provider after topology hiding; the edge node sends the ingress service The service provider network function identifier after the topology hiding in the request is replaced by the service provider network function identifier; the edge node sends a message carrying the service provider network function identifier to the service provider network function entity of the local network Request for service.

In this embodiment, the ingress service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network. Referring to the example in FIG. 1, if the edge node is the SEPP of network 2, then the The ingress service request is a service request sent from the NF of network 1 as a service user to the NF of network 2 as a service provider.

In this embodiment, the edge node replaces the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier, including: the edge node queries the preset A mapping table or a stored mapping relationship to obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding; the edge node hides the topology in the ingress service request The service provider network function identifier is replaced by the service provider network function identifier.

It can be understood that the edge node receives an ingress service request, the ingress service request carries a topology-hidden NF ID, and obtains the NF ID corresponding to the topology-hidden NF ID representing the real NF identity by querying the mapping table or mapping relationship; The edge node replaces the network function ID of the service provider after topology hiding (ie, the NF ID after topology hiding) in the request of the ingress server with the real network function ID (NF ID) of the service provider.

Adopting the technical solution of the embodiment of the present invention realizes the hiding of the service provider network function identifier of the service discovery response corresponding to the ingress service discovery request through the edge node in the service discovery scenario.

Embodiment two

The embodiment of the present invention also provides a topology hiding method. FIG. 3 is a schematic flow diagram of a topology hiding method according to Embodiment 2 of the present invention; as shown in FIG. 3 , the method includes:

Step 201: The service discovery network function entity receives an ingress service discovery request.

Step 202: The service discovery network function entity determines the service provider network function entity corresponding to the ingress service discovery request, and performs topology hiding on the service provider network function entity identifier.

Step 203: The service discovery network function entity returns a service discovery response corresponding to the ingress service discovery request, carrying the topology-hidden service provider network function entity identifier.

In this embodiment, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity. Referring to the example in FIG. 1, if the service discovery network functional entity is the NRF of network 2 , the ingress service discovery request is a service discovery request sent from the NRF of network 1 to the NRF of network 2.

In this embodiment, the service discovery network function entity receives the ingress service discovery request, and determines the service provider network function entity (NF) corresponding to the ingress service discovery request.

In the embodiment of the present invention, the topology hiding of the service provider network function entity identifier includes: the service discovery network function entity determines whether to store the mapping relationship containing the service provider network function entity identifier; For the mapping relationship of the service provider network function entity identifier, obtain the topology-hidden service provider network function entity identifier corresponding to the service provider network function entity identifier based on the mapping relationship; When mapping the service provider network function entity identifier, generate a service provider network function entity identifier after topology hiding for the service provider network function entity identifier, and store the service provider network function entity identifier and the topology hidden The mapping relationship of the subsequent service provider network function entity identifier.

Specifically, the service discovery network function entity stores at least one set of mapping relationship between the service provider network function entity identifier and the service provider network function entity identifier after topology hiding, then find the service provider network function corresponding to the ingress service discovery request After the entity, judge whether there is a mapping relationship containing the service provider network function entity identifier through the stored mapping relationship; if the mapping relationship containing the service provider network function entity identifier is stored, obtain the service provider network function entity Identifies the corresponding service provider network function entity identifier after topology hiding (that is, the NF ID after topology hiding); if no mapping relationship including the service provider network function entity identifier is stored, then the service provider network function The entity identification generates the service provider network function entity identification after topology hiding (that is, the NF ID after topology hiding), and records the mapping relationship between the service provider network function entity identification (ie, NF ID) and the topology hiding NF ID.

Further, the service discovery network function entity returns the service discovery response corresponding to the ingress service discovery request carrying the identity of the service provider network function entity after topology hiding. Referring to the example in FIG. 1 , it can be understood that if the service discovery network function The entity is the NRF of network 2, and the NRF of network 2 receives the ingress service discovery request sent by the NRF of network 1; the NRF of network 2 determines the NF, and performs topology hiding for the NF ID; the NRF of network 2 sends the NRF back to the NRF of network 1 There is a service discovery response corresponding to the ingress service discovery request with the NF ID after topology hiding.

In an embodiment, the method further includes: the service discovery network function entity receives a service discovery request from a node on the local network; the service discovery request carries a service provider network function entity identifier after topology hiding; the service The discovery network function entity determines the service provider network function entity identity corresponding to the service provider network function entity identity after the topology hiding; the service discovery network function entity returns to the local network node carrying the service provider Service Discovery Response identified by the network function entity.

Specifically, the service discovery network functional entity receives a service discovery request from a node of the local network, and the node of the local network may be an edge node (such as SEPP) of the local network, or other nodes of the local network, which is not performed in this embodiment. Definition; wherein, the service discovery request carries the service provider network function entity identifier after topology hiding. Wherein, the node of the local network receives the ingress service request, and the ingress service request carries the network function identifier of the service provider. Then the local network node extracts the topology-hidden service provider network function identifier from the ingress service request; sends a service discovery request carrying the topology-hidden service provider network function identifier to the local network service discovery network function entity. The entry service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the home network; referring to the example shown in Figure 1, the entry service request is the service request of the network 1 as the service user. A service request sent by the NF to the NF of the network 2 as the service provider.

Wherein, the service discovery network function entity determines the service provider network function entity identifier corresponding to the service provider network function entity identifier after the topology hiding, including: the service discovery network function entity queries the stored mapping relationship, The service provider network function identifier corresponding to the service provider network function identifier after the topology hiding is obtained.

Specifically, the service discovery network function entity stores at least one set of mapping relationships between service provider network function entity identifiers and service provider network function entity identifiers after topology hiding; then the service discovery network function entity queries the stored mapping relationship, Obtaining the service provider network function identifier corresponding to the service provider network function identifier carried in the service discovery request after topology hiding is to obtain the NF ID corresponding to the topology hidden NF ID. Further, the service discovery network function entity replaces the NF ID after topology hiding with the NF ID in the service discovery response returned to the local network node, that is, returns the service discovery network function entity identifier carrying the service provider network function entity response.

Adopting the technical solution of the embodiment of the present invention realizes the hiding of the service provider network function identifier of the service discovery response corresponding to the ingress service discovery request through the service discovery network function entity in the service discovery scenario.

Embodiment three

The embodiment of the present invention also provides a topology hiding method. FIG. 4 is a schematic flowchart of a topology hiding method according to Embodiment 3 of the present invention; as shown in FIG. 4 , the method includes:

Step 301: The node receives an ingress service request, and extracts a topology-hidden service provider network function identifier from the ingress service request.

Step 302: The node sends a service discovery request carrying the topology-hidden service provider network function identifier to the service discovery network function entity of the local network.

Step 303: The node receives the service discovery response carrying the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding returned by the service discovery network function entity.

Step 304: The node replaces the topology-hidden service provider network function identifier in the ingress service request with the service provider network function identifier carried in the service discovery response corresponding to the topology-hidden service provider network function identifier The service provider network function entity identifier of the service provider.

In this embodiment, the node may be an edge node (such as SEPP) of the local network, or other nodes of the local network, which is not limited in this embodiment. Wherein, the entry service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network. Referring to the example in FIG. 1 , if the node is a node of network 2, the ingress service request is a service request sent from the NF of network 1 as a service user to the NF of network 2 as a service provider.

In combination with the service discovery process in Embodiment 2, the service discovery network function entity returns the service discovery response corresponding to the ingress service discovery request carrying the service provider network function entity identifier after topology hiding, and the ingress service request received by the node carries The service provider network function identifier (ie, the NFID after topology hiding) that has been hidden in the topology is obtained, and then the service provider network function identifier (the NF ID after topology hiding) that has been hidden in the topology is extracted from the ingress service request. Further, the node sends a service discovery request carrying the topology-hidden service provider network function identifier (topology-hidden NF ID) to the local network service discovery network function entity.

In this embodiment of the present invention, the node receives the service provider network function returned by the service discovery network function entity and carries the service provider network function identifier (NF ID after topology hiding) corresponding to the service provider network function identifier after topology hiding The service discovery response of the entity identifier (NF ID), it can be understood that the service discovery network function entity obtains the service provider network function identifier (NF ID after topology hiding) corresponding to the service provider network function identifier after topology hiding by querying the stored mapping relationship. The service provider network function identifier (NF ID), and returns a service discovery response carrying the service provider network function entity identifier (NF ID) to the local network node.

The topology hiding method of the embodiment of the present invention will be further described below in combination with specific embodiments.

Taking the application architecture shown in Figure 1 as an example, assuming that network 1 is the source network, network 2 is the destination network, and the edge nodes and service discovery network functional entities are SEPP and NRF shown in Figure 1 respectively, then the nodes in network 1 Including SEP1 and NRF1, the nodes in network 2 include SEP2 and NRF2; the service user network function entity is NF1 in network 1, and the service provider network function entity is NF2 in network 2.

Specific embodiment one

Fig. 5 is a schematic diagram of a specific interaction flow of the topology hiding method of the embodiment of the present invention; as shown in Fig. 5, the topology hiding method includes:

Step 401: When NF1 in network 1 needs to invoke the service provided by NF2 in network 2, NF1 initiates a service discovery request to NRF1; based on the service discovery request, NRF1 determines that the corresponding service provider functional entity is in network 2, then through SEPP1 and SEPP2 initiate a service discovery request to NRF2 of network 2.

Step 402: NRF2 returns a service discovery response corresponding to the service discovery request to SEPP2, and the service discovery response carries the NF2 ID.

Step 403: SEPP2 receives the service discovery response, performs topology hiding on the NF2ID in the service discovery response, replaces the NF2ID with the topology-hiding NF2ID, and stores the mapping relationship between the NF2ID and the topology-hiding NF2ID in SEPP2.

Among them, SEPP2 can obtain the topology-hidden NF2ID corresponding to NF2ID by querying the preset mapping table; or, it can also generate the topology-hidden NF2ID corresponding to NF2ID through dynamic transformation, and store the NF2ID and the topology-hidden NF2ID Mapping relationship of NF2ID.

Step 404: SEPP2 returns the service discovery response carrying the topology-hidden NF2 ID to NRF1 through SEPP1, and NRF1 sends the service discovery response to NF1.

Step 405: NF1 initiates a service request to NF2, and the service request carries the NF2 ID after topology hiding; the service request is sent to SEPP2 through SEPP1.

Step 406: SEPP2 receives the service request, obtains the NF2ID corresponding to the topology-hidden NF2ID in the service request by querying the stored mapping relationship, and replaces the topology-hidden NF2ID in the service request with the NF2ID.

Step 407: SEPP2 sends a service request to NF2, and the service request carries NF2 ID.

Step 408: NF2 returns a service response corresponding to the service request to NF1.

In this specific embodiment, the SEPP2 of the destination network performs topology hiding on the NF2ID returned in the service discovery response, and saves the mapping relationship; subsequently restores the NF2ID after topology hiding in the service request for accessing the NF2, so as to realize the NF2ID through the edge node. The hiding of the service provider network function identifier of the service discovery response corresponding to the ingress service discovery request.

Specific embodiment two

FIG. 6 is a schematic diagram of another specific interaction flow of the topology hiding method according to an embodiment of the present invention; as shown in FIG. 6, the topology hiding method includes:

Step 501: When NF1 in network 1 needs to invoke the service provided by NF2 in network 2, NF1 initiates a service discovery request to NRF1; based on the service discovery request, NRF1 determines that the corresponding service provider functional entity is in network 2, then through SEPP1 and SEPP2 initiate a service discovery request to NRF2 of network 2.

Step 502: After receiving the service discovery request, NRF2 determines the corresponding service provider NF2, and judges whether the mapping relationship between NF2ID and NF2ID after topology hiding is stored. When the mapping relationship between NF2ID and NF2ID after topology hiding is stored , to obtain the NF2ID after the topology hiding corresponding to the NF2ID; when the mapping relationship between the NF2ID and the NF2ID after the topology hiding is not stored, generate the NF2ID after the topology hiding for the NF2ID, and store the mapping relationship between the NF2ID and the NF2ID after the topology hiding.

Step 503: NRF2 returns a service discovery response corresponding to the service discovery request carrying the topology-hidden NF2 ID, the service discovery response is sent to NF1 through SEPP2 and SEPP1, and NRF1 sends the service discovery response to NF1.

Step 504: NF1 initiates a service request to NF2, and the service request carries the NF2 ID after topology hiding; the service request is sent to SEPP2 through SEPP1.

Step 505-Step 506: SEPP2 extracts the NF2ID after topology hiding from the service request, and initiates a service discovery request to NRF2, and the service discovery request carries the NF2ID after topology hiding.

Step 507: NRF2 determines the NF2ID corresponding to the NF2ID after topology hiding, and returns a service discovery response corresponding to the service discovery request carrying the NF2ID to SEPP2.

Step 508 to Step 509: SEPP2 replaces the topology-hidden NF2ID in the service request from NF1 with NF2ID, and sends the service request carrying the NF2ID to NF2.

Step 510: NF2 returns a service response corresponding to the service request to NF1, and the service response is sent through SEPP2 and SEPP1.

In this specific embodiment, the NRF of the destination network receives a service discovery request from a different network, determines the corresponding NF, and obtains the topology-hidden NF ID corresponding to the NF by looking up the mapping relationship, or generates the topology-hidden NF ID corresponding to the NF ID The NF ID of the service discovery response is used to hide the topology of the NF2ID returned in the service discovery response; when the subsequent destination network node (such as SEPP) receives a service request from another network, it initiates the service discovery of the NRF of the local network, carrying the NFID after topology hiding; Obtain the NF ID corresponding to the NF ID after topology hiding through the NFR of the local network; the destination network node forwards the service request to the NF according to the service discovery response result of the local network, so as to realize the service corresponding to the ingress service discovery request through the service discovery network functional entity The hiding of the service provider network function identity of the discovery response.

Embodiment four

The embodiment of the present invention also provides an edge node. FIG. 7 is a schematic diagram of a composition structure of an edge node according to an embodiment of the present invention; as shown in FIG. 7 , the edge node includes: a first receiving unit 61, a first replacement unit 62, and a first sending unit 63, wherein,

The first receiving unit 61 is configured to receive an ingress service discovery request;

The first replacement unit 62 is configured to replace the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request received by the first receiving unit 61 with the service provider network function after topology hiding logo;

The first sending unit 63 is configured to forward a service discovery response corresponding to the ingress service discovery request and carrying the network function identifier of the service provider after topology hiding.

As a first implementation manner, the first replacement unit 62 is configured to query the preset mapping table to obtain the topology-hidden service provider network function identifier corresponding to the service provider network function identifier, and convert the entry service In the discovery request, the service provider network function identifier in the corresponding service discovery response is replaced with the service provider network function identifier after the topology is hidden.

As a second implementation manner, the first replacement unit 62 is configured to transform the service provider network function identifier into a topology-hidden service provider network function identifier, and map the ingress service discovery request to a service discovery response The service provider network function identifier in replaces the service provider network function identifier after the topology hiding.

In an embodiment, as shown in FIG. 8 , the edge node further includes a first storage unit 64 configured to store the mapping between the service provider network function identifier and the service provider network function identifier after topology hiding relation.

In an embodiment, as shown in FIG. 9 , the edge node further includes a first judging unit 65, configured to judge that the message is based on the uniform resource identifier carried in the message received by the first receiving unit 61 The service discovery request is determined to be an ingress service discovery request based on that the service discovery request is sent from the external network service discovery network functional entity to the home network service discovery network functional entity.

In an embodiment, the first receiving unit 61 is further configured to receive an ingress service request; the ingress service request carries the network function identifier of the service provider after the topology hiding;

The first replacement unit 62 is further configured to replace the topology-hidden service provider network function identifier in the ingress service request received by the first receiving unit 61 with the service provider network function logo;

The first sending unit 63 is further configured to send a service request carrying the service provider network function identifier to the local service provider network function entity.

Wherein, the first replacement unit 62 is configured to query a preset mapping table or a stored mapping relationship to obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding; The service provider network function identifier after the topology hiding in the ingress service request is replaced by the service provider network function identifier.

In this embodiment, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

The entry service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network.

In the embodiment of the present invention, the edge node can be implemented by a server in practical applications; the first replacement unit 62 and the first judging unit 65 in the edge node can be implemented by a central processing unit (CPU, Central Processing Unit) in practical applications. Unit), digital signal processor (DSP, Digital Signal Processor), micro control unit (MCU, Microcontroller Unit) or programmable gate array (FPGA, Field-Programmable Gate Array); the first storage unit in the edge node 64, which can be implemented by memory in practical applications; the first receiving unit 61 and the first sending unit 63 in the edge node can be implemented by communication modules (including: basic communication suite, operating system, communication module) in practical applications , standardized interfaces and protocols, etc.) and the implementation of transceiver antennas.

It should be noted that when the edge node provided in the above embodiment performs topology hiding, it only uses the division of the above-mentioned program modules as an example. In practical applications, the above-mentioned processing allocation can be completed by different program modules according to needs. The internal structure of the node is divided into different program modules to complete all or part of the processing described above. In addition, the edge node and the topology hiding method embodiment provided by the above embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Embodiment five

An embodiment of the present invention also provides an edge node, including a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the program, it realizes: receiving an entry service discovery request , replacing the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding; forwarding the service provider network function identifier corresponding to the ingress service discovery request carrying the topology hidden Service Discovery Response for Service Provider Network Function Identifier. Wherein, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In an embodiment, when the processor executes the program, it implements: querying a preset mapping table to obtain a topology-hidden service provider network function identifier corresponding to the service provider network function identifier; In the discovery request, the service provider network function identifier in the corresponding service discovery response is replaced with the service provider network function identifier after the topology is hidden.

In an embodiment, when the processor executes the program, it implements: transforming the service provider network function identifier into a topology-hidden service provider network function identifier, and mapping the ingress service discovery request to a service discovery response The service provider network function identifier in replaces the service provider network function identifier after the topology hiding.

In an embodiment, when the processor executes the program, it implements: storing the mapping relationship between the service provider network function identifier and the service provider network function identifier after the topology hiding.

In an embodiment, when the processor executes the program, it realizes: judging that the message is a service discovery request based on the uniform resource identifier carried in the received message, and based on that the service discovery request is discovered by an external network service The network function entity sends to the local network service discovery network function entity to determine that the service discovery request is an ingress service discovery request.

In an embodiment, when the processor executes the program, it realizes: receiving an ingress service request; the ingress service request carries the network function identifier of the service provider after the topology hiding; The service provider network function identifier after the topology hiding is replaced by the service provider network function identifier; and a service request carrying the service provider network function identifier is sent to the service provider network function entity of the local network. Wherein, the entry service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network.

In an embodiment, when the processor executes the program, it implements: querying a preset mapping table or a stored mapping relationship, and obtaining the service provider network corresponding to the service provider network function identifier after the topology hiding A function identifier: replacing the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier.

It can be understood that the memory may be a volatile memory or a nonvolatile memory, and may also include both volatile and nonvolatile memory. Wherein, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD, or CD-ROM (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface storage can be disk storage or tape storage. The volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Synchronous Static Random Access Memory), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM, Synchronous Dynamic Random Access Memory), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory) . The memory described by embodiments of the present invention is intended to include, but not be limited to, these and any other suitable types of memory.

The methods disclosed in the foregoing embodiments of the present invention may be applied to, or implemented by, a processor. A processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The aforementioned processor may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor may implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in a memory, and the processor reads the information in the memory, and combines with its hardware to complete the steps of the aforementioned method.

Embodiment six

The embodiment of the present invention also provides a computer storage medium, on which computer instructions are stored. When the instructions are executed by a processor, it is realized that: receiving an entry service discovery request, matching the entry service discovery request to the service in the service discovery response The provider network function identifier is replaced with the service provider network function identifier after topology hiding; and the service discovery response corresponding to the ingress service discovery request carrying the service provider network function identifier after topology hiding is forwarded. Wherein, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In an embodiment, when the instruction is executed by the processor, it realizes: querying the preset mapping table to obtain the topology-hidden service provider network function identifier corresponding to the service provider network function identifier, and sending the ingress service discovery request to The service provider network function identifier in the corresponding service discovery response is replaced with the service provider network function identifier after the topology is hidden.

In an embodiment, when the instruction is executed by the processor, it is implemented: transforming the service provider network function identifier into a topology-hidden service provider network function identifier, and matching the ingress service discovery request to the service discovery response The service provider network function identifier replaces the service provider network function identifier after the topology is hidden.

In an embodiment, when the instruction is executed by the processor, it implements: storing the mapping relationship between the service provider network function identifier and the service provider network function identifier after the topology hiding.

In an embodiment, when the instructions are executed by the processor, it is realized that: based on the uniform resource identifier carried in the received message, it is determined that the message is a service discovery request, and based on that the service discovery request is a network function discovered by an external network service The entity sends the service discovery network function entity of the local network to determine that the service discovery request is an ingress service discovery request.

In an embodiment, when the instruction is executed by the processor, it is realized that: an ingress service request is received; the ingress service request carries the network function identifier of the service provider after the topology hiding; the ingress service request includes the The service provider network function identifier after topology hiding is replaced by the service provider network function identifier; and the service request carrying the service provider network function identifier is sent to the service provider network function entity of the local network. Wherein, the entry service request is a service request sent by the network function entity of the service user of the external network to the network function entity of the service provider of the local network.

In an embodiment, when the instruction is executed by the processor, it implements: querying a preset mapping table or a stored mapping relationship, and obtaining the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding ; Replace the topology-hidden service provider network function identifier in the ingress service request with the service provider network function identifier.

Embodiment seven

The embodiment of the present invention also provides a service discovery network functional entity; FIG. 10 is a schematic diagram of a composition structure of the service discovery network functional entity according to the embodiment of the present invention; as shown in FIG. 10 , the service discovery network functional entity includes the first Two receiving units 71, a topology hiding unit 72 and a second sending unit 73; wherein,

The second receiving unit 71 is configured to receive an ingress service discovery request;

The topology hiding unit 72 is configured to determine the service provider network function entity corresponding to the ingress service discovery request received by the second receiving unit 71, and perform topology hiding on the service provider network function entity identifier;

The second sending unit 73 is configured to return a service discovery response corresponding to the ingress service discovery request that carries the topology-hidden service provider network function entity identifier.

In an embodiment, as shown in FIG. 11 , the service discovery network function entity further includes a second storage unit 74, configured to store a mapping relationship including the identifier of the service provider network function entity;

The topology hiding unit 72 is configured to determine whether the second storage unit 74 stores a mapping relationship containing the service provider network function entity identifier; when the second storage unit 74 stores a mapping relationship containing the service provider network In the mapping relationship of the functional entity identifier, the topology-hidden service provider network functional entity identifier corresponding to the service provider network functional entity identifier is obtained based on the mapping relationship; when the second storage unit 74 does not store any When the mapping relationship of the service provider network function entity identifier is described above, a topology-hidden service provider network function entity identifier is generated for the service provider network function entity identifier.

In an embodiment, the second receiving unit 71 is further configured to receive a service discovery request from a node of the local network; the service discovery request carries a service provider network function entity identifier after topology hiding;

The topology hiding unit 72 is further configured to determine the service provider network function entity identifier corresponding to the service provider network function entity identifier after the topology hiding;

The second sending unit 73 is further configured to return a service discovery response carrying the service provider network function entity identifier to the local network node.

Wherein, the topology hiding unit 72 is configured to query the stored mapping relationship, and obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding.

In the embodiment of the present invention, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In the embodiment of the present invention, the service discovery network functional entity can be realized by a server in practical applications; the topology hiding unit 72 in the service discovery network functional entity can be realized by CPU, DSP, MCU or FPGA in practical applications ; The second storage unit 74 in the service discovery network functional entity can be implemented by a memory in practical applications; the second receiving unit 71 and the second sending unit 73 in the service discovery network functional entity can be implemented in practical applications It can be realized through communication modules (including: basic communication suite, operating system, communication modules, standardized interfaces and protocols, etc.) and transceiver antennas.

It should be noted that when the service discovery network functional entity provided by the above-mentioned embodiment performs topology hiding, it only uses the division of the above-mentioned program modules for illustration. In practical applications, the above-mentioned processing can be assigned to different program modules according to needs. Completion means that the internal structure of the service discovery network functional entity is divided into different program modules, so as to complete all or part of the processing described above. In addition, the service discovery network functional entity provided by the above embodiment and the topology hiding method embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Embodiment eight

An embodiment of the present invention also provides a service discovery network functional entity, including a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the program, it realizes: receiving the entry Service discovery request; determine the service provider network function entity corresponding to the ingress service discovery request, perform topology hiding on the service provider network function entity identifier; return the service provider carrying the topology hiding corresponding to the ingress service discovery request Service Discovery Response for Network Function Entity Identification. Wherein, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In an embodiment, when the processor executes the program, it realizes: judging whether to store the mapping relationship including the service provider network function entity identifier; when the mapping relationship including the service provider network function entity identifier is stored When, based on the mapping relationship, obtain the service provider network function entity identifier corresponding to the service provider network function entity identifier after topology hiding; when the mapping relationship containing the service provider network function entity identifier is not stored, generating a topology-hidden service provider network function entity identity for the service provider network function entity identity, and storing a mapping relationship between the service provider network function entity identity and the service provider network function entity identity after topology hiding .

In an embodiment, when the processor executes the program, it realizes: receiving a service discovery request from a local network node; the service discovery request carries a service provider network function entity identifier after topology hiding; and determining the topology hiding The service provider network function entity identification corresponding to the subsequent service provider network function entity identification; return a service discovery response carrying the service provider network function entity identification to the local network node.

In an embodiment, when the processor executes the program, it implements: querying the stored mapping relationship, and obtaining the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding.

Embodiment nine

The embodiment of the present invention also provides a computer storage medium, on which computer instructions are stored, and when the instructions are executed by a processor, it is possible to: receive an entry service discovery request; determine the service provider network function corresponding to the entry service discovery request An entity that performs topology hiding on the service provider network function entity identifier; and returns a service discovery response corresponding to the ingress service discovery request that carries the topology hidden service provider network function entity identifier. Wherein, the ingress service discovery request is a service discovery request sent by the external network service discovery network functional entity to the local network service discovery network functional entity.

In an embodiment, when the instruction is executed by the processor, it is implemented: judging whether to store the mapping relationship including the service provider network function entity identifier; when the mapping relationship including the service provider network function entity identifier is stored, Obtain the service provider network function entity identifier corresponding to the service provider network function entity identifier after topology hiding based on the mapping relationship; when the mapping relationship including the service provider network function entity identifier is not stored, for the The service provider network function entity identifier generates a topology-hidden service provider network function entity identifier, and stores a mapping relationship between the service provider network function entity identifier and the topology-hidden service provider network function entity identifier.

In an embodiment, when the instruction is executed by the processor, it is implemented: receiving a service discovery request from a node on the local network; the service discovery request carries a service provider network function entity identifier after topology hiding; and determining the service provider network function entity identity after topology hiding The service provider network function entity identifier corresponding to the service provider network function entity identifier; returning a service discovery response carrying the service provider network function entity identifier to the local network node.

In an embodiment, when the instruction is executed by the processor, it implements: querying the stored mapping relationship, and obtaining the service provider network function identifier corresponding to the service provider network function identifier after the topology hiding.

Embodiment ten

The embodiment of the present invention also provides a node. FIG. 12 is a schematic diagram of the composition and structure of a node in an embodiment of the present invention; as shown in FIG. 12 , the node includes: a third receiving unit 81, an extraction unit 82, a third sending unit 83, and a second replacement unit 84; wherein,

The third receiving unit 81 is configured to receive an entry service request;

The extracting unit 82 is configured to extract the topology-hidden service provider network function identifier from the ingress service request received by the third receiving unit 81;

The third sending unit 83 is configured to send a service discovery request carrying the topology-hidden service provider network function identifier to the local network service discovery network function entity;

The third receiving unit 81 is further configured to receive the service discovery response returned by the service discovery network function entity and carrying the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding ;

The second replacement unit 84 is configured to replace the network function identifier of the service provider after topology hiding in the ingress service request with the service provider after topology hiding carried in the service discovery response The network function entity identifier of the service provider corresponding to the network function identifier.

In the embodiment of the present invention, the node can be realized by a server in practical application; the extraction unit 82 and the second replacement unit 84 in the node can be realized by CPU, DSP, MCU or FPGA in practical application; The third receiving unit 81 and the third sending unit 83 in the node can be implemented by communication modules (including: basic communication suite, operating system, communication modules, standardized interfaces and protocols, etc.) and transceiver antennas in practical applications.

It should be noted that when the nodes provided in the above embodiments perform topology hiding, they only use the division of the above-mentioned program modules as an example. The internal structure of the program is divided into different program modules to complete all or part of the processing described above. In addition, the node provided in the above embodiment and the embodiment of the topology hiding method belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Embodiment Eleven

An embodiment of the present invention also provides a node, including a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the program, it realizes: receiving an entry service request, from Extracting the network function identifier of the service provider whose topology has been hidden from the ingress service request; sending a service discovery request carrying the network function identifier of the service provider after the topology hiding to the service discovery network function entity of this network; receiving the The service discovery response returned by the service discovery network function entity carries the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding; the topology hidden in the ingress service request The service provider network function identifier is replaced with the service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding carried in the service discovery response.

Embodiment 12

The embodiment of the present invention also provides a computer storage medium, on which computer instructions are stored, and when the instructions are executed by a processor, the implementation: receiving an entry service request, extracting a topology-hidden service provider from the entry service request Network function identifier; sending a service discovery request carrying the network function identifier of the service provider after the topology hiding to the network service discovery network function entity of this network; receiving the service discovery network function entity returning the service discovery request carrying the topology hidden The service discovery response of the service provider network function entity identifier corresponding to the service provider network function identifier; replace the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier in the service discovery response The carried service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms of.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units; Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention can be integrated into one processing unit, or each unit can be used as a single unit, or two or more units can be integrated into one unit; the above-mentioned integration The unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: various media that can store program codes such as removable storage devices, ROM, RAM, magnetic disks or optical disks.

Alternatively, if the above-mentioned integrated units of the present invention are implemented in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for Make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: various media capable of storing program codes such as removable storage devices, ROM, RAM, magnetic disks or optical disks.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (34)

1. A topology hiding method, the method comprising:

the edge node receives an entrance service discovery request, and replaces a service provider network function identifier in a service discovery response corresponding to the entrance service discovery request with a service provider network function identifier after topology hiding;

and the edge node forwards a service discovery response which corresponds to the entry service discovery request and carries the service provider network function identifier after the topology is hidden.

2. The method of claim 1, wherein replacing the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the topology-hidden service provider network function identifier comprises:

and the edge node inquires a preset mapping table to obtain a service provider network function identifier after topology hiding corresponding to the service provider network function identifier, and replaces the service provider network function identifier in the service discovery response corresponding to the entry service discovery request with the service provider network function identifier after topology hiding.

3. The method of claim 1, wherein replacing the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the topology-hidden service provider network function identifier comprises:

and the edge node converts the service provider network function identifier into a service provider network function identifier after topology hiding, and replaces the service provider network function identifier after topology hiding with the service provider network function identifier in the service discovery response corresponding to the entry service discovery request.

4. The method of claim 3, further comprising:

and the edge node stores the mapping relation between the service provider network function identifier and the service provider network function identifier after the topology hiding.

5. The method of claim 1, further comprising:

the edge node judges that the message is a service discovery request based on the uniform resource identifier carried in the received message, and determines that the service discovery request is an entry service discovery request based on that the service discovery request is sent to a home network service discovery network functional entity by an external network service discovery network functional entity.

6. The method according to any one of claims 1 to 5, further comprising:

the edge node receives an entry service request; the entrance service request carries the service provider network function identification after the topology is hidden;

replacing, by the edge node, the service provider network function identifier after the topology hiding in the ingress service request with the service provider network function identifier;

and the edge node sends a service request carrying the service provider network function identifier to a home network service provider network function entity.

7. The method of claim 6, wherein the edge node replacing the topology hidden service provider network function identifier in the ingress service request with the service provider network function identifier comprises:

the edge node inquires a preset mapping table or a stored mapping relation to obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology is hidden;

and the edge node replaces the service provider network function identifier after the topology is hidden in the entry service request with the service provider network function identifier.

8. The method according to any of claims 1 to 5, wherein the ingress service discovery request is a service discovery request sent by an extranet service discovery network function entity to a home network service discovery network function entity.

9. The method of claim 6, wherein the portal service request is a service request sent from an extranet service user network function entity to a home network service provider network function entity.

10. A topology hiding method, the method comprising:

a service discovery network functional entity receives an entrance service discovery request;

the service discovery network functional entity determines a service provider network functional entity corresponding to the entry service discovery request, and topology hiding is carried out on the service provider network functional entity identification;

and the service discovery network functional entity returns a service discovery response which is corresponding to the entry service discovery request and carries the service provider network functional entity identifier after the topology is hidden.

11. The method of claim 10, wherein topology hiding service provider network function entity identities comprises:

the service discovery network functional entity judges whether a mapping relation containing the service provider network functional entity identification and the service provider network functional entity identification after topology hiding is stored;

when a mapping relation containing the service provider network functional entity identification and the service provider network functional entity identification after topology hiding is stored, acquiring the service provider network functional entity identification after topology hiding corresponding to the service provider network functional entity identification based on the mapping relation;

and when the mapping relation containing the service provider network functional entity identification is not stored, generating a service provider network functional entity identification with hidden topology for the service provider network functional entity identification, and storing the mapping relation between the service provider network functional entity identification and the service provider network functional entity identification with hidden topology.

12. The method according to claim 10 or 11, characterized in that the method further comprises:

the service discovery network functional entity receives a service discovery request of a local network node; the service discovery request carries a service provider network functional entity identifier after topology hiding;

the service discovery network functional entity determines the service provider network functional entity identifier corresponding to the service provider network functional entity identifier after the topology is hidden;

and the service discovery network functional entity returns a service discovery response carrying the service provider network functional entity identifier to the local network node.

13. The method according to claim 12, wherein the service discovery network function entity determining the service provider network function entity identifier corresponding to the service provider network function entity identifier after the topology hiding comprises:

and the service discovery network functional entity inquires the stored mapping relation and obtains the service provider network functional identifier corresponding to the service provider network functional identifier after the topology is hidden.

14. The method of claim 10, wherein the ingress service discovery request is a service discovery request sent by an extranet service discovery network function entity to a home network service discovery network function entity.

15. A topology hiding method, the method comprising:

the method comprises the steps that a node receives an entrance service request, and extracts a service provider network function identifier with hidden topology from the entrance service request;

the node sends a service discovery request carrying the service provider network function identifier after the topology is hidden to a home network service discovery network function entity;

the node receives a service discovery response which is returned by the service discovery network functional entity and carries a service provider network functional entity identifier corresponding to the service provider network functional identifier after the topology is hidden;

and the node replaces the service provider network function identifier after the topology hiding in the entrance service request with a service provider network function entity identifier which is carried in the service discovery response and corresponds to the service provider network function identifier after the topology hiding.

16. An edge node, wherein the edge node comprises: a first receiving unit, a first replacing unit and a first transmitting unit, wherein,

the first receiving unit is used for receiving an entrance service discovery request;

the first replacing unit is configured to replace the service provider network function identifier in the service discovery response corresponding to the entry service discovery request received by the first receiving unit with the service provider network function identifier after topology hiding;

the first sending unit is configured to forward a service discovery response carrying the service provider network function identifier after the topology is hidden, where the service discovery response corresponds to the portal service discovery request.

17. The edge node of claim 16, wherein the first replacing unit is configured to query a preset mapping table to obtain a service provider network function identifier after topology hiding corresponding to the service provider network function identifier, and replace the service provider network function identifier in the service discovery response corresponding to the ingress service discovery request with the service provider network function identifier after topology hiding.

18. The edge node of claim 16, wherein the first replacing unit is configured to transform the service provider network function identifier into a topology hidden service provider network function identifier, and replace the topology hidden service provider network function identifier with the service provider network function identifier in the corresponding service discovery request response.

19. The edge node of claim 18, wherein the edge node further comprises a first storage unit configured to store a mapping relationship between the service provider network function identifier and the topology hidden service provider network function identifier.

20. The edge node according to claim 16, wherein the edge node further comprises a first determining unit, configured to determine that the message is a service discovery request based on a uniform resource identifier carried in the message received by the first receiving unit, and determine that the service discovery request is an ingress service discovery request based on that the service discovery request is sent to a home network service discovery network function entity by an external network service discovery network function entity.

21. The edge node according to any of claims 16 to 20, wherein the first receiving unit is further configured to receive an ingress service request; the entrance service request carries the service provider network function identification after the topology is hidden;

the first replacing unit is further configured to replace the service provider network function identifier after the topology is hidden in the entry service request received by the first receiving unit with the service provider network function identifier;

the first sending unit is further configured to send a service request carrying the service provider network function identifier to a home network service provider network function entity.

22. The edge node of claim 21, wherein the first replacing unit is configured to query a preset mapping table or a stored mapping relationship, and obtain the service provider network function identifier corresponding to the service provider network function identifier after the topology is hidden; replacing the service provider network function identifier after the topology is hidden in the portal service request with the service provider network function identifier.

23. The edge node according to any of claims 16 to 20, wherein the ingress service discovery request is a service discovery request sent by an extranet service discovery network function entity to a home network service discovery network function entity.

24. The edge node of claim 21, wherein the ingress service request is a service request sent by an extranet service consumer network function entity to a home network service provider network function entity.

25. A service discovery network function entity, wherein the service discovery network function entity comprises a second receiving unit, a topology hiding unit and a second sending unit; wherein,

the second receiving unit is used for receiving an entrance service discovery request;

the topology hiding unit is configured to determine a service provider network functional entity corresponding to the entry service discovery request received by the second receiving unit, and perform topology hiding on a service provider network functional entity identifier;

and the second sending unit is configured to return a service discovery response carrying the service provider network functional entity identifier after the topology is hidden, to which the portal service discovery request corresponds.

26. The service discovery network function entity of claim 25, further comprising a second storage unit for storing a mapping relation containing said service provider network function entity identity;

the topology hiding unit is configured to determine whether the second storage unit stores a mapping relationship including an identifier of the service provider network functional entity; when the second storage unit stores a mapping relation containing the service provider network functional entity identifier, acquiring the service provider network functional entity identifier after topology hiding corresponding to the service provider network functional entity identifier based on the mapping relation; and when the second storage unit does not store the mapping relation containing the service provider network functional entity identifier, generating the service provider network functional entity identifier with hidden topology for the service provider network functional entity identifier.

27. The service discovery network function entity of claim 25 or 26, wherein the second receiving unit is further configured to receive a service discovery request of a home network node; the service discovery request carries a service provider network functional entity identifier after topology hiding;

the topology hiding unit is further configured to determine a service provider network functional entity identifier corresponding to the service provider network functional entity identifier after the topology hiding;

the second sending unit is further configured to return a service discovery response carrying the service provider network function entity identifier to the home network node.

28. The entity according to claim 27, wherein the topology hiding unit is configured to query a stored mapping relationship to obtain the service provider network function identifier corresponding to the service provider network function identifier after topology hiding.

29. The entity according to claim 25, wherein the ingress service discovery request is a service discovery request sent by an extranet service discovery network function entity to a home network service discovery network function entity.

30. A node, characterized in that the node comprises: a third receiving unit, an extracting unit, a third sending unit and a second replacing unit; wherein,

the third receiving unit is used for receiving an entrance service request;

the extracting unit is configured to extract a service provider network function identifier with hidden topology from the portal service request received by the third receiving unit;

the third sending unit is configured to send a service discovery request carrying the service provider network function identifier after the topology is hidden to a home network service discovery network function entity;

the third receiving unit is further configured to receive a service discovery response returned by the service discovery network functional entity and carrying a service provider network functional entity identifier corresponding to the service provider network functional identifier after the topology is hidden;

the second replacing unit is configured to replace the service provider network function identifier after the topology hiding in the entry service request with a service provider network function entity identifier corresponding to the service provider network function identifier after the topology hiding, which is carried in the service discovery response.

31. A computer storage medium having computer instructions stored thereon, wherein the instructions, when executed by a processor, perform the steps of the topology hiding method of any of claims 1 to 9; or,

the instructions when executed by a processor implement the steps of the topology hiding method of any of claims 10 to 14; or,

which when executed by a processor implement the steps of the topology hiding method of claim 15.

32. An edge node comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the topology hiding method according to any of claims 1 to 9 when executing the program.

33. A service discovery network function comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the program to implement the steps of the topology hiding method of any one of claims 10 to 14.

34. A node comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the topology hiding method of claim 15 are implemented when the processor executes the program.