MAP-E tunnel configuration management method, device, server and storage medium

Abstract

The present application discloses a configuration management method, device, server and storage medium for a MAP‑E tunnel. The configuration management method for the MAP‑E tunnel includes: sending a first HTTP request message carrying MAP‑E tunnel configuration parameter request information to a rule parameter server; receiving a first response message sent by the rule parameter server according to the MAP‑E tunnel configuration parameter request information in the first HTTP request message, the first response message including MAP‑E tunnel configuration parameters; configuring the MAP‑E tunnel based on the MAP‑E tunnel configuration parameters in the first response message. In an embodiment of the present application, by deploying a rule parameter server in the network and obtaining MAP‑E tunnel configuration parameters from the rule parameter server using an HTTP message, the MAP‑E tunnel can be guaranteed to start and run normally when the upper-layer device does not have the function of sending MAP‑E tunnel configuration parameters through DHCPv6 due to its own reasons.

Description

Technical Field

[0001] The embodiments of the present application relate to, but are not limited to, the field of communication technology, and in particular, to a configuration management method for a MAP-E tunnel, a user front-end device, a rule parameter server, and a computer-readable storage medium. Background Art

[0002] Due to the rapid development of the Internet, IPv4 addresses have been exhausted and need to be replaced with IPv6 to completely solve this problem. At present, countries and regions in the world are steadily promoting the transition from IPv4 to IPv6. Among the various transition plans, the DS-Lite (Dual Stack-Lite) tunnel plan has gradually evolved to the MAP-E (Mapping of Address and Port using Encapsulation, stateless mapping and dual encapsulation technology) plan. The MAP-E plan has advantages and overcomes some defects of the DS-Lite tunnel: for example, the DS-Lite tunnel plan only completes tunnel message encapsulation on the CPE (Customer Premise Equipment), but does not perform NAT (Network Address Translation) and port translation. The upper-layer local equipment (such as carrier-grade network equipment, such as CGN (Carrier-Grade NAT and port translation are completed on CPE (carrier-level network address translation) devices, dual-stack servers, etc.). This requires centralized management and maintenance of the message information of each flow, including addresses and ports, etc. The upper-layer local equipment has a large processing pressure, and the equipment investment and maintenance costs are high. As an evolutionary solution for DS-Lite tunnels, the MAP-E tunnel solution implements NAT and port translation on CPE, and then performs tunnel message encapsulation, which reduces the processing pressure on upper-layer local equipment.

[0003] Usually, CPE completes the acquisition of MAP-E tunnel configuration parameters through the IPv6 Dynamic Host Configuration Protocol for ipv6 (DHCPv6) interaction, thereby establishing the MAP-E IPv4 in IPv6 tunnel, and realizing the message reception and sending processing of the HOST host connected to the CPE to access the IPv4 network service. When the network device cannot complete the parameter acquisition through DHCPv6 interaction, the MAP-E tunnel cannot be established normally, and the MAP-E tunnel cannot operate normally, so it is impossible to realize the IPv4 network service access to the IPv4 through the MAP-E tunnel through the IPv6 network. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present application provide a configuration management method for a MAP-E tunnel, a user front-end device, a rule parameter server, and a computer-readable storage medium, which can ensure that a MAP-E tunnel is started and operated normally when an upper-layer device does not have the function of issuing MAP-E tunnel configuration parameters in a DHCPv6 manner due to its own reasons.

[0006] In a first aspect, an embodiment of the present application provides a configuration management method for a MAP-E tunnel, which is applied to a user front-end device CPE, including:

[0007] Sending a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server;

[0008] receiving a first response message sent by a rule parameter server according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, wherein the first response message includes a MAP-E tunnel configuration parameter;

[0009] A MAP-E tunnel is configured based on the MAP-E tunnel configuration parameters in the first response message.

[0010] In a second aspect, an embodiment of the present application further provides a configuration management method for a MAP-E tunnel, which is applied to a rule parameter server, including:

[0011] receiving a first HTTP request message sent by a CPE, wherein the first HTTP request message carries MAP-E tunnel configuration parameter request information;

[0012] A first response message carrying MAP-E tunnel configuration parameters is sent to the CPE according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, so that the CPE configures the MAP-E tunnel according to the MAP-E tunnel configuration parameters in the first response message.

[0013] In a third aspect, an embodiment of the present application further provides a user front-end device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the configuration management method of the MAP-E tunnel of the first aspect through the computer program.

[0014] In a fourth aspect, an embodiment of the present application further provides a rule parameter server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the configuration management method of the MAP-E tunnel of the second aspect through the computer program.

[0015] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the above MAP-E tunnel configuration management method.

[0016] The embodiment of the present application includes: sending a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server; receiving a first response message sent by the rule parameter server according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, the first response message including MAP-E tunnel configuration parameters; configuring the MAP-E tunnel based on the MAP-E tunnel configuration parameters in the first response message. According to the solution provided by the embodiment of the present application, by deploying a Rule Server (rule parameter server) in the network, when a MAP-E tunnel needs to be established, MAP-E tunnel configuration parameter request information is sent to the rule parameter server in HTTP message mode, and after receiving the response message from the rule parameter server, the MAP-E tunnel is established according to the MAP-E tunnel configuration parameters carried in the response message, so that the MAP-E tunnel can be guaranteed to start and run normally when the upper layer device does not have the function of sending MAP-E tunnel configuration parameters through DHCPv6 mode due to its own reasons.

[0017] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings are used to provide further understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0019] Figure 1 is a schematic diagram of a network topology for executing a configuration management method for a MAP-E tunnel provided by an embodiment of the present application;

[0020] Figure 2 is a flow chart of a configuration management method of a MAP-E tunnel provided by an embodiment of the present application;

[0021] Figure 3 This is a flow chart of sending an HTTP request message provided by an embodiment of the present application;

[0022] Figure 4 is a flowchart of configuring a MAP-E tunnel provided by an embodiment of the present application;

[0023] Figure 5 is a flowchart of a configuration management method of a MAP-E tunnel provided by another embodiment of the present application;

[0024] Figure 6 is a flowchart of a configuration management method of a MAP-E tunnel provided by another embodiment of the present application;

[0025] Figure 7 is a flowchart of a configuration management method of a MAP-E tunnel provided by another embodiment of the present application;

[0026] Figure 8 This is a flowchart of receiving an HTTP request message provided by an embodiment of the present application;

[0027] Fig. 9 is a general network processing flow chart provided by an embodiment of the present application;

[0028] Fig.10 This is a flowchart of starting / stopping a MAP-E tunnel provided by an embodiment of the present application;

[0029] Fig.11 is a flowchart of automatically obtaining MAP-E tunnel configuration parameters provided by an embodiment of the present application;

[0030] Fig.12 This is a flowchart of obtaining and maintaining MAP-E tunnel configuration parameters using HTTP, provided by an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0032] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0033] The embodiment of the present application provides a configuration management method for a MAP-E tunnel, a user front-end device, a rule parameter server, and a computer-readable storage medium. A Rule Server is deployed in a network, and MAP-E tunnel configuration parameters are stored in the rule parameter server. When a MAP-E tunnel needs to be established, MAP-E tunnel configuration parameter request information is sent to the rule parameter server in an HTTP message mode. After receiving a response message from the rule parameter server, the MAP-E tunnel is established according to the MAP-E tunnel configuration parameters carried in the response message. In this way, when an upper-layer device does not have the function of sending MAP-E tunnel configuration parameters in a DHCPv6 mode due to its own reasons, the MAP-E tunnel can be ensured to start and run normally.

[0034] The embodiments of the present application are further described below in conjunction with the accompanying drawings.

[0035] like Figure 1 As shown, Figure 1 FIG. 1 is a schematic diagram of a network topology for executing a configuration management method for a MAP-E tunnel provided by an embodiment of the present application. Figure 1 In the example, the network topology includes the user front-end device CPE, the user device such as PC (personal computer) connected to one end of CPE, the upper-layer BRAS (Broadband Remote Access Server) device connected to the other end of CPE, BR (edge ​​router, i.e. MAP-E tunnel server device), DNS resolution server (DNS Server), and rule parameter server (Rule Server). The BRAS device is responsible for allocating IPv6 addresses and gateways to CPE. The parameter distribution server software runs on the rule parameter server, which is responsible for authenticating each CPE connection request and responding to the HTTP request message sent by CPE. The response message carries MAP-E tunnel configuration parameters. After receiving the response message and decrypting and parsing the parameters, the CPE creates a MAP-E tunnel between the two devices "CPE-BR" as shown by the arrow in the figure.

[0036] The network topology and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of network topology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0037] It can be understood by those skilled in the art that Figure 1The various components and topological structures shown in the figure do not constitute a limitation on the embodiments of the present application, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0038] Based on the above network topology, various embodiments of the MAP-E tunnel configuration management method of the present application are proposed.

[0039] like Figure 2 As shown, Figure 2 It is a flowchart of a configuration management method of a MAP-E tunnel provided by an embodiment of the present application. The configuration management method of the MAP-E tunnel includes but is not limited to step S100, step S200 and step S300.

[0040] Step S100: sending a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server.

[0041] In one embodiment, referring to Figure 1 As shown, first start the CPE to obtain the address, gateway, DNS Server and other information of the IPv6 WAN connection, and obtain the WAN connection parameters by initiating a DHCPv6 (stateful address automatic configuration) or SLAAC (stateless address automatic configuration) request to the BRAS device. After receiving the request, the BRAS device responds and sends the parameters. The CPE starts the WAN connection according to the parameters, thus establishing the IPv6 network access channel. After the IPv6 network access channel is established, a notification is sent to the MAP-E module in the CPE, so that the MAP-E module sends an HTTP request message carrying the MAP-E tunnel configuration parameter request information to the rule parameter server.

[0042] In one embodiment, the data in the HTTP request message uses a custom data format, which can be flexibly adjusted and redefined according to actual needs.

[0043] Step S200: receiving a first response message sent by a rule parameter server according to MAP-E tunnel configuration parameter request information in a first HTTP request message, wherein the first response message includes MAP-E tunnel configuration parameters.

[0044] In one embodiment, referring to Figure 1As shown, in the embodiment of the present application, a rule parameter server is configured in the network, in which MAP-E tunnel configuration parameters are stored, including: (1) BR Address: MAP-E tunnel peer IPv6 address; (2) IPv6 prefix: IPv6 prefix; (3) IPv6 prefix length: IPv6 prefix length; (4) IPv4 prefix: IPv4 prefix; (5) IPv4 prefix length: IPv4 prefix length; (6) EA-bits-length: Embedded-Address (EA) bit length; (7) PSID: port sequence PORT-SET; (8) PSID Offset: PSID offset; (9) PSID length: PSID length. In one embodiment, according to actual needs, parameters (2) to (9) can be multiple groups.

[0045] In one embodiment, the data in the response message uses a custom data format, which can be flexibly adjusted and redefined according to actual needs.

[0046] Step S300: configure a MAP-E tunnel based on the MAP-E tunnel configuration parameters in the first response message.

[0047] Currently, CPE usually completes the acquisition of MAP-E tunnel configuration parameters through the Dynamic Host Configuration Protocol DHCPv6 interaction, thereby establishing the MAP-E IPv4 in IPv6 tunnel, and realizing the message reception and sending processing of the HOST host connected to the CPE to access the IPv4 network service. However, when the network device cannot complete the parameter acquisition through DHCPv6 interaction, the MAP-E tunnel cannot be established normally, and the MAP-E tunnel cannot work normally, so it is impossible to realize the IPv4 traversing the IPv6 network through the MAP-E tunnel to access the IPv4 network service. To address this problem, the embodiment of the present application adopts the above-mentioned steps S100, S200, and S300, and deploys a Rule Server (rule parameter server) in the network. The MAP-E tunnel configuration parameters are stored in the rule parameter server, and MAP-E tunnel configuration parameter request information is sent to the rule parameter server in HTTP message mode. After receiving a response message from the rule parameter server, a MAP-E tunnel is established according to the MAP-E tunnel configuration parameters carried in the response message, thereby ensuring that the MAP-E tunnel is started and runs normally when the upper-layer device does not have the function of sending the MAP-E tunnel configuration parameters in DHCPv6 mode due to its own reasons.

[0048] In one embodiment, before sending the first HTTP request message to the rule parameter server, the method also includes: sending a second HTTP request message to the rule parameter server, the second HTTP request message carrying authentication request information; receiving a second response message sent by the rule parameter server according to the authentication request information in the second HTTP request message, the second response message carrying information on whether the authentication is successful.

[0049] In the embodiment of the present application, when the HTTP message interaction method is used to obtain the MAP-E tunnel configuration parameters, an authentication interaction message is first sent to the rule parameter server. Only after the authentication is successful can the subsequent steps be performed to prevent other devices in the network from illegally obtaining the rule parameter server.

[0050] In one embodiment, referring to Figure 3 , step S100 includes the following steps:

[0051] Step S101, encrypting MAP-E tunnel configuration parameter request information, and establishing a first HTTP request message according to the encrypted MAP-E tunnel configuration parameter request information;

[0052] Step S102: Send a first HTTP request message to a rule parameter server.

[0053] Different from the current use of plain text to interact with some parameter data, the messages in the embodiments of the present application are sent after being encrypted, which reduces the possibility of tampering or theft during the message sending process, thereby increasing the security and reliability of data transmission.

[0054] In one embodiment, the data in the HTTP request message is encrypted by using a public-private key encryption method. Specifically, at the CPE end, the data in the HTTP request message is encrypted by a private key assigned to the CPE, and the HTTP request message with the internal data encrypted is sent to the rule parameter server, and the rule parameter server uses the public key matching the private key to decrypt the data in the HTTP request message.

[0055] It should be understood that the above encryption method is only one embodiment of the method of the present application, and the embodiments of the present application may also include other encryption methods, including but not limited to symmetric encryption, asymmetric encryption, hash algorithm, etc.

[0056] In one embodiment, referring to Figure 4 , step S300 includes the following steps:

[0057] Step S301, decrypting the internal data of the first response message to obtain MAP-E tunnel configuration parameters;

[0058] Step S302: configure a MAP-E tunnel according to MAP-E tunnel configuration parameters.

[0059] Different from the current use of plain text to interact with some parameter data, the messages in the embodiments of the present application are sent after being encrypted, which reduces the possibility of tampering or theft during the message sending process, thereby increasing the security and reliability of data transmission.

[0060] In one embodiment, the data in the HTTP response message is encrypted by using a public-private key encryption method. Specifically, at the rule parameter server end, the data in the HTTP response message is encrypted by a private key assigned to the rule parameter server, and the HTTP response message with the internal data encrypted is sent to the CPE, and the CPE decrypts the data in the HTTP response message using a public key matching the private key, thereby obtaining the MAP-E tunnel configuration parameters.

[0061] It should be understood that the above encryption method is only one embodiment of the method of the present application, and the embodiments of the present application may also include other encryption methods, including but not limited to symmetric encryption, asymmetric encryption, hash algorithm, etc.

[0062] In one embodiment, step S302 may include:

[0063] When the MAP-E tunnel configuration parameters are determined to be valid and to match the current network connection parameters, the MAP-E tunnel is configured using the MAP-E tunnel configuration parameters.

[0064] The embodiment of the present application verifies whether the MAP-E tunnel configuration parameters are valid and whether they successfully match the current network connection parameters (for example, information such as the prefix corresponding to the currently running WAN IPv6 connection), and only establishes the MAP-E tunnel when the MAP-E tunnel configuration parameters are determined to be valid and matched with the current network connection parameters, thereby greatly increasing the robustness of the method.

[0065] In another embodiment, step S302 may include:

[0066] When the MAP-E tunnel configuration parameters are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, the first HTTP request message is resent to the rule parameter server after a first preset time has elapsed.

[0067] In an embodiment of the present application, when the MAP-E tunnel configuration parameters are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, the obtained MAP-E tunnel configuration parameters are considered to be unavailable and cannot be used to create a MAP-E tunnel. At this time, a first preset time period (e.g., 10 minutes) is set, and after the first preset time period is reached, the process of obtaining the MAP-E tunnel configuration parameters from the rule parameter server is reinitiated. In this way, when the MAP-E tunnel configuration parameters in the rule parameter server are adjusted or changed, the CPE can also make timely adjustments and updates.

[0068] It should be understood that the first preset duration mentioned above can be reasonably modified according to specific circumstances, in order to enable the MAP-E tunnel to operate better and the parameters to be updated better and more timely.

[0069] In one embodiment, referring to Figure 5 In addition to the above steps S100, S200 and S300, the MAP-E tunnel configuration management method of the embodiment of the present application may further include the following steps:

[0070] Step S400: Update the MAP-E tunnel configuration parameters into the database of the CPE.

[0071] In one embodiment, after successfully obtaining the MAP-E tunnel configuration parameters from the rule parameter server, the MAP-E tunnel configuration parameters are compared with the current MAP-E tunnel configuration parameters in the database of the CPE to determine whether there are updates or changes. If there are updates or changes, the current MAP-E tunnel configuration parameters in the database of the CPE are replaced with the obtained MAP-E tunnel configuration parameters, otherwise the current MAP-E tunnel configuration parameters in the database of the CPE remain unchanged. In another embodiment, if the MAP-E tunnel is configured for the first time, the obtained MAP-E tunnel configuration parameters are directly saved in the data of the CPE.

[0072] In the embodiment of the present application, through the above step S400, when the MAP-E tunnel configuration parameters in the rule parameter server are adjusted or changed, the CPE can also be adjusted and updated in time.

[0073] In one embodiment, referring to Figure 6 Alternatively, the MAP-E tunnel configuration management method of the embodiment of the present application may further include the following steps:

[0074] Step S500, when the first response message sent by the rule parameter server is not received within the second preset time period, obtaining the MAP-E tunnel configuration parameters from the database of the CPE;

[0075] Step S600: When the MAP-E tunnel configuration parameters obtained from the database of the CPE are determined to be valid and are determined to match the current network connection parameters, the MAP-E tunnel configuration parameters are used to configure the MAP-E tunnel.

[0076] When a response message from the rule parameter server cannot be received within a specified time (e.g., 10 minutes) due to external factors such as network conditions, the embodiment of the present application obtains the last saved MAP-E tunnel configuration parameters from the CPE database to ensure that the MAP-E tunnel can be established in a timely manner.

[0077] It should be understood that the second preset duration mentioned above can be reasonably modified according to specific circumstances, in order to enable the MAP-E tunnel to operate better and the parameters to be updated better and more timely.

[0078] In one embodiment, continue to refer to Figure 6 The MAP-E tunnel configuration management method of the embodiment of the present application may also include the following steps:

[0079] Step S601: When the MAP-E tunnel configuration parameters obtained from the database of the CPE are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, a first HTTP request message is resent to the rule parameter server after a third preset time has elapsed.

[0080] In an embodiment of the present application, when the MAP-E tunnel configuration parameters are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, the obtained MAP-E tunnel configuration parameters are considered to be unavailable and cannot be used to create a MAP-E tunnel. At this time, a third preset time period (e.g., 10 minutes) is set, and after the third preset time period is reached, the process of obtaining the MAP-E tunnel configuration parameters from the rule parameter server is reinitiated. In this way, when the MAP-E tunnel configuration parameters in the rule parameter server are adjusted or changed, the CPE can also make timely adjustments and updates.

[0081] It should be understood that the third preset duration mentioned above can be reasonably modified according to specific circumstances, with the purpose of enabling the MAP-E tunnel to operate better and the parameters to be updated better and more timely.

[0082] In one embodiment, in step S100, after the IPv6 network access channel is established, a notification is sent to the MAP-E module in the CPE, so that the MAP-E module first sends a DHCPv6 request message carrying MAP-E tunnel configuration parameter request information to the broadband remote access server BRAS, and when the DHCPv6 response message sent by the BRAS is not received within a fourth preset time (e.g., 10 minutes), the first HTTP request message carrying MAP-E tunnel configuration parameter request information is sent to the rule parameter server. In this way, when the upper layer device does not have the function of sending MAP-E tunnel configuration parameters through DHCPv6 due to its own reasons, the MAP-E tunnel can be guaranteed to start and run normally.

[0083] It should be understood that the fourth preset duration mentioned above can be reasonably modified according to specific circumstances, with the purpose of enabling the MAP-E tunnel to operate better and the parameters to be updated better and more timely.

[0084] In one embodiment, after the configuration of the MAP-E tunnel is completed and a fifth preset time (eg, 360 minutes) is reached, the first HTTP request message is resent to the rule parameter server.

[0085] It should be understood that the fifth preset duration mentioned above can be reasonably modified according to specific circumstances, with the purpose of enabling the MAP-E tunnel to operate better and the parameters to be updated better and more timely.

[0086] In existing applications, some applications obtain parameters once and update them irregularly. In the embodiment of the present application, the CPE first stores the MAP-E tunnel configuration parameters and also provides a mechanism to ensure that the parameters are periodically triggered and re-requested, and to judge the parameters. If the parameters in the rule parameter server are adjusted or changed, the CPE can also make timely adjustments and updates.

[0087] In addition, an embodiment of the present application also provides a configuration management method for a MAP-E tunnel, such as Figure 7 As shown, Figure 7 It is a flowchart of a configuration management method of a MAP-E tunnel provided by another embodiment of the present application. The configuration management method of the MAP-E tunnel includes but is not limited to step S700 and step S800.

[0088] Step S700: receiving a first HTTP request message sent by a CPE, where the first HTTP request message carries MAP-E tunnel configuration parameter request information;

[0089] In one embodiment, the data in the HTTP request message uses a custom data format, which can be flexibly adjusted and redefined according to actual needs.

[0090] Step S800: Send a first response message carrying MAP-E tunnel configuration parameters to CPE according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, so that CPE configures the MAP-E tunnel according to the MAP-E tunnel configuration parameters in the first response message.

[0091] In one embodiment, referring to Figure 1 As shown, in the embodiment of the present application, a rule parameter server is configured in the network, in which MAP-E tunnel configuration parameters are stored, including: (1) BR Address: MAP-E tunnel peer IPv6 address; (2) IPv6 prefix: IPv6 prefix); (3) IPv6 prefix length: IPv6 prefix length; (4) IPv4 prefix: IPv4 prefix; (5) IPv4 prefix length: IPv4 prefix length; (6) EA-bits-length: Embedded-Address (EA) bit length; (7) PSID: port sequence PORT-SET; (8) PSID Offset: PSID offset; (9) PSID length: PSID length. In one embodiment, according to actual needs, parameters (2)-(9) can be multiple groups.

[0092] In one embodiment, the data in the response message uses a custom data format, which can be flexibly adjusted and redefined according to actual needs.

[0093] Currently, CPE usually completes the acquisition of MAP-E tunnel configuration parameters through Dynamic Host Configuration Protocol DHCPv6 interaction, thereby establishing MAP-E's IPv4 in IPv6 tunnel, and realizing the message reception and sending processing of the HOST host connected to the CPE to access the IPv4 network service. However, when the network device cannot complete the parameter acquisition through DHCPv6 interaction, the MAP-E tunnel cannot be established normally, and the MAP-E tunnel cannot work normally, so it is impossible to realize the access of IPv4 network services to IPv4 through the IPv6 network via the MAP-E tunnel. To address this problem, the embodiment of the present application adopts the above-mentioned steps S700 and S800, and deploys a Rule Server (rule parameter server) in the network. The MAP-E tunnel configuration parameters are stored in the rule parameter server, and MAP-E tunnel configuration parameter request information is sent to the rule parameter server in HTTP message mode. After receiving a response message from the rule parameter server, a MAP-E tunnel is established according to the MAP-E tunnel configuration parameters carried in the response message, thereby ensuring that the MAP-E tunnel is started and runs normally when the upper-layer device does not have the function of issuing the MAP-E tunnel configuration parameters through DHCPv6 due to its own reasons.

[0094] In one embodiment, before receiving the first HTTP request message sent by the CPE, the method further includes:

[0095] A second HTTP request message sent by the CPE is received, the second HTTP request message carrying authentication request information; a second response message is sent to the CPE according to the authentication request information in the second HTTP request message, the second response message carrying information on whether the authentication is successful.

[0096] In the embodiment of the present application, when the HTTP message interaction method is used to obtain the MAP-E tunnel configuration parameters, an authentication interaction message is first sent to the rule parameter server. Only after the authentication is successful can the subsequent steps be performed to prevent other devices in the network from illegally obtaining the rule parameter server.

[0097] In one embodiment, referring to Figure 8 , step S800 includes the following steps:

[0098] Step S801, decrypting the internal data of the first HTTP request message to obtain MAP-E tunnel configuration parameter request information;

[0099] Step S802, allocating MAP-E tunnel configuration parameters to the CPE according to the MAP-E tunnel configuration parameter request information;

[0100] Step S803: encrypt the MAP-E tunnel configuration parameters, and create a first response message according to the encrypted MAP-E tunnel configuration parameters;

[0101] Step S804: Send a first response message to the CPE.

[0102] Different from the current use of plain text to interact with some parameter data, the messages in the embodiments of the present application are sent after being encrypted, which reduces the possibility of tampering or theft during the message sending process, thereby increasing the security and reliability of data transmission.

[0103] In one embodiment, the data in the HTTP request message is encrypted by using a public-private key encryption method. Specifically, at the CPE end, the data in the HTTP request message is encrypted by a private key assigned to the CPE, and the HTTP request message with the internal data encrypted is sent to the rule parameter server, the rule parameter server uses the public key matching the private key to decrypt the data in the HTTP request message, allocates MAP-E tunnel configuration parameters to the CPE according to the decrypted data, encrypts the data in the response message to be sent by using the private key assigned to the rule parameter server, and sends it to the CPE, the CPE decrypts the data in the response message according to the public key matching the private key, and obtains the MAP-E tunnel configuration parameters.

[0104] It should be understood that the above encryption method is only one embodiment of the method of the present application, and the embodiments of the present application may also include other encryption methods, including but not limited to symmetric encryption, asymmetric encryption, hash algorithm, etc.

[0105] Regarding the configuration management method of the MAP-E tunnel provided in the above embodiment, the following reference is made to Figure 9-12 A detailed description is given with specific examples.

[0106] Example 1:

[0107] Reference Fig. 9 As shown, and continue to refer to Figure 1 ,in Fig. 9 This is a general network processing flow chart provided by an embodiment of the present application, including the entire process of establishing a tunnel by a CPE and Internet access initiated by a PC on the LAN side, specifically:

[0108] Step S901, when CPE starts, it first needs to obtain the address, gateway, DNS Server and other information of the IPv6 WAN connection, and obtain the WAN connection parameters by initiating a DHCPv6 (stateful address automatic configuration) or SLAAC (stateless address automatic configuration) request to the BRAS device.

[0109] Step S902: The BRAS device responds and sends parameters, and the CPE starts the IPv6 WAN connection. The CPE then establishes an IPv6 network access channel.

[0110] Step S903: After the IPv6 WAN connection of the CPE is started normally, a notification is sent to the MAP-E module, and then the MAP-E module sends a DHCPv6 message to obtain various parameters for configuring the MAP-E tunnel.

[0111] Step S904: Receive a DHCPv6 response message from the BRAS device, parse the DHCPv6 response message, obtain MAP-E tunnel configuration parameters, create and start a MAP-E tunnel, and then directly enter step S907.

[0112] Step S905: If the DHCPv6 response message of the BRAS device is not obtained in step S904, HTTP acquisition is automatically enabled again, and an HTTP request message is sent to the Rule Server.

[0113] Step S906: The Rule Server receives the request, responds, and sends a response message to the CPE.

[0114] Step S907, the CPE parses the received response message and creates a MAP-E tunnel, where one end of the tunnel is the CPE and the far end is the BR edge router, thus establishing a MAP-E tunnel.

[0115] Step S908, the PC device initiates Internet access and first performs DNS domain name resolution. The DNS domain name resolution request is sent by the PC in the form of an IPv4 "A" record request message. After reaching the CPE, the CPE performs DNS proxy and sends the IPv6 message to the DNS Server in the network through the IPv6 channel.

[0116] Step S909, the DNS Server responds after resolution, and the message is then returned to the PC via the CPE in the form of an "A" record response in the form of an IPv4 message.

[0117] In step S910, the PC device initiates an access connection in the form of TCP or UDP according to the resolved IP address. After the sent IPv4 message reaches the CPE, it is encapsulated in the MAP-E tunnel. The encapsulation method is: after NAT (network address translation) is performed on the IPv4 message, an IPv6 message header is added to form an IPv6 message, and the encapsulated message is sent from the tunnel to the BR edge router. The BR edge router decapsulates the message into an IPv4 message and sends it to the target server in the Internet network.

[0118] Step S911: The target server in the Internet network responds, and the message is encapsulated into an IPv6 message by the BR edge router and returned to the CPE via the tunnel. The CPE then decapsulates the message, takes out the IPv4 message and sends it to the PC on the LAN side.

[0119] Step S910 and step S911 are repeated, thus completing the two-way interaction of messages and successfully accessing the Internet network.

[0120] Example 2:

[0121] Reference Fig.10 As shown, and continue to refer to Figure 1 ,in Fig.10 This is a flowchart of starting / stopping a MAP-E tunnel provided by an embodiment of the present application.

[0122] There are two ways to start a MAP-E tunnel: when powered on, after the CPE successfully establishes an IPv6 WAN connection, it notifies the MAP-E module to trigger the creation of a MAP-E tunnel configuration process, or configures a new MAP-E tunnel through a configuration medium (WEB page or remote management). First, it triggers the acquisition of MAP-E tunnel parameters. The CPE can automatically obtain them using DHCPv6 or HTTP script according to the network conditions.

[0123] After obtaining the MAP-E tunnel configuration parameters, verify the parameters. If the parameters are normal, establish the MAP-E tunnel and configure them to the kernel to enable the normal operation of the MAP-E tunnel.

[0124] There are two ways to go offline for a MAP-E tunnel: deleting an established MAP-E tunnel through a configuration medium (WEB page or remote management), or going offline due to network abnormalities. This is mainly caused by abnormalities in the status of the IPv6 WAN connection. For example, if the WAN connection is offline or deleted and the CPE no longer has the ability to access the IPv6 WAN, the MAP-E tunnel offline process will be triggered.

[0125] MAP-E tunnel offline process: When any of the above two methods triggers the MAP-E tunnel offline, MAP-E will be stopped, the MAP-E tunnel configuration parameters configured in the kernel will be cleared, the tunnel will be destroyed and stop running.

[0126] Example 3:

[0127] Reference Fig.11 As shown, and continue to refer to Figure 1 ,in Fig.11 This is a flowchart of automatically obtaining MAP-E tunnel configuration parameters provided by an embodiment of the present application, which specifically includes the following steps:

[0128] Step S1101, the MAP-E module starts and waits for the notification that the IPv6 WAN connection is online normally;

[0129] Step S1102, receiving a notification that the IPv6 WAN connection is online normally, selecting a parameter acquisition method, if it is the first time to run, first use DHCPv6 to obtain, and then you can select which acquisition method is preferred according to the saved acquisition methods.

[0130] Step S1103: The MAP-E module of the CPE sends a DHCPv6 request message to obtain various parameters of MAP-E.

[0131] Step S1104: After receiving the DHCPv6 message responded by the upper layer device, the DHCPv6 module in the CPE notifies the MAP-E module.

[0132] Step S1105: parse the DHCPv6 message to obtain MAP-E tunnel configuration parameters.

[0133] Step S1106: Verify that the MAP-E tunnel configuration parameters are normal and valid, then create and run the MAP-E tunnel.

[0134] Step S1107, the DHCPv6 method, which is the method for successfully acquiring parameters this time, is saved, and this method is selected first for parameter acquisition next time.

[0135] Step S1109. In step S1104, when the upper layer device does not support the DHCPv6 mode for sending parameters, no response message will be returned. The basis for judging the failure of DHCPv6 can be, for example, whether the set DHCPv6 response waiting timer has timed out. When the CPE sends a DHCPv6 request message, a waiting timer is set. After the timer expires, it is considered that the DHCPv6 response has failed. At this time, it automatically selects to obtain the parameters through the script mode, and sends an HTTP request message to the rule parameter server to obtain the parameters.

[0136] Step S1110, the CPE receives an HTTP response message from the rule parameter server.

[0137] Step S1111, parse the HTTP response message, extract various parameters, and proceed to step S1106 to create a MAP-E tunnel.

[0138] Similarly, in step S1107, the method for successfully acquiring parameters this time - the HTTP message interaction method - is saved, and this acquisition method is first selected for parameter acquisition next time.

[0139] Example 4:

[0140] Reference Fig.12As shown, and continue to refer to Figure 1 ,in Fig.12 This is a flowchart of obtaining and maintaining MAP-E tunnel configuration parameters by HTTP in an embodiment of the present application. The MAP-E tunnel in the embodiment of the present application needs to obtain MAP-E tunnel configuration parameters before it is created and run. The embodiment of the present application obtains MAP-E tunnel configuration parameters by using a script HTTP message interaction method. For this method, a set of mechanisms is also established, that is, using a state machine mechanism to maintain the obtained parameters and update the parameters in time, which specifically includes the following steps:

[0141] Step S1201, the maintenance management module is started, and the maintenance management runs normally.

[0142] Step S1202, when the script HTTP message interaction mode is selected to obtain MAP-E tunnel configuration parameters, an authentication interaction message is first made to the rule parameter server. Only after the authentication is successful can the subsequent steps be performed to prevent other devices in the network from illegally obtaining the rule parameter server.

[0143] Step S1203: To ensure data security, the internal data of the HTTP request message and the response message are encrypted, and the data is decrypted using a secret key after reaching the other end.

[0144] Step S1204: The maintenance management module initiates acquisition of MAP-E tunnel configuration parameters and sends an HTTP request message.

[0145] Step S1205, wait for the rule parameter server to send a reply message, set a timer, and when a reply message is received within the timer, it is considered that the reply message is obtained, and enter step S1206; if the reply message is not received after the timeout, it is considered that the reply message has failed to be obtained, and enter step S1211.

[0146] Step S1206: successfully receive the response message sent back by the rule parameter server, parse the response message, and retrieve all MAP-E tunnel configuration parameters according to the parameter structure definitions at both ends.

[0147] Step S1207, check whether the parameters are normal and valid, and whether they match the prefix and other information corresponding to the currently running WAN IPv6 connection successfully. If so, go to step S1208; if the parameter check fails, or the parameters do not successfully match the WAN IPv6 connection parameters, go to step S1214.

[0148] Step S1208, verify the parameters and match successfully. If the original MAP-E tunnel has not been created, create a new MAP-E tunnel. If the original MAP-E tunnel already exists, compare whether the parameters have been updated. If the parameters have changed, update the parameters and apply them to the MAP-E tunnel. Otherwise, keep the existing MAP-E tunnel configuration parameters running.

[0149] Step S1209: Save the new MAP-E tunnel configuration parameters of step S1206 to the database.

[0150] Step S1210, set timer 1 (for example: 360 minutes), and after reaching timer 1, re-acquire the MAP-E tunnel configuration parameters, that is, return to step S1204. The purpose of this is to be able to obtain the updated parameters in time and apply them to the running MAP-E tunnel when the parameters in the network are adjusted and updated.

[0151] Step S1211: when no response is received from the rule parameter server in step S1205, the MAP-E tunnel configuration parameters are read from the database stored in the CPE itself.

[0152] Step S1212, read out the MAP-E tunnel configuration parameters, verify that the parameters are normal and valid and match the prefix and other information corresponding to the currently running WAN IPv6 connection, then perform the MAP-E tunnel creation process and directly enter step S1208.

[0153] Step S1213: In step S1212, if there are no saved MAP-E tunnel configuration parameters or the read MAP-E tunnel configuration parameters are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, set timer 2 (for example, 5 minutes). After reaching timer 2, obtain the MAP-E tunnel configuration parameters again, that is, return to step S1204.

[0154] Step S1214: In step S1207, if the MAP-E tunnel configuration parameters obtained from the rule parameter server are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, it is considered that the parameters are unavailable and the MAP-E tunnel cannot be created. In this case, a timer 3 (e.g., 10 minutes) is set. After reaching the timer 3, the MAP-E tunnel configuration parameters are obtained again, that is, the process returns to step S1204.

[0155] Each time duration of the above-mentioned setting timers 1, 2, and 3 can be reasonably modified according to specific circumstances, in order to make the MAP-E tunnel run better and the MAP-E tunnel configuration parameters be updated better and more timely.

[0156] In addition, an embodiment of the present application provides a user front-end device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the configuration management method of the MAP-E tunnel of the above embodiment through the computer program, for example, executing the above described Figure 2 The method steps S100 to S300, Figure 3 Steps S101-S102 of the method, Figure 4 Method steps S301-S302, Figure 5 The method steps S100 to S400, Figure 6 Method steps S500, S600 and S601 in.

[0157] In addition, an embodiment of the present application provides a rule parameter server, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the configuration management method of the MAP-E tunnel of the above embodiment through the computer program, for example, executing the above described Figure 7 Steps S700 to S800 of the method, Figure 8 Method steps S801-S804 in.

[0158] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0159] In addition, an embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions, which are executed by a processor or a controller, for example, by a processor in the above-mentioned user front-end device embodiment or a rule parameter server embodiment, so that the above-mentioned processor can execute the configuration management method of the MAP-E tunnel in the above-mentioned embodiment, for example, execute the above-mentioned Figure 2 The method steps S100 to S300, Figure 3 Steps S101-S102 of the method, Figure 4 Method steps S301-S302, Figure 5 The method steps S100 to S400, Figure 6 In the method steps S500, S600 and S601, or performing the above described Figure 7 Steps S700 to S800 of the method, Figure 8 Method steps S801-S804 in.

[0160] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0161] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions without violating the spirit of the present application. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A configuration management method for a MAP-E tunnel, applied to a user front-end device CPE, comprising: Sending a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server, wherein the rule parameter server is used to pre-store MAP-E tunnel configuration parameters; receiving a first response message sent by a rule parameter server according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, wherein the first response message includes the MAP-E tunnel configuration parameter; A MAP-E tunnel is configured based on the MAP-E tunnel configuration parameters in the first response message.

2. A MAP-E tunnel configuration management method according to claim 1, characterized in that: Before sending the first HTTP request message to the rule parameter server, the method further includes: Sending a second HTTP request message to the rule parameter server, where the second HTTP request message carries authentication request information; Receive a second response message sent by the rule parameter server according to the authentication request information in the second HTTP request message, where the second response message carries information on whether the authentication is successful.

3. A MAP-E tunnel configuration management method according to claim 1, characterized in that: The sending of a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server includes: Encrypting the MAP-E tunnel configuration parameter request information, and establishing a first HTTP request message according to the encrypted MAP-E tunnel configuration parameter request information; Send the first HTTP request message to the rule parameter server.

4. A MAP-E tunnel configuration management method according to claim 3, characterized in that: The configuring the MAP-E tunnel based on the MAP-E tunnel configuration parameters in the first response message includes: decrypting the internal data of the first response message to obtain the MAP-E tunnel configuration parameter; A MAP-E tunnel is configured according to the MAP-E tunnel configuration parameters.

5. A MAP-E tunnel configuration management method according to claim 4, characterized in that: The configuring the MAP-E tunnel according to the MAP-E tunnel configuration parameters includes: When the MAP-E tunnel configuration parameters are determined to be valid and to match the current network connection parameters, the MAP-E tunnel is configured using the MAP-E tunnel configuration parameters.

6. A MAP-E tunnel configuration management method according to claim 4, characterized in that: The configuring the MAP-E tunnel according to the MAP-E tunnel configuration parameters further includes: When the MAP-E tunnel configuration parameters are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, the first HTTP request message is resent to the rule parameter server after a first preset time has elapsed.

7. A MAP-E tunnel configuration management method according to claim 1, characterized in that: Also includes: The MAP-E tunnel configuration parameters are updated into the database of the CPE.

8. A MAP-E tunnel configuration management method according to claim 7, characterized in that: Also includes: When the first response message sent by the rule parameter server is not received within a second preset time period, acquiring the MAP-E tunnel configuration parameter from a database of the CPE; When the MAP-E tunnel configuration parameters obtained from the database of the CPE are determined to be valid and are determined to match the current network connection parameters, the MAP-E tunnel configuration parameters are used to configure the MAP-E tunnel.

9. A MAP-E tunnel configuration management method according to claim 8, characterized in that: Also includes: When the MAP-E tunnel configuration parameters obtained from the database of the CPE are determined to be invalid and / or determined to be inconsistent with the current network connection parameters, the first HTTP request message is resent to the rule parameter server after a third preset time has elapsed.

10. A MAP-E tunnel configuration management method according to claim 1, characterized in that: The sending of a first HTTP request message carrying MAP-E tunnel configuration parameter request information to a rule parameter server includes: Sending a DHCPv6 request message carrying MAP-E tunnel configuration parameter request information to the broadband remote access server BRAS; When no DHCPv6 response message sent by the BRAS is received within the fourth preset time period, a first HTTP request message carrying MAP-E tunnel configuration parameter request information is sent to the rule parameter server.

11. A MAP-E tunnel configuration management method according to any one of claims 1 to 10, characterized in that: Also includes: After the configuration of the MAP-E tunnel is completed and the fifth preset time period has expired, the first HTTP request message is resent to the rule parameter server.

12. A configuration management method for a MAP-E tunnel, applied to a rule parameter server, wherein: The rule parameter server is used to pre-store MAP-E tunnel configuration parameters, including: receiving a first HTTP request message sent by a CPE, wherein the first HTTP request message carries MAP-E tunnel configuration parameter request information; A first response message carrying the MAP-E tunnel configuration parameters is sent to the CPE according to the MAP-E tunnel configuration parameter request information in the first HTTP request message, so that the CPE configures the MAP-E tunnel according to the MAP-E tunnel configuration parameters in the first response message.

13. A MAP-E tunnel configuration management method according to claim 12, characterized in that: Before receiving the first HTTP request message sent by the CPE, the method further includes: receiving a second HTTP request message sent by the CPE, wherein the second HTTP request message carries authentication request information; A second response message is sent to the CPE according to the authentication request information in the second HTTP request message, wherein the second response message carries information on whether the authentication is successful.

14. A MAP-E tunnel configuration management method according to claim 12, characterized in that: The sending a first response message carrying the MAP-E tunnel configuration parameters to the CPE according to the MAP-E tunnel configuration parameter request information in the first HTTP request message includes: decrypting the internal data of the first HTTP request message to obtain the MAP-E tunnel configuration parameter request information; Allocate MAP-E tunnel configuration parameters to the CPE according to the MAP-E tunnel configuration parameter request information; Encrypting the MAP-E tunnel configuration parameters, and establishing a first response message according to the encrypted MAP-E tunnel configuration parameters; Send the first response message to the CPE.

15. A user front-end device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: The processor executes the MAP-E tunnel configuration management method according to any one of claims 1 to 11 through the computer program.

16. A rule parameter server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: The processor executes the MAP-E tunnel configuration management method according to any one of claims 12 to 14 through the computer program. 17 . A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the configuration management method of the MAP-E tunnel according to any one of claims 1 to 11 or the configuration management method of the MAP-E tunnel according to any one of claims 12 to 14.

Images