CN101674221A - Static routing generation method, method and device for implementing terminal routing - Google Patents

Abstract

The invention discloses a method for generating a static route, a method and a device for realizing a terminal route. By sending a routing policy to a terminal by a network element device or a DHCP server on the network side, the terminal generates a corresponding static route according to the routing policy issued by the network element device or the DHCP server. Routing and storing; the terminal matches the stored static route according to the attribute information of the data packet to be sent, determines a matching route, and uses the determined matching route to send the data packet. By adopting the solution of the invention, it is not necessary for the user to obtain various routing configuration parameters to manually configure the static routing, which can ensure that data packets pass through multiple network connections at the same time, and realize multi-connection of terminals.

Description

Static route generation method, terminal route realization method and device

technical field

The present invention relates to the communication field, and in particular to a method for generating a static route when a terminal is connected to multiple networks, a corresponding terminal route realization method, and a terminal and a network side device.

Background technique

With the rapid development of the Internet, the types of networks are constantly enriched, including Ethernet, GPRS network, LTE network, VPN, WiFi, etc. Each network has its own characteristics, such as Ethernet has high-speed characteristics, while GPRS network covers a wide area, and VPN has high security. Users access the corresponding network in order to obtain certain network characteristics. When users need to obtain several network characteristics at the same time, or a single network cannot meet the diverse needs of users, the demand for multi-connection of terminals arises. That is to say, a terminal is connected to multiple networks at the same time, and the most suitable network can be found for different application data packets, so that the terminal can work in multiple networks at the same time.

The rapid development of terminals makes the requirement of multi-connection guaranteed by physical hardware. At present, notebook computers on the market basically have built-in wireless network cards and Ethernet cards at the same time, and have 3G data card slots at the same time, and these network interfaces can all work at the same time. Smartphones can connect to mobile networks of multiple standards and support WiFi connections.

However, in the case of satisfying user requirements and terminal hardware guarantees, the terminal routing mechanism in the prior art ultimately limits the multi-connection of the terminal. Since the terminal routing uses the default gateway mechanism, in the case of multiple connections, the operating system will select a default network interface according to certain rules, so that all network traffic enters and exits through this default interface, which in fact causes The terminal multi-connection fails, so the purpose of the terminal multi-connection cannot be achieved, and the simultaneous use of the terminal for multiple network connections cannot be realized.

In the prior art, a method for ensuring that multiple network interfaces of a terminal have traffic at the same time is to configure a static route in a host routing table. The specific implementation method is that the user manually configures static routing entries through the command line, including inputting the destination IP, gateway, and metric value, etc., so as to ensure that the specified network interface for the specific destination IP address is routed, and other routes are still passed through The default network interface is completed, ensuring that multiple interfaces have traffic at the same time. However, this method is basically inoperable for users, because it is very difficult for users to obtain various routing configuration parameters.

The Windows Vista operating system can maintain multiple host connections under certain circumstances, that is, when the application communicates on the network, if the default interface is changed, the application that has been started will continue to use the old interface for communication, and the newly launched application will use the newly replaced default interface. interface. In this case, the old interface and the new default interface have traffic at the same time, achieving terminal multi-connection. However, this is a multi-connection in a passive situation. When the user actively needs to specify different networks for different applications, this method cannot function.

To sum up, in the prior art, since the terminal routing follows the default gateway mechanism, that is, no matter how many network interfaces the terminal has physically connected to different networks, the data packet routing of the terminal is only sent and received through a default interface. In this way, even if the terminal is connected to multiple networks, in fact all network traffic is sent or received from one interface, which cannot achieve the effect of multiple connections of the terminal.

Contents of the invention

Embodiments of the present invention provide a method for generating a static route, a corresponding terminal and a network element device, so that the terminal generates a corresponding static route according to the routing policy issued by the network element device on the network side, and solves the problem of manually configuring the static route by the user. operability issues.

The embodiment of the present invention also provides a method for generating a static route, a corresponding terminal and a DHCP server, so that the terminal uses the extended DHCP message to issue a routing policy through the DHCP server, and generates a corresponding static route, which solves the problem that the user manually configures the static route. operability issues.

The embodiment of the present invention also provides a method for implementing terminal routing, which sends data packets through the terminal matching the static route to realize multi-connection of the terminal.

A method for generating a static route provided by an embodiment of the present invention includes:

After the terminal accesses the network, it initiates a routing policy acquisition request to the network side;

Receive the routing policy sent by the network side;

According to the received routing policy, the corresponding static route is generated and stored.

An embodiment of the present invention provides a method for implementing terminal routing, including:

The terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route;

sending the data packet using the determined matching route;

Wherein, the static route is generated using the above static route generation method.

The embodiment of the present invention also provides a terminal, including:

a routing policy acquisition unit, configured to initiate a routing policy acquisition request to the network side, and receive a routing policy sent by the network side;

The static route generation storage unit is configured to generate and store a corresponding static route according to the received routing policy.

An embodiment of the present invention also provides a network element device, including:

a storage unit for storing routing policies;

a receiving unit, configured to receive a routing policy acquisition request initiated by the terminal;

a sending unit, configured to send the routing policy stored in the storage unit to the terminal.

The embodiment of the present invention further provides a method for generating a static route, including:

After the terminal accesses the network, it requests IP configuration from the DHCP server on the network side;

Receiving the DHCP message sent by the DHCP server, the DHCP message includes a routing policy;

Obtain the routing policy included in the DHCP message, generate and store a corresponding static route.

According to the above method for generating a static route using a DHCP message, an embodiment of the present invention provides a corresponding method for implementing terminal routing, including:

The terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route;

The data packet is sent using the determined matching route.

According to the above method for generating a static route using a DHCP message, an embodiment of the present invention provides a terminal, including:

An IP configuration request unit, configured to request an IP configuration from a DHCP server on the network side, and receive a DHCP message sent by the DHCP server, wherein the DHCP message includes a routing strategy;

The static route generation storage unit is used to obtain the routing policy included in the DHCP message, generate and store a corresponding static route.

According to the above-mentioned method for generating a static route using a DHCP message, the embodiment of the present invention provides a DHCP server, including:

a storage unit for storing routing policies;

a receiving unit, configured to receive an IP configuration acquisition request sent by the terminal;

a generating unit, configured to generate a DHCP message, and the DHCP message includes the routing policy stored in the storage unit;

a sending unit, configured to send the DHCP message generated by the generating unit to a terminal.

In the present invention, the routing policy is delivered to the terminal by the network element device or DHCP server on the network side, and the terminal only needs to generate a corresponding static route according to the routing policy issued by the network element device or the DHCP server, without requiring the user to obtain various routing configuration parameters to manually configure static routes. For the terminal, there is no need to maintain the routing algorithm on the terminal, which saves computing resources; for the user, the entire routing strategy does not require human participation, which is simple and easy to implement.

After the terminal generates a static route, it can match the static route according to the attribute information of the data packet to be sent (such as the destination address of the data packet, the service type identifier, etc.), which can ensure that data packets pass through multiple network connections at the same time, achieving the purpose of multiple connections.

Description of drawings

FIG. 1 is a flow chart of a method for generating a static route provided by Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a method for implementing terminal routing provided by Embodiment 2 of the present invention;

FIG. 3 is a schematic structural diagram of a terminal provided by Embodiment 3 of the present invention;

FIG. 4 is a schematic structural diagram of a network element device provided in Embodiment 4 of the present invention;

FIG. 5 is a flowchart of a method for generating a static route according to Embodiment 5 of the present invention;

6 is a schematic diagram of a specific signaling interaction process between the terminal and the DHCP server in Embodiment 5 of the present invention;

FIG. 7 is a schematic structural diagram of a terminal provided by Embodiment 7 of the present invention;

FIG. 8 is a schematic structural diagram of a DHCP server provided by Embodiment 8 of the present invention.

Detailed ways

The embodiment of the present invention provides a static route generation method, a corresponding terminal and a network element device or a DHCP server, so that the terminal generates a corresponding static route according to the routing policy issued by the network side, and solves the problem that the manual configuration of the static route by the user is not operable. sex issue. And when the terminal needs to send a data packet, it can match the generated static route according to the attribute information of the data packet to be sent, and send the data packet through the matched static route, so as to realize multiple connections of the terminal.

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

Embodiment one:

Embodiment 1 provides a method for generating a static route. The network side delivers a routing policy to the terminal, and the terminal generates and stores a static route according to the routing policy delivered by the network side.

Referring to Fig. 1, it is a flow chart of a method for generating a static route provided by Embodiment 1 of the present invention, which specifically includes:

Step S101, the terminal initiates a routing policy acquisition request to the network side after accessing the network;

Step S102, the terminal receives the routing policy sent by the network side;

Step S103, the terminal generates and stores a corresponding static route according to the received routing policy.

Among them, the routing policy can specifically include, for example:

Destination address/subnet mask and gateway address; or include service type identification and gateway address; or include destination address/subnet mask, service type identification and gateway address, etc.

When the routing policy issued by the network side contains the destination address/subnet mask and gateway address, in step S103, according to the received destination address/subnet mask and gateway address, a route containing the destination address/subnet mask is generated. A static route with code and gateway address, and add it to the terminal routing table;

When the routing policy issued by the network side contains the service type identifier and gateway address, in step S103, according to the received service type identifier and gateway address, a static route containing the service type identifier and gateway address is generated and added to In the terminal routing table;

When the routing policy sent by the network side contains the destination address/subnet mask, service type identifier and gateway address, in step S103, according to the received destination address/subnet mask, service type identifier and gateway address, generate A static route including the destination address/subnet mask, service type identifier and gateway address is added to the terminal routing table.

After the terminal leaves the network, the terminal automatically deletes the locally stored static route generated according to the routing policy sent by the corresponding network side.

According to the first embodiment of the present invention, the terminal only needs to generate the corresponding static route according to the routing policy issued by the network side, and the user does not need to obtain various routing configuration parameters to manually configure the static route, which solves the problem that the user manually configures the static route. operational issues.

Embodiment two:

Embodiment 2 provides a method for implementing terminal routing, in which the terminal selects a locally stored static route to send a data packet.

Referring to FIG. 2, it is a flow chart of a method for implementing terminal routing provided by Embodiment 2 of the present invention, which specifically includes:

Step S201, the terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route;

Step S202, the terminal sends the data packet using the determined matching route;

Wherein, the static route is generated using the method in the first embodiment above.

According to the method provided in Embodiment 2 of the present invention, when no matching route is determined, a default route is used to send the data packet.

As mentioned above, if the static route includes the destination address/subnet mask and gateway address, in step S201, it is necessary to determine whether the destination address of the data packet to be sent belongs to the destination address/subnet mask included in the static route, if , determine the corresponding static route as the matching route;

As mentioned above, if the static route includes a service type identifier and a gateway address, in step S201, it is necessary to judge whether the service type identifier of the data packet to be sent is the same as the service type identifier contained in the static route, and if so, determine the corresponding static route as match route;

As mentioned above, if the static route includes the destination address/subnet mask, service type identifier and gateway address, in step S201, it is necessary to determine whether the destination address of the data packet to be sent belongs to the destination address/subnet mask included in the static route. In the code, if so, determine the corresponding static route as the first matching route; and judge whether the service type identifier of the data packet to be sent is the same as the service type identifier contained in the static route, and if so, determine the corresponding static route as the second matching route ; When the first matching route and the second matching route are the same static route, determine the static route as the final matching route; otherwise, determine the first matching route as the final matching route.

According to the above-mentioned method of Embodiment 2 of the present invention, and when the terminal needs to send a data packet, it can match the generated static route according to the attribute information of the data packet to be sent (such as the destination address of the data packet, the service type identifier, etc.), by matching out Static routes to send data packets; since the destination addresses or service types of data packets of different applications may be different, the matching routes obtained are also different, so that the terminal can use multiple routes to send data packets to achieve multiple terminal connections.

Embodiment three:

Embodiment 3 provides a terminal capable of obtaining a routing policy from a network side, generating and storing a static route, and selecting the stored static route to send a data packet.

Referring to FIG. 3 , it is a schematic diagram of a terminal structure provided by Embodiment 3 of the present invention, which specifically includes:

A routing policy acquisition unit 301, configured to initiate a routing policy acquisition request to the network side, and receive a routing policy sent by the network side;

The static route generation and storage unit 302 is configured to generate and store a corresponding static route according to the received routing policy.

The terminal provided in Embodiment 3 of the present invention further includes:

A route determining unit 303, configured to match the stored static route according to the attribute information of the data packet to be sent, and determine a matching route;

The data sending unit 304 is configured to use the determined matching route to send the data packet.

With the terminal provided in Embodiment 3 of the present invention, it is only necessary to generate corresponding static routes according to the routing policies issued by the network side, and users do not need to obtain various routing configuration parameters to manually configure static routes, which solves the problem of users manually configuring static routes. There is a problem of operability; and when the terminal needs to send a data packet, it can match the generated static route according to the attribute information of the data packet to be sent, and send the data packet through the matched static route to realize multiple connections of the terminal.

Embodiment four:

Embodiment 4 provides a network element device to deliver routing policies to terminals.

Referring to Fig. 4, it is a schematic structural diagram of a network element device provided in Embodiment 4 of the present invention, specifically including:

a storage unit 401, configured to store routing policies;

a receiving unit 402, configured to receive a routing policy acquisition request initiated by a terminal;

The sending unit 403 is configured to send the routing policy stored in the storage unit 401 to the terminal.

Also includes:

The configuration unit 404 is configured to configure or modify the routing policy stored in the storage unit 401 .

Using the network element device provided in Embodiment 4 of the present invention, the routing policy is preset on the network side and stored in the network element device. After receiving the request from the terminal, the set routing policy is sent to the terminal; not only avoiding the need to maintain routes at the terminal The algorithm saves the computing resources of the terminal, and the operator can easily configure or update the routing policy stored in the network element device, and flexibly realize multiple connections of the terminal.

Based on the same inventive concept, the present invention also provides a static route generation method, a terminal route realization method and a corresponding terminal and DHCP server realized by extending the Dynamic Host Configuration Protocol (DHCP).

Embodiment five:

Embodiment 5 provides a method for generating a static route. When a terminal requests IP configuration from a DHCP server after accessing the network, the DHCP server includes a routing policy in the DHCP response message returned to the terminal, and the terminal then uses the received routing policy to Generate and store static routes.

Referring to FIG. 5 , it is a flow chart of a method for generating a static route according to Embodiment 5 of the present invention, which specifically includes:

Step S501, after the terminal accesses the network, it requests IP configuration from the DHCP server on the network side;

Step S502, the terminal receives the DHCP message sent by the DHCP server, and the returned DHCP message includes a routing policy;

Step S503, the terminal obtains the routing policy included in the DHCP message, generates and stores a corresponding static route.

After the terminal leaves the network, the locally stored static route generated according to the routing policy sent by the DHCP server in the corresponding network is deleted.

In the method of Embodiment 5, the specific signaling interaction process between the terminal and the DHCP server is shown in Figure 6, including:

1. After the terminal accesses the network, it sends a discovery (Discovery) broadcast message to the DHCP server on the network side to determine the locally available DHCP server;

2. The DHCP server on the network side sends an offer (Offer) message in a DHCP message format to the terminal, carrying the IP configuration information of the terminal and the routing policy set; wherein, the IP configuration information of the terminal includes an IP address, a gateway address, a domain name server (DNS) ), etc., routing policies are carried through extended DHCP options.

3. After receiving the Offer messages sent by multiple DHCP servers on the network side, the terminal selects a DHCP server, and sends a selection (Request) broadcast message to all DHCP servers to confirm the selection.

4. The selected DHCP server returns an acknowledgment (Acknowledge) message in the DHCP message format to the terminal, carrying the terminal's IP configuration information and the routing strategy set; wherein the IP configuration information includes IP address, gateway address, domain name server ( DNS), etc., routing policies are carried through extended DHCP options.

The following describes how to extend the DHCP option carrying routing policy:

The following table 1 is the message format of DHCP in the prior art:

Table 1:

The specific meanings of each field in Table 1 are:

OP(1): Indicates message op code/message type 1=BOOTREQUEST, 2=BOOTREPLY, length is 1 byte (byte);

Htype(1): Indicates the hardware address type, with a length of 1 byte (byte);

Hlen(1): Indicates the hardware address length, the length is 1 byte (byte);

Hops(1): Set to zero, it can be used by the forwarding agent when it is started by the forwarding agent, and the length is 1 byte (byte);

Transaction ID (4): Operation ID, which is a random number, used for synchronization messages and message responses between the terminal and the server, with a length of 4 bytes (byte);

Seconds(2): The time specified by the user, which is the time after the start of address acquisition and update, with a length of 2 bytes (byte);

Flags(2): flag bit, the length is 2 bytes (byte);

Ciaddr(4): user IP address, this field is only used when the user is in BOUND, RENEW or REBINDING state and can respond to ARP request, the length is 4 bytes (byte);

Yiaddr(4): user IP address, the length is 4 bytes (byte);

Siaddr(4): The IP address used in the bootstrap process, the length is 4 bytes (byte);

Giaddr(4): Forwarding proxy IP address, the length is 4 bytes (byte);

Chaddr(16): customer hardware address, length is 16 bytes (byte);

Sname(64): optional server host name, length is 64 bytes (byte);

File(128): start file name, length is 128 bytes (byte);

Options(variable): An optional parameter field with variable length.

It can be seen from the fields of the DHCP message format in Table 1 that, among them, Options (variable) is an optional parameter field, and its length is variable. The embodiment of the present invention extends this optional field to carry the routing policy set in the DHCP server. For example, the extension field is: Option N; the routing policy is carried through the OptionN field.

The specific routing strategy can include:

Destination address/subnet mask and gateway address; or include service type identification and gateway address; or include destination address/subnet mask, service type identification and gateway address, etc.

Taking the routing policy including destination address/subnet mask, service type identifier and gateway address as an example, the specific field structure of the extension field Option N is as follows:

Serial number N (1byte) Length M(1byte) Destination address 1 (4byte) Subnet mask 1 (1byte) Business type 1 (1byte) Gateway address 1 (4byte) Destination address 2 (4byte) Subnet mask 2 (1byte) Business type 2 (1byte) Gateway address 2 (4byte) ...

The above-mentioned field structure is only an example, and the present invention does not limit the specific structural form of the field structure and the specific length of each field.

In the above step S503, the terminal obtains the routing policy contained in the DHCP message, generates and stores the corresponding static route, and the specific implementation process is the same as that of the first embodiment, and will not be repeated.

According to the fifth embodiment of the present invention, the terminal only needs to generate the corresponding static route according to the routing policy issued by the DHCP server on the network side, and does not need the user to obtain various routing configuration parameters to manually configure the static route. Routing does not have operational issues.

Embodiment six:

Embodiment 6 is similar to Embodiment 2 above. When the terminal has a data packet to be sent, the terminal matches the static route stored in the local routing table according to the attribute information of the data packet to be sent, and determines a matching route; and uses the determined Outbound matching routes send packets.

The difference from the second embodiment is that the static route in the sixth embodiment is generated by the method described in the fifth embodiment.

Similarly, when the terminal does not determine a matching route in the locally stored static routes, the default route is used to send the data packet.

Embodiment seven:

According to the methods provided in the above-mentioned fifth and sixth embodiments, the present invention also provides a terminal with corresponding functions, the structural diagram of which is shown in FIG. 7 , including:

The IP configuration request unit 701 is configured to request an IP configuration from a DHCP server on the network side, and receive a DHCP message sent by the DHCP server, in which the DHCP message includes IP configuration information and a routing policy;

The static route generation and storage unit 702 is configured to obtain the routing policy included in the DHCP message, generate and store a corresponding static route.

Also includes:

The route determination unit 703 is configured to match the stored static route according to the attribute information of the data packet to be sent, and determine a matching route;

A data sending unit 704, configured to use the determined matching route to send the data packet.

With the terminal provided in Embodiment 7 of the present invention, it is only necessary to generate corresponding static routes according to the routing policy issued by the DHCP server on the network side, and users are not required to obtain various routing configuration parameters to manually configure static routes, which solves the problem of manual configuration of static routes by users There is no operability problem; and when the terminal needs to send a data packet, it can match the generated static route according to the attribute information of the data packet to be sent, and send the data packet through the matched static route to realize multiple connections of the terminal.

Embodiment eight:

Corresponding to the terminal provided in Embodiment 7, Embodiment 8 provides a DHCP server for sending a routing policy to the terminal. Its structural diagram is shown in FIG. 8 , including:

a storage unit 801, configured to store routing policies;

A receiving unit 802, configured to receive an IP configuration acquisition request sent by the terminal;

A generating unit 803, configured to generate a DHCP message, including the routing strategy stored in the storage unit 801 in the generated DHCP message;

The sending unit 804 is configured to send the DHCP message generated by the generating unit 803 to the terminal.

In a preferred solution, it also includes:

The configuration unit 805 is configured to configure or modify the routing policy stored in the storage unit 801 .

Adopt the DHCP server provided by the eighth embodiment of the present invention to store the preset routing policy, and after receiving the IP configuration request of the terminal, send the set routing policy to the terminal through the response message returned to the terminal; not only avoiding the need to maintain the route at the terminal The algorithm saves the computing resources of the terminal, and the operator can easily configure or update the routing policy stored in the DHCP server to flexibly realize multiple connections of the terminal.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (21)

1. A method for generating a static route, comprising: After the terminal accesses the network, it initiates a routing policy acquisition request to the network side; Receive the routing policy sent by the network side; According to the received routing policy, the corresponding static route is generated and stored. 2. The method according to claim 1, wherein the routing policy comprises: Destination address/subnet mask and gateway address; or business type identification and gateway address; Or destination address/subnet mask, service type identifier and gateway address; According to the received routing policy, generate and store corresponding static routes, specifically including: Generate a static route containing the destination address/subnet mask and gateway address according to the received destination address/subnet mask and gateway address, and add it to the terminal routing table; or Generate a static route containing the service type identifier and gateway address according to the received service type identifier and gateway address, and add it to the terminal routing table; or According to the received destination address/subnet mask, service type identifier and gateway address, generate a static route including the destination address/subnet mask, service type identifier and gateway address, and add it to the terminal routing table. 3. The method according to claim 1 or 2, further comprising: After the terminal leaves the network, the locally stored static route generated according to the routing policy sent by the corresponding network side is deleted. 4. A terminal routing implementation method, characterized in that, comprising: The terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route; sending the data packet using the determined matching route; Wherein, the static route is generated by any method described in claims 1-3. 5. The method according to claim 4, wherein if the static route includes a destination address/subnet mask and a gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent , determining a matching route, specifically including: judging whether the destination address of the data packet to be sent belongs to the destination address/subnet mask included in the static route, and if so, determining the corresponding static route as the matching route; If the static route includes a service type identifier and a gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route, which specifically includes: judging the service type of the data packet to be sent Whether the identifier is the same as the service type identifier contained in the static route, and if so, determine the corresponding static route as the matching route; If the static route includes destination address/subnet mask, service type identifier and gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route, which specifically includes: judging Whether the destination address of the packet to be sent belongs to the destination address/subnet mask included in the static route, if so, the corresponding static route is determined to be the first matching route; The service type identifiers contained in the static routes are the same, if so, determine the corresponding static route as the second matching route; when the first matching route and the second matching route are the same static route, determine the static route as the matching route; otherwise, determine the first matching route as the matching route. 6. A terminal, characterized by comprising: a routing policy acquisition unit, configured to initiate a routing policy acquisition request to the network side, and receive a routing policy sent by the network side; The static route generation storage unit is configured to generate and store a corresponding static route according to the received routing policy. 7. The terminal according to claim 6, further comprising: A route determination unit is configured to match the stored static route according to the attribute information of the data packet to be sent, and determine a matching route; A data sending unit, configured to use the determined matching route to send the data packet. 8. The terminal according to claim 6 or 7, further comprising: The static route deletion unit is configured to delete the static route generated according to the routing policy sent by the corresponding network side stored in the static route generation storage unit after the terminal leaves the network. 9. A network element device, comprising: a storage unit for storing routing policies; a receiving unit, configured to receive a routing policy acquisition request initiated by the terminal; a sending unit, configured to send the routing policy stored in the storage unit to the terminal. 10. The network element device according to claim 9, further comprising: A configuration unit, configured to configure or modify the routing policy stored in the storage unit. 11. A method for generating a static route, comprising: After the terminal accesses the network, it requests IP configuration from the DHCP server on the network side; Receiving the DHCP message sent by the DHCP server, the DHCP message includes a routing policy; Obtain the routing policy included in the DHCP message, generate and store a corresponding static route. 12. The method according to claim 11, wherein the routing policy is carried in an optional Options field in the DHCP message. 13. The method according to claim 11 or 12, wherein the routing policy includes: Destination address/subnet mask and gateway address; or service type identifier and gateway address; or destination address/subnet mask, service type identifier and gateway address; The acquisition of the routing policy contained in the DHCP message, generating and storing a corresponding static route, specifically includes: Obtain the destination address/subnet mask and gateway address, generate a static route including the destination address/subnet mask and gateway address, and add it to the terminal routing table; or Obtain the service type identifier and gateway address, generate a static route containing the service type identifier and gateway address, and add it to the terminal routing table; or Obtain the destination address/subnet mask, service type identifier and gateway address, generate a static route including the destination address/subnet mask, service type identifier and gateway address, and add it to the terminal routing table. 14. The method according to claim 11 or 12, further comprising: After the terminal leaves the network, the locally stored static route generated according to the routing policy sent by the DHCP server in the corresponding network is deleted. 15. A method for implementing terminal routing, comprising: The terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route; sending the data packet using the determined matching route; Wherein, the static route is generated by any method described in claims 11-14. 16. The method according to claim 15, wherein if the static route includes a destination address/subnet mask and a gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent , determining a matching route, specifically including: judging whether the destination address of the data packet to be sent belongs to the destination address/subnet mask included in the static route, and if so, determining the corresponding static route as the matching route; If the static route includes a service type identifier and a gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route, which specifically includes: judging the service type of the data packet to be sent Whether the identifier is the same as the service type identifier contained in the static route, and if so, determine the corresponding static route as the matching route; If the static route includes destination address/subnet mask, service type identifier and gateway address, the terminal matches the stored static route according to the attribute information of the data packet to be sent, and determines a matching route, which specifically includes: judging Whether the destination address of the packet to be sent belongs to the destination address/subnet mask included in the static route, if so, the corresponding static route is determined to be the first matching route; The service type identifiers contained in the static routes are the same, if so, determine the corresponding static route as the second matching route; when the first matching route and the second matching route are the same static route, determine the static route as the matching route; otherwise, determine the first matching route as the matching route. 17. A terminal, characterized by comprising: An IP configuration request unit, configured to request an IP configuration from a DHCP server on the network side, and receive a DHCP message sent by the DHCP server, wherein the DHCP message includes a routing strategy; The static route generation storage unit is used to obtain the routing policy included in the DHCP message, generate and store a corresponding static route. 18. The terminal according to claim 17, further comprising: A route determination unit is configured to match the stored static route according to the attribute information of the data packet to be sent, and determine a matching route; A data sending unit, configured to use the determined matching route to send the data packet. 19. The terminal according to claim 17 or 18, further comprising: The static route deletion unit is configured to delete the static route stored in the static route generation storage unit according to the routing policy sent by the DHCP server in the corresponding network after the terminal leaves the network. 20. A DHCP server, comprising: a storage unit for storing routing policies; a receiving unit, configured to receive an IP configuration acquisition request sent by the terminal; a generating unit, configured to generate a DHCP message, and the DHCP message includes the routing policy stored in the storage unit; a sending unit, configured to send the DHCP message generated by the generating unit to a terminal. 21. The DHCP server according to claim 20, further comprising: A configuration unit, configured to configure or modify the routing policy stored in the storage unit.

Images