A method for making CPE self-adapt to ACS

Abstract

The invention provides a method for making a CPE self-adapt to an ACS, which relates to the field of communication technology and comprises the following steps: S1, monitoring the IP address of a TR-069 management interface of a CPE through a Netlink protocol, generating a valid HTTP connection request URL, and making the ACS initiate a connection request to the CPE, wherein the TR-069 management interface is a network card that carries TR-069 data; S2, the CPE, as a client, resolves the IP address of the ACS according to a domain name, creates a corresponding socket, regularly initiates an HTTP connection request session to the ACS, and reports basic information of the CPE to the ACS, wherein the basic information includes the HTTP connection request URL and events occurring during the period, the ACS returns response information, and the HTTP connection is disconnected after the session ends; S3, the CPE, as a server, creates a socket compatible with IPv4 and IPv6, and when the CPE is operated, the ACS immediately initiates a connection request to the HTTP connection request URL of the CPE, actively connects to the CPE, the CPE actively initiates a session, and reports a "6CONNECTION REQUEST" event and response information to the ACS, thereby realizing self-adaptation of the CPE to the ACS.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method for enabling a CPE to adapt to an ACS. Background Art

[0002] The TR-069 protocol defines a new network management system structure, including management modules, interactive interfaces and basic management parameters, which can effectively manage home network terminal devices. The management server in the network management model is called the automatic configuration server (ACS), which is responsible for the unified management of customer terminal equipment (CPE). By applying this protocol, operators can realize the automatic configuration and installation of CPE, control the dynamic change of service parameters, monitor the status and performance of user equipment in real time, and simply locate equipment failures, etc., to ensure service quality and reduce maintenance costs.

[0003] The communication between CPE and ACS follows the C / S architecture, but it is not fixed that CPE acts as client and ACS acts as server. Their roles depend on who initiates the connection request first. The client initiates the connection request, while the server listens to the request. This design ensures the subordinate relationship between CPE and ACS. In order to ensure smooth communication between CPE and ACS, CPE needs to configure the URL, username, password and other information of ACS. It also needs to carry its own URL, i.e., the connection request URL, for ACS to use each time it informs. For IPv4 ACS, CPE behind the gateway also needs to enable STUN for gateway penetration.

[0004] In the current design, CPE will be adapted to each operator's ACS to generate an available connection request URL. For manufacturers supplying to multiple operators, such a design requires a lot of manpower and time costs from development to testing. Therefore, a solution that can make CPE adaptive to ACS is needed to reduce the cost of use. The design of adaptive ACS does not need to consider whether the operator's ACS is IPv4 or IPv6, whether it supports STUN, and other information. Once the CPE is configured with the ACS URL, username, and password, it will automatically generate an available connection request URL based on the URL and determine whether to start STUN. Developers do not need to adapt due to changes or upgrades to ACS, and testers do not need to repeatedly test this part of the function, which not only saves manpower and time costs, but also reduces the version maintenance cost from the perspective of software version, which is conducive to improving version stability. Summary of the invention

[0005] In order to overcome the deficiencies of the prior art, the present invention provides a method for enabling a CPE to adapt to an ACS, so as to solve the above technical problems.

[0006] The technical method adopted by the present invention to solve the technical problem is: a method for making CPE adaptive to ACS, and the improvement thereof is that it comprises the following steps: S1, through the Netlink protocol, the IP address of the TR-069 management interface of the CPE is monitored, and a valid HTTP connection request URL is generated, so that the ACS initiates a connection request to the CPE, the TR-069 management interface is the network card carrying TR-069 data, the URL is the Uniform Resource Locator, the ACS is the automatic configuration server, and the CPE is the user terminal equipment; S2, the CPE, as a client, resolves the IP address of the ACS according to the domain name, creates a corresponding socket, regularly initiates an HTTP connection request session to the ACS, and reports basic information of the CPE to the ACS, the basic information includes the HTTP connection request URL and events occurring during the period, the ACS returns response information, and the HTTP connection is disconnected after the session ends; S3, the CPE, as a server, creates a socket compatible with IPv4 and IPv6, when the CPE is operated, the ACS immediately initiates a connection request to the HTTP connection request URL of the CPE, actively connects to the CPE, the CPE actively initiates a session, and reports "6CONNECTION REQUEST" event and response information to ACS.

[0007] In the above method, step S1 comprises the following steps:

[0008] S11. Initialize the Netlink protocol to RTM_GETADDR type, indicating that the TR-069 process requests an IP address. When the IP address of the CPE changes, the kernel sends a Netlink message related to the IP address to the TR-069 process.

[0009] S12, determining the IP address type of the HTTP connection request URL, constructing a Netlink message requesting the IP address and sending it to the kernel, actively obtaining the IP address when the CPE is started for the first time, and generating the HTTP connection request URL;

[0010] S13, receiving and parsing the IP used to generate the HTTP connection request URL in the Netlink message;

[0011] S14. Generate an HTTP connection request URL according to the URL format.

[0012] In the above method, step S12 comprises the following steps:

[0013] S121. Determine the TR-069 management interface on the CPE according to the URL and routing information of the ACS in the configuration information;

[0014] S122. Obtain the IP address type supported by the TR-069 management interface on the CPE, and determine the IP address type supported by the TR-069 management interface. If it is IPv4 or IPv6, the IP address type of the HTTP connection request URL is the same as the IP address type supported by the management interface. If it is IPv4 / IPv6, the domain name is resolved to the URL of the ACS to obtain the IP address type of the ACS. The IP address type of the HTTP connection request URL is the same as the IP address type of the ACS.

[0015] S123. Construct a Netlink message using the IP address type of the HTTP connection request URL and send it to the kernel.

[0016] In the above method, step S13 comprises the following steps:

[0017] S131, determine whether the type of the Netlink message is RTM_NEWADDR and RTM_DELADDR, if so, re-collect, if not, jump to step S132;

[0018] S132, judging whether the network card name in the Netlink message is consistent with the TR-069 management interface, if not, discarding the message and continuing to judge the next one until they are consistent, if they are consistent, jumping to step S133;

[0019] S133, determine whether the Scope attribute in the Netlink message is Link, if so, discard it, if not, jump to step S134;

[0020] S134. Determine whether the IP address in the Netlink message is consistent with the IP address type of the HTTP connection request URL. If not, discard it. If consistent, the current IP address is the IP used to generate the HTTP connection request URL.

[0021] The beneficial effects of the present invention are: the CPE device can be used for both the ACS under the local area network and the ACS of IPv4 and IPv6, thereby realizing the self-adaptation of the CPE to the ACS, reducing the manpower cost and time cost of the manufacturer, and improving the stability of product use. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Attached Figure 1 The figure is a flow chart of a method for enabling CPE to adapt to ACS according to the present invention. DETAILED DESCRIPTION

[0023] The present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0024] The following will clearly and completely describe the concept, specific structure and technical effects of the present invention in combination with the embodiments and drawings, so as to fully understand the purpose, characteristics and effects of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, other embodiments obtained by technicians in this field without creative work are all within the scope of protection of the present invention. In addition, all the connection / connection relationships involved in the patent do not refer to the direct connection of components, but refer to the formation of a better connection structure by adding or reducing connection accessories according to the specific implementation situation. The various technical features in the invention can be combined interchangeably without conflicting with each other.

[0025] Reference Figure 1 A method for enabling a CPE to adapt to an ACS according to the present invention comprises the following steps:

[0026] S1. Through the Netlink protocol, monitor the IP address of the TR-069 management interface of the CPE and generate a valid HTTP connection request URL for the ACS to initiate a connection request to the CPE. The TR-069 management interface is the network card that carries the TR-069 data. The URL is the Uniform Resource Locator. The ACS is the automatic configuration server. The CPE is the user terminal equipment. Netlink is a network-based communication mechanism provided by Linux that allows communication between the kernel and the user-mode process.

[0027] Specifically, the following steps are included:

[0028] S11. Initialize the Netlink protocol to RTM_GETADDR type, indicating that the TR-069 process requests an IP address. Once the IP address of the CPE changes, the kernel will send a Netlink message related to the IP address to the TR-069 process. The RTM_GETADDR type is a message type of the Netlink protocol, which is sent by the user process to the kernel to obtain the IP information of the device.

[0029] S12, determine the IP address type of the HTTP connection request URL, construct a Netlink message requesting the IP address and send it to the kernel, so that the IP address can be actively obtained when the CPE is started for the first time, and the HTTP connection request URL can be generated, rather than waiting for the IP address to change before obtaining it;

[0030] Specifically, the following steps are included:

[0031] S121. Determine the TR-069 management interface on the CPE according to the URL and routing information of the ACS in the configuration information;

[0032] S122. Obtain the IP address type supported by the TR-069 management interface on the CPE, and determine the IP address type supported by the TR-069 management interface. If it is IPv4 or IPv6, the IP address type of the HTTP connection request URL is the same as the IP address type supported by the management interface. If it is IPv4 / IPv6, the domain name is resolved to the URL of the ACS to obtain the IP address type of the ACS. The IP address type of the HTTP connection request URL is the same as the IP address type of the ACS. IPv4 / IPv6 refers to IPv4 and IPv6. At this time, the TR-069 management interface supports both IPv4 and IPv6.

[0033] S123. Construct a Netlink message using the IP address type of the HTTP connection request URL and send it to the kernel.

[0034] S13, receiving and parsing the IP used to generate the HTTP connection request URL in the Netlink message;

[0035] Specifically, the following steps are included:

[0036] S131. Determine whether the type of the Netlink message is RTM_NEWADDR or RTM_DELADDR. If yes, collect it again. If not, jump to step S132. RTM_NEWADDR is a message type of the Netlink protocol, which is sent by the kernel to the user process, indicating that the IP message is newly created by the device. RTM_DELADDR is a message type of the Netlink protocol, which is sent by the kernel to the user process, indicating that the IP message is deleted by the device.

[0037] S132, judging whether the network card name in the Netlink message is consistent with the TR-069 management interface, if not, discarding the message and continuing to judge the next one until they are consistent, if they are consistent, jumping to step S133;

[0038] S133, determine whether the Scope attribute in the Netlink message is Link, if so, discard it, if not, jump to step S134, Scope is used to indicate the reachable range of the IP address in the message, Link is one of the Scopes, indicating that the IP address in the message is only meaningful within the local area network;

[0039] S134, judging whether the IP address in the Netlink message is consistent with the IP address type of the HTTP connection request URL, if not, discarding it, if consistent, the current IP address is the IP used to generate the HTTP connection request URL;

[0040] S14. Generate an HTTP connection request URL according to the URL format.

[0041] S2, CPE as a client, according to the domain name to resolve the ACS IP address, create a corresponding socket, regularly initiate HTTP connection request session to ACS, report the basic information of CPE to ACS, the basic information includes the HTTP connection request URL and the events that occurred during the period, ACS returns the response information, after the session ends, the HTTP connection is disconnected; at this time, if the administrator wants to operate CPE through ACS, such as restarting CPE, it is necessary to wait until the scheduled time is up to get the response of CPE, so that the administrator can know whether the operation is successful. In order to get a response in time, the following step S3 is also required;

[0042] The period refers to the time period of this timing, that is, the period from the end of the last session until the timing time is exhausted and then the current session is initiated.

[0043] S3, CPE as the server, creates a socket compatible with IPv4 and IPv6. When the administrator operates CPE, ACS immediately initiates a connection request to the HTTP connection request URL of CPE, actively connects to CPE, CPE actively initiates a session, reports the "6CONNECTION REQUEST" event and response information to ACS, and ends the session. "6CONNECTION REQUEST" is defined by the TR-069 protocol, indicating that ACS has initiated a "6th connection request" event to CPE, and then CPE reports it to ACS to let ACS know the reason why CPE is connecting to ACS this time. It is realized that CPE equipment can be used for ACS under LAN, and can also be used for ACS of IPv4 and IPv6, thus achieving self-adaptation.

[0044] The present invention enables the CPE device to be used for both the ACS in the local area network and the ACS in IPv4 and IPv6, thereby realizing the self-adaptation of the CPE to the ACS, reducing the manpower cost and time cost of the manufacturer, and improving the stability of product use.

[0045] The above is a specific description of the preferred implementation of the present invention, but the invention is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A method for enabling a CPE to adapt to an ACS, characterized in that: The steps include: S1. Monitor the IP address of the TR-069 management interface of the CPE through the Netlink protocol, generate a valid HTTP connection request URL, and enable the ACS to initiate a connection request to the CPE. The TR-069 management interface is the network card that carries the TR-069 data, the URL is the Uniform Resource Locator, the ACS is the automatic configuration server, and the CPE is the user terminal equipment, wherein the TR-069 management interface is determined by the URL and routing information of the ACS in the configuration information, including: S11. Initialize the Netlink protocol to the RTM_GETADDR type, indicating that the TR-069 process requests an IP address. When the IP address of the CPE changes, the kernel sends a Netlink message related to the IP address to the TR-069 process; S12. Determine the IP address type of the HTTP connection request URL, construct a Netlink message requesting the IP address and send it to the kernel, actively obtain the IP address when the CPE is started for the first time, and generate the HTTP connection request URL; S13. Receive and parse the IP used to generate the HTTP connection request URL in the Netlink message; S14. Generate the HTTP connection request URL according to the format of the URL; S2. As a client, CPE resolves the IP address of ACS according to the domain name, creates a corresponding socket, regularly initiates HTTP connection request session to ACS, and reports basic information of CPE to ACS, which includes the HTTP connection request URL and events that occur during the period. ACS returns response information, and the HTTP connection is disconnected after the session ends. S3. CPE acts as a server and creates a socket compatible with IPv4 and IPv6. When operating CPE, ACS immediately initiates a connection request to the HTTP connection request URL of CPE, actively connects to CPE, and CPE actively initiates a session and reports a "6CONNECTIONREQUEST" event and response information to ACS.

2. A method for making a CPE self-adapt to an ACS as claimed in claim 1, characterized in that: The step S12 comprises the following steps: S121. Determine the TR-069 management interface on the CPE according to the URL and routing information of the ACS in the configuration information; S122. Obtain the IP address type supported by the TR-069 management interface on the CPE, and determine the IP address type supported by the TR-069 management interface. If it is IPv4 or IPv6, the IP address type of the HTTP connection request URL is the same as the IP address type supported by the management interface. If it is IPv4 / IPv6, the domain name is resolved to the URL of the ACS to obtain the IP address type of the ACS. The IP address type of the HTTP connection request URL is the same as the IP address type of the ACS. S123. Construct a Netlink message using the IP address type of the HTTP connection request URL and send it to the kernel.

3. A method for making a CPE self-adapt to an ACS as claimed in claim 2, characterized in that: The step S13 comprises the following steps: S131, determine whether the type of the Netlink message is RTM_NEWADDR and RTM_DELADDR, if so, re-collect, if not, jump to step S132; S132, judging whether the network card name in the Netlink message is consistent with the TR-069 management interface, if not, discarding the message and continuing to judge the next one until they are consistent, if they are consistent, jumping to step S133; S133, determine whether the Scope attribute in the Netlink message is Link, if so, discard it, if not, jump to step S134; S134. Determine whether the IP address in the Netlink message is consistent with the IP address type of the HTTP connection request URL. If not, discard it. If consistent, the current IP address is the IP used to generate the HTTP connection request URL.

Images