Gateway collaborative management method, device, equipment and medium based on FTTR

Abstract

The FTTR-based gateway collaborative management method, device, equipment and medium provided in the present application relate to the field of gateway communication technology. In the present application, first, the gateway firmware version information sent by any other gateway device among multiple gateway devices in response to the networking success event of multiple gateway devices is received; secondly, the gateway firmware version information sent by each other gateway device is compared and analyzed with the target gateway firmware version information to obtain the corresponding comparative analysis result; then, in response to the comparative analysis result, the corresponding gateway firmware collaborative management operation is performed, wherein after the gateway firmware collaborative management operation is performed, the version information of the firmware currently running in each gateway device among the multiple gateway devices belongs to the latest version information. Based on the above content, the problem that the whole-house network performance and stability of FTTR in the prior art are difficult to be effectively guaranteed can be improved.

Description

Technical Field

[0001] The present application relates to the field of gateway communication technology, and in particular to a gateway collaborative management method and apparatus, device and medium based on FTTR. Background Art

[0002] FTTR (Fiber to The Room) technology is an innovative solution for deploying networks within homes and small businesses. It uses optical fiber to replace traditional network cables, extends optical fiber to each independent space, and achieves seamless interconnection with the home main gateway by deploying optical network terminal equipment. The corresponding networking system mainly includes components such as the main gateway, the slave gateway, and routers with similar functions. These components can be flexibly networked through direct optical fiber connection, wired transmission, or wireless methods.

[0003] However, the inventors have discovered that since the performance and stability of the FTTR's whole-house network largely depend on the collaborative work between the various component devices, it is necessary to improve the reliability of the collaborative work between the various component devices, that is, to ensure the reliability of gateway communication. However, in the prior art, there is a problem of relatively low reliability of gateway communication, which makes it difficult to effectively ensure the performance and stability of the FTTR's whole-house network. Summary of the invention

[0004] In view of this, the purpose of this application is to provide a gateway collaborative management method and device, equipment and medium based on FTTR, so as to improve the problem in the prior art that the performance and stability of the FTTR whole-house network are difficult to be effectively guaranteed.

[0005] To achieve the above objectives, this application adopts the following technical solutions:

[0006] A gateway collaborative management method based on FTTR is applied to a target gateway device in a gateway collaborative management system based on FTTR, wherein the gateway collaborative management system based on FTTR includes a plurality of gateway devices that have established communication connections with each other, and the target gateway device belongs to any one of the plurality of gateway devices. The gateway collaborative management method based on FTTR includes:

[0007] Receiving gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to a networking success event of the multiple gateway devices, wherein each gateway device among the multiple gateway devices is configured to send version information of its currently running firmware to the other gateway devices in response to the networking success event of the multiple gateway devices;

[0008] Comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain corresponding comparative analysis results, wherein the target gateway firmware version information is the version information of the firmware currently running on the target gateway device;

[0009] In response to the comparison and analysis result, a corresponding gateway firmware collaborative management operation is performed, wherein after the gateway firmware collaborative management operation is performed, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information.

[0010] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, the step of receiving the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices includes:

[0011] Performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one gateway device among the multiple gateway devices that has been offline and then has come online again;

[0012] An event that at least one of the multiple gateway devices comes back online after being offline is taken as a networking success event, and in response to the networking success event, version information of the firmware currently running on the gateway device is sent to each other gateway device in the multiple gateway devices;

[0013] Receive gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

[0014] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, the step of taking the event that at least one gateway device among the multiple gateway devices comes back online after being offline as a networking success event, and sending the version information of the firmware currently running on the multiple gateway devices to each other gateway device among the multiple gateway devices in response to the networking success event includes:

[0015] After determining that there is at least one gateway device among the multiple gateway devices that has been offline and then come back online, for each of the at least one gateway device that has come back online, send a log query request message to the gateway device, and receive device operation log data sent by the gateway device in response to the log query request message, wherein the device operation log data at least includes record data of each offline and online return of the corresponding gateway device in history;

[0016] For each of the at least one gateway device that has come back online, based on the device operation log data corresponding to the gateway device, analyze the time change characteristics of the gateway device with respect to being offline and coming back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the characteristic matching result corresponding to the gateway device;

[0017] When the feature matching result corresponding to any one of the at least one gateway devices that are back online is a match, a networking success event is generated, and in response to the networking success event, version information of the firmware currently running on the other gateway devices is sent to each other gateway device among the multiple gateway devices, wherein when the feature matching result corresponding to each of the at least one gateway device that is back online is a mismatch, it is determined that no networking success event is generated.

[0018] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, for each of the at least one gateway device that is back online, based on the device operation log data corresponding to the gateway device, the time change characteristics of the gateway device regarding offline and back online are analyzed, and it is determined whether the time change characteristics match the predetermined target change characteristics, and the step of obtaining the characteristic matching result corresponding to the gateway device includes:

[0019] For each gateway device of the at least one gateway device that is back online, obtaining the running time of the gateway device, and comparing the running time with a pre-configured target running time;

[0020] For each gateway device among the at least one gateway device that has come back online, when the running time of the gateway device is greater than the target running time, based on the device running log data corresponding to the gateway device, analyzing the time change feature of the gateway device regarding being offline and coming back online, and determining whether the time change feature matches a predetermined target change feature, and obtaining a feature matching result corresponding to the gateway device;

[0021] For each gateway device among at least one gateway device that is back online, when the operating time of the gateway device is not greater than the target operating time, among the other gateway devices, determine one other gateway device with the highest device correlation with the gateway device, and send a log query request message to the other gateway device, and receive device operation log data sent by the other gateway device in response to the log query request message, and use the device operation log data as the device operation log data added by the gateway device, and, based on the device operation log data corresponding to the gateway device and the added device operation log data, analyze the time change characteristics of the gateway device regarding offline and back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the feature matching result corresponding to the gateway device, wherein the added device operation log data at least includes the record data of each offline and back online of the corresponding gateway device in history.

[0022] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, the step of receiving the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices includes:

[0023] Performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one newly added gateway device among the multiple gateway devices;

[0024] Taking the event that at least one newly added gateway device exists in the plurality of gateway devices as a networking success event, and in response to the networking success event, sending version information of the firmware currently running on the gateway device to each other gateway device in the plurality of gateway devices;

[0025] Receive gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

[0026] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, the step of comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain the corresponding comparison and analysis results includes:

[0027] Compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information;

[0028] When the latest version information of the gateway firmware version information sent by each other gateway device and the target gateway firmware version information does not belong to the target gateway firmware version information, generating a corresponding first comparison analysis result;

[0029] In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, generating a corresponding second comparison analysis result;

[0030] In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, a corresponding third comparative analysis result is generated.

[0031] In a preferred embodiment of the present application, in the above-mentioned FTTR-based gateway collaborative management method, the step of executing the corresponding gateway firmware collaborative management operation in response to the comparative analysis result includes:

[0032] When the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, determine other gateway devices with gateway firmware version information belonging to the latest version information, and request the other gateway devices to obtain the gateway firmware belonging to the latest version information, and after obtaining the gateway firmware, update the currently running firmware to the gateway firmware to complete the corresponding gateway firmware collaborative management operation;

[0033] In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, determine other gateway devices whose gateway firmware version information does not belong to the latest version information, and send the target gateway firmware version information to the other gateway devices, and after obtaining the firmware request information sent by the other gateway devices based on the target gateway firmware version information, send the gateway firmware corresponding to the target gateway firmware version information to the other gateway devices, so as to complete the corresponding gateway firmware collaborative management operation;

[0034] In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, it is determined that the corresponding gateway firmware collaborative management operation has been completed.

[0035] The present application also provides a FTTR-based gateway collaborative management device, which is applied to a target gateway device in a FTTR-based gateway collaborative management system, wherein the FTTR-based gateway collaborative management system includes a plurality of gateway devices that have established communication connections with each other, and the target gateway device belongs to any one of the plurality of gateway devices. The FTTR-based gateway collaborative management device includes:

[0036] A firmware version information receiving module, configured to receive gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to a networking success event of the multiple gateway devices, wherein each gateway device among the multiple gateway devices is configured to send version information of its currently running firmware to other gateway devices in response to the networking success event of the multiple gateway devices;

[0037] A firmware version information comparison module, used to compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain a corresponding comparison and analysis result, wherein the target gateway firmware version information is the version information of the firmware currently running on the target gateway device;

[0038] The firmware collaborative management module is used to execute corresponding gateway firmware collaborative management operations in response to the comparison and analysis results, wherein after executing the gateway firmware collaborative management operations, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information.

[0039] On the basis of the above, the present application also provides a gateway device, including:

[0040] Memory for storing computer programs;

[0041] The processor connected to the memory is used to execute the computer program stored in the memory to implement the above-mentioned FTTR-based gateway collaborative management method.

[0042] On the basis of the above, the present application also provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is run, each step of the above-mentioned FTTR-based gateway collaborative management method is executed.

[0043] The FTTR-based gateway collaborative management method, device, equipment and medium provided in the present application can receive the gateway firmware version information sent by any other gateway device in response to the networking success event of multiple gateway devices; secondly, the gateway firmware version information sent by each other gateway device is compared and analyzed with the target gateway firmware version information to obtain the corresponding comparison and analysis results; then, in response to the comparison and analysis results, the corresponding gateway firmware collaborative management operation is performed, wherein, after the gateway firmware collaborative management operation is performed, the version information of the firmware currently running in each gateway device in the multiple gateway devices belongs to the latest version information. Based on the above content, since the networking success event is used as the trigger mechanism for firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, thereby avoiding compatibility failures, network instability, service anomalies and other problems caused by inconsistent firmware versions, thereby ensuring the communication reliability between gateway devices, so that the problem of low gateway communication reliability existing in the prior art can be improved, and reliable collaborative work between gateway devices can be achieved, thereby ensuring the whole-house network performance and stability of FTTR. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings.

[0045] Figure 1 A structural block diagram of a gateway device provided in an embodiment of the present application.

[0046] Figure 2 A flowchart of a gateway collaborative management method based on FTTR provided in an embodiment of the present application.

[0047] Figure 3 A block diagram of a gateway collaborative management device based on FTTR provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0049] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0050] like Figure 1 As shown, an embodiment of the present application provides a gateway device, wherein the gateway device may include a memory, a processor, and a gateway collaborative management device based on FTTR.

[0051] In detail, the memory and the processor are electrically connected directly or indirectly to achieve data transmission. For example, the memory and the processor can be electrically connected through one or more communication buses or signal lines. The FTTR-based gateway collaborative management device includes at least one software function module stored in the memory in the form of software or firmware. The processor is used to execute an executable computer program stored in the memory, for example, the software function modules and computer programs included in the FTTR-based gateway collaborative management device, so as to implement the FTTR-based gateway collaborative management method provided in the embodiment of the present application.

[0052] Optionally, the memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc.

[0053] Furthermore, the processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a system on chip (SoC), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0054] Understandably, Figure 1The structure shown is for illustration only. The gateway device may also include Figure 1 More or fewer components as shown, or with Figure 1 The different configurations shown, for example, may also include a communication unit for exchanging information with other devices (such as other gateway devices).

[0055] Combination Figure 2 , the embodiment of the present application also provides a FTTR-based gateway collaborative management method that can be applied to the above-mentioned gateway device. Among them, the method steps defined in the process related to the FTTR-based gateway collaborative management method can be implemented by the gateway device, and the gateway device can be a target gateway device in the FTTR-based gateway collaborative management system. The FTTR-based gateway collaborative management system can include multiple gateway devices that have established communication connections with each other, and the target gateway device belongs to any gateway device among the multiple gateway devices.

[0056] The following will Figure 2 The specific process shown is explained in detail.

[0057] Step S110: receiving gateway firmware version information sent by any other gateway device among the plurality of gateway devices in response to a networking success event of the plurality of gateway devices.

[0058] In an embodiment of the present application, the target gateway device can receive the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices. Wherein, each gateway device among the multiple gateway devices is configured to send the version information of the firmware currently running on itself to other gateway devices in response to the networking success event of the multiple gateway devices, so that each gateway device among the multiple gateway devices can receive the version information of the firmware of other gateway devices.

[0059] Step S120 , comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain corresponding comparison and analysis results.

[0060] In an embodiment of the present application, the target gateway device can compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain corresponding comparison and analysis results. The target gateway firmware version information is the version information of the firmware currently running on the target gateway device. In other words, its own firmware version information can be compared and analyzed with the firmware version information of other network devices.

[0061] Step S130, in response to the comparison and analysis result, executing corresponding gateway firmware collaborative management operations.

[0062] In an embodiment of the present application, the target gateway device may perform a corresponding gateway firmware collaborative management operation in response to the comparative analysis result. The specific content of the gateway firmware collaborative management operation is not limited, and after performing the gateway firmware collaborative management operation, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information.

[0063] Based on the above content, since the networking success event is used as the trigger mechanism for firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, thereby avoiding compatibility failures, network instability, service abnormalities and other problems caused by inconsistent firmware versions, and then ensuring the communication reliability between gateway devices, so that the problem of low gateway communication reliability in the prior art can be improved, and reliable collaborative work between gateway devices can be achieved, thereby ensuring the whole-house network performance and stability of FTTR.

[0064] First, it should be noted that for step S110, the specific method of receiving the gateway firmware version information sent in response to the networking success event is not limited and can be selected according to actual needs.

[0065] For example, in an alternative implementation, in order to ensure the reliability of the gateway firmware collaborative management operation, the above-mentioned step S110 may further include step S111, step S112 and step S113, and the specific content of each step is described as follows.

[0066] Step S111 : performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one newly added gateway device among the multiple gateway devices.

[0067] In the embodiment of the present application, a status monitoring operation may be performed on the multiple gateway devices to determine whether there is at least one newly added gateway device among the multiple gateway devices.

[0068] Step S112: taking the event that at least one newly added gateway device exists in the plurality of gateway devices as a networking success event, and in response to the networking success event, sending version information of the firmware currently running on the gateway device to each other gateway device in the plurality of gateway devices.

[0069] In the embodiment of the present application, the event that at least one newly added gateway device exists in the plurality of gateway devices can be regarded as a networking success event, and in response to the networking success event, the version information of the firmware currently running on the gateway device is sent to each other gateway device in the plurality of gateway devices. That is to say, for the newly added gateway device, generally speaking, the firmware version may be quite different from that of other gateway devices in the current networking, so there will be a problem of poor coordination, and the corresponding firmware version needs to be updated.

[0070] Step S113: receiving gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

[0071] In the embodiment of the present application, gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event may be received.

[0072] For example, in another alternative implementation, in order to ensure the reliability of the gateway firmware collaborative management operation, the above-mentioned step S110 may further include step S114, step S115 and step S116, and the specific content of each step is described as follows.

[0073] Step S114: performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one gateway device among the multiple gateway devices that has been offline and then has come back online.

[0074] In an embodiment of the present application, the status monitoring operation can be performed on the multiple gateway devices to determine whether there is at least one gateway device that has come back online after being offline among the multiple gateway devices. Exemplarily, each gateway device is configured to broadcast its own information about coming back online to other gateway devices after coming back online, and each gateway device is also configured to monitor the information about coming back online broadcasted by other gateway devices (specifically, it can be monitoring of a designated port), so that the status of other gateway devices can be obtained in time, thereby determining whether there is at least one gateway device that has come back online after being offline among the multiple gateway devices.

[0075] Step S115, taking the event of at least one gateway device among the multiple gateway devices being offline and then back online as a networking success event, and in response to the networking success event, sending version information of the firmware currently running on itself to each other gateway device among the multiple gateway devices.

[0076] In the embodiment of the present application, the event that at least one of the multiple gateway devices comes back online after being offline can be regarded as a networking success event, and in response to the networking success event, the version information of the firmware currently running on the device is sent to each other gateway device in the multiple gateway devices. In other words, if at least one gateway device comes back online after being offline, it can be considered that a networking success event has occurred.

[0077] Step S116: receiving gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

[0078] In an embodiment of the present application, the gateway firmware version information sent by each other gateway device in response to the networking success event can be received. That is to say, if at least one gateway device is offline and then back online, a subsequent firmware version update determination operation can be performed. That is to say, due to the offline situation, the firmware version update may be interrupted (i.e., the update fails) due to the offline situation, resulting in poor consistency between the firmware versions of the gateway devices. Therefore, a subsequent firmware version update determination operation is required.

[0079] It can be understood that, in the above-mentioned step S115, the specific method of using the event that at least one gateway device among the multiple gateway devices has been disconnected and then come back online as a networking success event is not limited and can be selected according to actual needs. For example, in an alternative implementation, in order to take into account the reliability of firmware updates and resource consumption of information transmission, the above-mentioned step S115 can further include step S115a, step S115b and step S115c, and the specific content of each step is described as follows.

[0080] Step S115a, after determining that there is at least one gateway device among the multiple gateway devices that has been offline and then back online, for each gateway device among the at least one gateway device that has come back online, send a log query request message to the gateway device, and receive the device operation log data sent by the gateway device in response to the log query request message.

[0081] In an embodiment of the present application, after determining that there is at least one gateway device among the multiple gateway devices that has been offline and then back online, for each of the at least one gateway device that has been back online, a log query request message can be sent to the gateway device, and the device operation log data sent by the gateway device in response to the log query request message can be received. The device operation log data includes at least the record data of each offline and back online event of the corresponding gateway device in history. In a specific application example, in order to reduce the resource consumption of log data transmission, the device operation log data may only include the record data of each offline and back online event of the corresponding gateway device in the recent period of time (such as one day, one week, one month, etc.).

[0082] Step S115b, for each gateway device among at least one gateway device that has come back online, based on the device operation log data corresponding to the gateway device, analyze the time change characteristics of the gateway device regarding disconnection and coming back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the feature matching result corresponding to the gateway device.

[0083] In the embodiment of the present application, for each of the at least one gateway device that is back online, based on the device operation log data corresponding to the gateway device, the time change characteristics of the gateway device regarding offline and back online are analyzed, and it is determined whether the time change characteristics match the predetermined target change characteristics, and the characteristic matching result corresponding to the gateway device is obtained. Exemplarily, the time change characteristics may refer to at least one of the information such as the number of times, frequency, and trend of offline and back online, which is not specifically limited and can be selected according to actual needs.

[0084] Step S115c, when the feature matching result corresponding to any one of the at least one gateway device that has come back online is a match, a networking success event is generated, and in response to the networking success event, the version information of the firmware currently running on the other gateway device is sent to each other gateway device among the multiple gateway devices.

[0085] In an embodiment of the present application, when the feature matching result corresponding to any one of the at least one gateway devices that are back online is a match, a networking success event is generated, and in response to the networking success event, the version information of the firmware currently running on itself is sent to each other gateway device in the multiple gateway devices. Wherein, when the feature matching result corresponding to each of the at least one gateway device that is back online is a mismatch, it is determined not to generate a networking success event. Exemplarily, the feature matching result being a match may mean that the number or frequency of the gateway device being offline and back online is less than the preset number or preset frequency (the specific value can be configured according to actual needs). In this way, the problem of transmission resource waste caused by high-frequency version information transmission due to high-frequency offline can be avoided.

[0086] It can be understood that in the above-mentioned step S115b, the specific method of analyzing the time-changing characteristics of the gateway device regarding disconnection and re-online is not limited and can be selected according to actual needs. For example, in an alternative implementation, in order to further ensure the reliability of the analyzed time-changing characteristics, the above-mentioned step S115b can include step b1, step b2 and step b3, and the specific content of each step is described as follows.

[0087] Step b1: for each gateway device among the at least one gateway device that is back online, obtain the running time of the gateway device, and compare the running time with a pre-configured target running time.

[0088] In the embodiment of the present application, for each of the at least one gateway device that is back online, the running time of the gateway device can be obtained, and the running time can be compared with the pre-configured target running time. The specific length of the target running time is not limited and can be selected according to actual needs, for example, one day, one week, etc.

[0089] Step b2, for each gateway device among at least one gateway device that is back online, when the running time of the gateway device is greater than the target running time, based on the device operation log data corresponding to the gateway device, analyze the time change characteristics of the gateway device regarding disconnection and coming back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the feature matching result corresponding to the gateway device.

[0090] In the embodiment of the present application, for each gateway device in at least one gateway device that is back online, when the operation time of the gateway device is greater than the target operation time, based on the device operation log data corresponding to the gateway device, the time change characteristics of the gateway device regarding offline and back online are analyzed, and it is determined whether the time change characteristics match the predetermined target change characteristics, and the characteristic matching result corresponding to the gateway device is obtained. That is to say, when the operation time of the gateway device itself is long, its own device operation log data is sufficient, so the device operation log data can be analyzed to obtain the corresponding time change characteristics.

[0091] Step b3, for each gateway device among at least one gateway device that is back online, when the operating time of the gateway device is not greater than the target operating time, among the other gateway devices, determine one other gateway device with the highest device correlation with the gateway device, and send a log query request message to the other gateway device, and receive the device operation log data sent by the other gateway device in response to the log query request message, and use the device operation log data as the device operation log data added by the gateway device, and, based on the device operation log data corresponding to the gateway device and the added device operation log data, analyze the time change characteristics of the gateway device regarding disconnection and re-online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the feature matching result corresponding to the gateway device.

[0092] In an embodiment of the present application, for each gateway device among at least one gateway device that is back online, when the operating time of the gateway device is not greater than the target operating time, among the other gateway devices, one other gateway device with the highest device correlation with the gateway device is determined, and a log query request message is sent to the other gateway device, and device operation log data sent by the other gateway device in response to the log query request message is received, and the device operation log data is used as the device operation log data added by the gateway device, and, based on the device operation log data corresponding to the gateway device and the added device operation log data, the time change characteristics of the gateway device regarding offline and back online are analyzed, and it is determined whether the time change characteristics match the predetermined target change characteristics, and the feature matching result corresponding to the gateway device is obtained, wherein the added device operation log data at least includes record data of each offline and back online of the corresponding gateway device in history. That is to say, when the operation time of the gateway device itself is short, its own equipment operation log data is not very sufficient. Therefore, based on its own equipment operation log data, it is possible to obtain the equipment operation log data of another gateway device with the highest equipment correlation for data expansion. For example, the number of offline times of another gateway device with the highest equipment correlation can be accumulated with its own offline times (or weighted summation, the weighting coefficient corresponding to its own offline times can be greater than the offline times of other gateway devices).

[0093] It should be noted that in the above content, the device correlation may refer to the type of gateway devices, such as the same type. Alternatively, in other implementations, the device correlation may also refer to the similarity of terminal devices connected to the gateway devices, such as both connected to the same terminal device.

[0094] Secondly, it should be noted that for step S120, the specific method of comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information is not limited and can be selected according to actual needs.

[0095] For example, in an alternative implementation, in order to ensure that the obtained comparative analysis results can fully reflect the relationship between the firmware versions, so as to make the subsequent gateway firmware collaborative management operations based on the comparative analysis results reliable (the granularity of the operation is finer), the above step S120 may further include the following contents:

[0096] First, the gateway firmware version information sent by each other gateway device can be compared and analyzed with the target gateway firmware version information;

[0097] Secondly, in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information does not belong to the target gateway firmware version information, a corresponding first comparison analysis result is generated, that is, the target gateway firmware version information does not belong to the latest version information;

[0098] Then, in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, generating a corresponding second comparative analysis result, that is, only the target gateway firmware version information belongs to the latest version information;

[0099] Furthermore, in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, a corresponding third comparative analysis result is generated, that is, the target gateway firmware version information and the gateway firmware version information sent by some other devices belong to the latest version information.

[0100] Thirdly, it should be noted that for step S130, the specific method of executing the corresponding gateway firmware collaborative management operation is not limited and can be selected according to actual needs.

[0101] For example, in an alternative implementation, in order to take into account both the reliability of firmware update and the resource consumption of message transmission, the above step S130 may further include the following contents:

[0102] First, when the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, determine other gateway devices with gateway firmware version information belonging to the latest version information, and request the other gateway devices to obtain the gateway firmware belonging to the latest version information, and after obtaining the gateway firmware, update the currently running firmware to the gateway firmware to complete the corresponding gateway firmware collaborative management operation;

[0103] Secondly, in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, determine other gateway devices whose gateway firmware version information does not belong to the latest version information, and send the target gateway firmware version information to the other gateway devices, and after obtaining the firmware request information sent by the other gateway devices based on the target gateway firmware version information, send the gateway firmware corresponding to the target gateway firmware version information to the other gateway devices to complete the corresponding gateway firmware collaborative management operation;

[0104] Furthermore, when, in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, it is determined that the corresponding gateway firmware collaborative management operation has been completed. At this time, for other gateway devices, it will be concluded that their own gateway firmware is not the latest version, and corresponding firmware requests will be made, which can also make the firmware versions of each gateway device consistent.

[0105] It should be noted that in a specific application example, after the gateway device successfully forms a network and establishes communication, when it receives a request from other gateway devices to obtain version information, it will first perform qualification verification to determine whether the requester and the current gateway device have the authority and conditions for mutual upgrade, including hardware solution inspection, software version number inspection, etc. If both parties meet the preset security policy and mutual trust relationship, the current gateway device will return its latest software version information; otherwise, it will return a notification that the upgrade conditions are not met. If the current gateway device has successfully sent version information to the requester and further receives the other party's instruction to request a complete software update package, it is also necessary to confirm again whether the requester still meets the requirements for mutual upgrade. Once the conditions are met, the current gateway device will read the latest firmware data from the local storage (Flash) and package it into a file format. Next, in order to ensure data security, the packaged file is encrypted using a pre-agreed encryption algorithm before transmission. After the encryption operation is completed and the verification is correct, the current gateway device sends the encrypted upgrade package data to the gateway device requesting the upgrade through the network, and ends the version sending process after the data is sent. If it is found that the upgrade conditions are not met at this time, the gateway device directly terminates the process of sending the upgrade package to prevent unauthorized or unsafe upgrade operations from occurring.

[0106] The encryption, decryption, integrity verification and identity verification processes are described as follows:

[0107] 1. Data encryption and synchronization: The encrypted transmission of software version information and upgrade packages adopts AES (Advanced Encryption Standard) symmetric encryption technology. Each gateway device has a pre-shared AES-256 key and uses AES-GCM (Galois / Counter Mode) mode to encrypt the upgrade package content to ensure safe and efficient data transmission in the networking environment. At the same time, the built-in authentication function of the GCM mode is used to prevent data tampering;

[0108] 2. Data decryption and verification: When the receiver decrypts and confirms the integrity, both parties use the same pre-shared AES key for decryption, and use the authentication tag provided by the GCM mode to verify the integrity of the data during transmission to ensure that it has not been illegally modified;

[0109] 3. Version information and update content integrity verification: ① Digital signature verification: Before sending version information and upgrade packages, each gateway device uses its own private key to generate a digital signature, which contains key information such as version number and source device identification code. After receiving it, other gateway devices use the public key to verify the digital signature to ensure that the source of the message is reliable and has not been tampered with; ② Hash verification: After decrypting the upgrade package, the gateway device calculates its SHA-256 secure hash value and compares it with the attached hash value to double-guarantee the integrity and consistency of the upgrade package content;

[0110] 4. Inter-gateway identity authentication (bidirectional identity authentication mechanism): When version information is exchanged and upgrade requests are made between gateway devices, not only version-related data is included, but also a security protocol agreed upon by both parties (an identity authentication token based on a public-private key pair) is carried out for identity verification. Both gateway devices will perform strict identity authentication before processing the request. Only gateway devices that have successfully passed the verification can obtain and push the latest software version, thereby achieving mutual trust upgrades between gateway devices.

[0111] In addition, during the process of requesting version information, you can configure at least 5 automatic retry mechanisms to ensure that you still have a chance to obtain version information when the network is unstable. If you fail to receive valid version information after multiple attempts, the log will be recorded and the synchronization process will be temporarily suspended, and you will wait for the next synchronization window (that is, the next version update).

[0112] Combination Figure 3 The embodiment of the present application also provides a FTTR-based gateway collaborative management device applicable to the above-mentioned gateway device. The FTTR-based gateway collaborative management device includes a firmware version information receiving module, a firmware version information comparison module and a firmware collaborative management module.

[0113] In detail, the firmware version information receiving module can be used to receive the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices, wherein each gateway device among the multiple gateway devices is configured to send the version information of the firmware currently running on itself to the other gateway devices in response to the networking success event of the multiple gateway devices. In the embodiment of the present application, the firmware version information receiving module can be used to perform Figure 2 As shown in step S110, the relevant contents of the firmware version information receiving module can refer to the above description of step S110.

[0114] In detail, the firmware version information comparison module can be used to compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain corresponding comparison and analysis results, wherein the target gateway firmware version information is the version information of the firmware currently running on the target gateway device. Figure 2 As shown in step S120, the relevant contents of the firmware version information comparison module can refer to the above description of step S120.

[0115] In detail, the firmware collaborative management module can be used to respond to the comparative analysis result and perform a corresponding gateway firmware collaborative management operation, wherein after performing the gateway firmware collaborative management operation, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information. Figure 2 As shown in step S130, the relevant contents of the firmware collaborative management module can refer to the above description of step S130.

[0116] In an embodiment of the present application, corresponding to the above-mentioned FTTR-based gateway collaborative management method applied to the gateway device, a computer-readable storage medium is also provided, in which a computer program is stored, and when the computer program is run, each step of the FTTR-based gateway collaborative management method is executed.

[0117] Among them, the steps executed when the aforementioned computer program is running will not be described one by one here, and reference may be made to the explanation of the aforementioned FTTR-based gateway collaborative management method in the previous text.

[0118] In summary, the gateway collaborative management method and apparatus, device and medium based on FTTR provided by the present application can receive the gateway firmware version information sent by any other gateway device in response to the networking success event of multiple gateway devices; secondly, the gateway firmware version information sent by each other gateway device is compared and analyzed with the target gateway firmware version information to obtain the corresponding comparative analysis result; then, in response to the comparative analysis result, the corresponding gateway firmware collaborative management operation is performed, wherein, after the gateway firmware collaborative management operation is performed, the version information of the firmware currently running by each gateway device in the multiple gateway devices belongs to the latest version information. Based on the above content, since the networking success event is used as the trigger mechanism for firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, thereby avoiding compatibility failures, network instability, service abnormalities and other problems caused by inconsistent firmware versions, thereby ensuring the communication reliability between gateway devices, so that the problem of low gateway communication reliability existing in the prior art can be improved, and reliable collaborative work between gateway devices can be achieved, thereby ensuring the whole-house network performance and stability of FTTR.

[0119] In several embodiments provided in the embodiments of the present application, it should be understood that the disclosed device and method can also be implemented in other ways. The device and method embodiments described above are merely schematic, for example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the device, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0120] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0121] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, electronic device, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code. It should be noted that in this article, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0122] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A gateway collaborative management method based on FTTR, characterized in that: A target gateway device applied to a gateway collaborative management system based on FTTR, wherein the gateway collaborative management system based on FTTR includes multiple gateway devices that have established communication connections with each other, the target gateway device belongs to any one of the multiple gateway devices, and the gateway collaborative management method based on FTTR includes: Receiving gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to a networking success event of the multiple gateway devices, wherein each gateway device among the multiple gateway devices is configured to send version information of its currently running firmware to the other gateway devices in response to the networking success event of the multiple gateway devices; Comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain corresponding comparative analysis results, wherein the target gateway firmware version information is the version information of the firmware currently running on the target gateway device; In response to the comparison and analysis result, a corresponding gateway firmware collaborative management operation is performed, wherein after the gateway firmware collaborative management operation is performed, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information.

2. The FTTR-based gateway collaborative management method according to claim 1, characterized in that: The step of receiving the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices includes: Performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one gateway device among the multiple gateway devices that has been offline and then has come online again; An event that at least one of the multiple gateway devices comes back online after being offline is taken as a networking success event, and in response to the networking success event, version information of the firmware currently running on the gateway device is sent to each other gateway device in the multiple gateway devices; Receive gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

3. The FTTR-based gateway collaborative management method according to claim 2, characterized in that: The step of taking the event that at least one gateway device among the multiple gateway devices comes back online after being offline as a networking success event, and sending version information of the firmware currently running on the gateway device to each other gateway device among the multiple gateway devices in response to the networking success event, comprises: After determining that there is at least one gateway device among the multiple gateway devices that has been offline and then come back online, for each of the at least one gateway device that has come back online, send a log query request message to the gateway device, and receive device operation log data sent by the gateway device in response to the log query request message, wherein the device operation log data at least includes record data of each offline and online return of the corresponding gateway device in history; For each of the at least one gateway device that has come back online, based on the device operation log data corresponding to the gateway device, analyze the time change characteristics of the gateway device with respect to being offline and coming back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the characteristic matching result corresponding to the gateway device; When the feature matching result corresponding to any one of the at least one gateway devices that are back online is a match, a networking success event is generated, and in response to the networking success event, version information of the firmware currently running on the other gateway devices is sent to each other gateway device among the multiple gateway devices, wherein when the feature matching result corresponding to each of the at least one gateway device that is back online is a mismatch, it is determined that no networking success event is generated.

4. The FTTR-based gateway collaborative management method according to claim 3, characterized in that: The step of analyzing, for each of the at least one gateway device that has come back online, a time variation feature of the gateway device regarding offline and coming back online based on the device operation log data corresponding to the gateway device, and determining whether the time variation feature matches a predetermined target variation feature, and obtaining a feature matching result corresponding to the gateway device, comprises: For each gateway device of the at least one gateway device that is back online, obtaining the running time of the gateway device, and comparing the running time with a pre-configured target running time; For each gateway device among the at least one gateway device that has come back online, when the running time of the gateway device is greater than the target running time, based on the device running log data corresponding to the gateway device, analyzing the time change feature of the gateway device regarding being offline and coming back online, and determining whether the time change feature matches a predetermined target change feature, and obtaining a feature matching result corresponding to the gateway device; For each gateway device among at least one gateway device that is back online, when the operating time of the gateway device is not greater than the target operating time, among the other gateway devices, determine one other gateway device with the highest device correlation with the gateway device, and send a log query request message to the other gateway device, and receive device operation log data sent by the other gateway device in response to the log query request message, and use the device operation log data as the device operation log data added by the gateway device, and, based on the device operation log data corresponding to the gateway device and the added device operation log data, analyze the time change characteristics of the gateway device regarding offline and back online, and determine whether the time change characteristics match the predetermined target change characteristics, and obtain the feature matching result corresponding to the gateway device, wherein the added device operation log data at least includes the record data of each offline and back online of the corresponding gateway device in history.

5. The FTTR-based gateway collaborative management method according to claim 1, characterized in that: The step of receiving the gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to the networking success event of the multiple gateway devices includes: Performing a status monitoring operation on the multiple gateway devices to determine whether there is at least one newly added gateway device among the multiple gateway devices; Taking the event that at least one newly added gateway device exists in the plurality of gateway devices as a networking success event, and in response to the networking success event, sending version information of the firmware currently running on the gateway device to each other gateway device in the plurality of gateway devices; Receive gateway firmware version information sent by each other gateway device among the multiple gateway devices in response to the networking success event.

6. The FTTR-based gateway collaborative management method according to claim 1, characterized in that: The step of comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain a corresponding comparison and analysis result includes: Compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information; When the latest version information of the gateway firmware version information sent by each other gateway device and the target gateway firmware version information does not belong to the target gateway firmware version information, generating a corresponding first comparison analysis result; In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, generating a corresponding second comparison analysis result; In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, a corresponding third comparative analysis result is generated.

7. The FTTR-based gateway collaborative management method according to any one of claims 1 to 6, characterized in that: The step of executing a corresponding gateway firmware collaborative management operation in response to the comparative analysis result includes: When the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, determine other gateway devices with gateway firmware version information belonging to the latest version information, and request the other gateway devices to obtain the gateway firmware belonging to the latest version information, and after obtaining the gateway firmware, update the currently running firmware to the gateway firmware to complete the corresponding gateway firmware collaborative management operation; In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by each other gateway device is different from the target gateway firmware version information, determine other gateway devices whose gateway firmware version information does not belong to the latest version information, and send the target gateway firmware version information to the other gateway devices, and after obtaining the firmware request information sent by the other gateway devices based on the target gateway firmware version information, send the gateway firmware corresponding to the target gateway firmware version information to the other gateway devices, so as to complete the corresponding gateway firmware collaborative management operation; In the gateway firmware version information sent by each other gateway device and the target gateway firmware version information, when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information sent by at least one other gateway device is the same as the target gateway firmware version information, it is determined that the corresponding gateway firmware collaborative management operation has been completed.

8. A gateway collaborative management device based on FTTR, characterized in that: A target gateway device applied to a gateway collaborative management system based on FTTR, wherein the gateway collaborative management system based on FTTR includes multiple gateway devices that have established communication connections with each other, the target gateway device belongs to any one of the multiple gateway devices, and the gateway collaborative management device based on FTTR includes: A firmware version information receiving module, configured to receive gateway firmware version information sent by any other gateway device among the multiple gateway devices in response to a networking success event of the multiple gateway devices, wherein each gateway device among the multiple gateway devices is configured to send version information of its currently running firmware to other gateway devices in response to the networking success event of the multiple gateway devices; A firmware version information comparison module, used to compare and analyze the gateway firmware version information sent by each other gateway device with the target gateway firmware version information to obtain a corresponding comparison and analysis result, wherein the target gateway firmware version information is the version information of the firmware currently running on the target gateway device; The firmware collaborative management module is used to execute corresponding gateway firmware collaborative management operations in response to the comparison and analysis results, wherein after executing the gateway firmware collaborative management operations, the version information of the firmware currently running on each of the multiple gateway devices belongs to the latest version information.

9. A gateway device, characterized in that: include: Memory for storing computer programs; A processor connected to the memory is used to execute the computer program stored in the memory to implement the FTTR-based gateway collaborative management method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is run, the FTTR-based gateway collaborative management method according to any one of claims 1 to 7 is executed.

Images