CN119071154B - Gateway collaborative management method, device, equipment and medium based on FTTR - Google Patents
Gateway collaborative management method, device, equipment and medium based on FTTR Download PDFInfo
- Publication number
- CN119071154B CN119071154B CN202411560035.0A CN202411560035A CN119071154B CN 119071154 B CN119071154 B CN 119071154B CN 202411560035 A CN202411560035 A CN 202411560035A CN 119071154 B CN119071154 B CN 119071154B
- Authority
- CN
- China
- Prior art keywords
- gateway
- version information
- firmware
- gateway device
- devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 102
- 230000006855 networking Effects 0.000 claims abstract description 70
- 230000004044 response Effects 0.000 claims abstract description 52
- 238000004891 communication Methods 0.000 claims abstract description 18
- 238000010835 comparative analysis Methods 0.000 claims abstract 6
- 230000008859 change Effects 0.000 claims description 36
- 238000004458 analytical method Methods 0.000 claims description 30
- 238000004590 computer program Methods 0.000 claims description 14
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000000034 method Methods 0.000 abstract description 20
- 230000005540 biological transmission Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000012795 verification Methods 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000470 constituent Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/283—Processing of data at an internetworking point of a home automation network
- H04L12/2834—Switching of information between an external network and a home network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a FTTR-based gateway collaborative management method and a FTTR-based gateway collaborative management device an apparatus and a medium thereof, relates to the technical field of gateway communication. The method comprises the steps of firstly, receiving gateway firmware version information sent by any one of a plurality of gateway devices in response to a networking success event of the plurality of gateway devices, secondly, carrying out comparative analysis on the gateway firmware version information sent by each other gateway device and target gateway firmware version information to obtain a corresponding comparative analysis result, and then, responding to the comparative analysis result, executing corresponding gateway firmware collaborative management operation, wherein after the gateway firmware collaborative management operation is executed, the version information of the firmware currently operated by each gateway device in the plurality of gateway devices belongs to the latest version information. Based on the above, the problem that the performance and stability of FTTR full-house network in the prior art are difficult to be effectively ensured can be improved.
Description
Technical Field
The application relates to the technical field of gateway communication, in particular to a FTTR-based gateway collaborative management method, a FTTR-based gateway collaborative management device, equipment and a medium.
Background
FTTR (Fiber to The Room) technology is an innovative deployment scheme of home and small enterprise internal networks, which replaces the traditional network cable with optical fibers, extends the optical fibers to each independent space, and realizes seamless interconnection with home main gateway by deploying optical network terminal equipment. The corresponding networking system mainly comprises a main gateway, a secondary gateway, a router with similar functions and other components, and the components can be flexibly networked in a fiber direct connection, wired transmission or wireless mode.
However, the inventor researches and discovers that, since the performance and stability of the full-house network of FTTR are greatly dependent on the cooperative work among the constituent devices, the reliability of the cooperative work among the constituent devices needs to be improved, that is, the reliability of gateway communication needs to be ensured, but in the prior art, the reliability of gateway communication is relatively low, so that the performance and stability of the full-house network of FTTR are difficult to be effectively ensured.
Disclosure of Invention
In view of the above, the present application aims to provide a method, a device and a medium for gateway collaborative management based on FTTR, so as to solve the problem that the performance and stability of the FTTR whole-house network in the prior art are difficult to be effectively ensured.
In order to achieve the above purpose, the application adopts the following technical scheme:
A FTTR-based gateway collaborative management method applied to target gateway equipment in a FTTR-based gateway collaborative management system, wherein the FTTR-based gateway collaborative management system comprises a plurality of gateway equipment with communication connection established with each other, the target gateway equipment belongs to any one gateway equipment of the plurality of gateway equipment, and the FTTR-based gateway collaborative management method comprises the following steps:
Receiving gateway firmware version information sent by any one other gateway device of the plurality of gateway devices in response to a networking success event of the plurality of gateway devices, wherein each gateway device of the plurality of gateway devices is configured to send version information of firmware currently running by itself to the other gateway devices in response to the networking success event of the plurality of 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 a corresponding comparison analysis result, wherein the target gateway firmware version information is the version information of the firmware currently operated by the target gateway device;
And responding to the comparison analysis result, executing corresponding gateway firmware collaborative management operation, wherein after executing the gateway firmware collaborative management operation, the version information of the firmware currently operated by each gateway device in the plurality of gateway devices belongs to the latest version information.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, the step of receiving gateway firmware version information sent by any one of the other gateway devices in the plurality of gateway devices in response to a networking success event of the plurality of gateway devices includes:
Performing state monitoring operation on the plurality of gateway devices to determine whether at least one gateway device which is on line again after the disconnection exists in the plurality of gateway devices;
taking an event of at least one gateway device which is on line again after the disconnection in the plurality of gateway devices as a networking success event, and responding to the networking success event, and sending version information of firmware which runs currently to each other gateway device in the plurality of gateway devices;
gateway firmware version information sent by each other gateway device of the plurality of gateway devices in response to the networking success event is received.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, the step of using an event of at least one gateway device that is on line again after the existence of the dropped line in the plurality of gateway devices as a networking success event, and transmitting version information of firmware currently running in itself to each other gateway device in the plurality of gateway devices in response to the networking success event includes:
After determining that at least one gateway device which is on line again after the disconnection exists in the plurality of gateway devices, sending log inquiry request information to each gateway device in the at least one gateway device which is on line again, and receiving device operation log data sent by the gateway device in response to the log inquiry request information, wherein the device operation log data at least comprises record data of each disconnection and line again of the corresponding gateway device in history;
Aiming at each gateway device in at least one online device, analyzing the time change characteristics of the gateway device about offline and online device based on the device operation log data corresponding to the gateway device, and determining whether the time change characteristics are matched with the predetermined target change characteristics or not to obtain a characteristic matching result corresponding to the gateway device;
Generating a networking success event when the feature matching result corresponding to any one of the at least one online gateway device belongs to matching, and responding to the networking success event, and sending the version information of the firmware currently running to each other gateway device in the plurality of gateway devices, wherein when the feature matching result corresponding to each gateway device in the at least one online gateway device belongs to non-matching, the networking success event is determined not to be generated.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, the step of analyzing the time variation characteristics of the gateway device about disconnection and re-connection based on the device operation log data corresponding to the gateway device for each gateway device in the at least one re-connection, and determining whether the time variation characteristics are matched with predetermined target variation characteristics, to obtain a feature matching result corresponding to the gateway device includes:
For each gateway device in at least one online device, acquiring the operation time length of the gateway device, and comparing the operation time length with a preset target operation time length;
Aiming at each gateway device in at least one online device, when the running time of the gateway device is longer than the target running time, analyzing the time change characteristics of the gateway device about offline and online device, and determining whether the time change characteristics are matched with the predetermined target change characteristics or not, so as to obtain a characteristic matching result corresponding to the gateway device;
And for each gateway device in at least one online re-connection gateway device, when the operation time of the gateway device is not more than the target operation time, determining one other gateway device with highest device correlation with the gateway device in other gateway devices, sending log query request information to the other gateway device, receiving device operation log data sent by the other gateway device in response to the log query request information, taking the device operation log data as added device operation log data of the gateway device, analyzing time change characteristics of the gateway device about offline and online re-connection based on the device operation log data corresponding to the gateway device and the added device operation log data, determining whether the time change characteristics are matched with the predetermined target change characteristics, and obtaining a characteristic matching result corresponding to the gateway device, wherein the added device operation log data at least comprises historical record data of each offline and online re-connection of the corresponding gateway device.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, the step of receiving gateway firmware version information sent by any one of the other gateway devices in the plurality of gateway devices in response to a networking success event of the plurality of gateway devices includes:
Performing a state monitoring operation on the plurality of gateway devices to determine whether there is at least one newly added gateway device of the plurality of gateway devices;
Taking an event that at least one newly added gateway device exists in the plurality of gateway devices as a networking success event, and responding to the networking success event, and sending version information of firmware currently running by the gateway device to each other gateway device in the plurality of gateway devices;
gateway firmware version information sent by each other gateway device of the plurality of gateway devices in response to the networking success event is received.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, 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 analysis result includes:
Comparing and analyzing the gateway firmware version information sent by each other gateway device with the target gateway firmware version information;
Generating a corresponding first comparison analysis result when the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information transmitted by each other gateway device;
Generating a corresponding second comparison analysis result when the latest version information belongs to the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information sent by each other gateway device and the gateway firmware version information sent by each other gateway device are different;
And generating a corresponding third comparison analysis result when the latest version information belongs to the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information transmitted by each other gateway device and the gateway firmware version information transmitted by at least one other gateway device is the same.
In a preferred option of the present application, in the gateway collaborative management method based on FTTR, the step of executing a corresponding gateway firmware collaborative management operation in response to the comparison analysis result includes:
Determining other gateway equipment of the gateway firmware version information belonging to the latest version information when the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information sent by each other gateway equipment, requesting to acquire the gateway firmware belonging to the latest version information from the other gateway equipment, and updating the currently operated firmware into the gateway firmware after acquiring the gateway firmware so as to complete corresponding gateway firmware collaborative management operation;
Determining other gateway devices which do not belong to gateway firmware version information of the latest version information when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information transmitted by each other gateway device is different from the target gateway firmware version information in the gateway firmware version information transmitted by each other gateway device, transmitting the target gateway firmware version information to the other gateway devices, and transmitting gateway firmware corresponding to the target gateway firmware version information to the other gateway devices after acquiring firmware request information transmitted by the other gateway devices based on the target gateway firmware version information so as to complete corresponding gateway firmware collaborative management operation;
And when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information transmitted by at least one other gateway device is the same as the target gateway firmware version information, determining that the corresponding gateway firmware collaborative management operation is completed.
The application also provides a gateway collaborative management device based on FTTR, which is applied to target gateway equipment in a gateway collaborative management system based on FTTR, wherein the gateway collaborative management system based on FTTR comprises a plurality of gateway equipment which are mutually established with communication connection, the target gateway equipment belongs to any gateway equipment of the plurality of gateway equipment, and the gateway collaborative management device based on FTTR comprises:
A firmware version information receiving module, configured to receive gateway firmware version information sent by any one of the plurality of gateway devices in response to a networking success event of the plurality of gateway devices, where each of the plurality of gateway devices is configured to send version information of firmware currently running by itself to the other gateway devices in response to the networking success event of the plurality of gateway devices;
The firmware version information comparison module is used for 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 analysis result, wherein the target gateway firmware version information is the version information of the firmware currently operated by the target gateway device;
And the firmware collaborative management module is used for responding to the comparison analysis result and executing corresponding gateway firmware collaborative management operation, wherein after the gateway firmware collaborative management operation is executed, the version information of the firmware currently operated by each gateway device in the plurality of gateway devices belongs to the latest version information.
On the basis of the above, the present application also provides a gateway device, including:
a memory for storing a computer program;
And the processor is connected with the memory and is used for executing the computer program stored in the memory so as to realize the gateway collaborative management method based on FTTR.
On the basis of the above, the present application also provides a computer readable storage medium, in which a computer program is stored, and the computer program executes the steps of the gateway collaborative management method based on FTTR.
The gateway collaborative management method, the gateway collaborative management device, the gateway collaborative management equipment and the gateway collaborative management medium based on FTTR can receive gateway firmware version information sent by any one other gateway equipment in the plurality of gateway equipment in response to a networking success event of the plurality of gateway equipment, compare and analyze the gateway firmware version information sent by each other gateway equipment with target gateway firmware version information to obtain a corresponding comparison analysis result, and then respond to the comparison analysis result to execute corresponding gateway firmware collaborative management operation, wherein after the gateway firmware collaborative management operation is executed, the version information of the currently running firmware of each gateway equipment in the plurality of gateway equipment belongs to the latest version information. Based on the above, since the networking success event is used as a trigger mechanism of firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, and the problems of compatibility failure, network instability, abnormal service and the like caused by inconsistent firmware versions are avoided, so that the communication reliability between gateway devices is ensured, the problem of low gateway communication reliability in the prior art can be improved, the reliable collaborative work between gateway devices is realized, and the whole house network performance and stability of FTTR are ensured.
Drawings
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Fig. 1 is a block diagram of a gateway device according to an embodiment of the present application.
Fig. 2 is a flow chart of a gateway collaborative management method based on FTTR according to an embodiment of the present application.
Fig. 3 is a block diagram of a gateway collaboration management apparatus based on FTTR according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
As shown in fig. 1, an embodiment of the present application provides a gateway device. The gateway device may include a memory, a processor, and FTTR-based gateway co-management means.
In detail, the memory and the processor are electrically connected directly or indirectly to realize data transmission. For example, the memory and the processor may be electrically connected by one or more communication buses or signal lines. The FTTR-based gateway co-management apparatus includes at least one software function module stored in the memory in the form of software or firmware (firmware). The processor is configured to execute an executable computer program stored in the memory, for example, a software function module and a computer program included in the FTTR-based gateway cooperative management apparatus, so as to implement the FTTR-based gateway cooperative management method provided by the embodiment of the present application.
Alternatively, the Memory may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
And the processor may be a general-purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a System on Chip (SoC), etc., a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
It will be appreciated that the architecture shown in fig. 1 is merely illustrative, and that the gateway device may also include more or fewer components than shown in fig. 1, or may have a different configuration than shown in fig. 1, e.g., may also include a communication unit for information interaction with other devices, such as other gateway devices.
With reference to fig. 2, the embodiment of the application further provides a gateway collaborative management method based on FTTR, which can be applied to the gateway device. The method steps defined by the flow related to the gateway collaborative management method based on FTTR may be implemented by the gateway device, the gateway device may be a target gateway device in a gateway collaborative management system based on FTTR, the gateway collaborative management system based on FTTR may include a plurality of gateway devices that mutually establish communication connection, and the target gateway device belongs to any one gateway device of the plurality of gateway devices.
The specific flow shown in fig. 2 will be described in detail.
Step S110, receiving gateway firmware version information sent by any one other gateway device of the plurality of gateway devices in response to the networking success event of the plurality of gateway devices.
In the embodiment of the application, the target gateway device may receive gateway firmware version information sent by any one other gateway device of the plurality of gateway devices in response to a networking success event of the plurality of gateway devices. Wherein each gateway device of the plurality of gateway devices is configured to send version information of firmware currently running by itself to other gateway devices in response to a networking success event of the plurality of gateway devices, such that each gateway device of the plurality of gateway devices can receive the version information of the firmware of the other gateway devices.
And 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 a corresponding comparison analysis result.
In the embodiment of the 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 a corresponding comparison analysis result. The target gateway firmware version information is version information of firmware currently operated by the target gateway equipment. That is, the firmware version information of the device itself may be compared with the firmware version information of other network devices.
And step S130, corresponding gateway firmware collaborative management operation is executed in response to the comparison analysis result.
In the embodiment of the application, the target gateway device can respond to the comparison analysis result to execute corresponding gateway firmware collaborative management operation. The specific content of the gateway firmware collaborative management operation is not limited, and after the gateway firmware collaborative management operation is executed, the version information of the firmware currently operated by each gateway device in the plurality of gateway devices belongs to the latest version information.
Based on the above, since the networking success event is used as a trigger mechanism of firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, and the problems of compatibility failure, network instability, abnormal service and the like caused by inconsistent firmware versions are avoided, so that the communication reliability between gateway devices is ensured, the problem of low gateway communication reliability in the prior art can be improved, the reliable collaborative work between gateway devices is realized, and the whole house network performance and stability of FTTR are ensured.
In the first aspect, it should be noted that, in step S110, the specific manner of receiving the gateway firmware version information sent in response to the networking success event is not limited, and may be selected according to actual requirements.
For example, in an alternative embodiment, in order to ensure the reliability of the collaborative management operation of the gateway firmware, the step S110 may further include a step S111, a step S112, and a step S113, where the specific contents of each step are as follows.
Step S111, performing a status monitoring operation on the plurality of gateway devices to determine whether there is at least one newly added gateway device in the plurality of gateway devices.
In the embodiment of the application, the state monitoring operation can be performed on the gateway devices to determine whether at least one newly added gateway device exists in the gateway devices.
And step S112, taking the event that at least one newly added gateway device exists in the gateway devices as a networking success event, and responding to the networking success event, and sending the version information of the firmware currently running to each other gateway device in the gateway devices.
In the embodiment of the application, the event that at least one newly added gateway device exists in the plurality of gateway devices is taken as a networking success event, and the version information of the firmware which is currently operated by the gateway device is sent to each other gateway device in the plurality of gateway devices in response to the networking success event. That is, for newly added gateway devices, generally, firmware versions of the newly added gateway devices may be different from those of other gateway devices in the current network, so that there is a problem of poor cooperativity, and thus, updating of corresponding firmware versions is required.
Step S113, receiving gateway firmware version information sent by each other gateway device of the plurality of gateway devices in response to the networking success event.
In the embodiment of the application, gateway firmware version information sent by each other gateway device in the plurality of gateway devices in response to the networking success event can be received.
For another example, in another alternative embodiment, also to ensure the reliability of the collaborative management operation of the gateway firmware, the step S110 may further include a step S114, a step S115, and a step S116, where the specific details of each step are as follows.
Step S114, performing a status monitoring operation on the plurality of gateway devices to determine whether there is at least one gateway device that is on-line again after the disconnection in the plurality of gateway devices.
In the embodiment of the application, the state monitoring operation can be performed on the plurality of gateway devices to determine whether at least one gateway device which is on line again after the disconnection exists in the plurality of gateway devices. Illustratively, each gateway device is configured to broadcast its own re-online information to other gateway devices after re-online, and each gateway device is also configured to monitor the re-online information broadcast by other gateway devices (specifically, may be monitoring a designated port), so that the status of the other gateway devices may be obtained in time, thereby determining whether there is at least one gateway device that is re-online after the offline in the plurality of gateway devices.
Step S115, taking the event of at least one gateway device on line again after the existence of the disconnection in the plurality of gateway devices as a networking success event, and responding to the networking success event, sending the version information of the firmware currently running by itself to each other gateway device in the plurality of gateway devices.
In the embodiment of the application, the event of at least one gateway device which is on line again after the disconnection exists in the plurality of gateway devices can be used as a networking success event, and the version information of the firmware which is currently operated by the gateway device is sent to each other gateway device in the plurality of gateway devices in response to the networking success event. That is, if there is at least one gateway device that is disconnected and then re-connected, the networking success event can be considered to occur.
Step S116, receiving gateway firmware version information sent by each other gateway device of the plurality of gateway devices in response to the networking success event.
In the embodiment of the application, gateway firmware version information sent by each other gateway device in the plurality of gateway devices in response to the networking success event can be received. That is, when at least one gateway device is disconnected and then is on-line again, a subsequent firmware version update determination operation may be performed, that is, when there is a disconnection, there may be an interruption of the update (i.e., an update failure) of the firmware version due to the disconnection, so that the consistency between the firmware versions of the gateway device is poor, and thus, a subsequent firmware version update determination operation is required.
It may be understood that, in the step S115, a specific manner of taking the event of at least one gateway device that is on line again after the disconnection in the plurality of gateway devices as the networking success event is not limited, and may be selected according to actual requirements, for example, in an alternative embodiment, in order to consider the reliability of firmware update and the resource consumption problem of information transmission, the step S115 may further include a step S115a, a step S115b, and a step S115c, where specific contents of each step are as follows.
Step S115a, after determining that there is at least one gateway device that is on-line again after the disconnection in the plurality of gateway devices, for each gateway device in the at least one gateway device that is on-line again, sending log query request information to the gateway device, and receiving device running log data sent by the gateway device in response to the log query request information.
In the embodiment of the application, after determining that at least one gateway device which is on line again after the disconnection exists in the plurality of gateway devices, for each gateway device in the at least one gateway device which is on line again, log inquiry request information can be sent to the gateway device, and device running log data sent by the gateway device in response to the log inquiry request information can be received. The device running log data at least comprises record data of each time of the corresponding gateway device is dropped and re-uploaded in history. In a specific application example, in order to reduce resource consumption of log data transmission, the device running log data may only include recorded data of each offline and online again of the corresponding gateway device in a recent period of time (such as a day, a week, a month, etc.).
Step S115b, for each gateway device in the at least one re-online gateway device, based on the device running log data corresponding to the gateway device, analyzing the time variation characteristics of the gateway device about the offline and the re-online gateway device, and determining whether the time variation characteristics are matched with the predetermined target variation characteristics, so as to obtain a feature matching result corresponding to the gateway device.
In the embodiment of the application, for each gateway device in at least one re-online gateway device, based on the device running log data corresponding to the gateway device, the time change characteristics of the gateway device about offline and re-online are analyzed, whether the time change characteristics are matched with the predetermined target change characteristics or not is determined, and the characteristic matching result corresponding to the gateway device is obtained. The time-varying feature may refer to at least one of information such as the number of dropped lines and re-line lines, frequency, trend, etc., and is not particularly limited, and may be selected according to actual requirements.
Step S115c, when the feature matching result corresponding to any one of the at least one online gateway device belongs to matching, generating a networking success event, and in response to the networking success event, transmitting version information of the firmware currently running by itself to each other gateway device of the plurality of gateway devices.
In the embodiment of the application, when the feature matching result corresponding to any one of the at least one gateway device which is on line again belongs to matching, a networking success event is generated, and in response to the networking success event, version information of firmware which runs currently is sent to each other gateway device in the plurality of gateway devices. And when the feature matching result corresponding to each gateway device in the at least one online gateway device belongs to mismatch, determining that the networking success event is not generated. For example, the feature matching result belongs to matching, which may mean that the number or frequency of times or frequency of disconnection and re-connection of the gateway device is smaller than a preset number or preset frequency (a specific numerical value may be configured according to actual requirements), so that the problem of transmission resource waste caused by high-frequency version information transmission due to high-frequency disconnection can be avoided.
It will be appreciated that in the step S115b, the specific manner of analyzing the time-varying characteristics of the gateway device about disconnection and re-connection is not limited, and may be selected according to practical requirements, for example, in an alternative embodiment, in order to further ensure the reliability of the analyzed time-varying characteristics, the step S115b may include the steps b1, b2 and b3, and the specific contents of each step are as follows.
Step b1, for each gateway device in the at least one online device, acquiring the operation duration of the gateway device, and comparing the operation duration with a preset target operation duration.
In the embodiment of the application, for each gateway device in the at least one online device, the operation time length of the gateway device can be acquired, and the operation time length is compared with the preset target operation time length. The specific length of the target operation duration is not limited, and may be selected according to actual requirements, for example, one day, one week, etc.
And b2, aiming at each gateway device in at least one online re-entry, when the operation time length of the gateway device is longer than the target operation time length, analyzing the time change characteristics of the gateway device about offline and online re-entry based on the device operation log data corresponding to the gateway device, and determining whether the time change characteristics are matched with the predetermined target change characteristics or not to obtain a characteristic matching result corresponding to the gateway device.
In the embodiment of the application, aiming at each gateway device in at least one online re-entry, when the running time of the gateway device is longer than the target running time, based on the device running log data corresponding to the gateway device, the time change characteristics of the gateway device about offline and online re-entry are analyzed, whether the time change characteristics are matched with the predetermined target change characteristics or not is determined, and a characteristic matching result corresponding to the gateway device is obtained. That is, when the running duration of the gateway device itself is long, the device running log data of the gateway device itself is sufficient, so that the device running log data of the gateway device itself can be analyzed to obtain the corresponding time variation characteristic.
And b3, determining one other gateway device with highest device correlation with the gateway device in each other gateway device when the running time of the gateway device is not longer than the target running time, sending log query request information to the other gateway device, receiving device running log data sent by the other gateway device in response to the log query request information, taking the device running log data as added device running log data of the gateway device, analyzing time change characteristics of the gateway device about disconnection and re-disconnection based on the device running log data and the added device running log data corresponding to the gateway device, determining whether the time change characteristics are matched with the predetermined target change characteristics, and obtaining a characteristic matching result corresponding to the gateway device.
In the embodiment of the application, for each gateway device in at least one online device, when the operation time of the gateway device is not longer than the target operation time, determining one other gateway device with highest device correlation with the gateway device in other gateway devices, sending log query request information to the other gateway device, receiving device operation log data sent by the other gateway device in response to the log query request information, taking the device operation log data as added device operation log data of the gateway device, analyzing time change characteristics of the gateway device about offline and online again based on the device operation log data corresponding to the gateway device and the added device operation log data, and determining whether the time change characteristics are matched with the predetermined target change characteristics to obtain characteristic matching results corresponding to the gateway device, wherein the added device operation log data at least comprises record data of each offline and online again of the corresponding gateway device in history. That is, when the running duration of the gateway device itself is shorter, the device running log data of the gateway device itself is not sufficient compared with the running log data of the gateway device itself, so that the device running log data of one other gateway device with the highest device correlation can be obtained to perform data expansion based on the device running log data of the gateway device itself, for example, the number of dropped lines of one other gateway device with the highest device correlation can be accumulated with the number of dropped lines of the gateway device itself (or weighted summation, and the weighting coefficient corresponding to the number of dropped lines of the gateway device itself can be larger than the number of dropped lines of the other gateway device).
It should be noted that, in the foregoing, the device correlation may refer to a type of gateway device, for example, the same type. Or in other embodiments, the device correlation may be a similarity of terminal devices connected to the gateway device, for example, all connected terminal devices.
In the second aspect, it should be noted that, in step S120, a specific manner 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 may be selected according to actual requirements.
For example, in an alternative embodiment, in order to ensure that the obtained comparison analysis result can sufficiently reflect the relationship between firmware versions, so that the reliability (granularity of operation is finer) of the gateway firmware collaborative management operation performed subsequently based on the comparison analysis result, the above step S120 may further include the following:
Firstly, gateway firmware version information sent by each other gateway device and the target gateway firmware version information can be compared and analyzed;
Secondly, when the latest version information does not belong to the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information sent by each other gateway device, a corresponding first comparison analysis result is generated, that is, the target gateway firmware version information does not belong to the latest version information;
Then, generating a corresponding second comparison analysis result when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information transmitted by each other gateway device is different from the target gateway firmware version information in the gateway firmware version information transmitted by each other gateway device and the target gateway firmware version information, namely, only the target gateway firmware version information belongs to the latest version information;
And generating a corresponding third comparison analysis result when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information transmitted by at least one other gateway device is the same as the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information transmitted by each other gateway device, that is, the target gateway firmware version information and part of the gateway firmware version information transmitted by other devices belong to the latest version information.
In the third aspect, it should be noted that, in step S130, a specific manner of executing the corresponding gateway firmware collaborative management operation is not limited, and may be selected according to actual requirements.
For example, in an alternative embodiment, in order to consider both the reliability of the firmware update and the resource consumption problem of the message transmission, the above step S130 may further include the following:
Firstly, determining other gateway equipment of gateway firmware version information belonging to the latest version information when the latest version information does not belong to the target gateway firmware version information in gateway firmware version information and target gateway firmware version information sent by each other gateway equipment, requesting to acquire the gateway firmware belonging to the latest version information from the other gateway equipment, and updating the currently operated firmware into the gateway firmware after acquiring the gateway firmware so as to complete corresponding gateway firmware collaborative management operation;
Secondly, determining other gateway devices which do not belong to the gateway firmware version information of the latest 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 in the gateway firmware version information and the target gateway firmware version information sent by each other gateway device, sending 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, sending the gateway firmware corresponding to the target gateway firmware version information to the other gateway devices so as to complete corresponding gateway firmware collaborative management operation;
And determining that corresponding gateway firmware collaborative management operation is completed when the latest version information belongs to the target gateway firmware version information and the gateway firmware version information transmitted by at least one other gateway device is the same as the target gateway firmware version information in the gateway firmware version information and the target gateway firmware version information transmitted by each other gateway device, and at this time, for the other gateway devices, obtaining a conclusion that own gateway firmware is not the latest version, carrying out corresponding firmware request, and also enabling the firmware versions of the gateway devices to be consistent.
It should be noted that, in a specific application example, after the gateway device successfully organizes and establishes communication, when receiving a request for other gateway devices to acquire version information, qualification verification is performed first to determine whether the requester and the current gateway device have mutually updated rights and conditions, including checking a hardware scheme, checking a software version number, and the like. If the two parties accord with the preset security policy and the mutual trust relationship, the current gateway equipment returns the latest software version information of the gateway equipment, otherwise, a notification that the upgrading condition is not met is returned. If the current gateway device has successfully sent version information to the requester and further receives an instruction that the counterpart requests to acquire the complete software update package, it is also necessary to confirm again whether the requester still meets the requirement of mutual upgrade. Once eligible, the current gateway device will read the latest firmware data from local storage (Flash) and package it into a file format. Next, in order to secure data, 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 equipment transmits the encrypted upgrade package data to the gateway equipment requesting the upgrade through the network, and the version transmission flow is ended after the data transmission is completed. If the upgrade condition is not met, the gateway device directly terminates the process of sending the upgrade package, so as to prevent unauthorized or unsafe upgrade operation.
The encryption, decryption, integrity verification and identity verification processes are described as follows:
1. The encryption transmission of software version information and an upgrade package adopts AES (Advanced Encryption Standard) symmetrical encryption technology, each gateway device has a pre-shared AES-256 key, and uses an AES-GCM (Galois/Counter Mode) Mode to encrypt the upgrade package content so as to ensure safe and efficient data transmission in a networking environment, and meanwhile, the data tampering is prevented through an identity verification function built in the GCM Mode;
2. When the receiving party decrypts and confirms the integrity, both parties decrypt by using the same pre-shared AES key, and verify the integrity of the data in the transmission process by using an authentication tag provided by a GCM mode, thereby ensuring that the data is not illegally modified;
3. The method comprises the steps of ① digital signature verification, ② hash verification, namely, after decrypting an upgrade package, calculating SHA-256 secure hash value of the upgrade package by gateway equipment, comparing the SHA-256 secure hash value with an attached hash value, and doubly guaranteeing the integrity and consistency of the content of the upgrade package;
4. When version information exchange and upgrading request are carried out between gateway devices, the method not only contains version related data, but also carries out identity authentication through security protocol agreed by both parties (authentication token based on public and private key pair), both gateway devices can execute strict authentication before processing request, and only gateway devices which pass the authentication successfully can acquire and push the latest software version, thereby realizing mutual trust upgrading between gateway devices.
In addition, in the process of requesting to acquire the version information, an automatic retry mechanism can be configured for at least 5 times, so that the version information still can be acquired when the conditions such as unstable network conditions occur. If no valid version information has been received for a number of consecutive attempts, log and suspend the synchronization process and wait for the next synchronization window (i.e., the next version update).
With reference to fig. 3, the embodiment of the application further provides a gateway collaborative management apparatus based on FTTR, which can be applied to the gateway device. The FTTR-based gateway collaborative management device comprises a firmware version information receiving module, a firmware version information comparing module and a firmware collaborative management module.
In detail, the firmware version information receiving module may be configured to receive gateway firmware version information sent by any one of the plurality of gateway devices in response to a networking success event of the plurality of gateway devices, where each of the plurality of gateway devices is configured to send version information of firmware currently running by itself to the other gateway devices in response to the networking success event of the plurality of gateway devices. In an embodiment of the present application, the firmware version information receiving module may be used to perform step S110 shown in fig. 2, and the description of step S110 may be referred to above for the relevant content of the firmware version information receiving module.
In detail, the firmware version information comparison module may be configured 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 analysis result, where the target gateway firmware version information is version information of a firmware currently operated by the target gateway device. In the embodiment of the present application, the firmware version information comparing module may be used to execute step S120 shown in fig. 2, and the description of step S120 may be referred to above for the relevant content of the firmware version information comparing module.
In detail, the firmware collaborative management module may be configured to perform a corresponding gateway firmware collaborative management operation in response to the comparison analysis result, where after the gateway firmware collaborative management operation is performed, version information of firmware currently operated by each of the plurality of gateway devices belongs to latest version information. In the embodiment of the present application, the firmware collaborative management module may be used to perform step S130 shown in fig. 2, and the description of step S130 may be referred to above for the relevant content of the firmware collaborative management module.
In an embodiment of the present application, corresponding to the gateway collaborative management method based on FTTR applied to the gateway device, a computer readable storage medium is further provided, where a computer program is stored in the computer readable storage medium, and the computer program executes each step of the gateway collaborative management method based on FTTR when running.
The steps executed when the computer program runs are not described in detail herein, and the explanation of the gateway collaborative management method based on FTTR can be referred to.
In summary, the method, the device, the equipment and the medium for gateway collaborative management based on FTTR provided by the application can receive gateway firmware version information sent by any one other gateway equipment in a plurality of gateway equipment in response to a networking success event of the plurality of gateway equipment, then, compare and analyze the gateway firmware version information sent by each other gateway equipment with target gateway firmware version information to obtain a corresponding comparison analysis result, and then, respond to the comparison analysis result to execute corresponding gateway firmware collaborative management operation, wherein after the gateway firmware collaborative management operation is executed, the version information of the firmware currently operated by each gateway equipment in the plurality of gateway equipment belongs to the latest version information. Based on the above, since the networking success event is used as a trigger mechanism of firmware update, the problem of inconsistent firmware versions between gateway devices caused by networking can be effectively avoided, and the problems of compatibility failure, network instability, abnormal service and the like caused by inconsistent firmware versions are avoided, so that the communication reliability between gateway devices is ensured, the problem of low gateway communication reliability in the prior art can be improved, the reliable collaborative work between gateway devices is realized, and the whole house network performance and stability of FTTR are ensured.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus and method embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, an optical disk, or other various media capable of storing program codes. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411560035.0A CN119071154B (en) | 2024-11-04 | 2024-11-04 | Gateway collaborative management method, device, equipment and medium based on FTTR |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411560035.0A CN119071154B (en) | 2024-11-04 | 2024-11-04 | Gateway collaborative management method, device, equipment and medium based on FTTR |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN119071154A CN119071154A (en) | 2024-12-03 |
| CN119071154B true CN119071154B (en) | 2025-01-24 |
Family
ID=93633716
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411560035.0A Active CN119071154B (en) | 2024-11-04 | 2024-11-04 | Gateway collaborative management method, device, equipment and medium based on FTTR |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119071154B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108491222A (en) * | 2018-03-27 | 2018-09-04 | 青岛海信智慧家居系统股份有限公司 | Gateway device upgrade method, device, gateway device and storage medium |
| CN117499236A (en) * | 2022-07-25 | 2024-02-02 | 北京小米移动软件有限公司 | A method, device and storage medium for gateway equipment upgrade |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118175464B (en) * | 2024-05-15 | 2024-08-27 | 中兴通讯股份有限公司 | FTTR gateway upgrade method, gateway device, system and computer readable storage medium |
-
2024
- 2024-11-04 CN CN202411560035.0A patent/CN119071154B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108491222A (en) * | 2018-03-27 | 2018-09-04 | 青岛海信智慧家居系统股份有限公司 | Gateway device upgrade method, device, gateway device and storage medium |
| CN117499236A (en) * | 2022-07-25 | 2024-02-02 | 北京小米移动软件有限公司 | A method, device and storage medium for gateway equipment upgrade |
Also Published As
| Publication number | Publication date |
|---|---|
| CN119071154A (en) | 2024-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3639498B1 (en) | Certificate pinning in highly secure network environments using public key certificates obtained from a dhcp (dynamic host configuration protocol) server | |
| JP7279899B2 (en) | Data collection method, data collection apparatus, data collection device and computer readable storage medium | |
| JP2021504865A (en) | Systems and methods to secure data transfer between non-IP endpoint devices connected to gateway devices and connected services | |
| KR20200066288A (en) | Asset update service | |
| CN113411190B (en) | Key deployment, data communication, key exchange and security reinforcement method and system | |
| KR20010004791A (en) | Apparatus for securing user's informaton and method thereof in mobile communication system connecting with internet | |
| US8515996B2 (en) | Secure configuration of authentication servers | |
| WO2019019887A1 (en) | Server authentication method, apparatus and system for terminal access, server and computer readable storage medium | |
| CN112749232A (en) | Production data monitoring method and device, block chain node and storage medium | |
| US20200014696A1 (en) | Secure confirmation exchange for offline industrial machine | |
| CN110557255A (en) | Method and device for certificate management | |
| CN116010910A (en) | Software authorization method, data processing method, device, equipment and medium | |
| CN112219416A (en) | Technology for authenticating data transmitted over cellular networks | |
| US20170324562A1 (en) | Recovery agents and recovery plans over networks | |
| CN110892695A (en) | Method, apparatus and computer program product for checking connection parameters of a password-protected communication connection during connection establishment | |
| CN115242480B (en) | Device access method, system and non-volatile computer storage medium | |
| CN111031067A (en) | Monitoring data transmission method and device of distributed system and electronic equipment | |
| US20170237716A1 (en) | System and method for interlocking intrusion information | |
| CN119071154B (en) | Gateway collaborative management method, device, equipment and medium based on FTTR | |
| US11757663B1 (en) | Blockchain-based monitoring of devices | |
| CN115801292A (en) | Access request authentication method and device, storage medium and electronic equipment | |
| CN109587134B (en) | Method, apparatus, device and medium for secure authentication of interface bus | |
| CN118051934A (en) | Data management method and device for transformer substation and electronic equipment | |
| JP2019008738A (en) | Verification device | |
| CN113572599B (en) | Electric power data transmission method, data source equipment and data access equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |