CN103200102A - Method, device and system for service routing - Google Patents

Abstract

The present invention discloses a service routing method, device and system, which are applied to the scenario where a client in a local peer-to-peer network domain communicates with service peers in other peer-to-peer network domains. The inter-domain service routing control server receives the local peer After waiting for the client in the network domain to send a service-related request, select a service gateway for this business session and issue a routing policy to the selected service gateway; the selected service gateway performs business messages according to the issued routing policy. forwarding. The method, device and system of the present invention have little impact on the involved peer-to-peer network itself, are scalable and manageable, and are simple to configure; meanwhile, the routing efficiency of service messages is high, and it is easy to realize load balance between service gateways.

Description

A service routing method, device and system

technical field

The present invention relates to the communication field, in particular to a service routing method, device and system.

Background technique

At present, peer-to-peer network (Peer-to-Peer, P2P) technology is developing rapidly. The coexistence of various network structures and algorithms has made a great contribution to the prosperity of Internet services, but it has also caused problems for the intercommunication between P2P service networks. Great difficulty. At present, intercommunication technology has become one of the factors restricting the scale of the P2P network industry. To this end, the P2P SIP (Session Initiation Protocol) working group of the International Internet Engineering Task Force (IETF) formulated the first P2P network protocol standard RELOAD (REsource Location And Discovery, Resource Location and Discovery Protocol), which made a contribution to the development of P2P network technology. significant contribution. However, even if RELOAD is uniformly adopted as the standard protocol of the P2P service network, there are still problems in the intercommunication of different P2P service networks. As shown in Figure 1, for the application scenario of the SIP service, when the client 103 of the peer-to-peer network domain 101 initiates a SIP call request, if the called user does not belong to the peer-to-peer network domain 101, the SIP call is failed, or A traditional SIP call is initiated, or the client 103 initiates a P2PSIP call as a client of the peer-to-peer network domain 102 to which the called user belongs. At this time, the client 103 needs to know the configuration information, routing algorithm, and protocol of the peer-to-peer network domain 102, which is unrealistic for the client when there are many peer-to-peer networks.

For this reason, a multi-layer overlay network solution is proposed in the prior art, that is, high-performance nodes in each peer-to-peer network are selected as super nodes to form a top-layer overlay network, which is responsible for message forwarding between different peer-to-peer networks. But this can only reduce the ability requirements of the client, and when a new peer-to-peer network joins or leaves, the super node still has the problem of configuration adjustment difficulties, such as when the P2P routing algorithm protocol or even HASH (ha) of the peer-to-peer network When the algorithms are different, the intercommunication between peer-to-peer networks will be difficult to achieve.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a service routing method, device and system to solve the problem of service interworking between different peer-to-peer networks.

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

A service routing method is applied to a scenario where a client in a local peer-to-peer network domain performs service interworking with service peers in another peer-to-peer network domain, and the method includes:

After receiving the service-related request sent by the client in the local peer-to-peer network domain, the inter-domain service routing control server selects a service gateway for this service session and issues a routing policy to the selected service gateway;

The selected service gateway forwards the service message according to the delivered routing policy.

When the peer-to-peer network domain applies for a service interworking function, it reports relevant information of the peer-to-peer network domain and deployed service gateways to the inter-domain service routing control server.

The related information includes: service gateway identification, service gateway configuration, link status with other peer-to-peer network domains, and configuration information of the peer-to-peer network domain to which the service gateway belongs.

When the client knows that the service peer is located in another peer-to-peer network domain, it initiates a service routing request to the inter-domain service routing control server, and sends a service request to the relevant service gateway according to the response returned by the inter-domain service routing control server; or,

The client directly initiates a service request to a known service gateway.

The service-related request is a service routing request, which carries information about the source and destination networks of both parties in the session.

The routing strategy is a forwarding flow table, and the service message includes a service request;

When performing the forwarding, the service gateway forwards the service message to other service gateways or clients for processing according to the delivered forwarding flow table.

When performing the forwarding, if no corresponding message can be queried according to the forwarding flow table, further query is made to the inter-domain service routing control server.

A service routing system, which is applied to the scenario where a client in a local peer-to-peer network domain and a service peer in another peer-to-peer network domain perform business interworking, the system includes an inter-domain service routing control server and a service gateway; wherein,

The inter-domain service routing control server is configured to select a service gateway for this service session and issue a routing policy to the selected service gateway after receiving a service-related request sent by a client in the local peer-to-peer network domain;

The selected service gateway is used to forward service messages according to the issued routing policy.

When the peer-to-peer network domain applies for the service interworking function, it is used to report the relevant information of the peer-to-peer network domain and the deployed service gateway to the inter-domain service routing control server.

The related information includes: service gateway identification, service gateway configuration, link status with other peer-to-peer network domains, and configuration information of the peer-to-peer network domain to which the service gateway belongs.

When the client knows that the service peer is located in another peer-to-peer network domain, it is used to initiate a service routing request to the inter-domain service routing control server, and send a service to the relevant service gateway according to the response returned by the inter-domain service routing control server request; or,

The client is used to directly initiate a service request to a known service gateway.

The service-related request is a service routing request, which carries information about the source and destination networks of both parties in the session.

The routing strategy is a forwarding flow table, and the service message includes a service request;

When performing the forwarding, the service gateway is used to forward the service message to other service gateways or clients for processing according to the issued forwarding flow table.

When performing the forwarding, if no corresponding message can be queried according to the forwarding flow table, the service gateway is used to further inquire the inter-domain service routing control server.

A service routing device, which is applied to a scene where a client in a local peer-to-peer network domain and a service peer in another peer-to-peer network domain perform business interworking, the device is set in an inter-domain service routing control server, and includes a service routing control module , a service gateway management module and a protocol control function module; wherein,

The service routing control module is used to select a service gateway for this service session; it also sends a routing strategy to the selected service gateway through the interface provided by the protocol control function module according to the selection result for the service gateway;

The service gateway management module is used to provide the basis for selecting a service gateway for the service routing control module;

The protocol control function module is used to provide an information exchange channel between the inter-domain service routing control server and the service gateway.

When the service routing control module selects the service gateway, it is used to judge the information of the source peer-to-peer network domain and the destination peer-to-peer network domain of both parties in the session according to the service route request, and select the service gateway for this service session accordingly;

The main basis for making the selection is the peer-to-peer network domain and the service gateway information of the peer-to-peer network domain provided by the service gateway management module.

The service gateway management module is used to collect basic configuration information of all peer-to-peer network domains and deployed service gateway information as a basis for the service routing control module to select a service gateway;

The collected service gateway information includes: service gateway identifier, service gateway configuration, link status with other peer-to-peer network domains, and configuration information of the peer-to-peer network domain to which the service gateway belongs.

The routing policy is a forwarding flow table.

The service routing method, device and system between peer-to-peer networks provided by the present invention have little impact on the involved peer-to-peer network itself, have scalability, manageability, and simple configuration; at the same time, the routing efficiency of service messages is high and easy to implement Load balancing between service gateways.

Description of drawings

FIG. 1 is a schematic diagram of a network architecture for realizing peer-to-peer network service intercommunication in the prior art;

FIG. 2 is a schematic structural diagram of a system implementing a peer-to-peer network service routing network according to Embodiment 1 of the present invention;

FIG. 3 is a flow chart of implementing peer-to-peer network service routing according to Embodiment 2 of the present invention;

FIG. 4 is a message flow diagram for implementing peer-to-peer network service routing according to Embodiment 3 of the present invention;

FIG. 5 is another message flow diagram for implementing peer-to-peer network service routing according to Embodiment 4 of the present invention;

FIG. 6 is a schematic diagram of a device implementing a peer-to-peer network inter-domain service routing control server according to Embodiment 5 of the present invention;

FIG. 7 is a simplified flowchart of a service routing process according to an embodiment of the present invention.

Detailed ways

