CN114513458B

CN114513458B - Communication method and device

Info

Publication number: CN114513458B
Application number: CN202210103544.5A
Authority: CN
Inventors: 许豫飞
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-01-27
Filing date: 2022-01-27
Publication date: 2023-12-08
Anticipated expiration: 2042-01-27
Also published as: CN114513458A

Abstract

The application provides a communication method and a device, wherein the method is applied to UP, the UP internally comprises a plurality of interface boards, and the method comprises the following steps: receiving a service message, wherein the service message comprises a destination IP address; searching a local routing table according to the destination IP address, and determining an output interface for forwarding the service message; according to the output interface, a first interface board identifier is obtained from an interface reachable routing table corresponding to the output interface; judging whether the first interface board mark is recorded in a host reachable route table corresponding to the outgoing interface; and if so, sending the service message to the host computer represented by the target IP address through the first interface board represented by the first interface board identifier.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communications method and apparatus.

Background

At present, in order to solve the problems that the capability of a control plane and a forwarding plane in a traditional broadband remote access server (English: broadband Remote Access Server, BRAS for short) is not matched, resources cannot be shared, new services are not deployed timely, and the like, a forwarding and control separation scheme based on the vBRAS is proposed in the industry.

The scheme of forwarding and control separation (hereinafter referred to as forwarding and control separation for short) refers to completely decoupling an original forwarding plane and a control plane in the BRAS, which are not constrained by each other. In the forwarding and Control separation scheme, the method comprises two roles of a Control Plane (English: control Plane, abbreviated as CP) and a User Plane (English: user Plane, abbreviated as UP), and the two roles jointly realize the BRAS function. Wherein: the CP is responsible for completing control plane functions such as user identity authentication, address allocation, management, etc. The CP is typically served by a virtual broadband remote access server (english: virtual Broadband Remote Access Server, abbreviated: vbas). The UP is responsible for completing forwarding plane functions such as user data traffic forwarding, traffic control and the like. The UP is typically served by a three-layer switch, router, or vbas.

As shown in fig. 1, fig. 1 is a schematic diagram of a conventional control-switching separation networking. In fig. 1, a host is online at UP and accesses the network through a CP. Before user service is deployed, a communication channel, namely a CP-UP channel, is established between the CP and the UP, so that operations such as protocol message interaction, BRAS service configuration, list item issuing and the like can be carried out between the CP and the UP. The channels between the CP and the UP include a management channel, a control channel, and a protocol channel according to the operation of the channels.

And NETCONF connection is used as a management channel between the CP and the UP, so that the functions of inquiring data, issuing configuration and the like from the CP to the UP are realized. And a Control/forwarding separation protocol (English: control-/User-plane Separetion Pretocol, CUSP) channel is used as a Control channel between the CP and the UP to realize the functions of issuing User table items such as PPPoE, IPoE and the like, reporting interface information and the like. And a VXLAN tunnel of a general protocol extension (English: generic Pretocol Extension, GPE for short) type is used as a protocol channel between the CP and the UP to realize DHCP, ARP, PPPoE protocol message interaction.

In the networking shown in fig. 1, the number of online hosts supported by each UP is 100 tens of thousands, but the number of hosts increases due to the rapid development of the internet. The number of the online hosts supported by the existing UP cannot meet the requirement, and the capacity expansion of the number of the online hosts supported by the UP is an urgent need to be solved.

The UP internally includes a plurality of interface boards inserted, after the host accesses the UP, the UP synchronizes user data of the host into each interface board, and each interface board cannot support a large-scale host number (for example, 400 ten thousand) due to limited interface board resources. Of course, by adding an interface board in the UP, the interface board resources can be enlarged, so that the UP supports a larger number of online hosts. However, this approach adds significantly to the cost.

Disclosure of Invention

In view of this, the present application provides a communication method and apparatus for solving the problem of increased cost caused by the fact that the UP supports a larger number of online hosts by adding an interface board inside the UP.

In a first aspect, the present application provides a communication method applied to an UP including a plurality of interface boards therein, the method comprising:

receiving a service message, wherein the service message comprises a destination IP address;

searching a local routing table according to the destination IP address, and determining an output interface for forwarding the service message;

according to the output interface, a first interface board identifier is obtained from an interface reachable routing table corresponding to the output interface;

judging whether the first interface board mark is recorded in a host reachable route table corresponding to the outgoing interface;

and if so, sending the service message to the host computer represented by the target IP address through the first interface board represented by the first interface board identifier.

In a second aspect, the present application provides a communication apparatus, the apparatus being applied to a UP, the UP including a plurality of interface boards therein, the apparatus comprising:

the receiving unit is used for receiving a service message, wherein the service message comprises a destination IP address;

the determining unit is used for searching a local routing table according to the destination IP address and determining an output interface for forwarding the service message;

the obtaining unit is used for obtaining a first interface board identifier from an interface reachable route table corresponding to the output interface according to the output interface;

the judging unit is used for judging whether the first interface board identifier is recorded in a host reachable routing table corresponding to the outgoing interface;

and the sending unit is used for sending the service message to the host computer represented by the target IP address through the first interface board represented by the first interface board identifier if the service message is recorded.

In a third aspect, the application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided by the first aspect of the application.

Therefore, by applying the communication method and the communication device provided by the application, the UP receives the service message, and the service message comprises the destination IP address; according to the destination IP address, UP searches the local routing table and determines the output interface for forwarding the service message; according to the output interface, the UP obtains a first interface board identifier from an interface reachable route table corresponding to the output interface; the UP judges whether the first interface board mark is recorded in a host reachable route table corresponding to the outgoing interface; if so, the UP sends a service message to a host computer represented by the destination IP address through a first interface board represented by the first interface board identifier.

Thus, each outgoing interface is provided with a corresponding interface reachable route table and a host reachable route table, and each interface reachable route table and each host reachable route table comprise a plurality of interface board identifiers. And determining the forwarding interface board for forwarding the service message by searching the interface reachable routing table and the host reachable routing table corresponding to the interface. The method solves the problem that the cost is increased because the UP supports more online hosts by adding an interface board in the UP. The number of UP supporting on-line hosts is improved, the number of the on-line hosts in each interface board can be controlled, and meanwhile, the interface board is not required to be additionally increased, so that the cost is saved.

Drawings

FIG. 1 is a schematic diagram of a conventional control-switching separation network;

FIG. 2 is a flow chart of a communication method according to an embodiment of the present application;

fig. 3 is a block diagram of a communication device according to an embodiment of the present application;

fig. 4 is a hardware structure of a network device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The communication method provided by the embodiment of the application is described in detail below. Referring to fig. 2, fig. 2 is a flowchart of a communication method according to an embodiment of the present application. The method is applied to UP. The communication method provided by the embodiment of the application can comprise the following steps.

Step 210, receiving a service message, where the service message includes a destination IP address.

Specifically, the host has accessed the UP, and the host sends a service message to the UP. The service message includes a destination IP address, which is specifically an IP address of the host.

The UP receives the service message and acquires the destination IP address from the service message.

Further, before this step, the UP will create multiple load balancing groups locally, bind its own interface (specifically, a logical port) with one load balancing group, and generate an interface reachable routing table and a host reachable routing table corresponding to each interface.

It should be noted that, in the embodiment of the present application, the physical port is not bound to the load balancing group, and the physical port direction interface board is determined.

The specific process is as follows: the UP includes a plurality of interfaces, for example, interface a and interface B. A plurality of interface boards, for example, interface board 1, interface board 2, interface board 3, interface board 4, interface board 5, interface board 6, have been inserted into UP.

The UP creates multiple load balancing groups locally, e.g., load balancing group 1, load balancing group 2, etc. The UP divides the plurality of interface boards inserted into the UP into different load balancing groups, so that each load balancing group comprises a first number of interface board identifiers and the first number of interface board identifiers contained in each load balancing group are different.

It should be noted that, the user issues a configuration instruction to the UP, where the configuration instruction includes a load balancing group identifier divided by the user for each interface board. And the UP divides the interface boards into corresponding load balancing groups according to the load balancing group identification.

For example, the load balancing group includes 3 interface board identifiers, namely, identifier 1 of interface board 1, identifier 2 of interface board 2, and identifier 3 of interface board 3. The load balancing group comprises 3 interface board identifiers, namely an identifier 4 of the interface board 4, an identifier 5 of the interface board 5 and an identifier 6 of the interface board 6.

And the UP respectively binds each interface with one load balancing group. For example, UP binds interface A with load balancing group 1 and interface B with load balancing group 2.

It should be noted that, the load balancing group bound with the interface includes at least one interface board, and one interface board included in the at least one interface board is an outgoing direction interface board of the interface.

According to the local routing protocol configuration and the tunnel configuration of each interface binding, the UP generates an interface reachable routing table 1 of an interface A and an interface reachable routing table 2 of an interface B. Each interface reachable routing table includes an interface identification and a second number of interface board identifications.

It should be noted that, the interface is bound to the tunnel, and a plurality of equivalent routes can be included between the source address of the tunnel and the destination address of the opposite end, each route corresponds to a different physical output interface, and the different physical output interfaces are distributed on different interface boards.

For example, the interface reachable route table 1 of the interface a includes an interface identifier 1 of the interface a, an identifier 1 of the interface board 1, and an identifier 2 of the interface board 2; the interface reachable route table 2 of the interface B comprises an interface identification 2 of the interface B and an identification 4 of the interface board 4.

According to the load balancing group 1 of the interface A and the interface reachable routing table 1 of the interface A, UP generates a host reachable routing table 1 of the interface A; according to the load balancing group 2 of the interface B and the interface reachable routing table 2 of the interface B, the UP generates the host reachable routing table 2 of the interface B. Each host reachable routing table includes an interface identification and a third number of interface board identifications.

In an embodiment of the present application, the UP may generate a host reachable routing table for each interface in the following manner.

The specific process is as follows: the UP acquires a first number of interface board identifiers included in a load balancing group of the interface and a second number of interface board identifiers included in an interface reachable routing table of the interface. The UP performs intersection processing on the first number of interface board identifiers and the second number of interface board identifiers, and acquires intersection interface board identifiers. The UP takes the intersection interface board identification as a third number of interface board identifications. The UP takes the interface identifier included in the load balancing group and the interface identifier included in the interface reachable route table as the interface identifier included in the host reachable route table. In this way, the UP generates the host reachable routing table of the interface.

Taking UP to generate the host reachable routing table of interface a as an example for illustration.

For example, the UP obtains the load balancing group 1 of interface a and the interface reachable route table 1 of interface a. The load balancing group 1 comprises 3 interface board identifiers, and the interface reachable route table 1 comprises 2 interface board identifiers. The UP performs intersection processing on the 3 interface board identifiers and the 2 interface board identifiers. In this example, the 3 interface board identifiers included in the load balancing group 1 are respectively an identifier 1 of the interface board 1, an identifier 2 of the interface board 2, and an identifier 3 of the interface board 3; the 2 interface board identifiers included in the interface reachable routing table 1 are identifier 1 of the interface board 1 and identifier 2 of the interface board 2 respectively. The UP acquires 2 intersection interface board identifiers, namely an identifier 1 of the interface board 1 and an identifier 2 of the interface board 2. The UP takes the identification 1 of the interface board 1 and the identification 2 of the interface board 2 as the third number of interface board identifications included in the host reachable routing table. The UP takes the interface identifier 1 of the interface a as the interface identifier included in the host reachable routing table, so the UP generates the host reachable routing table 1 of the interface a, and the host reachable routing table 1 includes the interface identifier 1 of the interface a, the identifier 1 of the interface board 1, and the identifier 2 of the interface board 2.

Similarly, the UP generates a host reachable route table 2 of the interface B, and the host reachable route table 2 includes an interface identifier 2 of the interface B and an identifier 4 of the interface board 4.

After the UP generates the load balancing group, the interface reachable route table and the host reachable route table of each interface, the load balancing group, the interface reachable route table and the host reachable route table of each interface are synchronized to each interface board. Thus, each interface board records the load balancing group, the interface reachable route table and the host reachable route table of each interface.

When a host accesses an UP through a certain interface, the UP creates a session with the host and synchronizes session information of the session to any interface board in a load balancing group corresponding to the interface. Therefore, when any interface board belonging to the load balancing group receives the service message sent by the host subsequently, as the corresponding session information is stored, any interface board belonging to the same load balancing group can process the service message sent by the host.

The specific process is as follows:

taking the example that the UP includes a first interface and the host accesses the UP through the first interface, description will be given.

When a first host accesses the UP through a first interface, the UP creates a first session with the host. It will be appreciated that after the host goes online through the UP, the CP will record the user information of the host and synchronize the user information into the UP. The UP creates a first session with the host according to the user information. According to the interface identification of the first interface, the UP acquires a first load balancing group bound with the first interface, wherein the first load balancing group comprises a fourth number of interface board identifications. The UP synchronizes session information for the first session to the interface board characterized by each of the fourth number of interface board identifications, the session information including an IP address of the first host.

For example, a first host accesses an UP through an interface a, and the UP creates a first session with the first host according to user information of the first host. The UP acquires a load balancing group 1, wherein the load balancing group 1 comprises an identifier 1 of an interface board 1, an identifier 2 of an interface board 2 and an identifier 3 of an interface board 3.UP synchronizes session information of the first session to interface board 1, interface board 2, interface board 3.

It will be appreciated that the session information also includes the MAC address of the first host, the access interface, the access VLAN, the VPN, the user name, the access domain, AAA authorization information, etc.

Step 220, according to the destination IP address, searching a local routing table, and determining an output interface for forwarding the service message.

Specifically, according to the description of step 210, the UP looks UP the local routing table according to the destination IP address, and obtains an interface, for example, interface a, from the local routing table. The output interface A is used for forwarding service messages.

Step 230, according to the output interface, a first interface board identifier is obtained from an interface reachable routing table corresponding to the output interface.

Specifically, after determining the interface a according to the description of step 220, the UP obtains the interface reachable route table 1 corresponding to the interface a from the local according to the interface identifier of the interface a, and obtains an interface board identifier, i.e. the first interface board identifier, from the interface reachable route table 1.

It should be noted that, in the routing table of the reachable interfaces, if the designated outbound interface board is already configured, the UP acquires the interface board identifier of the designated outbound interface board, otherwise, the UP selects to acquire the interface board identifier of the inbound interface board.

The interface reachable route table comprises an interface identifier and at least one interface board identifier. The interface reachable routing table is used for indicating that the service message sent by the interface characterized by the interface identifier can be sent out from any interface board characterized by at least one interface board identifier.

After the UP acquires the first interface board identification, the service message is forwarded to the first interface board represented by the first interface board identification.

It should be noted that, in step 220 and the output interface described in this step is a global VSI port. The global VSI port is a logic port, a mapping relation is formed between the logic port and a physical interface of an interface board, and the interface board is characterized by an interface board identifier included in an interface reachable routing table.

In this step, UP acquires the identifier 1 of the interface board 1 from the interface reachable routing table 1, and takes the identifier 1 of the interface board 1 as the first interface board identifier.

Step 240, determining whether the first interface board identifier is already recorded in the host reachable routing table corresponding to the outbound interface.

Specifically, according to the description of step 230, after the UP acquires the first interface board identifier from the interface reachable routing table, it is determined whether the first interface board identifier is already recorded in the host reachable routing table.

If the first interface board identification is already recorded in the host reachable routing table, the UP performs step 250.

If the first interface board identifier is not recorded in the host reachable routing table, the UP determines that the first interface board represented by the first interface board identifier is a non-forwarding board. The UP again randomly obtains a second interface board identification from the host reachable routing table, the second interface board identification being different from the first interface board identification.

At this time, the UP may issue an instruction to the first interface board, to instruct the first interface board to transmit the service packet to the second interface board. And after receiving the service message, the second interface board sends the service message to the host represented by the destination IP address.

In the embodiment of the application, the UP obtains the interface reachable route table 1 from the local according to the output interface A and obtains the host reachable route table 1 corresponding to the interface A from the local according to the interface identifier of the output interface A. In the host reachable routing table 1, an interface identification and at least one interface board identification are included. Wherein each interface board identified by at least one interface board is operable to actually forward a service message.

In this step, the UP determines whether the identifier 1 of the interface board 1 is already recorded in the host reachable routing table 1, and if so, step 250 is executed.

It will be appreciated that if in step 230 the UP obtains the identifier 3 of the interface board 3 from the interface reachable routing table 1, in this step the UP determines that the identifier 3 of the interface board 3 is not recorded in the host reachable routing table 1, and at this time the UP determines that the interface board 3 is a non-forwarding board. The UP again randomly retrieves an interface board identification from the host reachable routing table, e.g. the UP retrieves identification 2 of interface board 2.UP instructs interface board 3 to transmit traffic messages to interface board 2. After receiving the service message, the interface board 2 sends the service message to the host represented by the destination IP address.

Step 250, if the service message is recorded, the service message is sent to the host computer represented by the destination IP address through the first interface board represented by the first interface board identifier.

Specifically, according to the description of step 240, if the UP determines that the first interface board identifier is already recorded in the host reachable routing table, the UP sends a service packet to the host represented by the destination IP address through the first interface board represented by the first interface board identifier.

In this step, the UP determines that the identifier 1 of the interface board 1 is already recorded in the host reachable routing table 1, and the UP sends a service packet to the host characterized by the destination IP address through the interface board 1.

Based on the same inventive concept, the embodiment of the application also provides a communication device corresponding to the communication method. Referring to fig. 3, fig. 3 is a block diagram of a communication device according to an embodiment of the present application. The apparatus is applied to UP, and the apparatus includes:

a receiving unit 310, configured to receive a service packet, where the service packet includes a destination IP address;

a determining unit 320, configured to find a local routing table according to the destination IP address, and determine an outbound interface for forwarding the service packet;

an obtaining unit 330, configured to obtain, according to the output interface, a first interface board identifier from an interface reachable routing table corresponding to the output interface;

a determining unit 340, configured to determine whether the first interface board identifier is already recorded in a host reachable routing table corresponding to the outgoing interface;

and the sending unit 350 is configured to send the service packet to the host represented by the destination IP address through the first interface board represented by the first interface board identifier if the service packet is recorded.

Optionally, the obtaining unit 330 is further configured to, if not recorded, randomly obtain a second interface board identifier from the host reachable routing table, where the second interface board identifier is different from the first interface board identifier;

the sending unit 350 is further configured to send the service packet to the host represented by the destination IP address through the second interface board represented by the second interface board identifier.

Optionally, a plurality of interfaces are included in the UP;

the apparatus further comprises:

a creating unit (not shown in the figure) configured to create a plurality of load balancing groups, where each load balancing group includes a first number of interface board identifiers, and the first number of interface board identifiers included in each load balancing group is different;

a binding unit (not shown in the figure) for binding each interface with a load balancing group respectively;

a generating unit (not shown in the figure) configured to generate, according to a local routing protocol configuration and a tunnel configuration bound by each interface, an interface reachable routing table of each interface, where the interface reachable routing table includes an interface identifier and a second number of interface board identifiers, where the interface reachable routing table is configured to indicate that a service packet sent by an interface represented by the interface identifier may be sent from any interface board represented by the second number of interface board identifiers;

the generating unit (not shown in the figure) is further configured to generate a host reachable routing table of each interface according to the load balancing group of each interface and the interface reachable routing table of each interface, where the host reachable routing table includes an interface identifier and a third number of interface board identifiers;

and a synchronization unit (not shown in the figure) for synchronizing the load balancing group, the interface reachable routing table and the host reachable routing table of each interface to each interface board, so that each interface board records the load balancing group, the interface reachable routing table and the host reachable routing table of each interface.

Optionally, the generating unit (not shown in the figure) is specifically configured to obtain an intersection interface board identifier between the first number of interface board identifiers and the second number of interface board identifiers;

taking the intersection interface board identification as the third number of interface board identifications;

and taking the interface identifier included in the load balancing group and the interface identifier included in the interface reachable route table as the interface identifier included in the host reachable route table.

Optionally, the UP includes a first interface;

the creation unit (not shown in the figure) is further configured to create a first session with a first host when the first host accesses the UP through the first interface;

the obtaining unit 330 is further configured to obtain a first load balancing group bound to the first interface, where the first load balancing group includes a fourth number of interface board identifiers;

the synchronization unit (not shown in the figure) is further configured to synchronize session information of the first session to the interface board represented by each of the fourth number of interface board identifiers, where the session information includes an IP address of the first host.

Therefore, through the communication device provided by the application, the UP receives the service message, wherein the service message comprises the destination IP address; according to the destination IP address, UP searches the local routing table and determines the output interface for forwarding the service message; according to the output interface, the UP obtains a first interface board identifier from an interface reachable route table corresponding to the output interface; the UP judges whether the first interface board mark is recorded in a host reachable route table corresponding to the outgoing interface; if so, the UP sends a service message to a host computer represented by the destination IP address through a first interface board represented by the first interface board identifier.

Based on the same inventive concept, the embodiment of the present application also provides a network device, as shown in fig. 4, including a processor 410, a transceiver 420, and a machine-readable storage medium 430, where the machine-readable storage medium 430 stores machine executable instructions capable of being executed by the processor 410, and the processor 410 is caused to perform the communication method provided by the embodiment of the present application by the machine executable instructions. The communication device shown in fig. 3 may be implemented by using a hardware structure of a network device as shown in fig. 4.

The computer readable storage medium 430 may include a random access Memory (in english: random Access Memory, abbreviated as RAM) or a nonvolatile Memory (in english: non-volatile Memory, abbreviated as NVM), such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 430 may also be at least one storage device located remotely from the aforementioned processor 510.

The processor 410 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (English: digital Signal Processor; DSP; for short), an application specific integrated circuit (English: application Specific Integrated Circuit; ASIC; for short), a Field programmable gate array (English: field-Programmable Gate Array; FPGA; for short), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In an embodiment of the present application, processor 410 is enabled to implement the processor 410 itself and invoke transceiver 420 to perform the communication method described in the previous embodiment of the present application by reading machine-executable instructions stored in machine-readable storage medium 430.

Additionally, embodiments of the present application provide a machine-readable storage medium 430, the machine-readable storage medium 430 storing machine-executable instructions that, when invoked and executed by the processor 410, cause the processor 410 itself and the invoking transceiver 420 to perform the communication methods described in the foregoing embodiments of the present application.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present application without undue burden.

For the communication device and the machine-readable storage medium embodiments, since the method content involved is substantially similar to the method embodiments described above, the description is relatively simple, and reference will only be made to part of the description of the method embodiments.

The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.

Claims

1. A method of communication, the method being applied to an UP, the UP including a plurality of interface boards therein, the method comprising:

if so, sending the service message to a host computer represented by the target IP address through a first interface board represented by the first interface board identifier;

the UP comprises a plurality of interfaces;

before receiving the service message, the method further comprises:

creating a plurality of load balancing groups, wherein each load balancing group comprises a first number of interface board identifiers, and the first number of interface board identifiers in each load balancing group are different;

binding each interface with a load balancing group respectively;

generating an interface reachable routing table of each interface according to a local routing protocol configuration and a tunnel configuration bound by each interface, wherein the interface reachable routing table comprises an interface identifier and a second number of interface board identifiers, and the interface reachable routing table is used for indicating that a service message sent by an interface represented by the interface identifier can be sent from any interface board represented by the second number of interface board identifiers;

generating a host reachable route table of each interface according to the load balancing group of each interface and the interface reachable route table of each interface, wherein the host reachable route table comprises interface identifiers and a third number of interface board identifiers;

synchronizing the load balancing group, the interface reachable routing table and the host reachable routing table of each interface to each interface board, so that each interface board records the load balancing group, the interface reachable routing table and the host reachable routing table of each interface;

the generating a host reachable routing table of each interface according to the load balancing group of each interface and the interface reachable routing table of each interface specifically comprises the following steps:

acquiring intersection interface board identifiers between the first number of interface board identifiers and the second number of interface board identifiers;

2. The method according to claim 1, wherein the method further comprises:

if not, randomly acquiring a second interface board identifier from the host reachable routing table, wherein the second interface board identifier is different from the first interface board identifier;

and sending the service message to the host computer represented by the target IP address through the second interface board represented by the second interface board identifier.

3. The method of claim 1, wherein the UP comprises a first interface;

before receiving the service message, the method further comprises:

creating a first session with a first host when the first host accesses the UP through the first interface;

acquiring a first load balancing group bound with the first interface, wherein the first load balancing group comprises a fourth number of interface board identifiers;

synchronizing session information for the first session to interface boards characterized by each of the fourth number of interface board identifications, the session information including an IP address of the first host.

4. A communication device, the device being applied to an UP, the UP including a plurality of interface boards therein, the device comprising:

the sending unit is used for sending the service message to the host computer represented by the target IP address through the first interface board represented by the first interface board identifier if the service message is recorded;

the UP comprises a plurality of interfaces;

the apparatus further comprises:

the system comprises a creating unit, a load balancing unit and a processing unit, wherein the creating unit is used for creating a plurality of load balancing groups, each load balancing group comprises a first number of interface board identifiers, and the first number of interface board identifiers in each load balancing group are different;

the binding unit is used for binding each interface with one load balancing group respectively;

the generating unit is used for generating an interface reachable route table of each interface according to the local routing protocol configuration and the tunnel configuration bound by each interface, wherein the interface reachable route table comprises an interface identifier and a second number of interface board identifiers, and the interface reachable route table is used for indicating that a service message sent by an interface represented by the interface identifier can be sent from any interface board represented by the second number of interface board identifiers;

the generating unit is further configured to generate a host reachable routing table of each interface according to the load balancing group of each interface and the interface reachable routing table of each interface, where the host reachable routing table includes an interface identifier and a third number of interface board identifiers;

the synchronous unit is used for synchronizing the load balancing group, the interface reachable routing table and the host reachable routing table of each interface to each interface board so that each interface board records the load balancing group, the interface reachable routing table and the host reachable routing table of each interface;

the generating unit is specifically configured to obtain intersection interface board identifiers between the first number of interface board identifiers and the second number of interface board identifiers;

5. The apparatus of claim 4, wherein the obtaining unit is further configured to randomly obtain a second interface board identification from the host reachable routing table if not recorded, the second interface board identification being different from the first interface board identification;

the sending unit is further configured to send, through the second interface board represented by the second interface board identifier, the service packet to the host represented by the destination IP address.

6. The apparatus of claim 4, wherein the UP comprises a first interface;

the creation unit is further configured to create a first session with a first host when the first host accesses the UP through the first interface;

the obtaining unit is further configured to obtain a first load balancing group bound to the first interface, where the first load balancing group includes a fourth number of interface board identifiers;

the synchronization unit is further configured to synchronize session information of the first session to an interface board represented by each interface board identifier of the fourth number of interface board identifiers, where the session information includes an IP address of the first host.