CN103200102A - Method, device and system for service routing - Google Patents
Method, device and system for service routing Download PDFInfo
- Publication number
- CN103200102A CN103200102A CN2012100042113A CN201210004211A CN103200102A CN 103200102 A CN103200102 A CN 103200102A CN 2012100042113 A CN2012100042113 A CN 2012100042113A CN 201210004211 A CN201210004211 A CN 201210004211A CN 103200102 A CN103200102 A CN 103200102A
- Authority
- CN
- China
- Prior art keywords
- service
- peer
- domain
- routing
- service gateway
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 19
- 238000012545 processing Methods 0.000 claims description 18
- 230000004044 response Effects 0.000 claims description 12
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 230000003993 interaction Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 5
- 238000001514 detection method Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method, a device and a system for service routing. The method, the device and the system for the service routing are applied in scenes of service interworking between a client-side of a local peer-to-peer network domain and service opposite terminals in other peer-to-peer network domains. After an inter-domain routing control server receives a relevant service request sent by the client-side of the local peer-to-peer network domain, a service gateway is selected for a service session, a routing strategy is issued to the selected service gateway, and the selected service gateway transmits service information according to the issued routing strategy. According to the method, the device and the system for the service routing, influences on relevant peer-to-peer networks are small, the system has expansibility and manageability and is simple in configuration, meanwhile routing efficiency of the service information is high, and load balancing among network gateways is easily achieved.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for service routing.
Background
At present, Peer-to-Peer (Peer-to-Peer, P2P) technology is rapidly developed, and the coexistence of multiple network structures and algorithms makes a great contribution to the flourishing of internet services, but also makes great difficulty in the interworking between P2P service networks. Currently, interworking technology has become one of the factors that restrict the industrial scale of P2P network. For this reason, the international Internet Engineering Task Force (IETF) P2P SIP (session initiation protocol) working group has established the first P2P network protocol standard load (REsource Location and discovery protocol), which makes a significant contribution to the development of P2P network technology. However, even if the RELOAD is adopted uniformly as the standard protocol of the P2P service network, there is still a problem in the interworking of different P2P service networks. As shown in fig. 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 conventional SIP call is initiated, or the client 103 serving as a client of the peer-to-peer network domain 102 to which the called user belongs initiates a P2PSIP call. In this case, the client 103 needs to know configuration information, routing algorithm, protocol, and the like of the peer-to-peer network domain 102, and such a requirement for the client is not realistic when there are many peer-to-peer networks.
Therefore, a solution of a multi-layer overlay network 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 only relieves the capacity requirements of the client, and when a new peer-to-peer network joins or leaves, the super node still has the problem of difficult configuration adjustment, for example, when the P2P routing algorithm protocol of the peer-to-peer network and even the HASH algorithm are different, the intercommunication between the peer-to-peer networks is difficult to realize.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a service routing method, device and system, so as to solve the problem of service interworking between different peer-to-peer networks.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a service routing method is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with service opposite terminals of other peer-to-peer network domains, and comprises the following steps:
after receiving a request related to a service, sent by a client of a local peer-to-peer network domain, an inter-domain service routing control server selects a service gateway for the service session and issues a routing strategy to the selected service gateway;
and the selected service gateway forwards the service message according to the issued routing strategy.
When the peer-to-peer network domain applies for the service intercommunication function, the relevant information of the peer-to-peer network domain and the deployed service gateway is reported to the inter-domain service routing control server.
The related information includes: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
The client side initiates a service routing request to the inter-domain service routing control server when knowing that the service opposite end is positioned in other peer-to-peer network domains, and sends the service request to a related service gateway according to a response returned by the inter-domain service routing control server; or,
the client directly initiates a service request to a known service gateway.
The request related to the service is a service routing request, wherein the service routing request carries information of source and destination networks of both parties of the session.
The routing strategy is a forwarding flow table, and the service message comprises a service request;
and when the forwarding is carried out, the service gateway forwards the service message to other service gateways or clients for processing according to the issued forwarding flow table.
And when the forwarding is carried out, if the corresponding message can not be inquired according to the forwarding flow table, further inquiring the inter-domain service routing control server.
A service routing system is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with a service opposite terminal of other peer-to-peer network domains, and comprises an inter-domain service routing control server and a service gateway; wherein,
the inter-domain service routing control server is used for selecting a service gateway for the service session and issuing a routing strategy to the selected service gateway after receiving a service-related request sent by a client of a local peer-to-peer network domain;
and the selected service gateway is used for forwarding the service message according to the issued routing strategy.
And when the peer-to-peer network domain applies for the service intercommunication function, the peer-to-peer network domain is used for reporting the relevant information of the peer-to-peer network domain and the deployed service gateway to an inter-domain service routing control server.
The related information includes: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
The client end is used for initiating a service routing request to the inter-domain service routing control server when knowing that the service opposite end is positioned in other peer-to-peer network domains, and sending the service request to a related service gateway according to a response returned by the inter-domain service routing control server; or,
the client is used for directly initiating a service request to a known service gateway.
The request related to the service is a service routing request, wherein the service routing request carries information of source and destination networks of both parties of the session.
The routing strategy is a forwarding flow table, and the service message comprises a service request;
and when the forwarding is carried out, the service gateway is used for forwarding the service message to other service gateways or clients for processing according to the issued forwarding flow table.
And when the forwarding is carried out, if the corresponding message cannot be inquired according to the forwarding flow table, the service gateway is used for further inquiring the inter-domain service route control server.
A service routing device is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with a service opposite end of other peer-to-peer network domains, is arranged in an inter-domain service routing control server and comprises a service routing control module, a service gateway management module and a protocol control function module; wherein,
the service routing control module is used for selecting a service gateway for the service session; the routing strategy is also issued to the selected service gateway through an interface provided by the protocol control function module according to the selection result aiming at the service gateway;
the service gateway management module is used for providing a basis for selecting a service gateway for the service routing control module;
and the protocol control function module is used for providing an information interaction channel between the inter-domain service route control server and the service gateway.
When selecting a service gateway, the service routing control module is used for judging the information of a source peer network domain and a destination peer network domain of both parties of a session according to a service routing request, and selecting the service gateway for the service session;
the main basis for selection is the service gateway management module provided service gateway information of the peer-to-peer network domain and the peer-to-peer network domain.
The service gateway management module is used for collecting basic configuration information of all peer-to-peer network domains and deployed service gateway information to be used as a basis for the service routing control module to select a service gateway;
the collected service gateway information includes: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
The routing policy is a forwarding flow table.
The method, the device and the system for routing the service between the peer-to-peer networks have small influence on the related peer-to-peer networks, have expansibility and manageability and are simple to configure; meanwhile, the routing efficiency of the service messages is high, and the load balance among the service gateways is easy to realize.
Drawings
Fig. 1 is a schematic diagram of a network architecture for implementing peer-to-peer network service interworking in the prior art;
fig. 2 is a schematic diagram of a system structure for implementing a peer-to-peer network service routing network according to a first embodiment of the present invention;
fig. 3 is a flowchart of implementing peer-to-peer network service routing according to a second embodiment of the present invention;
fig. 4 is a message flow diagram for implementing peer-to-peer network service routing according to a third embodiment of the present invention;
fig. 5 is another message flow diagram for implementing peer-to-peer network traffic routing according to a fourth embodiment of the present invention;
fig. 6 is a schematic diagram of an apparatus for implementing a peer-to-peer inter-domain service routing control server according to a fifth embodiment of the present invention;
fig. 7 is a simplified diagram of a service routing process according to an embodiment of the present invention.
Detailed Description
In a basic technology of a Software Defined Network (SDN) technology, a forwarding/control separation architecture may be adopted, and an external control plane entity controls a forwarding plane device to implement various forwarding logics, and a main function of the forwarding plane device is to perform controlled forwarding according to routing policies such as a forwarding flow table, and a specific forwarding behavior is standardized: receiving a message, extracting the related field value of the header L (layer) 2/L3/L4, and using the field value as a keyword to look up a forwarding flow table; and after one table entry is matched, converting the message field according to the instruction set in the table entry content, and then forwarding the converted message to the logic port or the physical port according to the instruction.
Based on the technical content, controlled media plane forwarding equipment can be deployed to serve as a service gateway, and a centralized inter-domain service routing control server is adopted to manage the service gateway, so that an inter-domain service routing control function is realized.
In practical application, aiming at various heterogeneous peer-to-peer network environments, a service routing system between peer-to-peer networks can be set, wherein the service routing system comprises a client, a peer-to-peer network domain, an inter-domain service routing control server, a service gateway and the like; wherein,
when the peer-to-peer network domain applies for the service intercommunication function, the related information of the peer-to-peer network domain and the deployed service gateway is reported to an inter-domain service routing control server;
when the client communicates with the service opposite terminal of other peer-to-peer network domain, the client 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 proper service gateway for the service session and transmits routing strategies such as a forwarding flow table and the like to the selected service gateway;
and the service gateway forwards the service request to other service gateways or clients for processing according to the issued routing strategies such as the forwarding flow table and the like.
Further, when the peer-to-peer network domain applies for service 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 a service gateway identifier, a service gateway configuration, a link state with other peer-to-peer network domains, and peer-to-peer network domain configuration information to which the service gateway belongs, such as domain names of nodes and resources, IP address field distribution, and the like;
further, when the client knows that the service opposite end is located in other peer-to-peer network domains, the client initiates a service routing request to the inter-domain service routing control server and sends the service request to a related service gateway according to a response returned by the inter-domain service routing control server; of course, the client may also directly initiate a service request to a known service gateway;
further, when the client communicates with the service opposite end of other peer-to-peer network domain, 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 of 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, the service gateway further queries the inter-domain service routing control server;
it can be seen that service gateways can be deployed independently in peer-to-peer network domains, 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 a proper service gateway for the session and issuing routing strategies such as a forwarding flow table to the selected service gateway, and the service gateway forwards the service request and subsequent service messages according to the routing strategies such as the forwarding flow table.
The invention is described in detail below with reference to the figures and the specific embodiments.
Example one
Fig. 2 is a schematic diagram of a system architecture implementing a peer-to-peer network traffic routing network. As shown in fig. 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, and the like; where peer-to-peer network domain 201 is an overlay network consisting of a plurality of peer-to-peer nodes 206.
In order to realize the service intercommunication problem among a plurality of heterogeneous peer-to-peer network domains, the service gateway is independently deployed by an operator of each peer-to-peer network domain and is used as a service message outlet and inlet of the peer-to-peer network domain. The inter-domain service routing control server is responsible for managing service gateways of all peer-to-peer network domains, selecting a proper service gateway for cross-domain service routing and issuing 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, basic configuration information of the peer-to-peer network domain and a deployed service gateway needs to be reported to an inter-domain service routing control server to be used as a basis for selecting a path of a service route. Specifically, the information that the peer-to-peer network domain needs to report to the inter-domain service routing control server includes a service gateway identifier, service gateway configuration (port and state, etc.), a link state with other peer-to-peer network domains, and peer-to-peer network domain configuration (domain name distribution of nodes and resources, etc.) to which the service gateway belongs. The inter-domain service routing control server may further control the service gateways to perform a link layer detection protocol with each other to collect link states between the service gateways, and a specific method of performing the link layer detection protocol to collect the link states is similar to a topology detection method of an OpenFlow (open flow) network. The service gateway executes operations such as modification/forwarding and the like on the service message according to the forwarding flow table issued to the local, initiates a service routing request for the service message which can not be operated according to the local forwarding flow table through a control surface channel between the service gateway and the inter-domain service routing control server, issues a new forwarding flow table to the service gateway after further judgment by the inter-domain service routing control server, and then forwards the service message according to the newly issued forwarding flow table.
Example two
Fig. 3 is a flowchart of implementing peer-to-peer network traffic routing according to a second embodiment of the present invention, where the flowchart may be implemented based on the system shown in the first embodiment. The route shown in fig. 3 mainly includes the following steps:
step 301: the peer-to-peer network domain applies for the intercommunication with other peer-to-peer network domain services and reports the relevant information of the network domain to an inter-domain service routing control server;
the related information comprises a service gateway identification of the peer-to-peer network domain, service gateway configuration, link states with other peer-to-peer network domains and 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 comprises an allocated domain name and/or an IP address prefix of a terminal and the like;
step 302: the inter-domain service routing control server collects configuration information of all peer-to-peer network domains, service gateway information, link state information between service gateways of different peer-to-peer network domains, service intercommunication protocols between peer-to-peer network domains and the like;
the link state information between the service gateways of different peer-to-peer network domains can be directly reported when the peer-to-peer network domains apply for joining the intercommunication network, or the inter-domain service routing control server indicates that the service gateways carry out link detection mutually to obtain the link state information;
the service intercommunication protocol between the peer-to-peer network domains refers to the agreement between operators of the peer-to-peer network domains, such as which services are intercommunicated with which peer-to-peer network domains, service priority, charging information and the like;
step 303: the inter-domain service routing control server selects a proper service gateway to establish a session path according to the source network domain information and the destination network domain information of the service session carried in the service routing request, and issues a forwarding flow table to the selected service gateway;
when a service request crossing network domains occurs, or a client can directly initiate a service routing request to an inter-domain service routing control server; or the client directly initiates a service request to the service gateway of the local domain, and then the service gateway initiates the service routing request to the inter-domain service routing control server when the service gateway of the local domain does not locally have a corresponding forwarding flow table;
step 304: the service gateway forwards the service request and the subsequent service message to a target peer-to-peer network domain according to a local forwarding flow table;
if the local forwarding flow table of the service gateway does not have the forwarding table item of the service message, the service gateway initiates a service routing request to an inter-domain service routing control server, and then forwards the service message according to the forwarding flow table issued by the inter-domain service routing control server;
the service gateway can be connected to the peer-to-peer network domain as a client of the peer-to-peer network domain, and can also be connected to the client or a node of the peer-to-peer network domain as a common media forwarding device.
EXAMPLE III
Fig. 4 is a message flow diagram for implementing peer-to-peer network traffic routing according to a third embodiment of the present invention. Wherein the service gateway B of the peer-to-peer network domain 2 is connected as a common media forwarding device to the clients or nodes of the peer-to-peer network domain 2. In actual application, when a client initiates a service request, it first determines whether a service opposite end is located in the local peer-to-peer network domain, and if not, the client first requests a service routing path from an inter-domain service routing control server. The inter-domain service routing control server selects a proper service gateway for the service according to the service routing request of the client, transmits 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. The client sends 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 the node of the destination opposite terminal network domain according to the issued forwarding flow table. The specific steps are described as follows:
step 401: a client A of a peer-to-peer network domain 1 initiates a service request, and judges that a service opposite end is a client B located in a peer-to-peer network domain 2; a client A initiates a service routing request to an inter-domain service routing control server;
the service routing request carries necessary information, so that the inter-domain service routing control server can acquire information of a source peer network domain and a destination peer network domain of both parties of the service session, such as home domain name information of users of both parties of the session, address information of a client and the like;
the client A can acquire the address information of the inter-domain service routing control server in a pre-configuration mode or a DNS (domain name system) query mode;
step 402: the inter-domain service routing control server receives the service routing request, and selects a service gateway A of a peer-to-peer network domain 1 and a service gateway B of a peer-to-peer network domain 2 as forwarding nodes for the service;
step 403: the inter-domain service routing control server sends a forwarding flow table to the service gateway A for the service;
step 404: the inter-domain service routing control server issues a forwarding flow table to the service gateway B for the service;
step 405: the inter-domain service routing control server returns a service routing response message to the client A, wherein the service routing response message carries the address information of the service gateway A selected for the service session;
step 406: a client A sends a service request to a service gateway A;
step 407: the service gateway A receives the service request and locally forwards the flow table for matching and searching;
step 408: the service gateway A forwards the service request to the service gateway B according to the search result of the local forwarding flow table;
step 409: the service gateway B receives the service request and carries out matching search in a local forwarding flow table to acquire that the service request needs to be forwarded to a node C of a peer-to-peer network domain 2 connected with the service gateway B for processing;
step 410: the service gateway B sends a service request to a node C of the connected peer-to-peer network domain 2;
step 411: a node C of the peer-to-peer network domain 2 generates a service request to a destination client B of the service request;
step 412: the client B of the peer-to-peer network domain 2 completes the service processing and returns a response message;
here, step 411 and 412 are the internal processing flow of the service message in the peer-to-peer network domain 2, the specific processing manner is determined according to the P2P algorithm and the service mechanism of the peer-to-peer network domain 2, and the response message may be a P2P message;
step 413-415: and the node C of the peer-to-peer network domain 2 returns the service response message to the client A through the service gateway B and the service gateway A. The forwarding processing of the service response message by the service gateway is also realized based on the forwarding flow table.
Example four
Fig. 5 is another message flow diagram for implementing peer-to-peer network traffic routing according to a fourth embodiment of the present invention. The service gateway B of the peer-to-peer network domain 2 is connected to the peer node of the peer-to-peer network domain 2 as a client, that is, a peer-to-peer network client module in the service gateway B can directly perform peer-to-peer network service processing. In actual application, when a client initiates a service, a service request may be sent to a certain service gateway, and the service gateway forwards the service request according to a query result of a local forwarding flow table, and if the forwarding flow table does not have a forwarding table entry of the service request, the service gateway initiates a service routing request through a control plane channel between the service gateway and an inter-domain service routing control server. And the inter-domain service routing control server selects a proper service gateway for the service according to the service request, and issues a forwarding flow table to the selected service gateway to establish a forwarding path. And the service gateway forwards the service request to a client or a node of the destination opposite terminal network domain according to the issued forwarding flow table. The specific steps are described as follows:
step 501: a client A of a peer-to-peer network domain 1 initiates a service request, and judges that a service opposite end is a client B located in a peer-to-peer network domain 2; a client A initiates a traditional service request;
step 502: a client A directly initiates a service request to a service gateway A;
the client A can acquire the address information of the service gateway A in a pre-configuration mode or a DNS query mode;
step 503: the service gateway A receives the service request and carries out matching query in a local flow table;
for the first message of the service, the service gateway a generally has no corresponding forwarding flow table entry;
step 504: and the local forwarding table entry without the service request in the local forwarding table of the service gateway A initiates a service routing request to the inter-domain service routing control server. The inter-domain service routing control server selects a service gateway A of the peer-to-peer network domain 1 and a service gateway B of the peer-to-peer network domain 2 as forwarding nodes for the current service;
the service routing request carries necessary information, so that the inter-domain service routing control server can acquire information of a source peer network domain and a destination peer network domain of both parties of the service session, such as home domain name information of users of both parties of the session, address information of a client and the like;
step 505: the inter-domain service routing control server sends a forwarding flow table to the service gateway A for the service;
step 506: the inter-domain service routing control server issues a forwarding flow table to the service gateway B for the service;
step 507: the service gateway A forwards the service request to the service gateway B according to the forwarding flow table issued by the inter-domain service routing control server for the service;
step 508: the service gateway B receives the service request and forwards the flow table locally for matching and searching to acquire that the service message needs to be processed locally;
step 509-510: the service gateway B initiates a service request to the client B through the intermediate node C according to an internal processing mechanism of the peer-to-peer network domain 2;
step 511-512, the following steps: the client B returns a service response message to the service gateway C through the intermediate node C;
here, the service processing of step 509 plus 512 is performed inside the peer-to-peer network domain 2, and the specific service processing manner may be determined according to the P2P algorithm and the service mechanism of the peer-to-peer network domain 2, where the service message may be a P2P message;
step 513-: and the service gateway B returns the service processing result to the client A through the service gateway A. The operation of the service gateway a on returning the service processing result is realized based on the forwarding flow table.
EXAMPLE five
Fig. 6 is a schematic diagram of an apparatus for implementing a peer-to-peer inter-domain service routing control server according to a fifth embodiment of the present invention. The inter-domain service routing control server and the service gateway jointly form a peer-to-peer network inter-domain service routing system.
The inter-domain service routing control server mainly comprises a service routing control module, a service gateway management module and a protocol control function module; wherein,
and the service routing control module is responsible for realizing a service routing selection function, judging information of a source peer network domain and a destination peer network domain of both parties of the session according to the service routing request, and selecting a proper service gateway for the service session, wherein the selection is mainly carried out according to the service gateway management module provided service gateway information of the peer network domain and the peer network domain. And according to the selection result aiming at the service gateway, the service routing control module issues a forwarding flow table to the selected service gateway through an interface provided by the protocol control function module.
And the service gateway management module is responsible for collecting the basic configuration information and the deployed service gateway information of all peer-to-peer network domains and providing a 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 a service gateway identifier, service gateway configuration (port and state, etc.), link state with other peer-to-peer network domains, and peer-to-peer network domain configuration information (domain name distribution of nodes and resources, etc.) to which the service gateway belongs.
And the protocol control function module is used for providing an information interaction channel between the inter-domain service route control server and the service gateway. The interacted information mainly comprises communication security verification, peer-to-peer network domain information reporting, service gateway information reporting, configuration, issuing and management of a forwarding flow table and the like.
The communication protocol between the inter-domain service routing control server and the service gateway may be an OpenFlow protocol with separated control and forwarding defined by an Open network alliance (ONF), or may be other conventional protocols for implementing media gateway control, such as h.248, SIP, and the like.
The service gateway may be a transport layer device or an application layer device. The inter-domain service routing control server and the service gateway apply a protocol similar to OpenFlow, and the service gateway can be used as a transport layer device, that is, the service gateway only performs message modification and/or forwarding operation based on an instruction in a local forwarding flow table, and does not perform any service-related intelligent processing. If a 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 an IP layer, such as service message analysis, service policy execution, and the like.
The method, the device and the system for routing the service between the peer-to-peer networks have small influence on the related peer-to-peer networks, have expansibility and manageability and are simple to configure; meanwhile, the routing efficiency of the service messages is high, and the load balance among the service gateways is easy to realize.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (19)
1. A service routing method is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with a service opposite terminal of other peer-to-peer network domains, and is characterized by comprising the following steps:
after receiving a request related to a service, sent by a client of a local peer-to-peer network domain, an inter-domain service routing control server selects a service gateway for the service session and issues a routing strategy to the selected service gateway;
and the selected service gateway forwards the service message according to the issued routing strategy.
2. The method of claim 1, wherein when the peer-to-peer network domain applies for a service interworking function, the peer-to-peer network domain reports information related to the deployed service gateway to an inter-domain service routing control server.
3. The method of claim 2, wherein the related information comprises: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
4. The method according to any one of claims 1 to 3,
the client side initiates a service routing request to the inter-domain service routing control server when knowing that the service opposite end is positioned in other peer-to-peer network domains, and sends the service request to a related service gateway according to a response returned by the inter-domain service routing control server; or,
the client directly initiates a service request to a known service gateway.
5. A method according to any one of claims 1 to 3, wherein the request relating to a service is a service routing request carrying information of the source and destination networks of both parties to the session.
6. The method according to any of claims 1 to 3, wherein the routing policy is a forwarding flow table, and the traffic message comprises a traffic request;
and when the forwarding is carried out, the service gateway forwards the service message to other service gateways or clients for processing according to the issued forwarding flow table.
7. The method according to claim 6, wherein when forwarding, if no corresponding message can be queried according to the forwarding flow table, then further querying the inter-domain service routing control server.
8. A service routing system is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with a service opposite terminal of other peer-to-peer network domains, and is characterized by comprising an inter-domain service routing control server and a service gateway; wherein,
the inter-domain service routing control server is used for selecting a service gateway for the service session and issuing a routing strategy to the selected service gateway after receiving a service-related request sent by a client of a local peer-to-peer network domain;
and the selected service gateway is used for forwarding the service message according to the issued routing strategy.
9. The system according to claim 8, wherein said peer-to-peer network domain is configured to report information related to the peer-to-peer network domain and the deployed service gateway to an inter-domain service routing control server when applying for a service interworking function.
10. The system of claim 9, wherein the related information comprises: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
11. The system according to any one of claims 8 to 10,
the client end is used for initiating a service routing request to the inter-domain service routing control server when knowing that the service opposite end is positioned in other peer-to-peer network domains, and sending the service request to a related service gateway according to a response returned by the inter-domain service routing control server; or,
the client is used for directly initiating a service request to a known service gateway.
12. The system according to any of claims 8 to 10, wherein the request relating to the service is a service routing request carrying information of source and destination networks of both parties of the session.
13. The system according to any one of claims 8 to 10, wherein the routing policy is a forwarding flow table, and the traffic message comprises a traffic request;
and when the forwarding is carried out, the service gateway is used for forwarding the service message to other service gateways or clients for processing according to the issued forwarding flow table.
14. The system according to claim 13, wherein during said forwarding, if no corresponding packet can be queried according to a forwarding flow table, said service gateway is configured to further query an inter-domain service routing control server.
15. A service routing device is applied to a scene that a client of a local peer-to-peer network domain performs service intercommunication with a service opposite end of other peer-to-peer network domains, and is characterized in that the device is arranged in an inter-domain service routing control server and comprises a service routing control module, a service gateway management module and a protocol control function module; wherein,
the service routing control module is used for selecting a service gateway for the service session; the routing strategy is also issued to the selected service gateway through an interface provided by the protocol control function module according to the selection result aiming at the service gateway;
the service gateway management module is used for providing a basis for selecting a service gateway for the service routing control module;
and the protocol control function module is used for providing an information interaction channel between the inter-domain service route control server and the service gateway.
16. The apparatus of claim 15,
when selecting a service gateway, the service routing control module is used for judging the information of a source peer network domain and a destination peer network domain of both parties of a session according to a service routing request, and selecting the service gateway for the service session;
the main basis for selection is the service gateway management module provided service gateway information of the peer-to-peer network domain and the peer-to-peer network domain.
17. The apparatus of claim 15,
the service gateway management module is used for collecting basic configuration information of all peer-to-peer network domains and deployed service gateway information to be used as a basis for the service routing control module to select a service gateway.
18. The apparatus of claim 17,
the collected service gateway information includes: a service gateway identification, a service gateway configuration, a link state with other peer network domains, and peer network domain configuration information to which the service gateway belongs.
19. The apparatus according to any of claims 15 to 18, wherein the routing policy is a forwarding flow table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210004211.3A CN103200102B (en) | 2012-01-09 | 2012-01-09 | A kind of service routing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210004211.3A CN103200102B (en) | 2012-01-09 | 2012-01-09 | A kind of service routing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103200102A true CN103200102A (en) | 2013-07-10 |
| CN103200102B CN103200102B (en) | 2018-02-13 |
Family
ID=48722465
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210004211.3A Active CN103200102B (en) | 2012-01-09 | 2012-01-09 | A kind of service routing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103200102B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103532853A (en) * | 2013-10-21 | 2014-01-22 | 杭州华三通信技术有限公司 | Method and device for realizing heterogeneous stacking module |
| CN104168202A (en) * | 2014-08-26 | 2014-11-26 | 华为技术有限公司 | Method and device for forwarding Open Flow messages |
| CN104243340A (en) * | 2014-09-28 | 2014-12-24 | 杭州华三通信技术有限公司 | Message processing method and device in software-defined network |
| WO2015124026A1 (en) * | 2014-02-21 | 2015-08-27 | 华为技术有限公司 | Flow table entry generation method and device |
| CN105515975A (en) * | 2015-11-24 | 2016-04-20 | 武汉烽火网络有限责任公司 | Realization method and system for software defined networking based on application layer forwarding |
| CN105681215A (en) * | 2015-12-29 | 2016-06-15 | 华为技术有限公司 | Forwarding table entry generation method and controller |
| WO2016173233A1 (en) * | 2015-04-30 | 2016-11-03 | 华为技术有限公司 | Routing control method, device and system |
| CN106130787A (en) * | 2016-07-28 | 2016-11-16 | 中国电信集团工会上海市网络操作维护中心委员会 | A kind of transaction processing system based on software defined network |
| CN108243177A (en) * | 2016-12-27 | 2018-07-03 | 中国移动通信有限公司研究院 | A kind of data transmission method and device |
| CN109842680A (en) * | 2019-01-28 | 2019-06-04 | 南京钛佳汽车科技有限公司 | It is a kind of to realize the system and method to interconnect between gateway external sensor |
| WO2020238418A1 (en) * | 2019-05-28 | 2020-12-03 | 中兴通讯股份有限公司 | Inter-domain data interaction method and apparatus |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459650A (en) * | 2007-12-15 | 2009-06-17 | 华为技术有限公司 | Service routing method, service router, customer terminal equipment and service network system |
| CN101656765A (en) * | 2009-09-14 | 2010-02-24 | 中兴通讯股份有限公司 | Address mapping system and data transmission method of identifier/locator separation network |
| CN101677319A (en) * | 2008-09-19 | 2010-03-24 | 华为技术有限公司 | Method, apparatus and system for service access on the basis of XMPP protocol |
| CN101931999A (en) * | 2010-08-31 | 2010-12-29 | 深圳市赫迪威信息技术有限公司 | Service access method, portal switching server and service access system |
| GB2483280A (en) * | 2010-09-02 | 2012-03-07 | Skype Ltd | Point-to-point communication with persistent connection to front-end server |
| CN103188144A (en) * | 2011-12-29 | 2013-07-03 | 中兴通讯股份有限公司 | System and method for achieving distributed gateway intercommunication |
-
2012
- 2012-01-09 CN CN201210004211.3A patent/CN103200102B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459650A (en) * | 2007-12-15 | 2009-06-17 | 华为技术有限公司 | Service routing method, service router, customer terminal equipment and service network system |
| CN101677319A (en) * | 2008-09-19 | 2010-03-24 | 华为技术有限公司 | Method, apparatus and system for service access on the basis of XMPP protocol |
| CN101656765A (en) * | 2009-09-14 | 2010-02-24 | 中兴通讯股份有限公司 | Address mapping system and data transmission method of identifier/locator separation network |
| CN101931999A (en) * | 2010-08-31 | 2010-12-29 | 深圳市赫迪威信息技术有限公司 | Service access method, portal switching server and service access system |
| GB2483280A (en) * | 2010-09-02 | 2012-03-07 | Skype Ltd | Point-to-point communication with persistent connection to front-end server |
| CN103188144A (en) * | 2011-12-29 | 2013-07-03 | 中兴通讯股份有限公司 | System and method for achieving distributed gateway intercommunication |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103532853A (en) * | 2013-10-21 | 2014-01-22 | 杭州华三通信技术有限公司 | Method and device for realizing heterogeneous stacking module |
| CN103532853B (en) * | 2013-10-21 | 2016-11-09 | 杭州华三通信技术有限公司 | The implementation method of heterogeneous stacking model and device |
| WO2015124026A1 (en) * | 2014-02-21 | 2015-08-27 | 华为技术有限公司 | Flow table entry generation method and device |
| US11082262B2 (en) | 2014-02-21 | 2021-08-03 | Huawei Technologies Co., Ltd. | Flow entry generating method and apparatus |
| US10341141B2 (en) | 2014-02-21 | 2019-07-02 | Huawei Technologies Co., Ltd. | Flow entry generating method and apparatus |
| CN104168202B (en) * | 2014-08-26 | 2017-10-24 | 华为技术有限公司 | Open flows message forwarding method and device |
| CN104168202A (en) * | 2014-08-26 | 2014-11-26 | 华为技术有限公司 | Method and device for forwarding Open Flow messages |
| CN104243340A (en) * | 2014-09-28 | 2014-12-24 | 杭州华三通信技术有限公司 | Message processing method and device in software-defined network |
| CN104243340B (en) * | 2014-09-28 | 2017-11-10 | 新华三技术有限公司 | Message processing method and device in a kind of software defined network |
| CN106209628B (en) * | 2015-04-30 | 2019-05-28 | 华为技术有限公司 | A kind of route control method, equipment and system |
| WO2016173233A1 (en) * | 2015-04-30 | 2016-11-03 | 华为技术有限公司 | Routing control method, device and system |
| CN106209628A (en) * | 2015-04-30 | 2016-12-07 | 华为技术有限公司 | A kind of route control method, equipment and system |
| CN105515975B (en) * | 2015-11-24 | 2019-01-04 | 武汉烽火网络有限责任公司 | Software-oriented defines the realization method and system that network is forwarded based on application layer |
| CN105515975A (en) * | 2015-11-24 | 2016-04-20 | 武汉烽火网络有限责任公司 | Realization method and system for software defined networking based on application layer forwarding |
| CN105681215B (en) * | 2015-12-29 | 2019-02-12 | 华为技术有限公司 | A kind of generation method and controller of forwarding-table item |
| CN105681215A (en) * | 2015-12-29 | 2016-06-15 | 华为技术有限公司 | Forwarding table entry generation method and controller |
| CN106130787A (en) * | 2016-07-28 | 2016-11-16 | 中国电信集团工会上海市网络操作维护中心委员会 | A kind of transaction processing system based on software defined network |
| CN106130787B (en) * | 2016-07-28 | 2020-04-24 | 中国电信集团工会上海市网络操作维护中心委员会 | Service processing system based on software defined network |
| CN108243177B (en) * | 2016-12-27 | 2021-01-15 | 中国移动通信有限公司研究院 | Data transmission method and device |
| CN108243177A (en) * | 2016-12-27 | 2018-07-03 | 中国移动通信有限公司研究院 | A kind of data transmission method and device |
| CN109842680A (en) * | 2019-01-28 | 2019-06-04 | 南京钛佳汽车科技有限公司 | It is a kind of to realize the system and method to interconnect between gateway external sensor |
| CN109842680B (en) * | 2019-01-28 | 2021-10-12 | 南京钛佳汽车科技有限公司 | System and method for realizing interconnection and intercommunication between external sensors of gateway |
| WO2020238418A1 (en) * | 2019-05-28 | 2020-12-03 | 中兴通讯股份有限公司 | Inter-domain data interaction method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103200102B (en) | 2018-02-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103200102B (en) | A kind of service routing method, device and system | |
| CN104104742B (en) | It is manipulated using the user-plane traffic that network address translation and request redirect | |
| US9615318B2 (en) | Multiplexing core networks in RAN sharing | |
| WO2013040970A1 (en) | Relay node selecting method and device | |
| CN101116296A (en) | Voip network infrastructure components and method | |
| CN106789637B (en) | Cross-domain service intercommunication path establishment method, controller and system | |
| WO2012065531A1 (en) | Method, device, and system for implementing relay selection | |
| CN111294240B (en) | Cross-domain coordination method, coordination device and control device for network as-a-service (SERS) service | |
| US20070263538A1 (en) | Directed Pppoe Session Initiation Over a Switched Ethernet | |
| CN112218315A (en) | End-to-end QoS policy execution and Ethernet data forwarding method of 5G private network | |
| CN111435922B (en) | Bandwidth sharing method | |
| WO2012048613A1 (en) | Centralized p2p system that supports nat traversal and nat traversal method | |
| WO2009006847A1 (en) | Method, device and system for combination of resource admission control | |
| US20100226379A1 (en) | Policy control method and system for layer two devices | |
| JP6070700B2 (en) | Packet transfer system, control device, packet transfer method and program | |
| WO2007056960A1 (en) | A service device switch network and switch method?service device | |
| WO2009000181A1 (en) | Method for acquiring traversal resource, peer to peer node and peer to peer system | |
| WO2012149854A1 (en) | Rt-based method, system, and router for establishing lsp | |
| CN116016164A (en) | Virtual service network construction method based on software defined network | |
| CN101674245B (en) | Exit port route filtering method and device | |
| WO2008154848A1 (en) | Method for acquiring ability information of net node between domains, net node and communication system | |
| WO2012048615A1 (en) | Method and system for selecting relay nodes, and relay control node | |
| CN103416037B (en) | Method for setting up a communication link | |
| CN102752331B (en) | Method, resource control proxy and the system that implementation strategy controls in peer-to-peer network | |
| Zhang et al. | Research on Architecture and Application of Computing Network Convergence Service Orchestration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |