A communication method, system and storage medium based on TR069 protocol

Abstract

The present invention relates to the field of communication and data exchange technology, and in particular to a communication method, system and storage medium based on the TR069 protocol. The method of the present invention discloses a communication method based on the TR069 protocol, comprising: CPE (Customer Premises Equipment, i.e., user-side terminal equipment) reporting information to ACS (Auto Configuration Server, automatic configuration server) or requesting the services that the current CPE needs to process; ACS saving the reported information or requested information, and judging whether it is necessary to send the services to the current CPE in a preset order according to the type of services that the current CPE needs to process; after the CPE executes the services, it reports the results of the services to the ACS again or requests them. A specific implementation method for communication based on the TR069 protocol is provided, which is also highly efficient.

Description

Technical Field

[0001] The present invention relates to the technical field of communication and data exchange, and in particular to a communication method, system and storage medium based on the TR069 protocol. Background Art

[0002] As internet access methods continue to grow and diversify, including modems, routers, gateways, set-top boxes, and VOIP phones, end-user configuration and usage environments are becoming increasingly complex and diverse. In this context, efficiently managing these diverse end-user devices has become a critical issue. Traditional on-site installation, commissioning, and configuration methods are not only inefficient but also costly. Traditional remote management methods, such as Telnet, SSH, SNMP, and remote web login, are inadequate when faced with issues such as multi-vendor devices, changing device addresses, terminals behind NAT gateways, and unreliable UDP transmission. These methods are unable to achieve automated batch management of large numbers of CPEs (customer-side equipment). To address these issues, the DSL Forum (now renamed the Broadband Forum) launched the TR069 protocol in May 2004, aiming to provide an effective WAN management solution for customer premises equipment.

[0003] However, TR069 only defines general specifications and some RPC methods, without providing implementation methods for specific business scenarios. Publicly available information only describes the business processing carried out through TR069, without providing a detailed implementation of TR069. Based on this, we implemented our own TR069 system in our specific business system and proposed a specific implementation system and method. Summary of the Invention

[0004] In view of the deficiencies in the prior art, the present invention provides a communication method, system and storage medium based on the TR069 protocol, which are used to specifically implement the system and method of the TR069 protocol.

[0005] The present invention discloses, through an embodiment, a communication method based on the TR069 protocol, including: a customer premises equipment (CPE) sends a request to a Stun server to resolve the CPE's public network mapping IP and port; the Stun server returns the data to the CPE after the resolution is complete; and the CPE then reports its public network mapping IP and port to an Auto Configuration Server (ACS). Due to the complexity and diversity of networks, the CPE may be located on an intranet, preventing the external requester, the ACS, from notifying the CPE. Therefore, it is necessary for the CPE to report the CPE's public network mapping IP and port to the ACS so that the ACS can proactively notify the CPE. The CPE sends a request to the Stun server, which resolves the CPE's public network mapping IP and port and returns them to the CPE. The CPE then reports the IP and port to the ACS. The CPE reports information to the ACS or requests services that the CPE currently needs to process. The ACS saves the reported or requested information and, based on the type of service the CPE currently needs to process, determines whether product-level configuration services need to be executed. It further queries whether the current device has device-level services. After executing the service, the CPE reports the results of the service to the ACS again. It is worth noting that in this method, each session establishment under the TR069 protocol is initiated by the CPE by initiating an Inform request with an event code to inform the ACS of the information reported by the CPE and the service that the CPE currently needs to process. This is considered active reporting and requesting.

[0006] Furthermore, the method further includes: the ACS sending a UDP message to the CPE via the Stun server; after the CPE receives the UDP message, the CPE reports information to the ACS or requests services that the CPE needs to process.

[0007] Furthermore, the CPE reports information to the ACS or requests services that the CPE currently needs to process, including: the CPE sends an HTTPS session request to the ACS. If the HTTPS session request passes authentication, the ACS determines whether the CPE meets the currently configured product-level configuration requirements. If so, the HTTPS session request is processed after updating the product-level configuration of the user-side terminal device. If not, the HTTPS session request is processed directly. It is worth noting that authentication here involves the ACS receiving the request and verifying the authentication information. If verification fails, the ACS returns a 401 authorization message; if verification passes, subsequent actions can be taken.

[0008] Furthermore, the conditions for determining whether a CPE complies with the currently configured product-level configuration include determining whether devices within the CPE's system have undergone a device reboot or reset, and / or determining whether the CPE is meeting its first ACS session. Specifically, common configurations for devices within a product or region, such as the STUN server address and NTP server address, are configured. These configurations primarily perform product-level initialization on devices when they first access the ACS, are reset, or are rebooted. Product-level configuration is required during a reboot because common configurations, such as STUN addresses, may change and are then transmitted to the CPE upon reboot.

[0009] Furthermore, the ACS saves the CPE reported information or requested information, and determines whether the current device needs to perform product-level configuration services based on the current CPE reported information or request, and further queries whether the current device has device-level services including:

[0010] (1) If the CPE currently reports a reset or restart event, the CPE needs to perform global product-level configuration services;

[0011] (2) Next, the ACS will check whether the current CPE has device-level services that need to be executed. If so, it will issue the device-level services in order of priority and time.

[0012] Furthermore, the preset order includes service priority or service creation time. It's worth noting that in the aforementioned device-level services, device operations generate individual services. For example, if the CPE wants to execute a service as quickly as possible, and because all sessions require the CPE to establish them, the ACS must proactively notify the CPE to establish a session. This notification is done through the STUN server used by the CPE, which sends a UDP message to the CPE. The CPE proactively reports information to the ACS or requests services that the CPE needs to process. It's worth noting that services are delivered to the CPE in a preset order. For example, a device may have multiple services to execute. The ACS's policy for notifying the CPE of these services is based on priority and creation time. If the executed service A belongs to two sessions, the current session will be terminated after the CPE completes the service. After the CPE completes service A, it will establish a new session to notify the ACS of the completion of service A. The ACS will then execute the remaining transactions in A and, after completion, notify the CPE of service B, and so on for the next session.

[0013] Furthermore, after the CPE completes the service, it reports the service results to the ACS again or requests information about the service results. This includes: after the CPE completes the service, if the service spans two sessions, a new report or request is initiated; if the service spans a single session, the service results are accompanied by a completion flag, and the information or request is then reported to the ACS again. Because the CPE actively establishes a connection with the ACS for each session, the ACS allocates the service to the CPE after the CPE reports information or requests to the ACS for the first time. After the CPE completes the service, it must report information or request to the ACS again, with a completion flag. Under the TR069 protocol, this includes an event number 8 and the service ID number.

[0014] The relationship between the Stun server and the ACS is designed to be highly concurrent in the present invention and can be elastically scaled according to the business.

[0015] In order to achieve the above object, the present invention also provides a communication system based on the TR069 protocol, which includes: a CPE user side terminal device, an ACS automatic configuration server and a Stun server;

[0016] The CPE user-side terminal device communicates with the STUN server, the CPE user-side terminal device communicates with the ACS automatic configuration server, and the ACS automatic configuration server communicates with the STUN server;

[0017] The CPE user-side terminal device is used to report information to the ACS automatic configuration server or request services that the current CPE needs to process;

[0018] The ACS server is used to store reported or requested information and determine whether to deliver services to the current CPE in a preset order based on the type of services that the current CPE needs to process.

[0019] The Stun server is used to parse the public network mapping IP and port requests of the CPE and return the parsing results to the CPE.

[0020] It's worth noting that this system uses RPC (Remote Procedure Call) methods based on the services being implemented and the basic methods provided by TR069. While some services don't use corresponding RPC methods, the goal is to use the smallest set of methods possible while still adhering to the specification, thereby simplifying implementation. For example, for file downloads, this system doesn't use TR069's Download + Transfer Complete. Instead, it uses the TR069 protocol's Set Parameter Values ​​+ Get Parameter Values.

[0021] In order to achieve the above object, the present invention further provides a storage medium containing a plurality of computer instructions for executing the communication method based on the TR069 protocol as described above.

[0022] Compared with the existing TR069 communication protocol, the present invention has the following beneficial effects: it provides a set of specific implementation methods and systems based on the TR069 protocol, which can more simply implement the communication between the CPE and the ACS. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solution of the present invention and facilitate a further understanding of the technical effects, technical features and purposes of the present invention, the present invention is described in detail below in conjunction with the accompanying drawings. The accompanying drawings constitute an essential part of the specification and are used together with the embodiments of the present invention to illustrate the technical solution of the present invention, but do not constitute a limitation to the present invention.

[0024] Figure 1 A flow chart of the method of the present invention;

[0025] Figure 2 A timing diagram of the communication between the CPE and the ACS described in the method of the present invention;

[0026] Figure 3 TR069 protocol stack described in the method of the present invention;

[0027] Figure 4 The minimum RPC method described in the method of the present invention;

[0028] Figure 5 A flowchart of the CPE and ACS session execution described in the method of the present invention;

[0029] Figure 6 The core logic diagram of the method of the present invention;

[0030] Figure 7 This is a system architecture design diagram recorded in the system of the present invention. DETAILED DESCRIPTION

[0031] The present invention will be further described in detail below in conjunction with the accompanying drawings and examples. Of course, the specific embodiments described below are only for explaining the technical solutions of the present invention, and are not intended to limit the present invention. In addition, the parts described in the embodiments or drawings are merely illustrative of the relevant parts of the present invention, and are not intended to be exhaustive. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention should naturally fall within the scope of protection of the present invention.

[0032] like Figure 1 、 2 , 3 and 5, the present invention proposes a communication method based on the TR069 protocol through the following embodiments, including: CPE (Customer Premises Equipment, i.e., user-side terminal equipment) reports information to ACS (AutoConfiguration Server) or requests the services that the current CPE needs to process; ACS saves the reported information or requested information, and determines whether it is necessary to send the services to the current CPE in a preset order according to the type of services that the current CPE needs to process; after the CPE executes the services, it reports the results of the services to ACS again or requests them. It is worth noting that in this method, each session establishment under the TR069 protocol is done by the CPE initiating an Inform request and bringing an event code to inform the ACS to determine the information reported by the CPE and the services that the CPE currently needs to process, which are active reports and requests. Among them, the reported or requested protocol stack data is as follows: Figure 3 As shown,

[0033] like Figure 6 As shown, in this embodiment, the method further includes: the CPE sends a request to the Stun server to resolve the public network mapping IP and port of the CPE, and the Stun server returns data to the CPE after the resolution is completed, and then the CPE reports its public network mapping IP and port to the ACS. Due to the complexity and diversity of the network, the CPE may be on the intranet, resulting in the external requester ACS being unable to notify the CPE, so here it is necessary for the CPE to report the public network mapping IP and port of the CPE to the ACS so that the ACS can actively notify the CPE. The CPE sends a request to the Stun server, and the Stun server resolves the public network mapping IP and port of the CPE and returns them to the CPE, and then the CPE reports the IP and port to the ACS ( Figure 6 The arrows 3 and 4 in the figure can represent this process).

[0034] like Figure 6As shown, in this embodiment, the method further includes: the ACS sends a UDP message to the CPE via the Stun server. After the CPE receives the UDP message, the CPE reports information to the ACS or requests the services that the CPE needs to process. In this method, each device-level service is generated for each device operation. For example, if the CPE is expected to execute services such as restart as soon as possible, and since all sessions need to be established by the CPE, the ACS needs to actively notify the CPE to establish a session. Here, the Stun server used by the CPE sends a UDP message to the CPE to notify the CPE. The CPE actively reports information to the ACS or requests the services that the CPE needs to process ( Figure 6 2 and 4 can represent this process).

[0035] In this embodiment, the CPE reports information to the ACS or requests services that the CPE currently needs to process, including: the CPE sends an HTTPS session request to the ACS. If the HTTPS session request passes authentication, the ACS determines whether the CPE meets the currently configured product-level configuration requirements. If so, the HTTPS session request is processed after updating the product-level configuration of the user-side terminal device. If not, the HTTPS session request is processed directly. It is worth noting that authentication here involves the ACS receiving the request and verifying the authentication information. If verification fails, the ACS returns a 401 authorization message; if verification passes, subsequent actions can be taken.

[0036] In this embodiment, the conditions for determining whether a CPE complies with the currently preset product-level configuration include determining whether devices within the CPE's system have been rebooted or reset, and / or determining whether the CPE is in its first session with an ACS. Specifically, common configurations, such as the STUN server address and NTP server address, are configured for devices within a product or region. These configurations primarily perform product-level initialization on devices when they first access an ACS, are reset, or are rebooted. Product-level configuration is required during a reboot because common configurations, such as STUN addresses, may change and are then provided to the CPE upon reboot.

[0037] In this embodiment, the ACS stores the CPE report information or request information, and determines whether the current device needs to perform product-level configuration services based on the current CPE report information or request, and further queries whether the current device has device-level services including:

[0038] (1) If the CPE currently reports a reset or restart event, the CPE needs to perform global product-level configuration services;

[0039] (2) Next, the ACS will check whether the current CPE has device-level services that need to be executed. If so, it will issue the device-level services in order of priority and time.

[0040] In this embodiment, the preset order includes service priority or service creation time. It's worth noting that in the aforementioned device-level services, each device-level service generated by a device operation, such as a reboot, requires the ACS to proactively notify the CPE to establish a session. This notification is sent through the CPE's STUN server, which sends a UDP message to the CPE. The CPE then proactively reports information to the ACS or requests services that the CPE needs to process. Services are delivered to the CPE in a preset order. For example, a device may have multiple device-level services to execute. The ACS's policy for notifying the CPE of these services is based on priority and creation time. If the executed service A belongs to two sessions, the current session will be terminated after the CPE completes the service. After the CPE completes service A, it will establish a new session to notify the ACS of the completion of service A. The ACS will then execute the remaining transactions in A and, after completion, notify the CPE of service B, continuing the process for the next session.

[0041] In this embodiment, after the CPE completes the service, it reports the service results to the ACS again or requests them again. This includes: after the CPE completes the service, if the service spans two sessions, a new report or request is initiated; if the service spans a single session, the service results are accompanied by a completion flag. Since the CPE actively establishes a connection with the ACS for each session, the ACS allocates the service to the CPE after the CPE reports the service results to the ACS for the first time. After the CPE completes the service, it must report the service results to the ACS again, including a completion flag. In the TR069 protocol, this includes an event number 8 and the service ID number.

[0042] The relationship between the Stun server and the ACS is designed to be highly concurrent in the present invention and can be elastically scaled according to the business.

[0043] like Figure 5 、 6 As shown in FIG. 7 , in order to achieve the above-mentioned purpose, the present invention further provides a communication system based on the TR069 protocol, which includes: a CPE user-side terminal device, an ACS automatic configuration server and a Stun server;

[0044] The CPE user-side terminal device communicates with the STUN server, the CPE user-side terminal device communicates with the ACS automatic configuration server, and the ACS automatic configuration server communicates with the STUN server;

[0045] The CPE user-side terminal device is used to report information to the ACS automatic configuration server or request services that the current CPE needs to process;

[0046] The ACS server is used to store reported or requested information and determine whether to deliver services to the current CPE in a preset order based on the type of services that the current CPE needs to process.

[0047] The Stun server is used to parse the public network mapping IP and port requests of the CPE and return the parsing results to the CPE.

[0048] It is worth noting that if Figure 4 As shown, in this system, RPC (Remote Procedure Call) methods are selected based on the services to be implemented and the basic methods provided by TR069. Some services do not use corresponding RPC methods, but the goal is to use the smallest set of methods possible while complying with the specification to simplify implementation. For example, for file downloading, this system does not use TR069's Download + Transfer Complete. Instead, it uses the TR069 protocol's Set Parameter Values ​​+ Get Parameter Values.

[0049] In order to achieve the above object, the present invention further provides a storage medium containing a plurality of computer instructions for executing the communication method based on the TR069 protocol as described above.

[0050] It should be noted that the above embodiments are only for more clearly illustrating the technical solutions of the present invention. Those skilled in the art will understand that the implementation methods of the present invention are not limited to the above contents, and obvious changes, replacements or substitutions based on the above contents do not exceed the scope covered by the technical solutions of the present invention; other implementation methods will naturally fall within the scope of the present invention without departing from the concept of the present invention.

Claims

1. A communication method based on the TR069 protocol, characterized in that: include: The user-side terminal device sends a request to the Stun server to resolve the public network mapping IP and port of the user-side terminal device. After the Stun server completes the resolution, it returns the data to the user-side terminal device, and then the user-side terminal device reports its public network mapping IP and port to the automatic configuration server; The user-side terminal device reports information to the automatic configuration server or requests services that the current user-side terminal device needs to process; The automatic configuration server saves the reported information or requested information, and determines whether the current device needs to perform product-level configuration services based on the reported information or request of the current user-side terminal device, and further queries whether the current device has device-level services; After the user-side terminal device completes the execution of the service, it reports the result of the service to the automatic configuration server again. The automatic configuration server also sends a UDP message to the user-side terminal device through the Stun server. After receiving the UDP message, the user-side terminal device establishes a new request with the automatic configuration server through an Inform request and performs a complete session interaction.

2. The communication method based on the TR069 protocol as claimed in claim 1, wherein The user-side terminal device reporting information to the automatic configuration server or requesting the current user-side terminal device to process the service includes: The user-side terminal device sends an HTTPS session request to the automatic configuration server. If the HTTPS session request passes the authentication, it is determined whether the user-side terminal device meets the conditions of the currently preset product-level configuration. If so, the HTTPS session request is processed after the product-level configuration of the user-side terminal device is updated. If not, the HTTPS session request is processed directly.

3. The communication method based on TR069 protocol as claimed in claim 2, wherein: The conditions for whether the user-side terminal device meets the currently preset product-level configuration include: Determine whether a device in the system where the user-side terminal device is located meets the requirement of device restart or reset, and / or determine whether the user-side terminal device meets the requirement of conducting a conversation with the automatic configuration server for the first time.

4. The communication method based on the TR069 protocol as claimed in claim 1, wherein The automatic configuration server saves the reported information or requested information, and determines whether the current device needs to perform product-level configuration services based on the reported information or request of the current user-side terminal device, and further queries whether the current device has device-level services including: If the user-side terminal device reports a reset or restart event, it is necessary to process the product-level configuration service; Further judging, if the user-side terminal device has a device-level service to be executed, the service is delivered to the current user-side terminal device according to a preset device-level service sequence.

5. The communication method based on TR069 protocol as claimed in claim 4, wherein: The preset device-level service sequence includes: a priority sequence of the device-level services or a time sequence of creation of the device-level services.

6. The communication method based on TR069 protocol as claimed in claim 1, wherein: After the user-side terminal device completes the execution of the service, reporting the result of the service to the automatic configuration server again or requesting: After the user-side terminal device completes executing the service, if the service spans two sessions, a new reporting information or request needs to be initiated; If the service is a service of a session, a mark indicating that the service processing is completed is added to the result of the service and then the information or request is reported to the automatic configuration server.

7. A communication system based on the TR069 protocol, characterized in that: include: CPE user-side terminal equipment, ACS automatic configuration server and STUN server; The CPE user-side terminal device is in communication with the STUN server, the CPE user-side terminal device is in communication with the ACS automatic configuration server, and the ACS automatic configuration server is in communication with the STUN server; The CPE user-side terminal device is used to report information to the ACS automatic configuration server or request the services that the current user-side terminal device needs to process, and is also used to send a request to the STUN server to resolve the public network mapping IP and port of the user-side terminal device, and is also used to report its public network mapping IP and port to the automatic configuration server; The ACS server is used to store reported information or requested information, and determine whether to deliver services to the current user-side terminal device in a preset order based on the type of services that the current user-side terminal device needs to process, and is also used to send UDP messages to the user-side terminal device through the STUN server; The Stun server is used to parse the public network mapping IP and port request of the user-side terminal device, and return the parsing result data to the user-side terminal device, and is also used to transmit the UDP message sent by the automatic configuration server to the user-side terminal device.

8. A storage medium, characterized in that: It contains several computer instructions for executing the communication method based on the TR069 protocol described in any one of claims 1-6.

Images