In the basic technology of software-defined network (Software Defined Network, SDN) technology, the forwarding/control separation architecture can be adopted, and the external control plane entity controls the forwarding plane equipment to realize various forwarding logics, and the main function of the forwarding plane equipment is based on Routing policies such as forwarding flow tables implement controlled forwarding, and the specific forwarding behavior is standardized: when a message is received, take out the L (layer) 2/L3/L4 related field value in its header, and use the field value as a keyword to search Forwarding flow table; when an entry is matched, the packet field is transformed according to the instruction set in the entry content, and then the transformed packet is forwarded to a logical port or a physical port according to the instruction.

Based on the above technical content, a controlled media plane forwarding device can be deployed as a service gateway, and a centralized inter-domain service routing control server is used to manage the service gateway to realize the inter-domain service routing control function.

In practical applications, for a variety of heterogeneous peer-to-peer network environments, a service routing system between peer-to-peer networks can be set up, including clients, peer-to-peer network domains, inter-domain service routing control servers, and service gateways; among them,

When the peer-to-peer network domain applies for the service interworking function, it reports the relevant information of the peer-to-peer network domain and the deployed service gateway to the inter-domain service routing control server;

When the client communicates with service peers in other peer-to-peer network domains, it initiates a service routing request to the inter-domain service routing control server;

After receiving the service routing request, the inter-domain service routing control server selects a suitable service gateway for this service session and sends routing policies such as forwarding flow tables to the selected service gateway;

The service gateway forwards the service request to other service gateways or clients for processing according to the delivered routing policies such as the forwarding flow table.

Further, when the peer-to-peer network domain applies for business interworking with other peer-to-peer network domains, the relevant information that needs to be reported to the inter-domain service routing control server includes the service gateway identifier, service gateway configuration, and other peer-to-peer network domains. The link status between them, and the configuration information of the peer-to-peer network domain to which the service gateway belongs, such as the domain names of nodes and resources, the distribution of IP address segments, etc.;

Further, when the client knows that the service peer is located in another peer-to-peer network domain, the client initiates a service routing request to the inter-domain service routing control server, and reports to the relevant The service gateway sends a service request; of course, the client can also directly initiate a service request to a known service gateway;

Further, when the client communicates with service peers in other peer-to-peer network domains, the service routing request initiated to the inter-domain service routing control server needs to carry the information of the source and destination networks of both parties in the session;

Further, when the service gateway forwards the message according to the forwarding flow table, if the corresponding message cannot be queried according to the forwarding flow table, it further inquires to the inter-domain service routing control server;

It can be seen that service gateways can be independently deployed in the peer-to-peer network domain, and these service gateways are managed by a unified inter-domain service routing control server. When a cross-domain service request occurs, the inter-domain service routing control server is responsible for selecting an appropriate service gateway for the session and delivering routing policies such as forwarding flow table to the selected service gateway, and the service gateway then forwards the flow according to the forwarding flow table and other routing strategies to forward the service request and subsequent service messages.

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

Embodiment one

Fig. 2 is a schematic structural diagram of a system implementing a peer-to-peer network service routing network. As shown in Figure 2, the system includes a peer-to-peer network domain 201, a client 203, an inter-domain service routing control server 204, a service gateway 205, etc.; wherein the peer-to-peer network domain 201 is a superposition of multiple peer-to-peer nodes 206 net.

In order to realize the service intercommunication between multiple heterogeneous peer-to-peer network domains, the service gateway is independently deployed by the operator of each peer-to-peer network domain as the service message egress and entrance of the peer-to-peer network domain. The inter-domain service routing control server is responsible for managing service gateways in all peer-to-peer network domains, selecting a suitable service gateway for cross-domain service routing, and delivering a forwarding flow table to the selected service gateway.

When a peer-to-peer network domain applies for interworking with other peer-to-peer network domains, it needs to report the basic configuration information of itself and the deployed service gateway to the inter-domain service routing control server as the basis for path selection of service routing. Specifically, the information that the peer-to-peer network domain needs to report to the inter-domain service routing control server includes the service gateway identifier, the service gateway configuration (port and status, etc.), the link status with other peer-to-peer network domains, and the The assigned peer-to-peer network domain configuration (domain name distribution of nodes and resources, etc.). Among them, the inter-domain service routing control server can also control the link layer detection protocol between the service gateways to collect the link status between the service gateways, and the specific method of performing the link layer detection protocol to collect the link status Similar to the topology detection method of OpenFlow (Open Flow) network. The service gateway performs operations such as modifying/forwarding business messages according to the forwarding flow table that has been delivered to the local area. For service messages that cannot be operated according to the local forwarding flow table, the service is initiated through the control plane channel with the inter-domain service routing control server. For the routing request, the inter-domain service routing control server sends a new forwarding flow table to the service gateway after further judgment, and the service gateway forwards it according to the newly issued forwarding flow table.

Embodiment two

FIG. 3 is a flow chart of implementing peer-to-peer network service routing according to Embodiment 2 of the present invention, and this process can be realized based on the system shown in Embodiment 1. The route shown in Figure 3 mainly includes the following steps:

Step 301: The peer-to-peer network domain applies for service interworking with other peer-to-peer network domains, and reports relevant information of the network domain to the inter-domain service routing control server;

The relevant information includes the service gateway identifier of the peer-to-peer network domain, the service gateway configuration, the link status with other peer-to-peer network domains, and the configuration information of the peer-to-peer network domain to which the service gateway belongs;

The configuration information of the peer-to-peer network domain includes the assigned domain name, and/or the IP address prefix of the terminal, etc.;

Step 302: The inter-domain service routing control server collects configuration information of all peer-to-peer network domains, service gateway information, link status information between service gateways of different peer-to-peer network domains, and service interworking protocols between peer-to-peer network domains wait;

The link state information between the service gateways of different peer-to-peer network domains may be directly reported when the peer-to-peer network domains apply to join the interworking network, or the inter-domain service routing control server instructs the service gateways to perform link detection on each other to obtain;

The service interworking agreement between the peer-to-peer network domains refers to the agreement between the operators of the peer-to-peer network domains, such as which services are interoperable with which peer-to-peer network domains, as well as service priority, charging information, etc.;

Step 303: The inter-domain service routing control server selects an appropriate service gateway to establish a session path according to the source network domain information and destination network domain information of the service session carried in the service routing request, and sends a forwarding flow table to the selected service gateway ;

When a service request across network domains occurs, the client may directly initiate a service routing request to the inter-domain service routing control server; or the client may directly initiate a service request to the service gateway of the local domain. When there is no corresponding forwarding flow table, the service gateway initiates the service routing request to the inter-domain service routing control server;

Step 304: The service gateway forwards the service request and subsequent service messages to the destination peer-to-peer network domain according to the local forwarding flow table;

If there is no forwarding entry of the service message in the local forwarding flow table of the service gateway, the service gateway initiates a service routing request to the inter-domain service routing control server, and then according to the forwarding flow issued by the inter-domain service routing control server The table forwards business messages;

The service gateway can be connected to the peer-to-peer network domain as a client of the peer-to-peer network domain, or can be connected to the client or node of the peer-to-peer network domain as a common media forwarding device.

Embodiment three

FIG. 4 is a message flow chart for implementing peer-to-peer network service routing according to Embodiment 3 of the present invention. The service gateway B of the peer-to-peer network domain 2 is connected to the client or node of the peer-to-peer network domain 2 as a common media forwarding device. In actual application, when the client initiates a service request, it first judges whether the service peer is located in the peer-to-peer network domain. If not, the client first requests the service routing path from the inter-domain service routing control server. The inter-domain service routing control server selects the appropriate service gateway for this service according to the service routing request of the client, sends a forwarding flow table to the selected service gateway to establish a forwarding path, and notifies the client of the selection result of the service gateway end. The client sends a service request to the selected service gateway according to the selection result returned by the inter-domain service routing control server, and the service gateway forwards the received service request to the client or node in the destination peer network domain according to the issued forwarding flow table superior. The specific steps are described as follows:

Step 401: client A in peer-to-peer network domain 1 initiates a service request, and determines that the service peer is client B in peer-to-peer network domain 2; client A initiates a service routing request to the inter-domain service routing control server;

The service routing request carries necessary information, so that the inter-domain service routing control server can obtain the information of the source peer-to-peer network domain and the destination peer-to-peer network domain of both sides of the business session, such as the attribution domain name information of the users on both sides of the session, the customer end address information, etc.;

Client A can obtain the address information of the inter-domain service routing control server through pre-configuration or through DNS (Domain Name System) query;

Step 402: The inter-domain service routing control server receives the service routing request, and selects the service gateway A of the peer-to-peer network domain 1 and the service gateway B of the peer-to-peer network domain 2 as forwarding nodes for this service;

Step 403: The inter-domain service routing control server sends a forwarding flow table to service gateway A for this service;

Step 404: The inter-domain service routing control server sends a forwarding flow table to service gateway B for this service;

Step 405: The inter-domain service routing control server returns a service routing response message to client A, which carries the address information of service gateway A selected for this service session;

Step 406: client A sends a service request to service gateway A;

Step 407: Service gateway A receives the service request, and performs matching search in the local forwarding flow table;

Step 408: Service gateway A forwards the service request to service gateway B according to the search result of the local forwarding flow table;

Step 409: Service gateway B receives the service request, and performs a matching search in the local forwarding flow table, and learns that the service request needs to be forwarded to node C in the peer-to-peer network domain 2 connected to service gateway B for processing;

Step 410: Service gateway B sends a service request to node C in the connected peer-to-peer network domain 2;

Step 411: Node C in the peer-to-peer network domain 2 sends a service request to the destination client B of the service request;

Step 412: the client B in the peer-to-peer network domain 2 completes the business processing and returns a response message;

Here, steps 411-412 are the internal processing flow of the service message in the peer-to-peer network domain 2, and the specific processing method is determined according to the P2P algorithm and service mechanism of the peer-to-peer network domain 2, and the response message may be a P2P message;

Steps 413-415: Node C in the peer-to-peer network domain 2 returns the service response message to client A via service gateway B and service gateway A. The forwarding processing of the service response message by the service gateway is also realized based on the forwarding flow table.

Embodiment Four

FIG. 5 is another message flow diagram for implementing peer-to-peer network service routing according to Embodiment 4 of the present invention. Wherein, the service gateway B of the peer-to-peer network domain 2 itself is connected to the peer node of the peer-to-peer network domain 2 as a client, that is, there is a peer-to-peer network client module in the service gateway B that can directly process peer-to-peer network services. In actual application, when a client initiates a service, it can send a service request to a certain service gateway, and the service gateway forwards the service request according to the query result of the local forwarding flow table, if there is no such service request in the forwarding flow table For the forwarding entry of the service request, the service routing request is initiated through the control plane channel with the inter-domain service routing control server. The inter-domain service routing control server selects a suitable service gateway for this service according to the service request, and sends a forwarding flow table to the selected service gateway to establish a forwarding path. The service gateway forwards the service request to the client or node in the destination peer network domain according to the delivered forwarding flow table. The specific steps are described as follows:

Step 501: client A in peer-to-peer network domain 1 initiates a service request, and determines that the service peer is client B in peer-to-peer network domain 2; client A initiates a traditional service request;

Step 502: client A directly initiates a service request to service gateway A;

Client A can obtain the address information of service gateway A through pre-configuration or through DNS query;

Step 503: Service gateway A receives the service request, and performs a matching query in the local flow table;

For the first packet of this service, there is generally no corresponding forwarding flow entry on service gateway A;

Step 504: There is no forwarding entry for the service request in the local forwarding flow table of service gateway A, and initiates a service routing request to the inter-domain service routing control server. The inter-domain service routing control server selects the service gateway A of the peer-to-peer network domain 1 and the service gateway B of the peer-to-peer network domain 2 as forwarding nodes for this service;

The service routing request carries necessary information, so that the inter-domain service routing control server can obtain the information of the source peer-to-peer network domain and the destination peer-to-peer network domain of both sides of the business session, such as the attribution domain name information of the users on both sides of the session, the customer end address information, etc.;

Step 505: The inter-domain service routing control server sends a forwarding flow table to service gateway A for this service;

Step 506: The inter-domain service routing control server sends a forwarding flow table to service gateway B for this service;

Step 507: Service gateway A forwards the service request to service gateway B according to the forwarding flow table issued by the inter-domain service routing control server for this service;

Step 508: Service gateway B receives the service request, and performs a matching search in the local forwarding flow table, and learns that the service message needs to be processed locally;

Steps 509-510: Service gateway B initiates a service request to client B through intermediate node C according to the internal processing mechanism of peer-to-peer network domain 2;

Steps 511-512: client B returns a service response message to service gateway C via intermediate node C;

Here, the service processing in steps 509-512 is carried out inside the P2P network domain, and the specific service processing mode can be determined according to the P2P algorithm and service mechanism of the P2P network domain 2, and the service message may be a P2P message;

Steps 513-514: Service gateway B returns the result of service processing to client A via service gateway A. The operation of service gateway A to return the service processing result is realized based on the forwarding flow table.

Embodiment five

FIG. 6 is a schematic diagram of a device for implementing a peer-to-peer network inter-domain service routing control server according to Embodiment 5 of the present invention. The inter-domain service routing control server and the service gateway together form a peer-to-peer network inter-domain service routing system.

The inter-domain service routing control server mainly includes a service routing control module, a service gateway management module and a protocol control function module; wherein,

The service routing control module is responsible for realizing the service routing selection function, judging the information of the source peer-to-peer network domain and the destination peer-to-peer network domain of both parties in the session according to the service routing request, and selecting a suitable service gateway for this service session. The main basis is the peer-to-peer network domain and the service gateway information of the peer-to-peer network domain provided by the service gateway management module. According to the selection result for the service gateway, the service routing control module sends the forwarding flow table to the selected service gateway through the interface provided by the protocol control function module.

The service gateway management module is responsible for collecting the basic configuration information of all peer-to-peer network domains and deployed service gateway information, and provides the basis for selecting a service gateway for the service routing control module. Specifically, the information that the service gateway management module needs to collect includes service gateway identification, service gateway configuration (port and status, etc.), link status with other peer-to-peer network domains, and peer-to-peer network domain configuration to which the service gateway belongs Information (domain name distribution of nodes and resources, etc.).

The protocol control function module is used to provide an information exchange channel between the inter-domain service routing control server and the service gateway. The exchanged information mainly includes communication security verification, peer-to-peer network domain information reporting, service gateway information reporting, configuration, delivery and management of forwarding flow tables, etc.

The communication protocol between the inter-domain service routing control server and the service gateway can be the OpenFlow protocol defined by the Open Networking Foundation (ONF), which separates control and forwarding, or other traditional media gateway control protocols. Protocols, such as H.248, SIP, etc.

The service gateway may be a transport layer device or an application layer device. A protocol similar to OpenFlow is applied between the inter-domain service routing control server and the service gateway, and the service gateway can be used as a transport layer device, that is, the service gateway only performs message modification and/or The forwarding operation does not perform any business-related intelligent processing. If the traditional media gateway control protocol is applied between the inter-domain service routing control server and the service gateway, the service gateway can be used as an application layer device to perform some service intelligent processing on the IP layer, such as service message Analysis, business policy execution, etc.

The service routing method, device and system between peer-to-peer networks provided by the present invention have little impact on the involved peer-to-peer network itself, have scalability, manageability, and simple configuration; at the same time, the routing efficiency of service messages is high and easy to implement Load balancing between service gateways.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (19)

1. A service routing method, which is applied to the scene where the client in the local peer-to-peer network domain carries out business interworking with the service peers in other peer-to-peer network domains, it is characterized in that the method includes: After receiving the service-related request sent by the client in the local peer-to-peer network domain, the inter-domain service routing control server selects a service gateway for this service session and issues a routing policy to the selected service gateway; The selected service gateway forwards the service message according to the delivered routing policy. 2. The method according to claim 1, wherein when the peer-to-peer network domain applies for the service interworking function, it reports the relevant information of the peer-to-peer network domain and the deployed service gateway to the inter-domain service routing control server. 3. The method according to claim 2, wherein the relevant information includes: service gateway identifier, service gateway configuration, link status with other peer-to-peer network domains, and the peer-to-peer domain to which the service gateway belongs Network domain configuration information. 4. The method according to any one of claims 1 to 3, characterized in that, When the client knows that the service peer is located in another peer-to-peer network domain, it initiates a service routing request to the inter-domain service routing control server, and sends a service request to the relevant service gateway according to the response returned by the inter-domain service routing control server; or, The client directly initiates a service request to a known service gateway. 5. The method according to any one of claims 1 to 3, wherein the service-related request is a service routing request, which carries information about the source and destination networks of both parties in the session. 6. The method according to any one of claims 1 to 3, wherein the routing strategy is a forwarding flow table, and the service message includes a service request; When performing the forwarding, the service gateway forwards the service message to other service gateways or clients for processing according to the delivered forwarding flow table. 7. The method according to claim 6, wherein when performing the forwarding, if no corresponding message can be queried according to the forwarding flow table, further query is made to the inter-domain service routing control server. 8. A service routing system, which is applied to the scene where the client in the local peer-to-peer network domain and the service counterparts in other peer-to-peer network domains perform business interworking, it is characterized in that the system includes an inter-domain service routing control server, a service Gateway; where, The inter-domain service routing control server is configured to select a service gateway for this service session and issue a routing policy to the selected service gateway after receiving a service-related request sent by a client in the local peer-to-peer network domain; The selected service gateway is used to forward service messages according to the issued routing policy. 9. The system according to claim 8, wherein when the peer-to-peer network domain applies for the service interworking function, it is used to report the relevant information of the peer-to-peer network domain and the deployed service gateway to the inter-domain service routing control server. 10. The system according to claim 9, wherein the relevant information includes: service gateway identification, service gateway configuration, link status with other peer-to-peer network domains, and the peer-to-peer domain to which the service gateway belongs Network domain configuration information. 11. A system according to any one of claims 8 to 10, wherein When the client knows that the service peer is located in another peer-to-peer network domain, it is used to initiate a service routing request to the inter-domain service routing control server, and send a service to the relevant service gateway according to the response returned by the inter-domain service routing control server request; or, The client is used to directly initiate a service request to a known service gateway. 12. The system according to any one of claims 8 to 10, wherein the service-related request is a service routing request, which carries information about the source and destination networks of both parties in the session. 13. The system according to any one of claims 8 to 10, wherein the routing strategy is a forwarding flow table, and the service message includes a service request; When performing the forwarding, the service gateway is used to forward the service message to other service gateways or clients for processing according to the delivered forwarding flow table. 14. The system according to claim 13, wherein when performing the forwarding, if no corresponding message can be queried according to the forwarding flow table, the service gateway is used to further inquire the inter-domain service routing control server. 15. A service routing device, which is applied to the scenario where a client in a local peer-to-peer network domain and a service peer in another peer-to-peer network domain perform business interworking, characterized in that the device is set in an inter-domain service routing control server , including a service routing control module, a service gateway management module and a protocol control function module; wherein, The service routing control module is used to select a service gateway for this service session; it also sends a routing strategy to the selected service gateway through the interface provided by the protocol control function module according to the selection result for the service gateway; The service gateway management module is used to provide the basis for selecting a service gateway for the service routing control module; The protocol control function module is used to provide an information exchange channel between the inter-domain service routing control server and the service gateway. 16. The apparatus of claim 15, wherein: When the service routing control module selects the service gateway, it is used to judge the information of the source peer-to-peer network domain and the destination peer-to-peer network domain of both parties in the session according to the service route request, and select the service gateway for this service session accordingly; The main basis for making the selection is the peer-to-peer network domain and the service gateway information of the peer-to-peer network domain provided by the service gateway management module. 17. The apparatus of claim 15, wherein: The service gateway management module is used to collect basic configuration information of all peer-to-peer network domains and deployed service gateway information as a basis for the service routing control module to select a service gateway. 18. The apparatus of claim 17, wherein: The collected service gateway information includes: service gateway identifier, service gateway configuration, link status with other peer-to-peer network domains, and configuration information of the peer-to-peer network domain to which the service gateway belongs. 19. The device according to any one of claims 15 to 18, wherein the routing policy is a forwarding flow table.

Images