CN118175464A - FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium - Google Patents
FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium Download PDFInfo
- Publication number
- CN118175464A CN118175464A CN202410603827.5A CN202410603827A CN118175464A CN 118175464 A CN118175464 A CN 118175464A CN 202410603827 A CN202410603827 A CN 202410603827A CN 118175464 A CN118175464 A CN 118175464A
- Authority
- CN
- China
- Prior art keywords
- gateway
- upgrade
- version
- slave
- gateway device
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 83
- 230000004044 response Effects 0.000 claims description 31
- 238000004891 communication Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 abstract description 10
- 230000005856 abnormality Effects 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 239000000835 fiber Substances 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 239000002071 nanotube Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q11/0067—Provisions for optical access or distribution networks, e.g. Gigabit Ethernet Passive Optical Network (GE-PON), ATM-based Passive Optical Network (A-PON), PON-Ring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0079—Operation or maintenance aspects
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium. The method is applied to the main gateway equipment and comprises the following steps: acquiring upgrade version information of at least one slave gateway device, and acquiring gateway version information of at least one slave gateway device; determining at least one target slave gateway device to be upgraded in the slave gateway devices according to the upgrade version information and the gateway version information; and sending the upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to the gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message. By the method, centralized management of version upgrading of the slave gateway equipment can be realized, operation and maintenance cost of the slave gateway equipment is reduced, meanwhile, the risk of abnormality of the slave gateway equipment due to version misadaptation is reduced, and the safety of version upgrading of the slave gateway equipment is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium.
Background
The fiber-to-subscriber point (Fiber to The Room, FTTR) is a network architecture that extends a fiber network into a subscriber's home or business building to provide high-speed broadband access services. In FTTP architecture, the optical fiber will extend all the way to the user's room or inside the building, typically converted by an optical network terminal (Optical Network Terminal, ONT) or an optical network unit (Optical Network Unit, ONU) so that the user can connect to the fiber optic network.
Along with the application and popularization of the optical fiber to the user point network (Fiber to The Room-Home, FTTR-H) in the Home scene and the optical fiber to the user point network (Fiber to The Room-Business, FTTR-B) in the government and enterprise scene, the version upgrading difficulty of the gateway equipment is higher due to the large scale, difficult server nano-tube, large consumption of server resources (bandwidth, memory and the like) and the like, and the operation and maintenance cost of the gateway equipment is increased.
Disclosure of Invention
The embodiment of the application provides a FTTR gateway upgrading method, gateway equipment, a system and a computer readable storage medium, which are used for at least solving the problem of high version upgrading difficulty of gateway equipment in the related art.
In a first aspect, an embodiment of the present application provides a FTTR gateway upgrade method, which is applied to a primary gateway device, including: acquiring upgrade version information of at least one slave gateway device, and acquiring gateway version information of the at least one slave gateway device; determining target slave gateway equipment to be upgraded in the at least one slave gateway equipment according to the upgrading version information and the gateway version information; and sending an upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to a gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message.
In a second aspect, an embodiment of the present application provides a FTTR gateway upgrade method, which is applied to a slave gateway device, including: receiving an upgrade inquiry message sent by a main gateway device; the upgrade inquiry message is sent by the master gateway device under the condition that the slave gateway device is determined to be a target slave gateway device to be upgraded according to the upgrade version information of the slave gateway device and the gateway version information of the slave gateway device; and upgrading the version of the slave gateway equipment to a gateway upgrading version corresponding to the upgrading version information according to the upgrading query message.
In a third aspect, an embodiment of the present application provides a gateway device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the first or second aspect above.
In a fourth aspect, an embodiment of the present application provides a gateway upgrade system, including a master gateway device and a plurality of slave gateway devices, where the master gateway device is communicatively connected to the plurality of slave gateway devices; the master gateway device is configured to perform the steps of the method according to the first aspect, and the slave gateway device is configured to perform the steps of the method according to the second aspect.
In a fifth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method as described in the first or second aspects above.
In the embodiment of the application, a master gateway device acquires upgrade version information of at least one slave gateway device and acquires gateway version information of at least one slave gateway device; determining at least one target slave gateway device to be upgraded in the slave gateway devices according to the upgrade version information and the gateway version information; and sending the upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to the gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message. In this way, the target slave gateway equipment to be upgraded is determined through the master gateway equipment, and the upgrade inquiry information is sent to enable the target slave gateway equipment to upgrade the version, so that centralized management of the version upgrade of the slave gateway equipment can be realized, the operation and maintenance cost of the slave gateway equipment is reduced, meanwhile, the risk of abnormality of the slave gateway equipment caused by version mismatch is reduced, and the version upgrade safety of the slave gateway equipment is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 shows a schematic view of an application scenario provided by an embodiment of the present application;
fig. 2 is a schematic flow chart of a FTTR gateway upgrading method according to an embodiment of the present application;
Fig. 3a shows one of the AP Capability Report extended TLV structure encoding diagrams provided by the embodiment of the present application;
Fig. 3b shows a second exemplary diagram of a AP Capability Report extended TLV structure encoding provided by an embodiment of the present application;
Fig. 4a shows one of the LINK METRIC Query extension TLV structure encoding diagrams provided by the embodiment of the present application;
Fig. 4b shows a second exemplary diagram of a LINK METRIC Query extension TLV structure encoding provided by an embodiment of the present application;
Fig. 5a shows one of the LINK METRIC Report extension TLV structure encoding diagrams provided by the embodiment of the present application;
Fig. 5b shows a second exemplary diagram of a LINK METRIC Report extension TLV structure encoding provided by an embodiment of the present application;
fig. 6 is a schematic flow chart of another method for upgrading FTTR gateway according to an embodiment of the present application;
fig. 7 is a schematic flow chart of a method for proxy upgrading of a slave gateway device by a master gateway device according to an embodiment of the present application;
fig. 8 shows a schematic structural diagram of a gateway device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
Along with the application and popularization of the home scene FTTR-H and the government and enterprise scene FTTR-B, the gateway equipment becomes a bottleneck for operation and maintenance guarantee due to large scale, difficult server nano-tube, large consumption of server resources (bandwidth, memory and the like), and particularly, the processing speed and service function stability of the server are very challenging when the version of the gateway equipment is upgraded in a whole line.
Aiming at the problems existing in the FTTR slave gateway equipment version upgrading process, the embodiment of the application provides a FTTR gateway upgrading method, which uses FTTR master gateway equipment to proxy the slave gateway equipment version upgrading mode, namely, the target slave gateway equipment to be upgraded is determined through the master gateway equipment, and an upgrading inquiry message is sent to enable the target slave gateway equipment to upgrade the version, so that centralized management of the slave gateway equipment version upgrading is realized, and the operation and maintenance cost of the slave gateway equipment is reduced. As shown in fig. 1, the gateway upgrading system provided by the embodiment of the application includes a server, a master gateway device and a slave gateway device; wherein the master gateway device comprises FTTR master gateways a and FTTR master gateway N, the slave gateway device comprises FTTR slave gateways A1, FTTR slave gateways A2, FTTR slave gateways An, FTTR slave gateways N1, FTTR slave gateways Nn; the server is used for managing and maintaining the master gateway equipment, and the master gateway equipment is used for finishing the upgrading function of the slave gateway equipment through protocols such as IEEE 1905.1a and the like. When the large-scale slave gateway equipment of the whole network needs to be upgraded at the same time, the server does not need to receive all the slave gateway equipment and issue a large number of upgrading requests, and only needs to issue upgrading requests to the master gateway equipment in the network topology of all the slave gateway, so that the complexity of the version upgrading of the slave gateway equipment can be reduced, and the version upgrading efficiency of the slave gateway equipment is improved.
Referring to fig. 2, fig. 2 is a schematic flow chart of a FTTR gateway upgrade method according to an embodiment of the present application. The method may be applied to the application scenario shown in fig. 1, and in particular, may be applied to a primary gateway device, as shown in fig. 2, and the method 200 may include the following steps:
S201: the method comprises the steps of obtaining upgrade version information of at least one slave gateway device and obtaining gateway version information of the at least one slave gateway device.
The upgrade version information may include an upgrade version number, an applicable device model, and the like; the gateway version information of the slave gateway device may include a slave gateway device model number of the slave gateway device, a slave gateway version number, MAC information, and the like.
In a specific implementation, the main gateway device may automatically check periodically whether a new gateway upgrade version is available to the server to obtain upgrade version information of the new gateway upgrade version; and the method can also receive the upgrade request message sent by the server, download the gateway upgrade version according to the address information carried in the upgrade request message, and acquire the upgrade version information of the gateway upgrade version. For the acquisition of gateway version information of the slave gateway equipment, the master gateway equipment can be connected to the slave gateway equipment in a remote access mode and directly inquire the gateway version information of the slave gateway equipment; gateway version information of the slave gateway device can be acquired through API call; a query request may also be sent to all slave gateway devices within the networking topology to obtain their gateway version information. Thus, the master gateway equipment acquires the upgrade version information of at least one slave gateway equipment and acquires the gateway version information of at least one slave gateway equipment, so that the centralized management of the version upgrade of the slave gateway equipment can be realized, and the operation and maintenance cost of the slave gateway equipment is reduced.
S202: and determining target slave gateway equipment to be upgraded in the at least one slave gateway equipment according to the upgrading version information and the gateway version information.
In a specific implementation, the master gateway device may determine, according to the update version information and the gateway version information, whether the gateway update version is adapted to the version of the slave gateway device, so as to determine a target slave gateway device to be updated in at least one slave gateway device, so that the risk of abnormality of the slave gateway device due to version mismatch can be reduced, and the security of version update of the slave gateway device is improved.
S203: and sending an upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to a gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message.
In a specific implementation, after determining a target slave gateway device to be upgraded in the slave gateway devices, the master gateway device sends an upgrade inquiry message to the target slave gateway device; the target receives the upgrade inquiry information from the gateway equipment, upgrades the version of the target according to the upgrade inquiry information, and upgrades the version to the gateway upgrade version corresponding to the upgrade version information.
According to the steps, the target slave gateway equipment to be upgraded is determined through the master gateway equipment, and the upgrade inquiry information is sent to enable the target slave gateway equipment to upgrade the version, so that centralized management of version upgrade of the slave gateway equipment can be realized, the operation and maintenance cost of the slave gateway equipment is reduced, meanwhile, the risk of abnormality of the slave gateway equipment caused by version mismatch is reduced, and the version upgrade safety of the slave gateway equipment is improved.
In a possible implementation manner, in S201, the obtaining upgrade version information of the at least one slave gateway device includes:
Responding to an upgrade request message sent by a server, and acquiring first address information in the upgrade request message; downloading the gateway upgrading version of the at least one slave gateway device according to the first address information, and acquiring upgrading version information of the gateway upgrading version.
In the embodiment of the application, a server issues an upgrade request message to a main gateway device, wherein the upgrade request message carries first address information, and the first address information can be a uniform resource locator (Uniform Resource Locator, URL); the primary gateway device may immediately return an upgrade response message to the server after receiving the upgrade request message.
Further, the master gateway device downloads the slave gateway upgrade version according to the received first address information, the master gateway device stores the gateway upgrade version in the memory while downloading the gateway upgrade version, and after the downloading is completed, the master gateway device returns a download response message to the server, where the download response message may include download success status information (e.g., status=0), and obtains upgrade version information of the gateway upgrade version.
In this way, the master gateway device responds to the upgrade request message sent by the server, downloads the gateway upgrade version of the slave gateway device according to the first address information included in the upgrade request message, and acquires the upgrade version information of the gateway upgrade version, so that the master gateway device can be ensured to acquire accurate upgrade version information, and version confusion or errors are avoided.
In a possible implementation manner, in S201, acquiring gateway version information of the at least one slave gateway device includes:
sending a query request message to the at least one slave gateway device; and acquiring a query response message fed back by the at least one slave gateway device based on the query request message, wherein the query response message comprises gateway version information of each slave gateway device.
In the embodiment of the application, the master gateway device can actively trigger the capability query of a wireless Access Point (AP), and send query request messages to all the slave gateway devices in the networking topology, and in a specific application, the query request messages can be query messages with the type AP Capability Query of IEEE 1905.1a protocol type. The slave gateway device receives the query request message sent by the master gateway device, and based on the query response message fed back by the query request message, in a specific application, the query response message may be an IEEE 1905.1a protocol type AP Capability Report message.
The query response message includes gateway version information of each slave gateway device, as shown in fig. 3a and 3b, and AP Capability Report message contains a custom TLV (Type-Length-Value) field, where the TLV field custom defines tlvType of 1 byte (8 bits) and has a Value of 0xF0; TLVLENGTH bytes of value, which is the entire TLV length; and tlvValue bytes of value is gateway version information of the slave gateway device.
In one possible implementation, the upgrade version information includes an upgrade version number and an applicable device model number, and the gateway version information of the at least one slave gateway device includes a slave gateway device model number and a slave gateway version number of the at least one slave gateway device;
in S202, determining, according to the upgrade version information and the gateway version information, a target slave gateway device to be upgraded in the at least one slave gateway device includes:
Determining a slave gateway device corresponding to the gateway device model matched with the applicable device model as a candidate slave gateway device; and determining the candidate slave gateway device with the slave gateway version number lower than the upgrade version number as the target slave gateway device.
In the embodiment of the application, the master gateway device can extract all the slave gateway version numbers, the slave gateway device types and the MAC information in the networking topology and compare the slave gateway device types with the upgrade version numbers and the applicable device types in the memory. The master gateway equipment firstly compares the slave gateway equipment models, when the matching of the applicable equipment model of the gateway upgrading version and the slave gateway equipment model of the slave gateway equipment is inconsistent, the master gateway equipment does not process and continues to match other slave gateway equipment until the slave gateway equipment models of all the slave gateway equipment are compared, and the slave gateway equipment corresponding to the gateway equipment model matched with the applicable equipment model is determined as candidate slave gateway equipment. And then the master gateway device compares the slave gateway version numbers of the slave gateway devices, and the candidate slave gateway devices are determined to be target slave gateway devices only when the extracted slave gateway version numbers are lower than the upgrade version numbers in the memory.
Therefore, the master gateway device can avoid the abnormality of the slave gateway device caused by downloading the non-adaptive gateway upgrading version by comparing the slave gateway device model with the slave gateway version number, and ensure that the slave gateway device can normally communicate and operate after being upgraded.
In a possible implementation manner, the upgrade query message includes second address information and authentication information, where the second address information is used to instruct the target slave gateway device to obtain the address of the gateway upgrade version, and the authentication information is used to verify the identity and authority of the target slave gateway device.
In the embodiment of the application, after determining the target slave gateway device, the master gateway device sends an upgrade Query message to the target slave gateway device according to the MAC information, and in a specific application, the upgrade Query message may be an IEEE 1905.1a protocol type LINK METRIC Query message. The upgrade Query message includes second address information and authentication information, where the second address information may be a upgrade URL from a gateway version, specifically, the LINK METRIC Query message includes a custom TLV field, and the TLV field carries the upgrade URL from the gateway version and the authentication information. The main gateway simultaneously opens a random port for downloading the gateway upgrading version from gateway equipment by a target needing upgrading. As shown in fig. 4a and fig. 4b, the LINK METRIC Query packet contains a custom TLV field, where the TLV field is custom tlvType with 1 byte and the value is 0xF1; TLVLENGTH bytes of value, which is the entire TLV length; the value of tlvValue of 64 bytes is the upgrade URL and authentication information from the gateway version.
In a possible implementation manner, the upgrade query message includes an upgrade policy, where the upgrade policy is used to instruct the target slave gateway device to upgrade the version to the gateway upgrade version according to the upgrade policy.
In the embodiment of the application, the upgrade request message sent by the server to the main gateway device may include an upgrade policy, where the upgrade policy is batch immediate upgrade or idle upgrade. The master gateway device may send the upgrade policy to the target slave gateway device, specifically, carry the upgrade policy to the upgrade query message, so that the target slave gateway device upgrades the version to the gateway upgrade version according to the upgrade policy. In this way, stability and reliability of the target slave gateway in the upgrade process can be ensured.
In one possible implementation manner, after sending the upgrade query message to the target slave gateway device in S203 above, the method further includes:
Responding to the upgrade response message fed back by the target from the gateway equipment, and deleting the gateway upgrade version corresponding to the upgrade version information; the upgrade response message includes status indication information, where the status indication information is used to indicate that the target slave gateway device is successfully upgraded.
In the embodiment of the application, after the target slave gateway equipment is successfully upgraded, an upgrade response message is fed back to the master gateway equipment so as to inform the master gateway equipment that the version upgrade is successful. In a specific application, the upgrade response message may be an IEEE 1905.1a protocol type LINK METRIC Report message, where the message contains a custom TLV field, and the field carries status indication information (e.g., status=0) that is used to indicate that the target slave gateway device upgrade is successful. As shown in fig. 5a and 5b, the TLV field of LINK METRIC Report message defines tlvType of 1 byte with a value of 0xF2; TLVLENGTH bytes of value, which is the entire TLV length; tlvValue bytes, the value of which is the status indication information. And the master gateway equipment responds to the upgrade response message fed back by the target slave gateway equipment, closes the upgrade port channel and deletes the gateway upgrade version in the memory so as to avoid version confusion or error.
The embodiment of the application provides a FTTR gateway upgrading method which is applied to main gateway equipment and comprises the following steps: acquiring upgrade version information of at least one slave gateway device, and acquiring gateway version information of at least one slave gateway device; determining at least one target slave gateway device to be upgraded in the slave gateway devices according to the upgrade version information and the gateway version information; and sending the upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to the gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message. By the method, centralized management of version upgrading of the slave gateway equipment can be realized, operation and maintenance cost of the slave gateway equipment is reduced, meanwhile, the risk of abnormality of the slave gateway equipment due to version misadaptation is reduced, and the safety of version upgrading of the slave gateway equipment is improved.
Referring to fig. 6, fig. 6 is a schematic flow chart of another method for upgrading FTTR gateway according to an embodiment of the present application. The method may be applied to the application scenario shown in fig. 1, and in particular, may be applied to the slave gateway device, as shown in fig. 6, the method 600 may include the following steps:
s601: and receiving the upgrade inquiry message sent by the main gateway equipment.
The upgrade inquiry message is sent by the master gateway device under the condition that the slave gateway device is determined to be a target slave gateway device to be upgraded according to the upgrade version information of the slave gateway device and the gateway version information of the slave gateway device.
S602: and upgrading the version of the slave gateway equipment to a gateway upgrading version corresponding to the upgrading version information according to the upgrading query message.
In a possible implementation manner, in S601, before receiving the upgrade query message sent by the primary gateway device, the method further includes:
receiving a version inquiry message sent by the main gateway equipment;
and sending a query response message to the master gateway device based on the version query message, wherein the query response message comprises gateway version information of the slave gateway device.
In a possible implementation manner, the upgrade query message includes second address information and authentication information, and in S602, upgrading the version of the slave gateway device to a gateway upgrade version corresponding to the upgrade version information according to the upgrade query message includes:
and under the condition that the verification of the slave gateway equipment is confirmed to pass according to the authentication information, acquiring the gateway upgrading version according to the second address information.
In a possible implementation manner, in S602, after upgrading the version of the target slave gateway device to the gateway upgrade version corresponding to the upgrade version information according to the upgrade query message, the method further includes:
and sending an upgrade response message to the master gateway device, wherein the upgrade response message comprises state indication information, and the state indication information is used for indicating that the slave gateway device is successfully upgraded.
The embodiment of the application provides a FTTR gateway upgrading method which is applied to slave gateway equipment and comprises the following steps: receiving an upgrade inquiry message sent by a main gateway device; the method comprises the steps that an upgrade inquiry message is sent by a master gateway device under the condition that the slave gateway device is determined to be a target slave gateway device to be upgraded according to upgrade version information of the slave gateway device and gateway version information of the slave gateway device; and upgrading the version of the slave gateway equipment to the gateway upgrading version corresponding to the upgrading version information according to the upgrading query message. In this way, the target slave gateway equipment to be upgraded is determined through the master gateway equipment, and the update inquiry message is sent to enable the slave gateway equipment to update the version under the condition that the slave gateway equipment is determined to be the target slave gateway equipment to be upgraded, so that the centralized management of the version update of the slave gateway equipment can be realized, the operation and maintenance cost of the slave gateway equipment is reduced, the risk of abnormality of the slave gateway equipment due to version mismatch is reduced, and the version update safety of the slave gateway equipment is improved.
The embodiment of the application also provides a gateway upgrading system which comprises a master gateway device and a plurality of slave gateway devices, wherein the master gateway device is in communication connection with the plurality of slave gateway devices; the master gateway device is adapted to perform the steps of the method as described in fig. 2 above and the slave gateway device is adapted to perform the steps of the method as described in fig. 6 above.
In an exemplary embodiment, as shown in fig. 7, the gateway upgrade system adopts a mode of upgrading a slave gateway device by a master gateway device proxy, and specifically includes the following steps:
Step 701: the Server transmits an upgrade request message Server request to FTTR main gateway, wherein the upgrade request message carries upgrade URL (namely the first address information) and upgrade strategy;
Step 702: FTTR the main gateway returns a response message Server response to the Server immediately after receiving the upgrade request message;
Step 703: the FTTR main gateway downloads the gateway upgrade version according to the received upgrade URL, the FTTR main gateway downloads the gateway upgrade version and stores the gateway upgrade version in a memory, and the main gateway returns a download response message download response (containing download success state information status=0) to the server after downloading is completed;
step 704: the FTTR master gateway actively triggers the AP capability query, and transmits a query message with the IEEE 1905.1a protocol type of AP Capability Query (namely the query request message) to all FTTR slave gateways in the networking topology;
Step 705: FTTR the slave gateway replies a AP Capability Report message (i.e. the above query response message) with an IEEE 1905.1a protocol type to the FTTR master gateway, where the AP Capability Report message carries a slave gateway device model number and a slave gateway version number;
Step 706: FTTR the master gateway extracts the slave gateway equipment model numbers and slave gateway version numbers of all FTTR slave gateways, and compares the slave gateway equipment model numbers and the slave gateway version numbers with the upgrade version numbers and the applicable equipment model numbers in the memory;
Step 707: if the 3835.1 a protocol type is LINK METRIC Query message (i.e. the upgrade Query message) with the target slave gateway being FTTR slave gateway, the FTTR master gateway sends the target slave gateway an IEEE 1905.1a protocol type is LINK METRIC Query message, wherein the LINK METRIC Query message carries a slave gateway version upgrade URL (i.e. the second address information) and authentication information, and the FTTR master gateway simultaneously opens a random port for downloading a gateway upgrade version from the target slave gateway which needs to be upgraded;
step 708: extracting a slave gateway version upgrading URL and authentication information of LINK METRIC Query messages from a gateway by a target, downloading a gateway upgrading version to a FTTR master gateway by using a tftp or ftp protocol, and upgrading the version according to an upgrading strategy after successful downloading;
Step 709: after the target slave gateway is successfully upgraded, returning an IEEE 1905.1a protocol type LINK METRIC Report message (namely the upgrade response message) to the FTTR master gateway, wherein the LINK METRIC Report message carries state indication information which is used for indicating that the target slave gateway equipment is successfully upgraded;
Step 710: and FTTR, after the main gateway receives LINK METRIC Report messages carrying state indication information and sent by the target slave gateway to be upgraded, closing an upgrade port channel and deleting a gateway upgrade version in a memory.
By the method, centralized management of version upgrading of the slave gateway equipment can be realized, operation and maintenance cost of the slave gateway equipment is reduced, meanwhile, the risk of abnormality of the slave gateway equipment due to version misadaptation is reduced, and the safety of version upgrading of the slave gateway equipment is improved.
Fig. 8 shows a schematic structural diagram of a gateway device provided by an embodiment of the present application, and referring to this figure, at a hardware level, the gateway device 800 includes a processor 810, and optionally, an internal bus 820, a network interface 830, and a memory 840. The Memory 840 may include a Memory 841, such as a Random-Access Memory (RAM), and may also include a non-volatile Memory 842 (non-volatile Memory), such as at least 1 disk Memory. Of course, the gateway device 800 may also include hardware required for other services.
The processor 810, the network interface 830, and the memory may be interconnected by an internal bus 820, which internal bus 820 may be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in the figure, but not only one bus or one type of bus.
A memory 840 for storing programs. In particular, the program may include program code including computer-operating instructions. Memory 840 may include memory 841 and nonvolatile memory 842 and provide instructions and data to processor 810.
The processor 810 reads the corresponding computer program from the non-volatile memory 842 into memory and then runs to form a means of locating the target user at the logic level. The processor 810 executes a program stored in the memory, and specifically executes: the embodiments shown in fig. 2, fig. 6, or fig. 7 disclose the method and implement the functions and benefits of the methods described in the foregoing method embodiments, which are not described herein.
The methods disclosed above in the embodiments of the present application shown in fig. 2 or fig. 6 or fig. 7 may be applied to the processor 810 or implemented by the processor 810. The processor 810 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry in hardware or instructions in software in processor 810. The processor 810 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but may also be a digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The computer device may also execute the methods described in the foregoing method embodiments, and implement the functions and beneficial effects of the methods described in the foregoing method embodiments, which are not described herein.
Of course, other implementations, such as a logic device or a combination of hardware and software, are not excluded from the gateway device of the present application, that is, the execution subject of the following processing flows is not limited to each logic unit, but may be hardware or a logic device.
The embodiment of the present application further proposes a computer readable storage medium storing one or more programs, which when executed by a gateway device including a plurality of application programs, cause the gateway device to execute the method disclosed in the embodiment shown in fig. 2 or fig. 6 or fig. 7 and implement the functions and advantages of the methods described in the foregoing method embodiments, which are not described herein again.
The computer readable storage medium includes Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, etc.
Further, embodiments of the present application also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, implement the following flow: the embodiments shown in fig. 2, fig. 6, or fig. 7 disclose the method and implement the functions and benefits of the methods described in the foregoing method embodiments, which are not described herein.
The embodiment of the application can be applied to various gateway equipment cooperation or interconnection scenes, including: the mobile phone is cooperatively interconnected with the notebook computer/tablet computer; the mobile terminal is cooperatively interconnected with the intelligent television/display; the mobile phone or the tablet personal computer is cooperatively interconnected with the vehicle-mounted entertainment system; and the mobile terminal is cooperatively interconnected with the intelligent conference system. Thereby satisfying the diversified scene demands of users in intelligent house, intelligent office, intelligent trip etc.
In summary, the foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the present application. 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.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that 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 the element.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
Claims (14)
1. A FTTR gateway upgrade method, applied to a primary gateway device, the method comprising:
acquiring upgrade version information of at least one slave gateway device, and acquiring gateway version information of the at least one slave gateway device;
determining target slave gateway equipment to be upgraded in the at least one slave gateway equipment according to the upgrading version information and the gateway version information;
and sending an upgrade inquiry message to the target slave gateway equipment so that the target slave gateway equipment upgrades the version of the target slave gateway equipment to a gateway upgrade version corresponding to the upgrade version information according to the upgrade inquiry message.
2. The method of claim 1, wherein the obtaining updated version information of the at least one slave gateway device comprises:
responding to an upgrade request message sent by a server, and acquiring first address information in the upgrade request message;
Downloading the gateway upgrading version of the at least one slave gateway device according to the first address information, and acquiring upgrading version information of the gateway upgrading version.
3. The method of claim 1, wherein the obtaining gateway version information of the at least one slave gateway device comprises:
sending a query request message to the at least one slave gateway device;
and acquiring a query response message fed back by the at least one slave gateway device based on the query request message, wherein the query response message comprises gateway version information of each slave gateway device.
4. A method according to any of claims 1 to 3, wherein the upgrade version information comprises an upgrade version number and an applicable device model number, and the gateway version information of the at least one slave gateway device comprises a slave gateway device model number and a slave gateway version number of the at least one slave gateway device;
The determining, according to the upgrade version information and the gateway version information, a target slave gateway device to be upgraded in the at least one slave gateway device includes:
determining a slave gateway device corresponding to the gateway device model matched with the applicable device model as a candidate slave gateway device;
And determining the candidate slave gateway device with the slave gateway version number lower than the upgrade version number as the target slave gateway device.
5. A method according to any of claims 1 to 3, wherein the upgrade inquiry message includes second address information for instructing the target to obtain the address of the gateway upgrade version from the gateway device, and authentication information for verifying the identity and authority of the target from the gateway device.
6. A method according to any one of claims 1 to 3, wherein the upgrade inquiry message includes an upgrade policy, the upgrade policy being used to instruct the target slave gateway device to upgrade a version to the gateway upgrade version according to the upgrade policy.
7. A method according to any one of claims 1 to 3, further comprising, after said sending an upgrade inquiry message to said target slave gateway device:
Responding to the upgrade response message fed back by the target from the gateway equipment, and deleting the gateway upgrade version corresponding to the upgrade version information;
The upgrade response message includes status indication information, where the status indication information is used to indicate that the target slave gateway device is successfully upgraded.
8. A FTTR gateway upgrade method, for application to a slave gateway device, the method comprising:
Receiving an upgrade inquiry message sent by a main gateway device; the upgrade inquiry message is sent by the master gateway device under the condition that the slave gateway device is determined to be a target slave gateway device to be upgraded according to the upgrade version information of the slave gateway device and the gateway version information of the slave gateway device;
And upgrading the version of the slave gateway equipment to a gateway upgrading version corresponding to the upgrading version information according to the upgrading query message.
9. The method of claim 8, further comprising, prior to said receiving the upgrade inquiry message sent by the primary gateway device:
receiving a version inquiry message sent by the main gateway equipment;
and sending a query response message to the master gateway device based on the version query message, wherein the query response message comprises gateway version information of the slave gateway device.
10. The method of claim 8, wherein the upgrade query message includes second address information and authentication information, and wherein the upgrading the version of the slave gateway device to the gateway upgrade version corresponding to the upgrade version information according to the upgrade query message includes:
and under the condition that the verification of the slave gateway equipment is confirmed to pass according to the authentication information, acquiring the gateway upgrading version according to the second address information.
11. The method according to any one of claims 8 to 10, further comprising, after said upgrading the target from the version of the gateway device to the gateway upgrade version corresponding to the upgrade version information according to the upgrade query message:
and sending an upgrade response message to the master gateway device, wherein the upgrade response message comprises state indication information, and the state indication information is used for indicating that the slave gateway device is successfully upgraded.
12. A gateway device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method of any one of claims 1 to 11.
13. A gateway upgrade system comprising a master gateway device and a plurality of slave gateway devices, wherein the master gateway device is in communication connection with the plurality of slave gateway devices; the master gateway device being adapted to perform the steps of the method according to any of claims 1 to 7, and the slave gateway device being adapted to perform the steps of the method according to any of claims 8 to 11.
14. A computer readable storage medium, characterized in that it stores thereon a program or instructions, which when executed by a processor, implement the steps of the method according to any of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410603827.5A CN118175464B (en) | 2024-05-15 | 2024-05-15 | FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410603827.5A CN118175464B (en) | 2024-05-15 | 2024-05-15 | FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN118175464A true CN118175464A (en) | 2024-06-11 |
| CN118175464B CN118175464B (en) | 2024-08-27 |
Family
ID=91346943
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410603827.5A Active CN118175464B (en) | 2024-05-15 | 2024-05-15 | FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118175464B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119071154A (en) * | 2024-11-04 | 2024-12-03 | 四川天邑康和通信股份有限公司 | Gateway collaborative management method, device, equipment and medium based on FTTR |
Citations (5)
| 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 |
| CN115225494A (en) * | 2022-07-26 | 2022-10-21 | 武汉烽火技术服务有限公司 | Method and device for upgrading composite mirror image of gateway equipment |
| CN116634310A (en) * | 2022-02-10 | 2023-08-22 | 中兴通讯股份有限公司 | Home all-optical network gateway version upgrade method, electronic equipment and storage medium |
| CN117369854A (en) * | 2023-12-07 | 2024-01-09 | 浪潮云洲工业互联网有限公司 | OTA upgrading method, device and medium for active identification industrial equipment |
| CN117499236A (en) * | 2022-07-25 | 2024-02-02 | 北京小米移动软件有限公司 | Gateway equipment upgrading method, device and storage medium |
-
2024
- 2024-05-15 CN CN202410603827.5A patent/CN118175464B/en active Active
Patent Citations (5)
| 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 |
| CN116634310A (en) * | 2022-02-10 | 2023-08-22 | 中兴通讯股份有限公司 | Home all-optical network gateway version upgrade method, electronic equipment and storage medium |
| CN117499236A (en) * | 2022-07-25 | 2024-02-02 | 北京小米移动软件有限公司 | Gateway equipment upgrading method, device and storage medium |
| CN115225494A (en) * | 2022-07-26 | 2022-10-21 | 武汉烽火技术服务有限公司 | Method and device for upgrading composite mirror image of gateway equipment |
| CN117369854A (en) * | 2023-12-07 | 2024-01-09 | 浪潮云洲工业互联网有限公司 | OTA upgrading method, device and medium for active identification industrial equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119071154A (en) * | 2024-11-04 | 2024-12-03 | 四川天邑康和通信股份有限公司 | Gateway collaborative management method, device, equipment and medium based on FTTR |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118175464B (en) | 2024-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100527080C (en) | Method for software program synchronization | |
| RU2442295C2 (en) | Apparatus and methods for network identification of open market wireless devices | |
| CN115442423A (en) | Method for discovering services provided by a network repository function | |
| CN106471465A (en) | Service enabler function | |
| CN118175464B (en) | FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium | |
| CN112230969B (en) | Method and equipment for formatting user space storage area in firmware upgrading process | |
| CN111148088A (en) | Method, apparatus, device and storage medium and system for managing mobile terminal | |
| US12177751B1 (en) | System, method, and computer program for transferring subscriber identity module (SIM) information for SIM card or eSIM activation | |
| CN103415014A (en) | Method and device for authenticating mobile terminal | |
| CN106101984A (en) | Security module management method and terminal of an NFC mobile payment terminal | |
| KR20190061060A (en) | Profile-based content and services | |
| CN113434293A (en) | Method and apparatus for processing repeat request, storage medium, and electronic apparatus | |
| US11012830B2 (en) | Automated activation and onboarding of connected devices | |
| CN111372224A (en) | Method, device and equipment for sharing seed code number by eSIM (embedded subscriber identity Module) | |
| CN114125812A (en) | Data synchronization method, device, server and storage medium | |
| CN102904935B (en) | Downloading method, downloading device and downloading system based on home gateway | |
| CN109672756B (en) | Data transmission method and related device, server and storage medium | |
| CN116708394B (en) | Terminal upgrading method, electronic equipment and computer readable storage medium | |
| CN111131324A (en) | Login method and device of business system, storage medium and electronic device | |
| CN113055254A (en) | Address configuration method, device, access server and storage medium | |
| CN111934928A (en) | Terminal equipment upgrading method, device, management platform, system and equipment | |
| CN107528797B (en) | Data processing method, device and system | |
| CN110941805A (en) | Identity authentication method and device | |
| CN112235784B (en) | vSIM-based code number management method, device and equipment | |
| WO2018188073A1 (en) | Content deployment method and distribution controller |
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 |