CN116055393A - Private line communication method, device and system - Google Patents
Private line communication method, device and system Download PDFInfo
- Publication number
- CN116055393A CN116055393A CN202111252901.6A CN202111252901A CN116055393A CN 116055393 A CN116055393 A CN 116055393A CN 202111252901 A CN202111252901 A CN 202111252901A CN 116055393 A CN116055393 A CN 116055393A
- Authority
- CN
- China
- Prior art keywords
- address
- client
- service message
- equipment
- determining
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/58—Association of routers
- H04L45/586—Association of routers of virtual routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a special line communication method, a device and a system, which relate to the technical field of communication, and introduce intermediate equipment, wherein the whole flow direction of service messages sent by a VPC server is as follows: the service message sent by the VPC server passes through the target gateway equipment, the target gateway equipment sends the service message to the corresponding intermediate equipment, the intermediate equipment sends the service message to the corresponding first border router, and finally the first border router sends the service message to the target client. When the special line fails, the next hop of the gateway equipment is fixedly directed to the intermediate equipment, the route convergence can be realized through the intermediate equipment, and the route on the gateway equipment does not need to be changed, namely, the route convergence process does not need to be participated by an SDN controller.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for dedicated line communications.
Background
The private line often carries customer core service, and in order to avoid service interruption caused by private line interruption, a redundant design is generally required, that is, a plurality of private lines jointly carry customer service, and customer IDC (Internet Data Center ) equipment accesses to a boundary router of a cloud manufacturer through a plurality of lines. On the premise of redundant design, when a special line fails, how to quickly converge is a design key point.
Different from a single network device (such as a router or a switch) in the IDC (internet data center) scene, various gateways are introduced in the cloud network scene, and when the client IDC is accessed by the flow in the VPC (Virtual Private Cloud ), the client IDC device needs to be accessed by passing through different gateways, then reaching a cloud manufacturer boundary router and finally reaching the client IDC device. When a private line fails, not only does the routing on the border router need to converge, but the convergence and optimization of the entire routing link from the VPC server to the customer IDC device is also considered globally.
As shown in fig. 1, the main scheme of route convergence caused by a private line fault in the prior art is as follows: the communication network comprises a VPC server 101, a gateway device 102, a border router 103 and a client IDC device 104, wherein the VPC server 101 is in communication connection with the gateway device 102, the gateway device 102 is respectively in communication connection with two border routers 103 on two special lines, the two border routers 103 have different IP (Internet Protocol, protocol interconnected between networks) addresses (as shown in figure 1, the IP addresses of the two border routers 103 are respectively 1.1.1.2 and 1.1.1.4), and the two border routers 103 are respectively in communication connection with the corresponding client IDC devices 104 through EBGPs (External Border Gateway Protocol ); an independent monitoring server 105 monitors the health status of the private line on the border router 103, when the private line on the border router 103 with the IP address of 1.1.1.2 fails, the monitoring server 105 reports the route withdrawal information to an SDN (software defined network ) controller in the VPC server 101, and after receiving the route withdrawal information, the SDN controller issues a command for deleting the route to the corresponding gateway device 102, so that route convergence is achieved on the gateway device 102 by changing the next hop, that is, the gateway device 102 adjusts the next hop to the border router 103 with the IP address of 1.1.1.4, and no longer forwards traffic to the border router 103 with the IP address of 1.1.1.2.
However, in the above solution for route convergence on the gateway device based on the SDN controller, the convergence path is too long, resulting in longer convergence time.
Disclosure of Invention
The invention aims to provide a special line communication method, a special line communication device and a special line communication system, so as to shorten convergence time and improve convergence speed.
In a first aspect, an embodiment of the present invention provides a private line communication method, which is applied to a border router, including:
receiving a service message sent by an intermediate device, wherein the service message comprises a client identifier, the client is a private line client, the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share an IP address;
determining an IP address of the target client based on the client identification;
and sending the service message to the target client based on the IP address of the target client.
Further, the method further comprises the following steps:
receiving a response message sent by the target client in response to the service message, wherein the response message comprises a client identifier;
determining an IP address of the target gateway device based on the client identification;
and sending the response message to the target gateway equipment based on the IP address of the target gateway equipment so that the target gateway equipment sends the response message to the VPC server.
Further, the service message further includes a first destination IP address, and a first routing table is maintained locally, where the first routing table includes a correspondence between the first destination IP address and a next hop IP address; the determining the IP address of the target client based on the client identifier includes:
determining a first routing table based on the customer identification;
and determining a first next-hop IP address in the first routing table based on the first destination IP address, wherein the first next-hop IP address is the IP address of the target client.
In a second aspect, an embodiment of the present invention further provides a private line communication method, which is applied to an intermediate device, where the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all the intermediate devices in the device group share an IP address; the private line communication method comprises the following steps:
receiving a service message sent by target gateway equipment, wherein the service message comprises a client identifier, and the client is a private line client;
determining an IP address of a first border router based on the customer identification;
and sending the service message to the first boundary router based on the IP address of the first boundary router.
Further, the service message further includes a first destination IP address, and a second routing table is maintained locally, where the second routing table includes a correspondence between the first destination IP address and a next hop IP address; the determining the IP address of the first border router based on the client identification includes:
determining a second routing table based on the customer identification;
and determining a second next-hop IP address in the second routing table based on the first destination IP address, wherein the second next-hop IP address is the IP address of the first border router.
Further, the determining, based on the first destination IP address, a second next-hop IP address in the second routing table includes:
determining a plurality of next hop IP addresses corresponding to the first destination IP address in the second routing table;
determining a second next-hop IP address from a plurality of next-hop IP addresses corresponding to the first destination IP address according to a preset rule; wherein the preset rule comprises a priority-based determination and/or a link-based load state determination.
Further, the method further comprises the following steps:
detecting the reachability of links between the router and each boundary router in real time;
and deleting a path corresponding to the second boundary router in the second routing table when the link between the second boundary router and the second boundary router is not reachable.
In a third aspect, an embodiment of the present invention further provides a private line communication method, which is applied to a gateway device, including:
receiving a service message sent by a VPC server, wherein the service message comprises a client identifier, and the client is a private line client;
determining an IP address of an intermediate device based on the client identifier, wherein the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share one IP address;
and sending the service message to the intermediate equipment based on the IP address of the intermediate equipment.
In a fourth aspect, an embodiment of the present invention further provides a private line communication apparatus, which is applied to a border router, including:
the first receiving module is used for receiving a service message sent by an intermediate device, wherein the service message comprises a client identifier, the client is a private line client, the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share one IP address;
a first determining module, configured to determine an IP address of a target client based on the client identifier;
and the first sending module is used for sending the service message to the target client based on the IP address of the target client.
In a fifth aspect, an embodiment of the present invention further provides a private line communication apparatus, which is applied to an intermediate device, where the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all intermediate devices in the device group share one IP address; the private line communication apparatus includes:
the second receiving module is used for receiving the service message sent by the target gateway equipment, wherein the service message comprises a client identifier, and the client is a private line client;
a second determining module, configured to determine an IP address of the first border router based on the client identifier;
and the second sending module is used for sending the service message to the first border router based on the IP address of the first border router.
In a sixth aspect, an embodiment of the present invention further provides a private line communication apparatus, which is applied to a gateway device, including:
the third receiving module is used for receiving the service message sent by the VPC server, wherein the service message comprises a client identifier, and the client is a private line client;
a third determining module, configured to determine an IP address of an intermediate device based on the client identifier, where the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all intermediate devices in the device group share one IP address;
And the third sending module is used for sending the service message to the intermediate equipment based on the IP address of the intermediate equipment.
In a seventh aspect, an embodiment of the present invention further provides a border router, including a memory, and a processor, where the memory stores a computer program that can be run on the processor, and when the processor executes the computer program, the processor implements the private line communication method described in the first aspect.
In an eighth aspect, an embodiment of the present invention further provides an intermediate device, including a memory, and a processor, where the memory stores a computer program that can be executed on the processor, and the processor implements the private line communication method described in the second aspect when executing the computer program.
In a ninth aspect, an embodiment of the present invention further provides a gateway device, including a memory, and a processor, where the memory stores a computer program that can be run on the processor, and the processor implements the private line communication method described in the third aspect when executing the computer program.
In a tenth aspect, an embodiment of the present invention further provides a private line communication system, including the border router in the seventh aspect, the intermediate device in the eighth aspect, and the gateway device in the ninth aspect.
In an eleventh aspect, an embodiment of the present invention further provides a computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to perform the private line communication method according to the first aspect, the second aspect, or the third aspect.
The method, the device and the system for dedicated line communication provided by the embodiment of the invention introduce intermediate equipment, and the overall flow direction of the service message sent by the VPC server is as follows: the service message sent by the VPC server passes through the target gateway equipment, the target gateway equipment sends the service message to the corresponding intermediate equipment, the intermediate equipment sends the service message to the corresponding first border router, and finally the first border router sends the service message to the target client. Therefore, when the special line fails, the routing convergence can be realized through the intermediate device, and the routing on the gateway device does not need to be changed, namely, the routing convergence process does not need to be participated by an SDN controller.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of route convergence performed on a gateway device in the prior art;
fig. 2 is a network architecture diagram of a communication network according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of a private line communication method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a dedicated line communication device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another dedicated line communication device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another dedicated line communication device according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a network device according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a private line communication system according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be clearly and completely described in connection with the embodiments, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
After customer service clouds, when local IDC equipment and on-line equipment are required to be interconnected and intercommunicated, one of the main stream modes is a private line. The special line is used for constructing a high-speed, low-delay, stable and safe special connection channel between the user local data center and the cloud VPC, one end of the special line is the switching equipment of the client IDC, and the other end of the special line is the switching equipment of a cloud manufacturer. Customer traffic is commonly carried through a plurality of private lines, and when the private lines fail, convergence and optimization of routing links are required.
The solution for route convergence on gateway devices based on SDN controllers shown in fig. 1 has the following drawbacks:
(1) The convergence path is too long, resulting in a longer convergence time. Gateway device 102 in the cloud network is uniformly managed by the SDN controller, and the following process is required to be performed to enable gateway device 102 to perceive a private line fault: the border router 103 automatically perceives a private line failure; the monitoring server 105 captures a route failure event; the monitoring server 105 reports route withdrawal information to the SDN controller; the SDN controller processes the route withdrawal information and informs gateway device 102 to update the route. That is, the above steps are needed to update the route on the gateway device 102, so that the convergence path is too long, resulting in long convergence time, and many times, the customer cannot accept the convergence time, especially for the core business of banks.
(2) Gateway device 102 needs to support multiple next hops. Gateway device 102 can point to different next hops, i.e., to multiple border routers, for the same route.
Aiming at the problem of time consumption of convergence and the problem of additional function support of gateway equipment caused by overlong convergence paths, the special line communication method, the device and the system provided by the embodiment of the invention can realize rapid convergence of routes after special line faults in a cloud network scene, and the gateway equipment is not required to support a plurality of next hops.
The embodiment of the invention provides a private line communication method, device and system, which can be applied to a communication network introducing intermediate equipment, for example, see a network architecture diagram of a communication network shown in fig. 2, where the communication network may include a VPC server 201, a gateway device 202, an intermediate equipment 203, a border router 204 and a client IDC device 205, where the intermediate equipment 203 passes through the equipment as outgoing traffic, and the next hop of the gateway device 202 points directly to the intermediate equipment 203 instead of directly to the border router 204; the intermediate device 203 and all the border routers 204 start the EVPN (Ethernet Virtual Private Network ) function, so that the routing synchronization can be realized in the cloud network multi-tenant environment; the intermediate device 203 turns on the route reflector function and acts as a central node device synchronizing the routing tables on all the border routers 204.
The EVPN described above is a VPN (Virtual Private Network ) technology for realizing two-layer network (data link layer) interworking. Several types of BGP EVPN route types are added by extending the NLRI (Network Layer Reachability Information ) of BGP (Border Gateway Protocol, border gateway protocol) for advertising MAC address (Media Access Control Address, local area network address) and IP address information of hosts between different sites.
The intermediate device 203 serves as an RR (Route Reflector), all the border routers 204 serve as clients (clients) to establish a neighbor relation with the intermediate device 203, and the intermediate device 203 and the border routers 204 can automatically synchronize all routes under different tenant routing domains in the cloud network. The intermediate device 203 passes (reflects) routing information (paths to specific network addresses) between all of the border routers 204 without the need to establish neighbors between the border routers 204. The neighbor relation may be established mainly through HELLO packet interaction and negotiating various parameters, where the parameters may include a circuit type, a Hold time, a network type, a support protocol, a zone number, a system ID (Identity document, an identification number), a PDU (Protocol Data Unit, a protocol data unit) length, an interface IP address, and the like.
In some possible embodiments, to avoid single point of failure, the intermediate devices 203 may be put on shelf in groups to form a device group, where the device group includes at least one intermediate device, and all the intermediate devices 203 in the device group share an IP address as a VIP address (Virtual IP Address ), as shown in fig. 2, where two intermediate devices 203 share a VIP address: 1.1.1.1. the intermediate device 203 may be a general-purpose switch or a custom gateway device. As shown in fig. 2, communication between the border router 204 and the corresponding customer IDC device 205 may be via EBGP.
After introduction of the intermediate device 203, the overall flow direction of the service message sent by the VPC server 201 is: the service message sent by the VPC server 201 passes through the corresponding gateway device 202, the gateway device 202 sends the service message to the corresponding intermediate device 203, the intermediate device 203 can send the service message to the corresponding border router 204 according to the route information learned from each border router 204, and finally the border router 204 sends the service message to the client IDC device 205.
Under the network architecture of the communication network, the route convergence process after the private line fault is as follows:
When the private line fails, the border router 204 withdraws the failed route, and the intermediate device 203 can automatically synchronize to the route change information due to the EVPN protocol existing between the border router 204 and the intermediate device 203, and when the service message sent by the VPC server 201 reaches the intermediate device 203, the intermediate device 203 can automatically forward the service message to other private lines which normally run due to the failure route withdrawal.
The special line communication method, the device and the system provided by the embodiment of the invention have the following advantages:
(1) By introducing the intermediate device 203, the next hop on the gateway device 202 fixes the VIP address pointing to the intermediate device 203, the convergence process does not need the participation of the gateway device 202, that is, the route on the gateway device 202 does not need to be changed, so that the participation of an SDN controller is not needed, the time-consuming problem caused by the overlong convergence link is avoided, meanwhile, a plurality of intermediate devices 203 share one VIP address, the next hop of the gateway device 202 directly points to the VIP address, and a plurality of next hops do not need to be additionally supported.
(2) The route change control brought by the special line fault is converged at the hardware level, the SDN controller is not needed to participate, and the calculation and route change configuration issuing process of the software level is avoided, so that the stability of the special line communication system is improved.
(3) All the convergence occurs at the hardware level, enabling convergence in the second level. EVPN neighbors are established between the intermediate device 203 and the border router 204, the neighbors can learn routes mutually, and when the route is cancelled due to the special line fault on the border router 204, the route can be automatically transferred to the intermediate device 203, so that the rapid convergence of the route is realized.
The specific embodiments and application scenarios thereof are used to describe the method, the device and the system for private line communication provided by the embodiment of the invention in detail.
The embodiment of the invention provides a private line communication method, as shown in fig. 3, which mainly comprises the following steps S302 to S330:
in step S302, the target gateway device receives a service message sent by the VPC server, where the service message includes a client identifier, and the client is a private line client.
In some embodiments, the service message may be a data flow in a packet form, where the service message may include a client identifier, a first source IP address, and a first destination IP address, where the first source IP address is an IP address of the VPC server, and the first destination IP address is an IP address of the target client.
In step S304, the target gateway device determines the IP address of the intermediate device based on the client identifier in the service message.
The target gateway device is herein referred to as gateway device 202 in fig. 2, and the intermediate device is referred to as one of intermediate devices 203 in fig. 2. In some possible embodiments, the intermediate devices may correspond to a device group, where the device group includes at least one intermediate device, and all the intermediate devices in the device group share one IP address.
The target gateway device locally maintains a third routing table that includes a correspondence between the first destination IP address and the next hop IP address. Therefore, the target gateway device may determine the third routing table based on the client identifier in the service message, and then determine the third next-hop IP address in the third routing table based on the first destination IP address in the service message, where the third next-hop IP address is the IP address of the intermediate device.
In step S306, the target gateway device sends a service message to the intermediate device based on the IP address of the intermediate device.
In step S308, the intermediate device receives the service message sent by the target gateway device.
In step S310, the intermediate device determines the IP address of the first border router based on the client identification in the service message.
The first border router here is one of the border routers 204 in fig. 2. The intermediate device locally maintains a second routing table, where the second routing table includes a correspondence between a first destination IP address and a next hop IP address, so that the intermediate device may determine the second routing table based on the client identifier first, and then determine a second next hop IP address in the second routing table based on the first destination IP address, where the second next hop IP address is an IP address of the first border router.
In some possible embodiments, the second next hop IP address may be determined by: determining a plurality of next hop IP addresses corresponding to the first destination IP address in a second routing table; determining a second next-hop IP address from a plurality of next-hop IP addresses corresponding to the first destination IP address according to a preset rule; wherein the preset rules include a priority-based determination and/or a link-based load status determination.
In one possible implementation, different private lines may have different priorities, so that corresponding different border routers also have different priorities, so that a next-hop IP address corresponding to the border router with the highest priority may be selected from a plurality of next-hop IP addresses corresponding to the first destination IP address as the second next-hop IP address;
in another possible implementation manner, the second next-hop IP address may be determined based on a load balancing manner, for example, a hash algorithm is performed on the first destination IP address by using a preset hash algorithm, so as to obtain a hash value, and the second next-hop IP address is selected from a plurality of next-hop IP addresses corresponding to the first destination IP address based on the hash value. Since the hash computation is random, so is the second next hop IP address chosen each time, thus achieving load balancing.
In addition, the intermediate device may automatically maintain the second routing table based on the routing reflector function, specifically as follows: the intermediate device detects the reachability of the link between the intermediate device and each boundary router in real time, for example, the intermediate device establishes an EVPN neighbor with each boundary router, the intermediate device starts a route reflector function and serves as a central node device, the intermediate device and each boundary router mutually send HELLO packets, and when detecting that the HELLO packets sent by the second boundary router are not received within a preset interval time, the intermediate device determines that the link between the intermediate device and the second boundary router is not reachable; and deleting the path corresponding to the second boundary router in the second routing table when the link between the second boundary router and the second boundary router is not reachable. The intermediate device can thus synchronize the routing tables on all border routers.
In step S312, the intermediate device sends a service message to the first border router based on the IP address of the first border router.
In step S314, the first border router receives the service message sent by the intermediate device.
In step S316, the first border router determines the IP address of the target client based on the client identification in the service message.
The target client is here one of the client IDC devices 205 in fig. 2. The first border router locally maintains a first routing table, where the first routing table includes a correspondence between a first destination IP address and a next-hop IP address, so that the first border router may determine the first routing table based on the client identifier, and then determine, based on the first destination IP address, a first next-hop IP address in the first routing table, where the first next-hop IP address is an IP address of the target client.
In step S318, the first border router sends the service message to the target client based on the IP address of the target client.
In step S320, the first border router receives a response message sent by the target client in response to the service message, where the response message includes the client identifier.
The response message may include a client identifier, a second source IP address, and a second destination IP address, where the second source IP address is an IP address of the target client, and the second destination IP address is an IP address of the VPC server.
In step S322, the first border router determines the IP address of the target gateway device based on the client identification in the response message.
The first routing table locally maintained by the first border router further includes a correspondence between the second destination IP address and the next-hop IP address, so that the first border router may determine the first routing table based on the client identifier, and then determine, based on the second destination IP address, a fourth next-hop IP address in the first routing table, where the fourth next-hop IP address is the IP address of the target gateway device.
In step S324, the first border router sends a response message to the target gateway device based on the IP address of the target gateway device.
In step S326, the target gateway device receives the response message sent by the first border router.
In step S328, the target gateway device determines the IP address of the VPC server based on the client identification in the response message.
The third routing table locally maintained by the target gateway device further includes a correspondence between the second destination IP address and the next-hop IP address, so that the target gateway device may determine the third routing table based on the client identifier first, and then determine a fifth next-hop IP address in the third routing table based on the second destination IP address, where the fifth next-hop IP address is an IP address of the VPC server.
In step S330, the target gateway device sends a response message to the VPC server.
This completes the complete communication process from the VPC server to the target client.
According to the private line communication method provided by the embodiment of the invention, the intermediate equipment is introduced, and the overall flow direction of the service message sent by the VPC server is as follows: the service message sent by the VPC server passes through the target gateway equipment, the target gateway equipment sends the service message to the corresponding intermediate equipment, the intermediate equipment sends the service message to the corresponding first border router, and finally the first border router sends the service message to the target client. Therefore, when the special line fails, the routing convergence can be realized through the middle device, and the routing on the gateway device does not need to be changed, namely, the routing convergence process does not need to be participated by an SDN controller.
The embodiment of the invention also provides a special line communication device, which is applied to the boundary router, and referring to a schematic structural diagram of the special line communication device shown in fig. 4, the device comprises:
a first receiving module 42, configured to receive a service message sent by an intermediate device, where the service message includes a client identifier, the client is a private line client, the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all intermediate devices in the device group share an IP address;
a first determining module 44, configured to determine an IP address of the target client based on the client identifier;
a first sending module 46, configured to send a service message to the target client based on the IP address of the target client.
Further, the service message further includes a first destination IP address, and the border router locally maintains a first routing table, where the first routing table includes a correspondence between the first destination IP address and a next hop IP address; the first determining module 44 specifically is configured to: determining a first routing table based on the customer identification; based on the first destination IP address, a first next-hop IP address is determined in a first routing table, the first next-hop IP address being the IP address of the target client.
Further, the first receiving module 42 is further configured to receive a response message sent by the target client in response to the service message, where the response message includes a client identifier; the first determining module 44 is further configured to determine an IP address of the target gateway device based on the client identifier; the first sending module 46 is further configured to send a response message to the target gateway device based on the IP address of the target gateway device, so that the target gateway device sends the response message to the VPC server.
The embodiment of the invention also provides a private line communication device, which is applied to the above intermediate devices, wherein the intermediate devices correspond to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share an IP address, and referring to a schematic structural diagram of another private line communication device shown in fig. 5, the device comprises:
a second receiving module 52, configured to receive a service message sent by the target gateway device, where the service message includes a client identifier, and the client is a private line client;
a second determining module 54 for determining an IP address of the first border router based on the customer identification;
the second sending module 56 is configured to send a service message to the first border router based on the IP address of the first border router.
Further, the service message further includes a first destination IP address, and the intermediate device locally maintains a second routing table, where the second routing table includes a correspondence between the first destination IP address and a next hop IP address; the second determining module 54 specifically is configured to: determining a second routing table based on the customer identification; and determining a second next-hop IP address in a second routing table based on the first destination IP address, wherein the second next-hop IP address is the IP address of the first border router.
Further, the second determining module 54 is further configured to: determining a plurality of next hop IP addresses corresponding to the first destination IP address in a second routing table; determining a second next-hop IP address from a plurality of next-hop IP addresses corresponding to the first destination IP address according to a preset rule; wherein the preset rules include a priority-based determination and/or a link-based load status determination.
Further, the apparatus further includes a route maintenance module connected to the second determining module 54, where the route maintenance module is configured to: detecting the reachability of links between the router and each boundary router in real time; and deleting the path corresponding to the second boundary router in the second routing table when the link between the second boundary router and the second boundary router is not reachable.
An embodiment of the present invention provides a private line communication device, which is applied to the gateway apparatus described above, and see a schematic structural diagram of another private line communication device shown in fig. 6, where the device includes:
a third receiving module 62, configured to receive a service message sent by the VPC server, where the service message includes a client identifier, and the client is a private line client;
a third determining module 64, configured to determine an IP address of an intermediate device based on the client identifier, where the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all intermediate devices in the device group share one IP address;
a third sending module 66, configured to send a service message to the intermediate device based on the IP address of the intermediate device.
The device provided in this embodiment has the same implementation principle and technical effects as those of the foregoing method embodiment, and for brevity, reference may be made to the corresponding content of the foregoing method embodiment where the device embodiment is not mentioned.
The embodiment of the invention also provides a network device which can be a boundary router, an intermediate device or a gateway device. As shown in fig. 7, a network device 700 provided in an embodiment of the present invention includes a processor 701, a memory 702, and a bus, where the memory 702 stores a computer program that can be run on the processor 701, when the network device 700 runs, the processor 701 communicates with the memory 702 through the bus, and the processor 701 executes the computer program to implement the steps of the above-mentioned private line communication method.
Specifically, the memory 702 and the processor 701 can be general-purpose memories and processors, and are not particularly limited herein, and the dedicated line communication method can be performed when the processor 701 runs a computer program stored in the memory 702.
The network device provided in this embodiment has the same implementation principle and technical effects as those of the foregoing method embodiment, and for a brief description, reference may be made to corresponding contents in the foregoing method embodiment where the network device embodiment is not mentioned.
The embodiment of the present invention further provides a private line communication system, referring to a schematic structural diagram of a private line communication system shown in fig. 8, where the private line communication system includes the above-mentioned border router 204, intermediate device 203 and gateway device 202. When transmitting the service message sent by the VPC server, the next hop of the gateway device 202 is the intermediate device 203, and the next hop of the intermediate device 203 is the border router 204.
According to the private line communication system provided by the embodiment of the invention, the intermediate equipment is introduced, the next hop of the gateway equipment is fixedly directed to the intermediate equipment, when the private line fails, the routing convergence can be realized through the intermediate equipment, the routing on the gateway equipment does not need to be changed, namely, the routing convergence process does not need to be participated by the SDN controller.
The embodiment of the invention also provides a computer readable storage medium, and a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the special line communication method in the previous method embodiment is executed. The computer-readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a RAM, a magnetic disk, or an optical disk, etc., which can store program codes.
Any particular values in all examples shown and described herein are to be construed as merely illustrative and not a limitation, and thus other examples of exemplary embodiments may have different values.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
Claims (15)
1. A private line communication method, applied to a border router, comprising:
receiving a service message sent by an intermediate device, wherein the service message comprises a client identifier, the client is a private line client, the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share an IP address;
determining an IP address of the target client based on the client identification;
and sending the service message to the target client based on the IP address of the target client.
2. The private line communication method according to claim 1, further comprising:
Receiving a response message sent by the target client in response to the service message, wherein the response message comprises a client identifier;
determining an IP address of the target gateway device based on the client identification;
and sending the response message to the target gateway equipment based on the IP address of the target gateway equipment so that the target gateway equipment sends the response message to the VPC server.
3. The private line communication method according to claim 1, wherein the service message further includes a first destination IP address, and a first routing table is maintained locally, and the first routing table includes a correspondence between the first destination IP address and a next hop IP address; the determining the IP address of the target client based on the client identifier includes:
determining a first routing table based on the customer identification;
and determining a first next-hop IP address in the first routing table based on the first destination IP address, wherein the first next-hop IP address is the IP address of the target client.
4. The special line communication method is characterized by being applied to intermediate equipment, wherein the intermediate equipment corresponds to an equipment group, the equipment group comprises at least one intermediate equipment, and all the intermediate equipment in the equipment group share one IP address; the private line communication method comprises the following steps:
Receiving a service message sent by target gateway equipment, wherein the service message comprises a client identifier, and the client is a private line client;
determining an IP address of a first border router based on the customer identification;
and sending the service message to the first boundary router based on the IP address of the first boundary router.
5. The method of claim 4, wherein the traffic message further comprises a first destination IP address, and wherein a second routing table is maintained locally, the second routing table comprising a correspondence of the first destination IP address to a next hop IP address; the determining the IP address of the first border router based on the client identification includes:
determining a second routing table based on the customer identification;
and determining a second next-hop IP address in the second routing table based on the first destination IP address, wherein the second next-hop IP address is the IP address of the first border router.
6. The method of claim 5, wherein determining a second next hop IP address in the second routing table based on the first destination IP address comprises:
determining a plurality of next hop IP addresses corresponding to the first destination IP address in the second routing table;
Determining a second next-hop IP address from a plurality of next-hop IP addresses corresponding to the first destination IP address according to a preset rule; wherein the preset rule comprises a priority-based determination and/or a link-based load state determination.
7. The method as recited in claim 5, further comprising:
detecting the reachability of links between the router and each boundary router in real time;
and deleting a path corresponding to the second boundary router in the second routing table when the link between the second boundary router and the second boundary router is not reachable.
8. A method for dedicated line communication, applied to a gateway device, comprising:
receiving a service message sent by a VPC server, wherein the service message comprises a client identifier, and the client is a private line client;
determining an IP address of an intermediate device based on the client identifier, wherein the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share one IP address;
and sending the service message to the intermediate equipment based on the IP address of the intermediate equipment.
9. A private line communication apparatus, for use in a border router, comprising:
The first receiving module is used for receiving a service message sent by an intermediate device, wherein the service message comprises a client identifier, the client is a private line client, the intermediate device corresponds to a device group, the device group comprises at least one intermediate device, and all the intermediate devices in the device group share one IP address;
a first determining module, configured to determine an IP address of a target client based on the client identifier;
and the first sending module is used for sending the service message to the target client based on the IP address of the target client.
10. The special line communication device is characterized by being applied to intermediate equipment, wherein the intermediate equipment corresponds to an equipment group, the equipment group comprises at least one intermediate equipment, and all the intermediate equipment in the equipment group share one IP address; the private line communication apparatus includes:
the second receiving module is used for receiving the service message sent by the target gateway equipment, wherein the service message comprises a client identifier, and the client is a private line client;
a second determining module, configured to determine an IP address of the first border router based on the client identifier;
and the second sending module is used for sending the service message to the first border router based on the IP address of the first border router.
11. A private line communication apparatus, applied to a gateway device, comprising:
the third receiving module is used for receiving the service message sent by the VPC server, wherein the service message comprises a client identifier, and the client is a private line client;
a third determining module, configured to determine an IP address of an intermediate device based on the client identifier, where the intermediate device corresponds to a device group, the device group includes at least one intermediate device, and all intermediate devices in the device group share one IP address;
and the third sending module is used for sending the service message to the intermediate equipment based on the IP address of the intermediate equipment.
12. A border router comprising a memory, a processor, the memory having stored therein a computer program executable on the processor, wherein the processor implements the method of any of claims 1-3 when the computer program is executed.
13. An intermediate device comprising a memory, a processor, the memory having stored therein a computer program executable on the processor, wherein the processor implements the method of any of claims 4-7 when the computer program is executed.
14. Gateway device comprising a memory, a processor, in which a computer program is stored which is executable on the processor, characterized in that the processor implements the method of claim 8 when executing the computer program.
15. A private line communication system comprising the border router of claim 12, the intermediate device of claim 13, and the gateway device of claim 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111252901.6A CN116055393A (en) | 2021-10-27 | 2021-10-27 | Private line communication method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111252901.6A CN116055393A (en) | 2021-10-27 | 2021-10-27 | Private line communication method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116055393A true CN116055393A (en) | 2023-05-02 |
Family
ID=86131818
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111252901.6A Pending CN116055393A (en) | 2021-10-27 | 2021-10-27 | Private line communication method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116055393A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116760830A (en) * | 2023-08-14 | 2023-09-15 | 腾讯科技（深圳）有限公司 | Method and device for processing routing information, computer readable medium and electronic equipment |
-
2021
- 2021-10-27 CN CN202111252901.6A patent/CN116055393A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116760830A (en) * | 2023-08-14 | 2023-09-15 | 腾讯科技（深圳）有限公司 | Method and device for processing routing information, computer readable medium and electronic equipment |
| CN116760830B (en) * | 2023-08-14 | 2024-03-01 | 腾讯科技（深圳）有限公司 | Method and device for processing routing information, computer readable medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9197583B2 (en) | Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers | |
| US9858163B2 (en) | Dual adjacency between edge devices at a network site | |
| EP1905203B1 (en) | Router and method for protocol process migration | |
| CN107733793B (en) | Forwarding table item maintenance method and device | |
| US8694664B2 (en) | Active-active multi-homing support for overlay transport protocol | |
| EP3399703B1 (en) | Method for implementing load balancing, apparatus, and network system | |
| CN112422307B (en) | Method, equipment and system for EVPN and VPLS coexistence dual-activity | |
| CN106559246B (en) | Cluster implementation method and server | |
| WO2021227863A1 (en) | Disaster recovery method and apparatus for hybrid cloud private line access network | |
| US8667174B2 (en) | Method and system for survival of data plane through a total control plane failure | |
| CN114448877B (en) | Path switching method, device and system | |
| EP3989512A1 (en) | Method for controlling traffic forwarding, device, and system | |
| CN115277305A (en) | Network management method, device, equipment and machine readable storage medium | |
| CN113037883B (en) | Method and device for updating MAC address table entries | |
| EP3429139B1 (en) | Ingress gateway selection for a shortest path bridging network to support inter domain multicast routing | |
| CN116055393A (en) | Private line communication method, device and system | |
| CN113615132A (en) | Fast flooding topology protection | |
| CN108768845B (en) | Multi-homing host routing synchronization method and device | |
| CN113810297B (en) | Multi-network converged train network system and communication method thereof | |
| CN112039765A (en) | Routing information sending method, routing method and device | |
| Tien et al. | A novel ring-based dual paths approach for reducing redundant traffic in HSR networks | |
| Cisco | Configuring Banyan VINES | |
| Cisco | Configuring OSPF | |
| US10938590B2 (en) | Synchronizing multi-homed network elements for multicast traffic | |
| CN108737263B (en) | Data center system and data stream processing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |