WO2010028545A1

WO2010028545A1 - Static route generation method, terminal route realization method and apparatus

Info

Publication number: WO2010028545A1
Application number: PCT/CN2009/001018
Authority: WO
Inventors: 惠敏; 邓辉; 刘大鹏; 陈刚; 胡雪南
Original assignee: 中国移动通信集团公司
Priority date: 2008-09-09
Filing date: 2009-09-09
Publication date: 2010-03-18
Also published as: CN101674221A

Abstract

A static route generation method, terminal route realization method and apparatus are provided. Through that the network side network element apparatus or the DHCP server transmits a route policy down to a terminal, the terminal generates a static route and stores it according to the route policy transmitted down by the network element apparatus or the DHCP server; the terminal matches the attribute information of the data packet waiting for transmitting with the stored static route, and determines a matching route, sends the data packet using the determined matching route. By applying the scheme of the invention, the user doesn't need to obtain a multiple route configuration parameter to configure the static route manually, that the data packets pass a multiple network connection at the same time can be ensured, and the multi -connection of the terminal can be realized.

Description

Static route generation method, terminal route implementation method and device

The present invention relates to the field of communications, and in particular, to a static route generation method when a terminal is connected to multiple networks, a corresponding terminal route implementation 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 networks, LTE networks, VPNs, WiFi, and so on. Each network has its own characteristics, such as Ethernet with high speed, 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, it has created the need for multiple connections of terminals. A terminal can access multiple networks at the same time, and can find the most suitable network for different application data packets, and keep the terminal working in multiple networks at the same time.

The rapid development of terminals has made physical hardware assurance for the needs of multiple connections. At present, the notebook on the market basically has a wireless network card and an Ethernet card at the same time, and at the same time, a 3G data card slot is left, and these network interfaces can work at the same time. Smartphones can connect to a variety of mobile networks and support WiFi connections.

However, in the case of user requirements and terminal hardware guarantees, the terminal routing mechanism in the prior art ultimately limits the terminal multi-connection. Since the terminal routing uses the default gateway mechanism, in the case of multiple connections, the operating system selects a default network interface according to certain rules, so that all network traffic enters and exits through this default interface, which actually causes The failure of multiple connections of the terminal cannot achieve the purpose of multi-connection of the terminal, and the simultaneous use of multiple network connections by the terminal 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 manner is that the user manually configures the command line. Set the static routing entry, including the destination IP address, gateway, and metric value. This ensures that the network interface of the specified destination IP address is routed. The routing of other traffic is still completed through the default network interface. There are multiple interfaces with traffic at the same time. However, this method is basically not operative to the user because it is difficult for the user to obtain various routing configuration parameters.

The Windows Vista operating system can maintain multiple connections in a specific situation. That is, when the application performs network communication, if the default interface is replaced, the already started application will continue to communicate using the old interface, and the newly launched application uses the latest replacement default. The interface communicates. In this case, the old interface and the new default interface have traffic at the same time, achieving multiple connections to the terminal. However, this is a multi-connection in a passive situation, and this approach does not work when users need to proactively specify different networks for different applications.

In summary, in the prior art, since the terminal routing complies with the default gateway mechanism, that is, no matter how many different networks are accessed by several physical ports on the physical terminal, the packet routing of the terminal is only sent and received from a default interface. This results in the fact that even if the terminal accesses multiple networks, virtually all network traffic is sent or received from one interface, which does not achieve the effect of multiple connections to the terminal. Summary of the invention

The embodiment of the present invention provides a method for generating a static route, a corresponding terminal, and a network element device, and the terminal generates a corresponding static route according to the routing policy sent by the network element device, and solves the problem that the static route manually configured by the user does not have The problem of operability.

The embodiment of the present invention further provides a method for generating a static route, a corresponding terminal, and a DHCP server, so that the terminal sends a routing policy by using a DHCP server to generate a corresponding static route, which solves the problem that the user manually configures the static route. The problem of operability.

The embodiment of the invention further provides a method for implementing terminal routing, and the terminal is matched with a static route to send a data packet to implement multiple connection of the terminal.

A static route generation method provided by an embodiment of the present invention includes:

After the terminal accesses the network, the routing policy acquisition request is initiated to the network side;

Receiving a routing policy sent by the network side; Generate a corresponding static route and store it according to the received routing policy.

The embodiment of the invention provides a method for implementing terminal routing, which includes:

The terminal matches the attribute information of the data packet to be sent with the stored static route to determine a matching route.

Sending the data packet using the determined matching route;

The static route is generated by using the static route generation method.

The embodiment of the invention further provides a terminal, including:

a routing policy obtaining 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.

The embodiment of the invention further provides a network element device, including:

a storage unit, configured to store a routing policy;

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

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

The embodiment of the invention further provides a static route generation method, including:

After the terminal accesses the network, the dynamic host configuration protocol is configured on the network side, and the DHCP server requests the IP configuration; receiving the DHCP message sent by the DHCP server, where the DHCP message includes a routing policy;

Obtain the routing policy contained in the DHCP packet, generate a corresponding static route, and store it. According to the foregoing method for generating a static route using a DHCP message, an embodiment of the present invention provides a method for implementing a terminal route, including:

The 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: The IP configuration requesting unit is configured to request the network side DHCP server to obtain an IP configuration, and receive the DHCP message sent by the DHCP server, where the DHCP message includes a routing policy;

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

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

a storage unit, configured to store a routing policy;

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

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

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

The present invention sends a routing policy to the terminal by the network side network element device or the DHCP server, and the terminal only needs to generate a corresponding static route according to the routing policy delivered by the network element device or the DHCP server, and does not need to obtain various routing configuration parameters by the user. To manually configure a static route. For the terminal, the routing algorithm is not required to be maintained in the terminal, which saves computing resources. For the user, the entire routing policy does not require human participation, and is simple and easy.

After the static route is generated, the terminal 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, and so on), so that multiple network connections can pass the data packet at the same time to achieve the purpose of multiple connections. DRAWINGS

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

2 is a flowchart of a method for implementing terminal routing according to Embodiment 2 of the present invention;

3 is a schematic structural diagram of a terminal according to Embodiment 3 of the present invention;

4 is a schematic structural diagram of a network element device according to 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;

FIG. 6 is a specific signaling interaction process between a terminal and a DHCP server according to Embodiment 5 of the present invention; Schematic diagram

7 is a schematic structural diagram of a terminal according to Embodiment 7 of the present invention;

FIG. 8 is a schematic structural diagram of a DHCP server according to Embodiment 8 of the present invention. detailed description

The embodiment of the present invention provides a static route generation method, a corresponding terminal route implementation method, and a corresponding terminal and network element device or a DHCP server, so that the terminal generates a corresponding static route according to the routing policy sent by the network side, and the manual is solved manually. Configuring static routes is not an issue of operability. When the terminal needs to send a data packet, the attribute information of the data packet to be sent can be matched with the generated static route, and the data packet is sent through a static route matching the attribute information of the data packet to be sent, so that the terminal is connected multiple times.

The method and apparatus provided by the present invention will be described in detail below with reference to the accompanying drawings. Embodiment 1:

The first embodiment provides a method for generating a static route. In this method, the network sends a routing policy to the terminal, and the terminal generates a static route according to the routing policy sent by the network.

FIG. 1 is a flowchart of a static route generation method according to Embodiment 1 of the present invention, which specifically includes:

Step S101: After the terminal accesses the network, the terminal initiates a routing policy acquisition request to the network side.

Step S102: The terminal receives a routing policy sent by the network side.

Step S103: The terminal generates a corresponding static route according to the received routing policy and stores the static route. The routing policy may specifically include, for example:

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 destination address/subnet mask can represent the subnet address, that is, the subnet address = the length of the network identifier bit in the destination address/subnet mask. For example, the subnet address can be obtained from 220.10.0.125/24. .0.0. In step S103, the destination address is generated according to the received destination address/subnet mask and the gateway address. a static route of the subnet mask and the gateway address, and added to the terminal routing table; when the routing policy delivered by the network side includes the service type identifier and the gateway address,

In S103, a static route including the service type identifier and the gateway address is generated according to the received service type identifier and the gateway address, and is added to the terminal routing table.

When the routing policy delivered by the network side includes the destination address/subnet mask, the service type identifier, and the gateway address, in step S103, the destination address/subnet mask, service type identifier, and gateway address are generated according to the received destination address/subnet mask, service type identifier, and gateway address. A static route containing the destination address/subnet mask, service type identifier, and gateway address, and added to the terminal routing table.

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

According to the above-mentioned first embodiment of the present invention, the terminal only needs to generate a corresponding static route according to the routing policy sent by the network side, and does not need to obtain various routing configuration parameters to manually configure the static route, and solves the problem that the user manually configures the static route. Operational problems.

Embodiment 2:

The second embodiment provides a terminal routing implementation method, where the terminal selects a locally stored static route to send a data packet.

2 is a flowchart of a method for implementing terminal routing according to Embodiment 2 of the present invention, which specifically includes:

Step S201: The terminal matches the attribute information of the to-be-sent data packet with the stored static route to determine a matching route.

Step S202: The terminal sends the data packet by using the determined matching route.

The static route is generated by the method in the first embodiment.

According to the method provided by Embodiment 2 of the present invention, when a matching route is not determined, the data packet is sent by using a default route.

As described above, if the static route includes the destination address/subnet mask and the gateway address, in step S201, it is determined 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 , determining the corresponding static route as a matching route; As described above, if the static route includes the service type identifier and the gateway address, the identification is the same in step S201, and if so, the corresponding static route is determined as the matching route;

As described above, if the static route includes the destination address/subnet mask, the service type identifier, and the gateway address, in step S201, it is determined whether the destination address of the data packet to be sent belongs to the destination address/subnet mask included in the static route. The code, if yes, determines the corresponding static route as the first matching route; and determines whether the service type identifier of the data packet to be sent is the same as the service type identifier included in the static route, and if yes, determines the corresponding static route as the second matching route. When the first matching route and the second matching route are the same static route, the static route is determined as the final matching route; otherwise, the first matching route is determined as the final matching route.

According to the foregoing method of the second embodiment of the present invention, when the terminal needs to send a data packet, the generated static route can be matched 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.), and the matching is performed. The static route sends data packets. Because the data packets of different applications may have different destination addresses or service types, the matching routes may be different. Therefore, the terminal can use multiple routes to send data packets to implement multiple connections.

Embodiment 3:

The third embodiment provides a terminal, which can obtain a routing policy from the network side to generate a static route and store, and select a stored static route to send a data packet.

3 is a schematic structural diagram of a terminal according to Embodiment 3 of the present invention, which specifically includes: a routing policy obtaining unit 301, configured to initiate a routing policy acquisition request to a network side, and receive a routing policy sent by a network side;

The static route generation 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:

The routing determining unit 303 is configured to match the attribute information of the data packet to be sent with the stored static route to determine a matching route.

The data sending unit 304 is configured to send the data packet by using the determined matching route. The terminal provided in Embodiment 3 of the present invention may further include:

The static route deleting unit is configured to delete the static route generated by the routing policy sent by the corresponding network side stored in the static route generating storage unit after the terminal leaves the network.

The terminal provided by the third embodiment of the present invention only needs to generate a corresponding static route according to the routing policy delivered by the network side, and does not need to obtain various routing configuration parameters by the user to manually configure the static route, thereby solving the problem that the user manually configures the static route. The problem is operability; and when the terminal needs to send a data packet, the attribute information of the data packet to be sent can be matched with the generated static route, and the data packet is sent through the matched static route to implement multiple connection of the terminal.

Embodiment 4:

The fourth embodiment provides a network element device, and implements a routing policy to the terminal.

4 is a schematic structural diagram of a network element device according to Embodiment 4 of the present invention, which specifically includes: a storage unit 401, configured to store a routing policy;

The receiving unit 402 is configured to receive a routing policy acquisition request initiated by the terminal.

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

The network element device may further include:

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

The network element device provided by the fourth embodiment of the present invention pre-sets the routing policy through the network side and stores the routing policy in the network element device. After receiving the request from the terminal, the device sends the set routing policy to the terminal. The algorithm saves the computing resources of the terminal, and the operator can conveniently configure or update the routing policy stored in the network element device, and flexibly implement multiple connections of the terminal.

Based on the same inventive concept, the present invention further provides a static route generation method, a terminal route implementation method, and a corresponding terminal and a DHCP server, which are implemented by extending a dynamic host configuration protocol (DHCP).

Embodiment 5:

The fifth embodiment provides a method for generating a static route. When the terminal requests access to the network and requests the IP configuration from the DHCP server, the DHCP server includes the routing policy in the DHCP response message returned to the terminal, and the terminal according to the received routing policy. Generate a static route and store it. 5 is a flowchart of a method for generating a static route according to Embodiment 5 of the present invention, which specifically includes: Step S501: After a terminal accesses a network, requesting an IP configuration from a DHCP server on a network side; Step S502: The terminal receives a DHCP message sent by a DHCP server. The routing policy is included in the returned DHCP message.

Step S503: The terminal acquires a routing policy included in the DHCP packet, and generates a corresponding static route and stores the corresponding route.

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

In the method of the fifth embodiment, the specific signaling interaction process between the terminal and the DHCP server is as shown in FIG. 6, and includes:

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

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

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

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

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

Table 1 below shows the packet format of DHCP in the prior art:

Table 1 : OP(1) Htype(1) Hlen(1) Hops(1)

Transaction ID(4)

Seconds(2) Flags(2)

Ciaddr (4)

Yiaddr ( 4 )

Siaddr (4)

Giaddr (4)

Chaddr (16)

Sname ( 64 )

File (128)

Options ( variable ) The specific meaning of each field in Table 1 is:

OP(1): indicates the message op code I message type BOOTREQUEST, 2=BOOTREPLY, length is 1 byte (byte);

Htype(1): indicates the hardware address type, which is 1 byte in length;

Hlen(1): indicates the length of the hardware address, and the length is 1 byte.

Hops(1): Set to zero, can be used by the forwarding agent when starting through the forwarding agent, and has a length of 1 byte;

Transaction ID (4): The operation ID is a random number used for the response of the synchronization message and message between the terminal and the server, and has a length of 4 bytes.

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

Flags(2): The flag bit, which is 2 bytes in length;

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

Yiaddr (4): User IP address, length is 4 bytes;

Siaddr (4): The IP address used in the bootstrap process, which is 4 bytes in length; Giaddr ( 4 ): Forward proxy IP address, length 4 bytes;

Chaddr ( 16 ): Customer hardware address, length 16 bytes;

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

File ( 128 ): Start file name, length 128 bytes;

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

It can be seen from the fields of the DHCP message format in Table 1, where Options (variable) is an optional parameter field whose length is not fixed. The embodiment of the present invention extends this optional field to carry a routing policy set in the DHCP server. For example, the extension field is: Option N; The Option N field carries the routing policy.

A specific routing policy can include:

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

For example, the routing policy includes the destination address/subnet mask, service type identifier, and gateway address. The specific field structure of the extended field Option N is as follows:

The above field structure is merely an example. The specific structure of the field structure and the specific length of each field are not limited.

In the foregoing step S503, the specific implementation process of the terminal acquiring the routing policy included in the DHCP message to generate the corresponding static route and storing the same is the same as that in the first embodiment, and is no longer fascinating.

According to the foregoing fifth embodiment of the present invention, the terminal only needs to generate a corresponding static route according to the routing policy delivered by the DHCP server on the network side, and does not need to obtain various routing configuration parameters by the user to manually configure the static route, which also solves the problem that the user manually configures the static route. Routing does not have the problem of operability. The sixth embodiment is similar to the second embodiment. When the terminal has a data packet to be sent, the terminal matches the attribute information of the data packet to be sent with the static route stored in the local routing table to determine a matching route. Determine the matching route to send the packet.

Different from the second embodiment, 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 static route stored locally, the default route is used to send the data packet.

Example 7:

According to the method provided in the foregoing embodiment 5 and the sixth embodiment, the present invention further provides a terminal having a corresponding function, and a schematic structural diagram thereof is shown in FIG. 7, which includes:

The IP configuration requesting unit 701 is configured to request the network side DHCP server to obtain an IP configuration, and receive the DHCP message sent by the DHCP server, where the DHCP message includes the IP configuration information and the routing policy.

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

The terminal in this embodiment further includes:

The routing determining unit 703 is configured to match the attribute information of the data packet to be sent with the stored static route to determine a matching route.

The data sending unit 704 is configured to send the data packet by using the determined matching route.

The terminal in this embodiment may further include: a static route deleting unit, configured to delete a static route generated by the routing policy sent by the DHCP server in the corresponding network stored in the static route generating storage unit after the terminal leaves the network.

The terminal provided by the seventh embodiment of the present invention only needs to generate a static route according to the routing policy sent by the DHCP server on the network side, and does not need to obtain various routing configuration parameters to manually configure a static route, thereby solving the problem that the user manually configures the static route. There is no problem of operability; and when the terminal needs to send a data packet, the attribute information of the data packet to be sent can be matched with the generated static route, and the data packet is sent through the matched static route to implement terminal multi-connection. Example 8:

Corresponding to the terminal provided in the seventh embodiment, the eighth embodiment provides a DHCP server, which is used to send a routing policy to the terminal.

The storage unit 801 is configured to store a routing policy.

The receiving unit 802 is configured to receive an IP configuration request sent by the terminal.

The generating unit 803 is configured to generate a DHCP message, where the generated DHCP message includes a routing policy stored in the storage unit 801.

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

In a preferred solution, the DHCP server further includes:

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

The DHCP server provided in Embodiment 8 of the present invention stores a preset routing policy, and after receiving the IP configuration request of the terminal, sends a set routing policy to the terminal by using a response message returned to the terminal; The algorithm saves the computing resources of the terminal, and the operator can conveniently configure or update the routing policy stored in the DHCP server, and flexibly implement multiple connections of the terminal.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Therefore, it is intended that the present invention cover the modifications and variations of the invention as claimed.

Claims

Rights request

A static route generation method, comprising:

Receiving a routing policy sent by the network side;

Generate a corresponding static route and store it according to the received routing policy.

2. The method of claim 1 wherein:

The routing policy includes a destination address/subnet mask and a gateway address. The generating a corresponding static route according to the received routing policy and storing the method includes: generating the inclusion according to the received destination address/subnet mask and the gateway address. a static route of the destination address/subnet mask and the gateway address, and added to the terminal routing table;

Or

The routing policy includes a service type identifier and a gateway address, and the corresponding static route is generated according to the received routing policy, and the method includes: generating, according to the received service type identifier and the gateway address, the service type identifier and the gateway address. Static route, and join to the terminal routing table;

Or

The routing policy includes a destination address/subnet mask, a service type identifier, and a gateway address. The generating a static route according to the received routing policy and storing the information includes: receiving the destination address/subnet mask, service A type identifier and a gateway address are generated, and a static route including the destination address/subnet mask, service type identifier, and gateway address is generated and added to the terminal routing table.

A method for implementing terminal routing, which is characterized in that:

Sending the data packet using the determined matching route;

The static route is generated by the method of any one of claims 1-2.

The method according to claim 3, wherein if the static route includes a destination address/subnet mask and a gateway address, the terminal sets the attribute information of the data packet to be sent and the stored static route. The matching to determine the matching route specifically includes: determining whether the target address of the data packet to be sent belongs to the destination address/subnet mask included in the static route, and if yes, determining the corresponding static route as the matching route;

If the static route includes the service type identifier and the gateway address, the terminal matches the attribute information of the data packet to be sent with the stored static route to determine that the matching route specifically includes: the same, if yes, the corresponding static route Determined to be the matching route;

If the static route includes the destination address/subnet mask, the service type identifier, and the gateway address, the terminal matches the attribute information of the data packet to be sent with the stored static route to determine that the matching route specifically includes: 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, the corresponding static route is determined as the first matching route; and whether the service type identifier of the data packet to be sent is determined The static route includes the same service type identifier. If yes, the corresponding static route is determined as the second matching route. When the first matching route and the second matching route are the same static route, the static route is determined as the matching. Routing; otherwise, determining the first matching route as the matching route.

5. A terminal, comprising:

The terminal according to claim 5, further comprising:

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

And a data sending unit, configured to send the data packet by using the determined matching route.

7. The terminal of claim 5, wherein: The routing policy includes a destination address/subnet mask and a gateway address. The generating a corresponding static route according to the received routing policy and storing the method includes: generating the inclusion according to the received destination address/subnet mask and the gateway address. a static route of the destination address/subnet mask and the gateway address, and added to the terminal routing table;

Or

The routing policy includes a service type identifier and a gateway address, and the generated static route is generated according to the received routing policy, and the method includes: generating, according to the received service type identifier and the gateway address, the service type identifier and the gateway address. Static route, and join to the terminal routing table;

Or

The routing policy includes a destination address/subnet mask, a service type identifier, and a gateway address. The generating a static route according to the received routing policy and storing the information includes: receiving the destination address/subnet mask, service The type identifier and the gateway address are generated, and a static route including the destination address/subnet mask, the service type identifier, and the gateway address is generated and added to the terminal routing table.

8. A network element device, comprising:

a storage unit, configured to store a routing policy;

9. The network element device of claim 8, wherein:

The routing policy includes a destination address/subnet mask and a gateway address, or includes a service type identifier and a gateway address, or a destination address/subnet mask, a service type identifier, and a gateway address.

10. A static route generation method, which is characterized by:

Obtain the routing policy contained in the DHCP packet, generate a corresponding static route, and store it.

11. The method of claim 10, wherein the routing policy passes DHCP The optional Options field in the packet is carried.

12. A method as claimed in claim 10 or 11, characterized in that:

The routing policy includes a destination address/subnet mask and a gateway address, and the routing policy included in the DHCP packet is generated to generate a static route and is stored, including: acquiring a destination address/subnet mask and a gateway. Address, generating a static route including the destination address/subnet mask and gateway address, and adding to the terminal routing table;

Or

The routing policy includes a service type identifier and a gateway address, and the obtaining the routing policy included in the DHCP packet to generate a static route and storing the static route, and the method includes: acquiring a service type identifier and a gateway address, and generating the service type A static route identifying the address of the gateway and adding it to the terminal routing table;

Or

The routing policy includes a destination address/subnet mask, a service type identifier, and a gateway address, and the routing policy included in the DHCP packet is generated to generate a static route and is stored, including: acquiring a destination address/subnet A mask, a service type identifier, and a gateway address are generated, and a static route including the destination address/subnet mask, the service type identifier, and the gateway address is generated and added to the terminal routing table.

13. The method of claim 10, further comprising:

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

A terminal routing implementation method, comprising:

Sending the data packet using the determined matching route;

The static route is generated by the method described in any one of claims 10-13.

The method according to claim 14, wherein if the static route includes a destination address/subnet mask and a gateway address, the terminal stores attribute information and storage of the data packet to be sent. The matching of the static route to determine the matching route includes: determining 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 the service type identifier and the gateway address, the terminal matches the attribute information of the data packet to be sent with the stored static route to determine a matching route, which includes: the same knowledge, if yes, the corresponding static route Determined to be the matching route;

If the static route includes a destination address/subnet mask, a service type identifier, and a gateway address, the terminal matches the attribute information of the data packet to be sent with the stored static route to determine a matching route, which includes: 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, the corresponding static route is determined as the first matching route; and the same is known; if yes, the corresponding static route is determined to be the second The matching route is determined as the matching route when the first matching route and the second matching route are the same static route; otherwise, the first matching route is determined as the matching route.

16. A terminal, comprising:

The IP configuration requesting unit is configured to request the network side DHCP server to obtain the IP configuration, and receive the DHCP message sent by the DHCP server, where the DHCP message includes a routing policy, and the static route generating storage unit is configured to acquire the A routing policy contained in a DHCP packet generates a corresponding static route and stores it.

The terminal according to claim 16, further comprising:

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

18. The terminal of claim 16, wherein:

The routing policy includes a destination address/subnet mask and a gateway address. The obtaining a routing policy to generate a corresponding static route and storing the specific includes: according to the received destination address/subnet mask and gateway Address, generating a static route including the destination address/subnet mask and gateway address, and adding to the terminal routing table;

Or

The routing policy includes a service type identifier and a gateway address. The obtaining the routing policy to generate a corresponding static route and storing the specific information includes: generating a static information including the service type identifier and the gateway address according to the received service type identifier and the gateway address. Routing, and join to the terminal routing table; or

The routing policy includes a destination address/subnet mask, a service type identifier, and a gateway address. The obtaining the routing policy to generate a corresponding static route and storing the content specifically includes: according to the received destination address/subnet mask, service type identifier And the gateway address, generating a static route including the destination address/subnet mask, service type identifier, and gateway address, and adding to the terminal routing table.

19. A DHCP server, comprising:

a storage unit, configured to store a routing policy;

20. The DHCP server of claim 19, wherein: