Method for realizing remote configuration management of home intelligent gateway

By assigning a fixed domain name to CPE devices via dynamic DNS and securing communication with SSL/TLS, the method addresses inefficiencies in remote configuration management, ensuring stable and efficient operation and maintenance in home smart gateway systems.

CN119094338AActive Publication Date: 2024-12-06JIANGSU YINHE ELECTRONICS
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202411166696.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-23
Publication Date
2024-12-06
Estimated Expiration
2044-08-23

AI Technical Summary

Technical Problem

Existing home smart gateway systems face inefficiencies in remote configuration management due to dynamic IP address changes, leading to connection interruptions and reduced operation and maintenance efficiency.

Method used

Implementing a method that assigns a fixed domain name to the CPE device through a dynamic DNS service, establishing a TCP connection using the TCP/IP protocol, and securing communication with SSL/TLS, enabling stable and efficient remote configuration management by ensuring the ACS can consistently connect to the CPE despite IP address changes.

Benefits of technology

The method ensures stable and efficient operation and maintenance by maintaining a consistent connection through dynamic DNS, reducing connection interruptions and enhancing scalability and stability in home smart gateway systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094338A_ABST
    Figure CN119094338A_ABST
Patent Text Reader

Abstract

The invention discloses a method for realizing remote configuration management of a home intelligent gateway, which comprises the steps that a home gateway network management system ITMS and a database are built in the home intelligent gateway, the ITMS adopts a TR-069 protocol as a core communication protocol, the home gateway network management system ITMS comprises two types of logic equipment, namely customer premise equipment CPE and an automatic configuration server ACS, and an HTTP protocol is built in the CPE. The domain name is bound with the dynamic IP address of the CPE through the dynamic DNS service, when the IP address of the CPE changes, the dynamic DNS service can automatically update the DNS record, it is ensured that the domain name always points to the latest IP address, the dynamic DNS service ensures stable connection between the ACS and the CPE, the problem of connection interruption caused by the change of the IP address is reduced, and the user experience is improved. And moreover, the troubleshooting time caused by the connection problem is shortened, the operation and maintenance efficiency is improved, the operation and maintenance process is simplified, the risk of connection interruption is reduced, and the expandability and stability of the network are enhanced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent gateway management, and in particular to a method for realizing remote configuration management of a home intelligent gateway. Background Art

[0002] With the development of the Internet and intelligence, our lives are increasingly dependent on the Internet and electronic devices. The Internet and electronic devices in the smart home system are connected through the home smart gateway. The home smart gateway is the core component of the smart home system. The home smart gateway connects, manages and controls various smart devices in the home. For example, the home smart gateway can realize the information collection, information input, information output, centralized control, remote control, linkage control and other functions of various sensors, network devices, cameras and host devices in the local area network, so that residents can view and monitor the operation of various devices in the home through various communication means anytime and anywhere. With the rapid development of smart home technology, the home smart gateway is the core hub for connecting and controlling home smart devices. Its remote configuration management capability has become the key to improving user experience and ensuring the stable operation of the system; When the existing ACS actively explores CPE, the IP address of CPE often changes because the IP address of CPE exceeds the valid time of DHCP IP address. ACS can no longer actively contact CPE and can only wait for CPE to connect to ACS in the next cycle to establish connection again. This brings a lot of inconvenience to the operation and management of remote control and operation of CPE equipment, and the operation and maintenance efficiency is low. Therefore, it is urgent to build a method for realizing remote configuration management of home smart gateways. Summary of the invention

[0003] The purpose of the present invention is to provide a method for realizing remote configuration management of a home intelligent gateway to solve the problems raised in the above background technology.

[0004] To achieve the above object, the present invention provides the following technical solutions: A method for realizing remote configuration management of a home intelligent gateway includes a home gateway network management system ITMS and a database built into the home intelligent gateway, the ITMS system adopts the TR-069 protocol as its core communication protocol, the home gateway network management system ITMS includes two types of logical devices: a user terminal device CPE and an automatic configuration server ACS, the CPE has a built-in HTTP protocol, and includes the following steps: Step 1: Assign a fixed domain name to the CPE device and bind the domain name to the dynamic IP address of the CPE device through the dynamic DNS service. When the CPE is started for the first time and the network configuration is changed, such as when the IP address is changed, the CPE initiates an HTTP connection request to the ACS through a SOAP request. The specific steps are as follows: S1. Establish a TCP connection: Based on the three-way handshake of the TCP / IP protocol, the CPE first attempts to establish a TCP connection with the ACS. S2. Send HTTP request: After the TCP connection is established successfully, the CPE sends an HTTP POST request to the ACS. S3. Contains a SOAP message: The body of the HTTP POST request will contain a SOAP message that encapsulates the RPC method that the CPE wants to execute and its CPE registration parameters. When the CPE registers, it will send a SOAP message containing the Inform RPC method. S4. CPE initiates an operation request to ACS by sending an HTTP POST request containing a SOAP message with a specific RPC method. After receiving the HTTP request, ACS parses the SOAP message. After determining the operation that CPE wants to perform, ACS sends an HTTP response to CPE. The HTTP response contains a SOAP message to obtain CPE-specific information, such as serial number, MAC address, device ID, URL and port number, and authentication credentials, such as username and password. Step 2: After obtaining CPE-specific information, ACS makes an authentication credential request. ACS will ask CPE to perform HTTPDigest Authentication. If the authentication is successful, ACS will respond with a connection confirmation and the connection is successfully established. Step 3: After the connection between CPE and ACS is successfully established, CPE will immediately send an Inform request to ACS by calling the Inform RPC method. The request contains the device information and authentication information of CPE, as well as the reason for sending the Inform request. After receiving the Inform request from CPE, ACS will process it accordingly according to the connection request content in the request. The steps are as follows: S1. ACS authenticates the Inform request. Based on the authentication information in the Inform request, ACS will first check whether the username in the authentication information exists in its database. If so, ACS will further verify whether the provided password matches the password stored in the database. If the authentication is successful, ACS will allow CPE to continue subsequent management operations. If not, ACS will reject CPE's request. S2. When the matching authentication of the username and password succeeds and the ACS allows the CPE to access, the ACS will respond with an InformResponse, indicating that the RPC method processing is completed and the CWMP connection is successfully established. S3. During the CWMP connection establishment process, the CPE and ACS use the SSL / TLS protocol for encrypted communication. Step 4: After the connection is successfully established and authenticated, the ACS and CPE begin to exchange information through the RPC method. The RPC method is divided into the method supported by the ACS and the method supported by the CPE. The ACS calls the RPC method supported by the CPE for remote configuration management, and the CPE calls the RPC method supported by the ACS to report status information and request hardware image file download operations.

[0005] Preferably, in step 1, the domain name is bound to the dynamic IP address of the CPE device through a dynamic DNS service, and the specific steps are as follows: S1. Register an account with a dynamic DNS service provider to obtain a domain name; S2. Install and configure dynamic DNS client software or plug-in on the CPE device to bind the domain name to the dynamic IP address of the CPE device; S3. Update the access method of the CPE device on the ACS, use a fixed domain name instead of the original IP address, and test whether the ACS can successfully access the CPE device through the domain name; S4. Monitor the operating status and performance of the dynamic DNS service, and adjust configuration parameters or optimize the network environment according to actual conditions.

[0006] Preferably, in step 1, the CPE establishes a TCP connection with the ACS, and the steps are as follows: (1) CPE sends a SYN packet: CPE sends a TCP segment with a synchronization sequence number SYN flag to the ACS. In the segment, the SYN flag is set to 1, indicating that this is a connection request message. At the same time, the segment also contains a sequence number Sequence Number, which is randomly generated by the CPE and used for subsequent confirmation and data packet sorting during the communication process; (2) CS responds with a SYN-ACK packet: When ACS receives the SYN packet sent by CPE, it sends a synchronization confirmation SYN-ACK segment as a response. In the SYN-ACK segment, both the SYN and ACK flags are set to 1, indicating that this is a confirmation of the connection request, and ACS is also preparing its own sequence number for the new connection. The SYN-ACK segment contains an acknowledgment number for the sequence number in the CPE's SYN segment, that is, the CPE's sequence number plus 1, and the ACS's own initial sequence number. (3) CPE sends ACK packet: When CPE receives the SYN-ACK segment from ACS, it sends an ACK segment in response. In the ACK segment, the ACK flag is set to 1, indicating that this is an acknowledgment of the SYN-ACK segment. The acknowledgment number in the ACK segment is set to the initial sequence number of ACS plus 1, indicating that CPE has received the SYN-ACK segment from ACS and is ready to exchange data. Through the above three steps, a reliable TCP connection is established between CPE and ACS. Preferably, in step 3, the CPE and the ACS use the SSL / TLS protocol for encrypted communication, and the steps are as follows: (1) The ACS responds to the CPE's connection request and sends its own SSL / TLS certificate to the CPE. The certificate contains the ACS's public key, information about the CA that issued the certificate, and the validity period. (2) After receiving the certificate from ACS, CPE will verify the legitimacy of the certificate, whether it is issued by a trusted CA, whether the certificate has expired, and whether the domain name in the certificate matches the requested domain name. If the certificate verification is successful, CPE will generate a random number, called a pre-set key or Pre-Master Secret, and encrypt the random number with the ACS's public key and send it to ACS. This process is called key exchange. (3) During the key exchange process, the CPE and ACS will perform key exchange and protocol parameter negotiation to determine the encryption algorithm, key length, and session key used in subsequent communications. The CPE and ACS will also negotiate the use of preset keys and random numbers of the client and server, and generate session keys through algorithms such as the pseudo-random number generation function PRF of the TLS protocol. The session key will be used for encryption and decryption of subsequent communications. (4) CPE uses the session key to encrypt the data sent to ACS, and then sends the encrypted data to ACS. When ACS receives the encrypted data, ACS will use the session key to decrypt the data to restore the original data. Similarly, ACS also uses the session key to encrypt the data sent to CPE. When CPE receives the encrypted data, CPE uses the session key to decrypt the data to restore the original data.

[0007] Compared with the prior art, the beneficial effects of the present invention are as follows: the domain name is bound to the dynamic IP address of the CPE device through the dynamic DNS service. When the IP address of the CPE device changes, the dynamic DNS service automatically updates the DNS record to ensure that the domain name always points to the latest IP address, so that the dynamic DNS service can automatically complete the purpose of updating the IP address of the CPE device in the ACS, which helps to maintain a stable improvement in operation and maintenance efficiency. The fixed domain name is configured on the ACS to access the CPE device instead of directly using the IP address. Regardless of how the IP address of the CPE device changes, the ACS can find and connect to the CPE device through the domain name. The dynamic DNS service ensures a stable connection between the ACS and the CPE, reduces the connection interruption problem caused by the IP address change, and the operation and maintenance personnel can manage and monitor the CPE device more efficiently, reducing the troubleshooting time caused by the connection problem. The dynamic DNS service is applied to solve the problem caused by the IP address change when the ACS actively explores the CPE, thereby improving the operation and maintenance efficiency, simplifying the operation and maintenance process, reducing the risk of connection interruption, and enhancing the scalability and stability of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A flowchart of a method for implementing remote configuration management of a home intelligent gateway according to the present invention; Figure 2 A flow chart of HTTP connection request for a method for implementing remote configuration management of a home intelligent gateway according to the present invention; Figure 3 It is a flow chart of HTTP DigestAuthentication authentication in a method for realizing remote configuration management of a home intelligent gateway of the present invention; Figure 4 A flow chart of establishing a CWMP connection in a method for realizing remote configuration management of a home intelligent gateway according to the present invention; Figure 5 The present invention is a flow chart of information exchange between an ACS and a CPE through an RPC method in a method for realizing remote configuration management of a home intelligent gateway. DETAILED DESCRIPTION

[0009] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0010] Example See also Figure 1-5The embodiment of the present invention provides a method for remote configuration management of a home smart gateway, including a home gateway network management system ITMS and a database built into the home smart gateway, the ITMS system adopts the TR-069 protocol as its core communication protocol, the home gateway network management system ITMS includes two types of logical devices: a user terminal device CPE and an automatic configuration server ACS, the CPE has a built-in HTTP protocol, and includes the following steps: Step 1: Assign a fixed domain name to the CPE device and bind the domain name to the dynamic IP address of the CPE device through the dynamic DNS service. The specific steps are as follows: S1. Register an account with a dynamic DNS service provider to obtain a domain name; S2. Install and configure dynamic DNS client software or plug-in on the CPE device to bind the domain name to the dynamic IP address of the CPE device; S3. Update the access method of the CPE device on the ACS, use a fixed domain name instead of the original IP address, and test whether the ACS can successfully access the CPE device through the domain name. The ACS sends a connection request or management instruction to the CPE through the domain name, and observe whether the ACS can successfully connect to the CPE device and receive a response from the CPE. S4. Monitor the operation status and performance of the dynamic DNS service, adjust the configuration parameters or optimize the network environment according to the actual situation to ensure the stability and efficiency of the dynamic DNS service; When the CPE is started for the first time or when the network configuration is changed, such as when the IP address is changed, the CPE initiates an HTTP connection request to the ACS through a SOAP request. The specific steps are as follows: S1. Establish a TCP connection: Based on the three-way handshake of the TCP / IP protocol, the CPE first attempts to establish a TCP connection with the ACS. The steps are as follows: (1) CPE sends a SYN packet: CPE sends a TCP segment with a synchronization sequence number SYN flag to the ACS. In the segment, the SYN flag is set to 1, indicating that this is a connection request message. At the same time, the segment also contains a sequence number Sequence Number, which is randomly generated by the CPE and used for subsequent confirmation and data packet sorting during the communication process; (2) CS responds with a SYN-ACK packet: When ACS receives the SYN packet sent by CPE, it sends a synchronization confirmation SYN-ACK segment as a response. In the SYN-ACK segment, both the SYN and ACK flags are set to 1, indicating that this is a confirmation of the connection request, and ACS is also preparing its own sequence number for the new connection. The SYN-ACK segment contains an acknowledgment number for the sequence number in the CPE's SYN segment, that is, the CPE's sequence number plus 1, and the ACS's own initial sequence number. (3) CPE sends ACK packet: When CPE receives the SYN-ACK segment from ACS, it sends an ACK segment in response. In the ACK segment, the ACK flag is set to 1, indicating that this is an acknowledgment of the SYN-ACK segment. The acknowledgment number in the ACK segment is set to the initial sequence number of ACS plus 1, indicating that CPE has received the SYN-ACK segment from ACS and is ready to exchange data. Through the above three steps, a reliable TCP connection is established between CPE and ACS. S2. Send HTTP request: After the TCP connection is established successfully, the CPE will send an HTTP POST request to the ACS. The URI of the request will point to the service endpoint on the ACS that processes TR-069 requests, ensuring that the ACS can correctly identify and process the request from the CPE. S3. Contains a SOAP message: The body of the HTTP POST request will contain a SOAP message that encapsulates the RPC method that the CPE wants to execute and its CPE registration parameters. For example, for CPE registration, a SOAP message containing the Inform RPC method will be sent. S4. CPE initiates an operation request to ACS by sending an HTTP POST request containing a SOAP message with a specific RPC method. After receiving the HTTP request, ACS parses the SOAP message. After determining the operation that CPE wants to perform, ACS sends an HTTP response to CPE. The HTTP response contains a SOAP message to obtain CPE-specific information, such as serial number, MAC address, device ID, URL and port number, and authentication credentials, such as username and password. Step 2: After obtaining CPE-specific information, ACS makes an authentication credential request. ACS will require CPE to perform HTTP Digest Authentication. The specific steps are as follows: S1. The ACS sends an HTTP 401 Unauthorized response to the CPE, which contains a WWW-Authenticate header field, indicating that the ACS expects to use Digest authentication, and contains the realm, nonce, and quality of protection qop parameters; After receiving the 401 response, S2 and CPE use the MD5 hash algorithm to calculate a digest based on the URL, realm, nonce, and qop parameters provided by the ACS and the user name and password entered by the user. The specific steps are as follows: (1) Obtain necessary information: obtain the URL, realm, nonce, qop parameters, and the username and password entered by the user from the WWW-Authenticate header of the 401 response; (2) Construct the A1 string: For qop of auth or auth-int, A1=username:realm:password; (3) Perform MD5 hashing on A1: HA1=MD5(A1) (4) Build the A2 string: for qop=auth, A2=method:URI Where method is the HTTP request method, such as GET or POST, and URI is the requested URI, excluding the query string. (5) Perform MD5 hashing on A2: HA2 = MD5(A2). When calculating the response digest, A2 will participate in the non-hashed form. (6) Construct the response digest: For qop=auth,response=MD5(HA1:nonce:nonceCount:cnonce:qop:HA2) Where nonceCount and cnonce are values ​​generated by the CPE. NonceCount is usually initialized to '00000001' and incremented with each request. cnonce is a random string provided by the client to increase the complexity of the digest. S3. CPE adds the calculated digest to the "Authorization" header field of the request and resends the request to ACS. The "Authorization" header field contains the username, URI, realm, nonce, qop, client random number cnonce, and digest information. S4. After receiving the request with digest, ACS will use the same algorithm and parameters to calculate an expected digest, and compare it with the digest provided by CPE. If the two are consistent, the authentication is successful, and ACS will respond with connection confirmation. Otherwise, the authentication fails, and ACS returns a 401 response to CPE. CPE calculates the response according to the digest authentication algorithm based on the WWW-Authenticate information, URL, user name and password responded by ACS, and constructs the digest authentication information for the re-request. Then, it initiates the HTTP request again and records the number of retries. Step 3: After successfully establishing the connection between CPE and ACS, CPE will immediately send an Inform request to ACS by calling the Inform RPC method. The request contains the device information and authentication information of CPE, as well as the reason for sending the Inform request. Device information: such as manufacturer, model, serial number, software version; authentication information: such as username username and password password; reason for the Inform request: such as connection request, status change notification. After receiving the Inform request from CPE, ACS will process it accordingly according to the connection request content in the request. The steps are as follows: S1. ACS authenticates the Inform request. Based on the authentication information in the Inform request, ACS will first check whether the username in the authentication information exists in its database. If so, ACS will further verify whether the provided password matches the password stored in the database. If the authentication is successful, ACS will allow CPE to continue subsequent management operations. If not, ACS will reject CPE's request. S2. When the matching authentication of the username and password succeeds and the ACS allows the CPE to access, the ACS will respond with an InformResponse, indicating that the RPC method processing is completed and the CWMP connection is successfully established. S3. In the process of establishing a CWMP connection, in order to ensure the security of communication between the CPE and the ACS, the CPE and the ACS use the SSL / TLS protocol for encrypted communication to ensure the confidentiality of the communication and the integrity of the data. The steps are as follows: (1) The ACS responds to the CPE's connection request and sends its own SSL / TLS certificate to the CPE. The certificate contains the ACS's public key, information about the CA that issued the certificate, and the validity period. (2) After receiving the certificate from ACS, CPE will verify the legitimacy of the certificate, whether it is issued by a trusted CA, whether the certificate has expired, and whether the domain name in the certificate matches the requested domain name. If the certificate verification is successful, CPE will generate a random number, called a pre-set key or Pre-Master Secret, and encrypt the random number using the ACS's public key and send it to ACS. (3) During the key exchange process, the CPE and ACS will perform key exchange and protocol parameter negotiation to determine the encryption algorithm, key length, and session key used in subsequent communications. The CPE and ACS will also negotiate the use of preset keys and random numbers of the client and server, and generate session keys through algorithms such as the pseudo-random number generation function PRF of the TLS protocol. The session key will be used for encryption and decryption of subsequent communications. (4) CPE uses the session key to encrypt the data sent to ACS, and then sends the encrypted data to ACS. When ACS receives the encrypted data, ACS will use the session key to decrypt the data to restore the original data. Similarly, ACS also uses the session key to encrypt the data sent to CPE. When CPE receives the encrypted data, CPE uses the session key to decrypt the data to restore the original data. Through SSL / TLS authentication, the communication between CPE and ACS is encrypted and protected, thus preventing security threats such as eavesdropping, tampering and identity spoofing. During the interaction between CPE and ACS, SSL / TLS ensures the confidentiality, integrity and authentication of data, providing strong security protection for remote management and configuration; Step 4: After the connection is successfully established and the authentication is passed, the ACS and CPE begin to exchange information through the RPC method. The RPC method is divided into the method supported by the ACS and the method supported by the CPE. The message transmission between the ACS and the CPE is based on the HTTP1.1 protocol. The message content is packaged in a SOAP packet. The SOAP message consists of a SOAP header and a SOAP body, both of which are XML format data. The SOAP request sent by the ACS to the CPE is based on the HTTP response, and the SOAP response returned by the CPE to the ACS is based on the subsequent HTTP post. ACS calls the RPC method supported by CPE for remote configuration management, such as obtaining CPE parameters, setting CPE parameters, remote configuration management, hardware upgrade, or restarting the device. The steps are as follows: S1. When ACS calls an RPC method, it sends a SOAP packet containing the function name and parameters to CPE. S2. After receiving the RPC call from ACS, CPE will parse the SOAP packet and perform corresponding operations according to the request; S3. After the CPE completes the operation, it sends a response SOAP packet to the ACS to inform it of the operation result and required information. S4. After the communication ends, ACS will send an HTTP 204 No Content response to indicate the end of this session; The CPE calls the RPC method supported by the ACS to report status information and request hardware image file download operations. The steps are as follows: S1. CPE will periodically call the RPC method of ACS to report status information, which is implemented through the Inform RPC method. The information includes the device information, status information, and possible error or alarm information of CPE. After receiving the status information, ACS can monitor the status of CPE. S2. When ACS detects that CPE needs to update firmware and perform system upgrade, CPE will request hardware image file from ACS. S3. The CPE can send a request containing the required image file information to the ACS; S4. After receiving the request, ACS verifies the CPE's authority and the validity of the request. If the verification is successful, ACS will provide the download address of the image file and send the image file to CPE. S5. After receiving the image file, the CPE will download and install it to update and upgrade the system.

[0011] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

Claims

1. A method for implementing remote configuration management of a home intelligent gateway, comprising a home gateway network management system ITMS and a database built into the home intelligent gateway, the ITMS system adopting the TR-069 protocol as its core communication protocol, the home gateway network management system ITMS including two types of logical devices: a user terminal device CPE and an automatic configuration server ACS, the CPE having a built-in HTTP protocol, characterized in that: The following steps are involved: Step 1: Assign a fixed domain name to the CPE device and bind the domain name to the dynamic IP address of the CPE device through the dynamic DNS service. When the CPE is started for the first time and the network configuration is changed, such as when the IP address is changed, the CPE initiates an HTTP connection request to the ACS through a SOAP request. The specific steps are as follows: S1. Establish a TCP connection: Based on the three-way handshake of the TCP / IP protocol, the CPE first attempts to establish a TCP connection with the ACS. S2. Send HTTP request: After the TCP connection is established successfully, the CPE sends an HTTP POST request to the ACS. S3. Contains a SOAP message: The body of the HTTP POST request will contain a SOAP message that encapsulates the RPC method that the CPE wants to execute and its CPE registration parameters. When the CPE registers, it will send a SOAP message containing the Inform RPC method. S4. CPE initiates an operation request to ACS by sending an HTTP POST request containing a SOAP message with a specific RPC method. After receiving the HTTP request, ACS parses the SOAP message. After determining the operation that CPE wants to perform, ACS sends an HTTP response to CPE. The HTTP response contains a SOAP message to obtain CPE-specific information, such as serial number, MAC address, device ID, URL and port number, and authentication credentials, such as username and password. Step 2: After obtaining CPE-specific information, ACS makes an authentication credential request. ACS will ask CPE to perform HTTPDigest Authentication. If the authentication is successful, ACS will respond with a connection confirmation and the connection is successfully established. Step 3: After the connection between CPE and ACS is successfully established, CPE will immediately send an Inform request to ACS by calling the Inform RPC method. The request contains the device information and authentication information of CPE, as well as the reason for sending the Inform request. After receiving the Inform request from CPE, ACS will process it accordingly according to the connection request content in the request. The steps are as follows: S1. ACS authenticates the Inform request. Based on the authentication information in the Inform request, ACS will first check whether the username in the authentication information exists in its database. If so, ACS will further verify whether the provided password matches the password stored in the database. If the authentication is successful, ACS will allow CPE to continue subsequent management operations. If not, ACS will reject CPE's request. S2. When the matching authentication of the username and password succeeds and the ACS allows the CPE to access, the ACS will respond with an InformResponse, indicating that the RPC method processing is completed and the CWMP connection is successfully established. S3. During the CWMP connection establishment process, the CPE and ACS use the SSL / TLS protocol for encrypted communication. Step 4: After the connection is successfully established and authenticated, the ACS and CPE begin to exchange information through the RPC method. The RPC method is divided into the method supported by the ACS and the method supported by the CPE. The ACS calls the RPC method supported by the CPE for remote configuration management, and the CPE calls the RPC method supported by the ACS to report status information and request hardware image file download operations.

2. A method for implementing remote configuration management of a home intelligent gateway according to claim 1, characterized in that: In step 1, the domain name is bound to the dynamic IP address of the CPE device through the dynamic DNS service. The specific steps are as follows: S1. Register an account with a dynamic DNS service provider to obtain a domain name; S2. Install and configure dynamic DNS client software or plug-in on the CPE device to bind the domain name to the dynamic IP address of the CPE device; S3. Update the access method of the CPE device on the ACS, use a fixed domain name instead of the original IP address, and test whether the ACS can successfully access the CPE device through the domain name; S4. Monitor the operating status and performance of the dynamic DNS service, and adjust configuration parameters or optimize the network environment according to actual conditions.

3. A method for implementing remote configuration management of a home intelligent gateway according to claim 1, characterized in that: In step 1, the CPE establishes a TCP connection with the ACS, as follows: (1) CPE sends a SYN packet: CPE sends a TCP segment with a synchronization sequence number SYN flag to the ACS. In the segment, the SYN flag is set to 1, indicating that this is a connection request message. At the same time, the segment also contains a sequence number Sequence Number, which is randomly generated by the CPE and used for subsequent confirmation and data packet sorting during the communication process; (2) CS responds with a SYN-ACK packet: When ACS receives the SYN packet sent by CPE, it sends a synchronization confirmation SYN-ACK segment as a response. In the SYN-ACK segment, both the SYN and ACK flags are set to 1, indicating that this is a confirmation of the connection request, and ACS is also preparing its own sequence number for the new connection. The SYN-ACK segment contains an acknowledgment number for the sequence number in the CPE's SYN segment, that is, the CPE's sequence number plus 1, and the ACS's own initial sequence number; (3) CPE sends ACK packet: When CPE receives the SYN-ACK segment from ACS, it sends an ACK segment in response. In the ACK segment, the ACK flag is set to 1, indicating that this is an acknowledgment of the SYN-ACK segment. The acknowledgment number in the ACK segment is set to the initial sequence number of ACS plus 1, indicating that CPE has received the SYN-ACK segment from ACS and is ready to exchange data. Through the above three steps, a reliable TCP connection is established between CPE and ACS.

4. A method for implementing remote configuration management of a home intelligent gateway according to claim 1, characterized in that: In step 3, the CPE and ACS use the SSL / TLS protocol for encrypted communication, and the steps are as follows: (1) The ACS responds to the CPE's connection request and sends its own SSL / TLS certificate to the CPE. The certificate contains the ACS's public key, information about the CA that issued the certificate, and the validity period. (2) After receiving the certificate from ACS, CPE will verify the legitimacy of the certificate, whether it is issued by a trusted CA, whether the certificate has expired, and whether the domain name in the certificate matches the requested domain name. If the certificate verification is successful, CPE will generate a random number, called a pre-set key or Pre-Master Secret, and encrypt the random number with the ACS's public key and send it to ACS. This process is called key exchange. (3) During the key exchange process, the CPE and ACS will perform key exchange and protocol parameter negotiation to determine the encryption algorithm, key length, and session key used in subsequent communications. The CPE and ACS will also negotiate the use of preset keys and random numbers of the client and server, and generate session keys through algorithms such as the pseudo-random number generation function PRF of the TLS protocol. The session key will be used for encryption and decryption of subsequent communications. (4) CPE uses the session key to encrypt the data sent to ACS, and then sends the encrypted data to ACS. When ACS receives the encrypted data, ACS will use the session key to decrypt the data to restore the original data. Similarly, ACS also uses the session key to encrypt the data sent to CPE. When CPE receives the encrypted data, CPE uses the session key to decrypt the data to restore the original data.

Citation Information

Patent Citations

  • Device, system and method for automatically configuring application terminal in household network

    CN101867509A

  • TR069 protocol-based remote centralized monitoring method and TR069 protocol-based remote centralized monitoring system for IMS access network equipment

    CN112333202A

  • Method for realizing interaction between APK and ACS by packaging TR069 message

    CN112910884A

  • Digital home intelligent gateway configuration management method based on long connection

    CN117411785A

  • Method and system for remote management of wide area network intelligent gateway equipment based on web

    CN117857131A