WO2016011607A1 - 一种终端升级方法及相关设备 - Google Patents

一种终端升级方法及相关设备 Download PDF

Info

Publication number
WO2016011607A1
WO2016011607A1 PCT/CN2014/082779 CN2014082779W WO2016011607A1 WO 2016011607 A1 WO2016011607 A1 WO 2016011607A1 CN 2014082779 W CN2014082779 W CN 2014082779W WO 2016011607 A1 WO2016011607 A1 WO 2016011607A1
Authority
WO
WIPO (PCT)
Prior art keywords
upgrade
terminal
version
ems
multicast
Prior art date
Application number
PCT/CN2014/082779
Other languages
English (en)
French (fr)
Inventor
杨神龙
杜波
郑晓娅
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2014/082779 priority Critical patent/WO2016011607A1/zh
Priority to CN201480065652.1A priority patent/CN105993147B/zh
Priority to EP14898250.7A priority patent/EP3163796B1/en
Priority to US15/328,417 priority patent/US10419291B2/en
Publication of WO2016011607A1 publication Critical patent/WO2016011607A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/004Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056Systems characterized by the type of code used
    • H04L1/0061Error detection codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0806Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H04L41/0809Plug-and-play configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00Encapsulation of packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H04L41/0856Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22Parsing or analysis of headers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0005Switch and router aspects
    • H04Q2011/0037Operation
    • H04Q2011/0047Broadcast; Multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0079Operation or maintenance aspects
    • H04Q2011/0083Testing; Monitoring

Definitions

  • the present invention relates to the field of optical network technologies, and in particular, to a terminal upgrade method and related equipment. Background technique
  • ONT optical network terminals
  • FTTH Fiber To The Home
  • ONT optical line terminal
  • the Element Management System receives the version numbers of various types of ONTs reported by the OLT, and the version numbers reported by the various ONTs are respectively associated with the EMS.
  • the version numbers of the saved ONTs are compared, and the types of ONTs to be upgraded are determined according to the comparison result.
  • the OLTs perform the version upgrade operations on the upgraded ONTs in turn, that is, for each type of ONT to be upgraded, the OLT determines whether the OLT determines whether For the first time, the upgrade operation of the ONT is performed.
  • the OLT can obtain the upgrade version file of the ONT from the EMS and send it to the ONT to enable the ONT to perform the version upgrade operation. If the upgrade of the ONT is performed for the first time, the upgrade version file of the ONT is saved in the flash of the OLT. The OLT can directly extract the upgrade version of the ONT from the flash and deliver it to the ONT. , to enable this type of ONT to perform version upgrade operations.
  • the control body for upgrading various types of ONTs is the OLT, which will intensify the workload of the OLT when the number of various types of ONTs to be upgraded is large. Therefore, it affects service performance such as service provisioning, user status monitoring, and user bandwidth allocation.
  • the upgrade operation of the various types of ONTs to be upgraded by the OLT is serialized, which often causes the upgrade time of various types of ONTs to be upgraded to be long, thereby affecting the ONT. Upgrade efficiency. Summary of the invention
  • the embodiment of the invention discloses a terminal upgrade method and related equipment, which can effectively reduce the workload of the OLT and improve the upgrade efficiency of the terminal.
  • the first aspect of the embodiment of the present invention discloses a terminal upgrade method, including:
  • the network element management system EMS encapsulates the upgrade version file supported by the terminal type into a multicast program and stores it to the multicast server. Alternatively, the network element management system EMS sends the upgrade version file supported by the terminal type to the multicast server, so that the The multicast server encapsulates the upgrade version file into a multicast section 3 ⁇ 4;
  • the EMS establishes a version address mapping relationship, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address.
  • the encapsulating the upgrade version file supported by the terminal type into a multicast program includes:
  • the EMS sends the version address mapping relationship to the The terminal includes:
  • the EMS loads the version address mapping relationship into an XML configuration file to obtain a target XML configuration file;
  • the EMS delivers the target XML configuration file to the terminal.
  • the method further include:
  • the EMS sends an upgrade test command to the terminal, where the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade version number;
  • the EMS receives a check result of the terminal reported by the terminal for the upgrade check parameter
  • the EMS determines whether the verification result is a check pass, and if the check passes, performs the step of delivering the upgrade start command to the terminal.
  • a second aspect of the embodiment of the present invention discloses a method for upgrading a terminal, including:
  • the terminal receives the version address mapping relationship delivered by the EMS of the network element management system, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address.
  • the multicast program stored in the multicast program storage address is a multicast program encapsulated by an upgrade version file supported by the terminal type;
  • the terminal performs a version upgrade operation according to the received multicast program.
  • the performing, by the terminal, the version upgrade operation according to the received multicast program includes:
  • the terminal extracts each upgrade version sub-file from the received multicast program, where the upgrade version sub-file includes a control header, and the control header includes information required for the terminal upgrade;
  • the level version sub-files are combined to obtain an upgrade version file supported by the terminal type.
  • the terminal receives the network element.
  • the version address mapping relationship delivered by the management system EMS includes:
  • the terminal receives the target XML configuration file delivered by the EMS, where the target XML configuration file is loaded with a version address mapping relationship.
  • the method further includes:
  • the terminal performs verification on the upgrade verification parameter, and obtains a verification result of the terminal for the upgrade verification parameter.
  • the terminal reports the verification result to the EMS, so that when the EMS is triggered to determine that the verification result is a verification pass, an upgrade start command is sent to the terminal.
  • a third aspect of the embodiments of the present invention discloses a network element management system, including:
  • the encapsulating unit is configured to encapsulate the upgraded version file supported by the terminal type into a multicast program and store it to the multicast server; or send the upgraded version file supported by the terminal type to the multicast server, so that the multicast server will The upgrade version file is encapsulated into a multicast program;
  • establishing a unit configured to establish a version address mapping relationship, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address;
  • a first communication unit configured to send the version address mapping relationship to the terminal, and start a second communication unit;
  • the second communication unit is configured to send an upgrade start command to the terminal, to trigger the terminal to send a multicast program on demand to the multicast server according to the multicast program storage address in the version address mapping relationship. And receiving, by the terminal, a multicast program stored by the multicast program storage address of the terminal sent by the multicast server, and performing, by the terminal, a version upgrade operation according to the received multicast program.
  • the method for encapsulating the upgrade version file supported by the terminal type into a multicast program is specifically:
  • the first communications unit includes:
  • a loading subunit configured to load the version address mapping relationship into an XML configuration file to obtain a target XML configuration file
  • a communication subunit configured to send the target XML configuration file to the terminal, and start a second communication unit.
  • the communication subunit is further configured to configure the target XML After the file is sent to the terminal, the upgrade test command is sent to the terminal, and the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade. version number;
  • the communication subunit is further configured to receive a verification result of the terminal for reporting the upgrade verification parameter reported by the terminal;
  • the network element management system further includes a first determining unit, configured to determine whether the verification result is a check pass, and if the check passes, triggering the second communication unit to execute the sending the upgrade start command to the The operation performed by the terminal.
  • a fourth aspect of the embodiment of the present invention discloses a terminal, including:
  • a first interaction unit configured to receive a version address mapping relationship delivered by the EMS of the network element management system, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address; wherein the multicast program storage address
  • the stored multicast program is a multicast program encapsulated by an upgrade version file supported by the terminal type;
  • a second interaction unit configured to receive an upgrade startup instruction delivered by the EMS
  • a program on demand unit configured to send a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship in response to the upgrade start instruction;
  • the program on demand unit is further configured to receive a multicast program stored by the multicast program storage address sent by the multicast server; And an upgrade operation unit, configured to perform a version upgrade operation according to the received multicast program.
  • the upgrade operation unit includes:
  • a first extracting subunit configured to extract, from the received multicast program, each upgrade version subfile, where the upgrade version subfile includes a control header, and the control header includes information required for the terminal upgrade;
  • a file combination sub-unit configured to combine each upgrade version sub-file according to a control header included in each upgrade version sub-file to obtain an upgrade version file supported by the terminal type
  • the version upgrade subunit is used to perform the version upgrade operation according to the upgrade version file.
  • the first interaction unit is configured to receive a target XML configuration file sent by the EMS, where the target XML configuration file is loaded with the terminal type support.
  • the upgrade target version number is mapped to the version address of the multicast program storage address.
  • the first interaction unit is further configured to send the EMS After the target XML configuration file, the upgrade test command is sent by the EMS, and the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade version number.
  • the terminal further includes a parameter verification unit, configured to perform verification on the upgrade verification parameter, and obtain a verification result of the terminal for the upgrade verification parameter;
  • the first interaction unit is further configured to report the verification result to the EMS, so that when the EMS is triggered to determine that the verification result is a verification pass, an upgrade start command is sent to the terminal.
  • a fifth aspect of the embodiments of the present invention discloses a network element management system, including a receiver, a processor, a memory, and a transmitter, where the receiver, the processor, the memory, and the transmitter are respectively connected to a bus, where the memory is A set of terminal upgrade program code is stored, and the processor is configured to invoke terminal upgrade program code stored in the memory, to perform the following operations:
  • the upgrade version file supported by the terminal type is encapsulated into a multicast program and transmitted to the multicast server through the transmitter, or the upgrade version file supported by the terminal type is sent to the multicast server by the transmitter. Causing the multicast server to encapsulate the upgrade version file into a multicast section ⁇ ⁇ ,
  • the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address.
  • the manner of encapsulating the upgrade version file supported by the terminal type into a multicast program is specifically:
  • the processor by using the transmitter, the version
  • the manner in which the address mapping relationship is sent to the terminal is specifically as follows:
  • the processor loads the version address mapping relationship into an XML configuration file to obtain a target XML configuration file;
  • the processor sends the target XML configuration file to the terminal by using the transmitter.
  • the processor configures the target XML by using the transmitter After the file is sent to the terminal, and the processor sends an upgrade start command to the terminal through the transmitter, the processor further performs the following operations:
  • the processor sends an upgrade test command to the terminal by using the transmitter, where the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the type of the terminal, and Upgrade version number;
  • the processor determines whether the verification result is a check pass, and if the check passes, performing the operation of delivering the upgrade start command to the terminal by using the transmitter.
  • a sixth aspect of the embodiments of the present invention discloses a terminal, including a receiver, a processor, a memory, and a transmitter, where the receiver, the processor, the memory, and the transmitter are respectively connected to a bus, wherein the memory stores a group
  • the terminal upgrades the program code
  • the processor is configured to invoke the terminal upgrade program code stored in the memory, to perform the following operations:
  • the multicast program is a multicast program encapsulated by an upgrade version file supported by the terminal type;
  • the manner in which the processor performs a version upgrade operation according to the received multicast program is specifically:
  • each upgrade version subfile where the upgrade version subfile includes a control header, where the control header includes information required for the terminal to be upgraded;
  • the manner in which the processor receives the version address mapping relationship issued by the EMS by using the receiver is specifically:
  • the processor receives, by the receiver, a target XML configuration file delivered by the EMS, where the target XML configuration file is loaded with a version address mapping relationship.
  • the processor receives the target XML configuration file delivered by the EMS
  • the processor receives the upgrade sent by the EMS by using the receiver Before starting the instruction, the processor also performs the following operations:
  • the processor performs verification on the upgrade check parameter, and obtains a check result of the terminal for the upgrade check parameter.
  • the processor reports the verification result to the EMS by using the transmitter, so that when the EMS is triggered to determine that the verification result is a verification, an upgrade start command is sent to the terminal.
  • the embodiment of the invention has the following beneficial effects:
  • the control entity that performs the upgrade operation of the terminal may be dropped from the OLT to the terminal, that is, the terminal may send the multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship. And receiving the multicast program stored in the multicast program storage address sent by the multicast server, and performing a version upgrade operation according to the received multicast program, thereby eliminating the upgrade operation control of the terminal (such as the ONT) by the OLT
  • the OLT is only used as a transmission channel, so that the workload of the OLT can be effectively reduced.
  • the terminal performs multicast program on-demand to implement version upgrade, and a massive terminal can be realized.
  • the parallel version upgrade operation can improve the upgrade efficiency of the terminal.
  • FIG. 1 is a schematic structural diagram of a terminal upgrade system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of an EMS according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of another EMS according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of still another EMS according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of still another EMS according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of still another terminal according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of a method for upgrading a terminal according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart of another method for upgrading a terminal according to an embodiment of the present invention
  • FIG. 11 is a schematic flowchart of still another method for upgrading a terminal according to an embodiment of the present invention.
  • the embodiment of the invention discloses a method for upgrading a terminal and related devices and systems, which can effectively reduce the workload of the OLT and improve the upgrade efficiency of the terminal.
  • the terminal may be an ONT (including an active or passive network unit) or a digital subscriber line (DSL) terminal, which is not limited in the embodiment of the present invention.
  • the terminal is a DSL terminal
  • the DSL terminal can connect to the OLT through a copper wire. The details are described below separately.
  • FIG. 1 is a schematic structural diagram of an optical network terminal upgrading system according to an embodiment of the present invention.
  • the optical network terminal upgrade system shown in FIG. 1 may include:
  • the EMS 10, the multicast server 11, the OLT 12, and the terminal 13 under the OLT 12 are generally installed on the user side, and the terminal 13 can access the user terminal, such as a telephone, a computer, an interactive network television (IPTV), and the like.
  • IPTV interactive network television
  • the number of terminals 13 under the OLT 12 may be one or more.
  • the types of the multiple terminals 13 may be The same may be used.
  • the multiple terminals 13 may also be terminals of different vendors, which are not limited in the embodiment of the present invention.
  • the EMS 10 can pass through a wired network (such as a fiber network). Or a wireless network (such as a wireless local area network) is connected to the multicast server 11; the simple network management protocol (SNMP) can be used for communication between the EMS 10 and the OLT 12; the multicast server 11 can pass through a wired network (such as a fiber network) Or a wireless network (such as a wireless local area network) is connected to the OLT 12; optionally, the multicast server 11 can also be connected to the terminal 13 through a dedicated multicast channel (using a proprietary protocol); the optical fiber can be used between the OLT 12 and the terminal 13 copper
  • SNMP simple network management protocol
  • the FTP protocol or the TR069 protocol communicates.
  • the EMS 10 encapsulates the upgrade version file supported by the terminal 13 into a multicast program and stores it in the multicast server 11; or the EMS sends the upgrade version file supported by the terminal 13 type to the multicast server 11 so that the multicast server 11 will be upgraded.
  • the version file is encapsulated into a multicast program and stored;
  • the EMS 10 establishes a version address mapping relationship, where the establishment version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address; wherein the upgrade version number refers to the version number of the upgrade version file, and the multicast program storage address
  • the storage address of the multicast program encapsulated in the upgrade version file is stored in the multicast server 11; optionally, the multicast program storage address may be returned by the multicast server 11 to the EMS 10, or the multicast program storage address is also Can be specified by EMS10;
  • the EMS 10 is used to deliver the version address mapping relationship to the terminal 13 via the OLT 12; and the upgrade start command is sent to the terminal 13 via the OLT 12;
  • the terminal 13 receives the version address mapping relationship sent by the EMS 10 by the OLT 12, and receives the upgrade start command sent by the EMS 10 via the OLT 12, and responds to the upgrade start command, and stores the multicast program storage address according to the version address mapping relationship.
  • the multicast program on demand request is sent to the multicast server 11; optionally, the terminal 13 may send a multicast program on demand request to the multicast server 11 via the OLT 12, or the terminal 13 may also use a dedicated program with the multicast server 11.
  • the multicast channel sends a multicast program on demand request to the multicast server 11, which is not limited in the embodiment of the present invention;
  • the multicast program stored by the multicast server 11 to the terminal 13 stores the multicast program stored in the address; optionally, the multicast server 11 can transmit the multicast program stored in the multicast program storage address to the terminal 13 via the OLT 12. Alternatively, the multicast server 11 can also pass a dedicated group with the terminal 13. The broadcast channel sends the multicast program stored in the multicast program storage address to the terminal 13 , which is not limited in the embodiment of the present invention;
  • the terminal 13 also receives the multicast program stored in the multicast program storage address sent by the multicast server 11, and performs a version upgrade operation according to the multicast program.
  • the manner in which the EMS 10 or the multicast server 11 encapsulates the upgrade version file supported by the terminal 13 into a multicast program may be:
  • the upgrade version file supported by the terminal 13 type is divided into at least one upgrade version sub-file; wherein, the EMS 10 divides the upgrade version file supported by the terminal 13 type into at least one upgrade version clause and allocates a control header for the upgrade version sub-file, and controls
  • the header includes the information required for the terminal upgrade; it should be noted that the information required for the terminal upgrade included in the foregoing control header may include a software upgrade package valid flag, a header CRC, an upgrade package number, an upgrade version number, and a group. Broadcast server IP, multicast server port number, and description of upgrade control.
  • the manner in which the terminal 13 performs the version upgrade operation according to the multicast program may be:
  • the terminal 13 extracts each upgrade version subfile from the received multicast program, and the upgrade version subfile includes a control header, and the control header includes information required for the terminal upgrade;
  • the terminal 13 combines the upgraded version sub-files according to the control headers included in each upgrade version sub-file to obtain an upgrade version file supported by the terminal type;
  • the terminal 13 performs a version upgrade operation according to the upgrade version file.
  • the manner in which the EMS 10 sends the version address mapping relationship to the terminal 13 through the OLT 12 may be specifically:
  • the EMS 10 is used to load the version address mapping relationship into the XML configuration file to obtain the target XML configuration file.
  • the EMS 10 is also used to deliver the target XML configuration file to the terminal 13 via the OLT 12.
  • the manner in which the terminal 13 receives the version address mapping relationship sent by the OLT 12 by the EMS 10 may be:
  • the terminal 13 is configured to receive the target XML configuration file that is sent by the OLT 12 and is loaded with the version address mapping relationship, so as to implement the correspondence between the upgrade version number supported by the terminal 13 and the multicast program storage address supported by the OLT 12. the goal of.
  • the EMS 10 may map the version address including the mapping relationship between the upgrade version number supported by the terminal 13 type and the multicast program storage address.
  • the XML configuration file is loaded to obtain the target XML configuration file, that is, the target XML configuration file can be loaded with n version address mapping relationships.
  • the EMS 10 can deliver the target XML configuration file to the n OLT12. Terminal 13.
  • each terminal 13 may retain only the target XML configuration file after receiving the target XML configuration file sent by the OLT 12 by the EMS 10.
  • the version address mapping relationship between the upgrade version number supported by the type of the terminal 13 and the multicast program storage address is loaded, and the remaining version address mapping relationships are filtered out. For example, after the nth terminal 13 receives the target XML configuration file sent by the OLT 12, the nth terminal 13 may only retain the upgrade version number included in the target XML configuration file including the nth terminal 13 type support. The version address mapping relationship of the mapping relationship with the multicast program storage address, and the remaining version address mapping relationship is filtered out.
  • the EMS 10 can first test whether the terminal 13 supports the version upgrade operation.
  • the EMS 10 starts the version upgrade operation of the terminal 13. The specific way is:
  • the upgrade test command is sent to the terminal 13 via the OLT 12.
  • the upgrade test command includes an upgrade check parameter, and the upgrade check parameter includes at least the The current version number and the upgrade version number supported by the terminal 13 type; further, the upgrade verification parameter may further include information such as manufacturer information supported by the terminal 13 type;
  • the terminal 13 further receives the upgrade test command sent by the EMS 10 via the OLT 12, and verifies the upgrade check parameter included in the upgrade test command, and obtains the verification result of the upgrade check parameter of the terminal 13;
  • the test results are reported to EMS10 via OLT12; for example, when When the level check parameter includes the current version number, the upgrade version number, and the manufacturer information supported by the type of the terminal 13, the terminal 13 can check whether the version number of the supported current version and the upgrade check parameter include that supported by the terminal 13.
  • the current version number is the same, and the terminal 13 can verify whether the upgrade version number included in the upgrade verification parameter is legal, and the terminal can verify whether the manufacturer information included in the upgrade verification parameter is supported, and the verification result is Reported to EMS10 via OLT12;
  • the EMS 10 is further configured to receive, by the terminal 13, the verification result of the upgrade check parameter by the terminal 13 reported by the OLT 12, and determine whether the check result is a check pass, and if the check passes, the terminal 13 is indicated. Supporting the version upgrade operation, the EMS 10 may perform an operation of delivering the upgrade start command to the terminal 13 via the OLT 12.
  • the terminal 13 may The verification result used to indicate the verification pass is reported to the EMS 10 via the OLT 12, so that the EMS 10 determines that the verification result is a verification pass, indicating that the terminal 13 supports the version upgrade operation, and the EMS 10 executes the upgrade start command by the OLT 12. The operation is delivered to the terminal 13.
  • the EMS 10 may first determine whether the EMS upgrade is satisfied.
  • the EMS 10 can suspend the operation of delivering the upgrade start command from the OLT 12 to the terminal 13 by performing the operation of sending the upgrade start command to the terminal 13 via the OLT 12 when the EMS upgrade policy is satisfied.
  • the EMS upgrade policy may be an upgrade policy preset in the terminal, or may be an upgrade policy delivered by the EMS. The invention is not specifically limited.
  • the EMS 10 is further configured to determine whether the preset EMS upgrade policy is met after determining that the verification result of the upgrade check parameter of the terminal 13 is verified. If the preset EMS upgrade policy is met, the upgrade start command is executed. The operation delivered to the terminal 13 by the OLT 12;
  • the EMS upgrade policy may include any one or several of the following combinations of policies:
  • the terminal 13 is a terminal of a specified type
  • the upgrade target version supported by the terminal 13 is the upgrade target version of the specified vendor.
  • the foregoing target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare whether the versions are consistent.
  • the manner in which the EMS 10 sends the target XML configuration file to the terminal 13 via the OLT 12 may be:
  • the terminal 13 is configured to report the CRC check value added by the remote XML configuration file to the EMS 10 via the OLT 12.
  • the remote XML configuration file is used to load the remote mapping relationship, and the remote mapping relationship is supported by the terminal 13 type. a mapping relationship between the current version number and the storage address of the multicast program encapsulated in the current version;
  • the EMS 10 is configured to receive the CRC check value added by the terminal 13 from the remote XML configuration file reported by the OLT 12; and the CRC check value added to the remote XML configuration file and the CRC check value added to the target XML configuration file. The values are compared. If the comparison is inconsistent, the protocol message including the target XML configuration file is delivered to the terminal 13 via the OLT 12.
  • the terminal 13 can report the CRC check value added by the remote XML configuration file to the EMS 10 through the OLT 12 when the power is turned on, and compare the CRC check value and the target XML configuration added by the remote XML configuration file to the EMS 10.
  • the EMS 10 can learn that the multicast program encapsulated in the current version supported by the terminal 13 is different from the multicast program encapsulated in the upgrade target version supported by the terminal 13.
  • the EMS 10 can target the XML.
  • the configuration file (the target XML configuration file is loaded with the version number mapping relationship between the upgrade version number supported by the terminal 13 and the multicast program storage address) is sent to the terminal 13 via the OLT 12 to subsequently initiate the version upgrade operation of the terminal 13.
  • the terminal 13 is further configured to: after receiving the upgrade startup command sent by the OLT 12, determine whether the preset terminal upgrade policy is met. If the preset terminal upgrade policy is met, the response upgrade start command is executed, and the multicast program on demand request is sent to the multicast server 11 according to the multicast program storage address in the version address mapping relationship;
  • the terminal upgrade policy may include a combination of any one or several of the terminal load service, the voice service, or the terminal current load being less than the preset load value.
  • the on-demand service may include a high-definition video on demand service, and the current load of the terminal refers to the current load of the processor of the terminal.
  • the terminal upgrade policy may further include the terminal determining that the multicast program is stored in the multicast program storage address. Specifically, the terminal may send a multicast program query request to the multicast server according to the multicast program storage address, and the receiving multicast server sends the query response, and determine, according to the query response, whether the multicast program is stored in the multicast program storage address.
  • the terminal 13 executes the response upgrade start command, and sends the multicast program on demand to the multicast server 11 according to the multicast program storage address in the version address mapping relationship.
  • the requested operation can implement adaptive control of the upgrade operation of the terminal 13 version, which can effectively prevent the version upgrade from affecting the service used by the user (such as causing the HD video on demand service to be unsmooth), and/or can effectively prevent
  • the version upgrade increases the current load on the terminal and prevents the terminal from crashing.
  • the terminal can obtain the version upgrade file required for the terminal upgrade through the multicast server.
  • the terminal obtains the upgrade version file from the OLT and obtains the upgrade version file from the multicast server. Therefore, the upgrade tasks of different vendors and different types of terminals can be concurrently performed. Limited by the processing power of the OLT.
  • the manner in which the terminal 13 performs the version upgrade operation according to the upgrade version file may be specifically:
  • the terminal 13 is configured to perform a version upgrade operation on the terminal 13 according to the upgrade version file and in a state machine manner.
  • the version upgrade operation of the terminal in the state machine mode ensures that the version is completely upgraded, and the repeated upgrade of the same upgrade version can be avoided.
  • the control body of the upgrade operation of the terminal can be dropped from the OLT to the terminal (such as an ONT), that is, the terminal (such as an ONT) can perform multicast according to the version address mapping relationship.
  • the program storage address sends a multicast program on demand request to the multicast server, and receives the multicast program stored in the multicast program storage address sent by the multicast server, and performs a version upgrade operation according to the multicast program, thereby eliminating the OLT
  • the upgrade operation control is performed on the terminal (such as the ONT), so that the OLT only serves as a transmission channel during the version upgrade process of the terminal (such as the ONT).
  • the terminal (such as ONT) performs multicast program on demand to implement version upgrade, and can realize massive terminals (such as ONT).
  • Parallel version upgrade operation which can improve the upgrade efficiency of the terminal (such as ONT).
  • a terminal upgrade system disclosed in the embodiment of the present invention has been introduced.
  • the EMS in the terminal upgrade system disclosed in the embodiment of the present invention is further introduced.
  • FIG. 2 is a schematic structural diagram of an EMS according to an embodiment of the present invention.
  • the EMS shown in Figure 2 may include:
  • the package element 21 is configured to encapsulate the upgrade version file supported by the terminal (such as the ONT) type of the OLT into a multicast program and store the file to the multicast server; or send the upgrade version file supported by the terminal type to the multicast server. So that the multicast server encapsulates the upgrade version file into a multicast program and stores it;
  • the establishing unit 22 is configured to establish a version address mapping relationship, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address.
  • the multicast program storage address may be returned by the multicast server to the encapsulation unit. 21, or, the multicast program storage address may also be specified by the encapsulation unit 21;
  • the first communication unit 23 is configured to send a version address mapping relationship to the terminal via the OLT, and start the second communication unit 24;
  • the second communication unit 24 is configured to send an upgrade start command to the terminal by using the OLT, to trigger the terminal to send a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship, and The terminal receives the multicast program stored in the multicast program storage address sent by the multicast server, and the terminal performs a version upgrade operation according to the received multicast program.
  • FIG. 3 is a schematic structural diagram of another EMS according to an embodiment of the present invention.
  • the EMS shown in Figure 3 is optimized by the EMS shown in Figure 2.
  • the encapsulating unit 21 may include:
  • a file division subunit 211 configured to divide the upgrade target version file supported by the terminal type into at least one upgrade target version subfile
  • the control header allocation subunit 212 is configured to allocate a control header for the upgrade version subfile, and the control header includes information required for the terminal upgrade; the program is stored and stored in the multicast server.
  • the multicast program storage address may be returned by the multicast server to the message combining subunit 213 of the encapsulating unit 21, or the multicast program storage address may also be specified by the message combining subunit 213 of the encapsulating unit 21. .
  • the first communication unit 23 may include:
  • the loading subunit 231 is configured to load the version address mapping relationship into the XML configuration file to obtain the target XML configuration file.
  • the communication subunit 232 is configured to send the target XML configuration file to the terminal via the OLT, and start the second communication unit 24.
  • the communication sub-unit 232 is further configured to deliver the upgrade test command by the OLT after the target XML configuration file is sent to the terminal by the OLT.
  • the upgrade test command may include an upgrade check parameter, where the upgrade check parameter may include at least a current version number supported by the terminal type and an upgrade version number; and further, the upgrade check parameter may further include Manufacturer information supported by the terminal;
  • the communication sub-unit 232 is further configured to receive the verification result of the terminal for the upgrade verification parameter reported by the terminal by the OLT; for example, when the upgrade verification parameter includes the current version number supported by the terminal type, and the upgrade
  • the terminal can verify whether the version number of the supported current version is the same as the current verification version parameter supported by the terminal, and the terminal can verify that the upgrade verification parameter is included.
  • the upgrade version number is legal, and the terminal can verify whether the manufacturer information included in the upgrade check parameter is supported, and the verification result is reported to the EMS by the OLT1;
  • the EMS shown in FIG. 3 may further include a first determining unit 25, configured to determine whether the verification result is a check pass, and if the check passes, triggering the second communication unit 24 to execute the upgrade start command.
  • the OLT delivers the operation to the terminal. For example, when the terminal verification supports the current version of the version number and the upgrade verification parameter includes the current version number supported by the terminal, and the terminal If the upgrade version number included in the upgrade check parameter is valid, and the terminal checks to support the manufacturer information included in the upgrade check parameter, the terminal may report the check result used to indicate the pass verification by the OLT.
  • the first determining unit 25 of the EMS determines that the verification result is a verification pass, indicating that the terminal supports the target version upgrade, and the first determining unit 25 may trigger the second communication unit 24 to execute the upgrade start command.
  • the operation is sent to the terminal via the OLT.
  • FIG. 4 is a schematic structural diagram of another EMS according to an embodiment of the present invention.
  • the EMS shown in Figure 4 is optimized by the EMS shown in Figure 3.
  • the EMS shown in Figure 4 it also includes:
  • the second judging unit 26 is configured to determine whether the EMS upgrade policy is met after the first judging unit 25 determines that the check result is the check pass, and if the EMS upgrade policy is met, triggering the upgrade start command executed by the second communication unit 24 The operation delivered to the terminal by the OLT;
  • the EMS upgrade policy may include any one or several of the following combinations of policies:
  • the terminal is a terminal of the specified type
  • the upgrade target version supported by the terminal is the upgrade target version of the specified vendor.
  • the target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare the versions.
  • the manner in which the communication sub-unit 232 sends the target XML configuration file to the terminal via the OLT may be:
  • the communication sub-unit 232 is configured to receive a CRC check value that is added by the terminal to the remote XML configuration file that is reported by the OLT.
  • the remote XML configuration file is used to load the remote mapping relationship, where the remote mapping relationship is the terminal. The mapping between the current version number supported by the type and the storage address of the multicast program encapsulated in the current version;
  • the communication subunit 232 is configured to compare the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file;
  • the communication sub-unit 232 is configured to send, by the OLT, a protocol message including the target XML configuration file to the terminal when the comparison result of the comparison module is inconsistent.
  • the CRC check value added by the remote XML configuration file is reported by the terminal to the EMS through the OLT, and the communication sub-unit 232 compares the remote XML configuration.
  • the communication sub-unit 232 can learn that the multicast program encapsulated by the current version supported by the terminal is encapsulated with the upgrade target version supported by the terminal. The multicast program is different.
  • the communication sub-unit 232 can deliver the target XML configuration file to the terminal through the OLT, so as to subsequently start the version upgrade operation of the terminal.
  • the foregoing protocol message includes but is not limited to an OMCI/OAM protocol message, an FTP protocol message, or a TR069 protocol message.
  • the control body of the upgrade operation of the terminal (such as the ONT) can be reduced from the OLT to the terminal by using the EMS shown in FIG. 2 to FIG. 4, so that the upgrade operation control of the terminal by the OLT can be omitted, so that the terminal is in the opposite terminal.
  • the OLT is only used as a transmission channel, so that the workload of the OLT can be effectively reduced.
  • the terminal performs multicast program on demand to implement version upgrade.
  • the parallel version upgrade operation of the massive terminal can be realized, thereby improving the upgrade efficiency of the terminal.
  • the terminal can obtain the version upgrade file required for the terminal upgrade through the multicast server.
  • FIG. 5 is a schematic structural diagram of another EMS according to an embodiment of the present invention.
  • the network element management system EMS shown in FIG. 5 may include a receiver 50, a processor 51, a memory 52, and a transmitter 53, wherein the receiver 50, the processor 51, the memory 52, and the transmitter 53 are respectively connected to the bus 54.
  • the memory 52 stores a set of terminal upgrade program codes, and the processor 51 is configured to call the terminal upgrade program code stored in the memory 52, and is configured to: receive, by the receiver 50, an upgrade version file supported by the terminal type;
  • the upgrade version file supported by the terminal type managed by the OLT is encapsulated into a multicast program and transmitted to the multicast server through the transmitter 53.
  • the upgrade version file supported by the terminal type is sent to the multicast server through the transmitter 53. Enable the multicast server to encapsulate the upgrade version file into a multicast program and store it;
  • the version address mapping relationship includes the upgrade version number and multicast program storage.
  • the mapping relationship of the storage address; optionally, the multicast program storage address may be returned to the processor 51 by the multicast server through the receiver 50, or the multicast program storage address may also be specified by the processor 51;
  • the address mapping relationship is sent to the terminal by the OLT;
  • the upgrade initiation command is sent by the OLT to the terminal by the OLT to trigger the terminal to send a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship, and the terminal receives the group by the terminal.
  • the multicast program stored by the broadcast server stores the multicast program stored in the address, and the terminal performs a version upgrade operation according to the received multicast program.
  • the manner in which the processor 51 encapsulates the upgrade version file supported by the terminal type into a multicast program is specifically:
  • the manner in which the processor 51 sends the version address mapping relationship to the terminal through the transmitter 53 may be specifically:
  • the processor 51 loads the version address mapping relationship into the XML configuration file to obtain the target XML configuration file.
  • the processor 51 delivers the target XML configuration file to the terminal via the OLT through the transmitter 53.
  • the processor 51 sends the target XML configuration file to the terminal through the OLT through the transmitter 53, and the processor 51 upgrades through the transmitter 53.
  • the processor 51 also performs the following operations before the boot command is sent to the terminal via the OLT:
  • the processor 51 sends the upgrade test command to the terminal by using the OLT.
  • the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade version number. Further, the upgrade verification parameter may further include manufacturer information supported by the terminal;
  • the processor 51 receives, by the receiver 50, the verification result of the terminal for the upgrade check parameter reported by the terminal that is reported by the OLT; for example, when the upgrade check parameter includes the current version number and the upgrade target version number supported by the terminal type. And the manufacturer information, the terminal can verify the current version of the support Whether the version number is the same as the current version number supported by the terminal, and the ONT can verify whether the upgrade version number included in the upgrade check parameter is legal, and the terminal can verify whether the upgrade check is supported. The manufacturer information of the parameter is included, and the verification result is reported to the EMS by the OLT1;
  • the processor 51 determines whether the verification result is a check pass. If the check passes, the operation of transmitting the upgrade start command by the transmitter 53 to the terminal by the OLT is performed. For example, when the version number of the current version supported by the terminal verification type is the same as the current version number supported by the terminal type included in the upgrade verification parameter, and the terminal verifies the upgrade version number included in the upgrade verification parameter. When the terminal checks and supports the manufacturer information included in the upgrade check parameter, the terminal may report the check result indicating the pass verification to the EMS via the OLT, so that the processor 51 of the EMS determines the When the verification result is that the verification is passed, it indicates that the terminal supports the version upgrade, and the processor 51 can perform the operation of delivering the upgrade startup command to the terminal through the OLT.
  • the processor 51 sends the upgrade start command to the device through the OLT through the transmitter 53. Before the terminal, the processor 51 also performs the following operations:
  • the processor 51 determines whether the EMS upgrade policy is met. If the EMS upgrade policy is met, the operation of transmitting the upgrade start command by the transmitter 53 to the terminal is performed by the transmitter 53;
  • the EMS upgrade policy may include any one or several of the following combinations of policies:
  • the terminal is a terminal of the specified type
  • the upgrade target version supported by the terminal is the upgrade target version of the specified vendor.
  • the foregoing target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare whether the versions are consistent.
  • the manner in which the processor 51 sends the target XML configuration file to the terminal through the OLT through the transmitter 53 may be:
  • the processor 51 receives the CRC check value added by the terminal from the remote XML configuration file reported by the OLT through the receiver 50.
  • the remote XML configuration file is used to load the remote mapping relationship, where the remote mapping relationship is The mapping relationship between the current version number supported by the terminal type and the storage address of the multicast program encapsulated in the current version;
  • the processor 51 compares the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file, and if the comparison is inconsistent, the protocol including the target XML configuration file is delivered by the OLT through the transmitter 53. A message is sent to the terminal.
  • the CRC check value added by the remote XML configuration file is reported by the terminal to the EMS through the OLT, and the processor 51 compares the CRC check value added by the remote XML configuration file.
  • the processor 51 can learn that the multicast program encapsulated in the current version supported by the terminal is different from the multicast program encapsulated in the upgrade target version supported by the terminal.
  • the processor 51 can deliver the target XML configuration file to the terminal via the OLT, so as to subsequently initiate the version upgrade operation of the terminal.
  • the foregoing protocol message includes but is not limited to an OMCI/OAM protocol message, an FTP protocol message, or a TR069 protocol message.
  • the control body of the upgrade operation of the terminal can be lowered from the OLT to the terminal by implementing the EMS shown in FIG. 5, so that the upgrade operation control of the terminal by the OLT can be omitted, so that the OLT only performs the version upgrade process on the terminal.
  • the workload of the OLT can be effectively reduced.
  • the terminal performs multicast program on demand to implement version upgrade, and the parallel version upgrade operation of the massive terminal can be realized. It can improve the upgrade efficiency of the terminal.
  • the terminal can obtain the version upgrade file required for the terminal upgrade through the multicast server.
  • the terminal obtains the upgrade version file from the OLT and obtains the upgrade version file from the multicast server.
  • FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present invention. As shown in FIG. 6, the terminal may include:
  • the first interaction unit 61 is configured to receive a version address mapping relationship delivered by the EMS, where the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address, where the multicast program stored in the multicast program storage address is The multicast version of the upgrade version file supported by the terminal type is encapsulated into a multicast program; wherein, the upgrade version number refers to the version number of the upgrade version file;
  • the second interaction unit 62 is configured to receive an upgrade start command sent by the OLT by the OLT.
  • the program on-demand unit 63 is configured to send the group to the multicast server according to the multicast program storage address in the version address mapping relationship in response to the upgrade start command. Broadcast program on demand request;
  • the program on demand unit 63 is further configured to receive a multicast program stored in the multicast program storage address sent by the multicast server;
  • the upgrade operation unit 64 is configured to perform a version upgrade operation according to the received multicast program.
  • the upgrade operation unit 64 may include:
  • the first extraction sub-unit 641 extracts each upgrade version sub-file from the received multicast program, and the upgrade version sub-file includes a control header, and the control header includes information required for the terminal upgrade;
  • the file combination sub-unit 642 is configured to combine each upgrade version sub-file according to the control header included in each upgrade version sub-file to obtain an upgrade version file supported by the terminal type;
  • the version upgrade subunit 643, is used to perform a version upgrade operation according to the upgrade version file.
  • the first interaction unit 61 may be configured to receive a target XML configuration file sent by the OLT by the OLT, where the target XML configuration file is loaded with a version address.
  • the mapping relationship is implemented, so that the first interaction unit 61 can receive the mapping relationship between the upgrade version number supported by the terminal type and the version address of the multicast program storage address that is sent by the OLT.
  • the first interaction unit 61 is further configured to receive an upgrade of the EMS by the OLT after receiving the target XML configuration file sent by the OLT by the OLT.
  • the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade version number; and further, the upgrade check parameter may further include manufacturing supported by the terminal.
  • the terminal shown in FIG. 6 may further include a parameter verification unit 65, configured to perform verification on the upgrade verification parameter, and obtain a verification result of the terminal for the upgrade verification parameter; for example, when upgrading the school
  • the parameter verification unit 65 may check whether the version number of the current version supported by the terminal type is the terminal included in the upgrade verification parameter. The current version number supported is the same, and the upgrade check can be verified. Whether the upgrade version number included in the parameter is legal, and whether the terminal supports the manufacturer information included in the upgrade check parameter, and the verification result is reported to the EMS by the OLT;
  • the first interaction unit 61 is further configured to report the verification result to the EMS by the OLT, so that when the triggering EMS determines that the verification result is a verification pass, the upgrade start command is sent to the terminal by the OLT.
  • the first interaction unit 61 may report the check result used for the check pass to the EMS through the OLT, so that the EMS determines the check result.
  • the check is passed, it indicates that the terminal supports the target version upgrade, and the EMS can perform the operation of sending the upgrade start command to the terminal through the OLT.
  • the foregoing target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare whether the versions are consistent.
  • the manner in which the first interaction unit 61 receives the target XML configuration file sent by the OLT via the OLT may be:
  • the first interaction unit 61 is configured to report the CRC check value added by the remote XML configuration file to the EMS by using the OLT; where the remote XML configuration file is used to load the remote mapping relationship, where the remote mapping relationship is the terminal The mapping between the current version number supported by the type and the storage address of the multicast program encapsulated in the current version;
  • the first interaction unit 61 is further configured to receive, by the EMS, a protocol including the target XML configuration file delivered by the OLT after comparing the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file. Message.
  • the first interaction unit 61 may report the CRC check value added by the remote XML configuration file to the EMS when the terminal is powered on, and compare the CRC of the remote XML configuration file by the EMS.
  • the EMS can learn that the multicast program encapsulated in the current version supported by the terminal is different from the multicast program encapsulated in the upgrade target version supported by the terminal.
  • the EMS can send the target XML configuration file to the terminal through the OLT, so as to subsequently start the version upgrade operation of the terminal.
  • the foregoing protocol message includes, but is not limited to, an OMCI/OAM protocol message, FTP protocol message or TR069 protocol message.
  • FIG. 7 is a schematic structural diagram of another terminal according to an embodiment of the present invention.
  • the terminal shown in FIG. 7 is optimized by the terminal shown in FIG. 6.
  • the terminal shown in FIG. 7 may further include:
  • the determining unit 66 is configured to determine, after the second interworking unit 62 receives the upgrade start command sent by the OLT, whether the preset terminal upgrade policy is met, and if the preset terminal upgrade policy is met, triggering the program on demand unit 64: executing a response upgrade start command, and sending a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship;
  • the terminal upgrade policy may include any combination of the on-demand service, the voice service, or the current load of the terminal being less than a preset load value.
  • the on-demand service may include a high-definition video on demand service, and the current load of the terminal refers to the current load of the processor of the terminal.
  • the program on-demand unit 64 when the determining unit 66 determines that the preset terminal upgrade policy is met, the program on-demand unit 64 is triggered to execute the response upgrade start command, and sends the multicast program storage address in the version address mapping relationship to the multicast server.
  • the operation of the multicast program on-demand request can implement the adaptive control of the terminal version upgrade, which can effectively prevent the version upgrade from affecting the service used by the user (such as causing the HD video on-demand service to be unsmooth), and/or can be effective. Prevent the version upgrade from accelerating the current load of the terminal and prevent the terminal from crashing.
  • the manner in which the version upgrade subunit 643 performs the version upgrade operation according to the upgrade version file may be specifically:
  • the version upgrade subunit 643 is used to perform a version upgrade operation on the terminal according to the upgraded version file and using the state machine mode.
  • the version upgrade operation of the terminal in the state machine mode ensures a complete upgrade of the version, and can also avoid repeated upgrades of the same upgrade version.
  • the terminal can be used as the control body of the upgrade operation, so that the OLT can perform the upgrade operation control on the terminal, so that the OLT can only be used as the transmission channel during the version upgrade process of the terminal. Therefore, the workload of the OLT can be effectively reduced.
  • the terminal can perform multicast program-on-demand to implement version upgrade, and the parallel version upgrade operation of the mass terminal can be implemented, thereby improving the upgrade efficiency of the terminal. Because the terminal can obtain the terminal through the multicast server. The version upgrade file required for the upgrade, the terminal obtains the upgrade version file from the OLT and obtains the upgrade version file from the multicast server.
  • FIG. 8 is a schematic structural diagram of another terminal according to an embodiment of the present invention.
  • the terminal shown in FIG. 8 may include a receiver 80, a processor 81, a memory 82, and a transmitter 83.
  • the receiver 80, the processor 81, the memory 82, and the transmitter 83 are respectively connected to the bus 84, wherein the memory 82 stores A set of terminal upgrade program code, and the processor 81 is configured to call the terminal upgrade program code stored in the memory 82 for performing the following operations:
  • the receiver 80 receives the version address mapping relationship of the EMS delivered by the OLT.
  • the version address mapping relationship includes a mapping relationship between the upgrade version number and the multicast program storage address.
  • the multicast program stores the multicast program stored in the multicast program address.
  • the multicast version of the upgraded version file supported by the type is encapsulated into a multicast program; and the upgrade start command sent by the OLT by the OLT is received by the receiver 80;
  • the multicast program on-demand request is sent to the multicast server by the transmitter 83 according to the multicast program storage address in the version address mapping relationship;
  • the manner in which the processor 81 performs the version upgrade operation according to the received multicast program is specifically:
  • the upgrade version subfile includes a control header, and the control header includes information required for the terminal upgrade;
  • each upgrade version sub-file is combined to obtain an upgrade version file supported by the terminal type
  • the manner in which the processor 81 receives the version address mapping relationship delivered by the EMS through the receiver 80 may be specifically:
  • the processor 81 receives, by the receiver 80, the target XML configuration file sent by the EMS by the OLT.
  • the target XML configuration file is loaded with a version address mapping relationship, so that the processor 81 can receive the mapping relationship between the upgrade version number supported by the terminal type and the version address of the multicast program storage address supported by the OLT.
  • the processor 81 receives the EMS from the target XML configuration file sent by the OLT through the receiver 80, and the processor 81 receives the EMS through the receiver 80. Before the upgrade start command issued by the OLT, the processor 81 performs the following operations:
  • the processor 81 receives, by the receiver 80, an upgrade test command sent by the OLT by the OLT, where the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the terminal type and an upgrade version number; Further, the upgrade verification parameter may further include manufacturer information supported by the terminal;
  • the processor 81 verifies the upgrade verification parameter, and obtains a verification result of the terminal for the upgrade verification parameter.
  • the processor 81 sends the verification result to the EMS through the OLT, so that the triggering EMS determines that the verification result is the verification pass, and the upgrade start command is sent to the terminal by the OLT.
  • the processor 81 may check whether the version number of the current version supported by the terminal is included with the upgrade check parameter.
  • the terminal supports the same current version number, and can verify whether the upgrade version number included in the upgrade check parameter is legal, and can verify whether the terminal supports the manufacturer information included in the upgrade check parameter, and will verify The result is reported to the EMS by the OLT;
  • the processor 81 may report the verification result indicating that the verification pass is reported to the EMS by the OLT, so that the EMS determines that the check result is a check pass. Indicates that the terminal supports the version upgrade.
  • the EMS can perform the operation of sending the upgrade startup command to the terminal through the OLT.
  • the foregoing target XML configuration The file can be added with a unique CRC check value, and the CRC check value is used to compare the versions.
  • the manner in which the processor 81 receives the target XML configuration file sent by the OLT through the OLT through the receiver 80 may be specifically:
  • the processor 81 sends the CRC check value added by the remote XML configuration file to the EMS through the OLT.
  • the remote XML configuration file is used for the remote mapping relationship, and the remote mapping relationship is the terminal type. a mapping relationship between the supported current version number and the storage address of the multicast program encapsulated by the current version;
  • the processor 81 receives, by the receiver 80, the protocol message including the target XML configuration file delivered by the OLT after the EMS compares the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file. .
  • the processor 81 may report the CRC check value added by the remote XML configuration file to the EMS when the terminal is powered on, and compare the CRC check added by the remote XML configuration file by the EMS.
  • the EMS can learn that the multicast version encapsulated in the current version supported by the terminal is different from the multicast program encapsulated in the upgrade version supported by the terminal.
  • the EMS can The target XML configuration file is delivered to the terminal by the OLT, so as to subsequently start the version upgrade operation of the terminal.
  • the foregoing protocol message includes but is not limited to an OMCI/OAM protocol message, an FTP protocol message, or a TR069 protocol message.
  • the processor 81 receives the upgrade start command sent by the OLT by the receiver 80, and the processor 81 responds to the upgrade start command according to the version address. Before the multicast program storage address in the mapping relationship is sent by the transmitter 83 to the multicast server for the multicast program on demand request, the processor 81 also performs the following operations:
  • the processor 81 determines whether the preset terminal upgrade policy is met. If the preset terminal upgrade policy is met, the executed response upgrade start command is sent to the multicast server by the transmitter 83 according to the multicast program storage address in the version address mapping relationship. The operation of the multicast program on demand request;
  • the terminal upgrade policy may include any combination of the on-demand service, the voice service, or the current load of the terminal being less than a preset load value.
  • the on-demand service may include a high-definition video on demand service, and the current load of the terminal refers to the location of the terminal.
  • the current load of the processor may include a high-definition video on demand service, and the current load of the terminal refers to the location of the terminal. The current load of the processor.
  • the processor 81 determines that the preset terminal upgrade policy is met, the response upgrade start command is executed, and the multicast program on-demand request is sent to the multicast server according to the multicast program storage address in the version address mapping relationship.
  • the operation can implement adaptive control of the terminal version upgrade, which can effectively prevent the version upgrade from affecting the services used by the user (such as causing the HD video on demand service to be unsmooth), and/or can effectively prevent the version upgrade from being intensified.
  • the terminal is currently loaded to prevent the terminal from crashing.
  • the manner in which the processor 81 performs the version upgrade operation according to the upgrade version file may be specifically:
  • the processor 81 is configured to perform a version upgrade operation on the terminal according to the upgrade version file and in a state machine manner.
  • the version upgrade operation of the terminal in the state machine mode ensures a complete upgrade of the version, and can also avoid repeated upgrades of the same upgrade version.
  • the terminal can be used as the control body of the upgrade operation, so that the upgrade operation control of the terminal by the OLT can be omitted, so that the OLT can only be used as a transmission channel during the version upgrade process of the terminal, thereby being effective.
  • the OLT's workload is reduced.
  • the terminal performs multicast program on-demand to implement version upgrade, which enables parallel version upgrade operations of massive terminals, thereby improving terminal upgrade efficiency.
  • the terminal can obtain the version upgrade file required for the terminal upgrade through the multicast server.
  • the terminal obtains the upgrade version file from the OLT and obtains the upgrade version file from the multicast server. Therefore, the upgrade tasks of different vendors and different types of terminals can be concurrently performed. Limited by the processing power of the OLT.
  • optical terminal upgrading system and the EMS and the terminal disclosed in the embodiment of the present invention are described above.
  • the optical terminal upgrading method disclosed in the embodiment of the present invention is further described below.
  • FIG. 9 is a schematic flowchart diagram of a method for upgrading a terminal according to an embodiment of the present invention. Among them, the method described in FIG. 9 is described from the perspective of EMS. As shown in Figure 9, the method can include the following steps:
  • the EMS encapsulates the upgrade version file supported by the terminal type managed by the OLT into a multicast program and stores it in the multicast server.
  • the EMS establishes a mapping relationship between the upgrade version number supported by the terminal type and the version address of the multicast program storage address.
  • the EMS delivers the version address mapping relationship to the terminal through the OLT.
  • the EMS sends an upgrade start command to the terminal by using the OLT, to trigger the terminal to send a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship, and receive the multicast by the terminal.
  • the multicast program sent by the server stores the multicast program stored in the address, and the terminal performs a version upgrade operation according to the multicast program.
  • the mapping between the upgrade target version number supported by the terminal type and the version address address of the multicast program storage address of the terminal in the foregoing step 92 may include the following table.
  • the manner in which the EMS sends the version address mapping relationship to the terminal through the OLT may be:
  • the EMS loads the version address mapping relationship into the XML configuration file, obtains the target XML configuration file, and the EMS delivers the target XML configuration file to the terminal via the OLT.
  • the EMS may send a protocol message including the target XML configuration file to the terminal via the OLT, so as to implement the target XML configuration file to be delivered to the terminal by the OLT.
  • the protocol message may include, but is not limited to, an OMCI/OAM protocol message, an FTP protocol message, or a TR069 protocol message.
  • the terminal when the OLT sends a protocol message including the target XML configuration file to the terminal, the terminal notifies the OLT, so that the OLT re-issues the protocol message including the target XML configuration file.
  • the EMS may perform the following steps after the target XML configuration file is delivered to the terminal by the OLT, and before the EMS performs step 94. :
  • the EMS sends the upgrade test command to the terminal by the OLT.
  • the upgrade test command includes an upgrade check parameter, and the upgrade check parameter includes at least a current version number supported by the terminal type and an upgraded version number.
  • the EMS receives the verification result of the ONT by the terminal reported by the OLT for the upgrade check parameter;
  • the EMS determines whether the verification result is a check pass, and if the check passes, step S904 is performed.
  • the EMS determines that the verification result is the verification pass, it indicates that the terminal supports the version upgrade, and the EMS may perform step 904 to start the version upgrade operation of the terminal.
  • the EMS may further perform the following steps:
  • the EMS determines whether the preset EMS upgrade policy is met. If the preset EMS upgrade policy is met, perform EMS to perform step 94.
  • the foregoing target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare whether the versions are consistent.
  • the foregoing EMS sending the target XML configuration file to the terminal by using the OLT may include:
  • the EMS receives the CRC check value added by the terminal by the remote XML configuration file reported by the OLT.
  • the remote XML configuration file is used to load the remote mapping relationship, where the remote mapping relationship is the current version supported by the terminal type.
  • the EMS compares the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file, and if the comparison is inconsistent, the OLT sends a protocol message including the target XML configuration file to the terminal. .
  • FIG. 10 is a schematic flowchart of another terminal upgrading method according to an embodiment of the present invention. Among them, the method described in FIG. 10 is described from the perspective of the ONT. As shown in Figure 10, the method can include the following steps:
  • the ONT receiving EMS is mapped by the version number of the upgraded version number supported by the ONT type and the version address of the multicast program storage address, and the multicast program stored in the multicast program storage address is supported by the ONT type.
  • the upgraded version is packaged into a multicast program. 102.
  • the ONT receives the upgrade start command sent by the OLT by the OLT.
  • the ONT responds to the upgrade start command, and sends a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship.
  • the ONT receives the multicast program stored in the multicast program storage address sent by the multicast server. 105. The ONT performs a version upgrade operation according to the multicast program.
  • the ONT receiving EMS in the foregoing step 101 is mapped by the version number of the upgrade version number supported by the ONT type and the version address of the multicast program storage address delivered by the OLT.
  • the ONT receives the target XML configuration file sent by the OLT through the OLT.
  • the target XML configuration file is loaded with the version number mapping relationship between the upgrade version number supported by the ONT type and the multicast program storage address.
  • the ONT receives the target XML configuration file sent by the OLT, and the ONT performs the receiving EMS in the foregoing step 102, the OLT is delivered by the OLT. Before upgrading the boot command, the ONT can also perform the following steps:
  • the ONT receives the upgrade test command sent by the OLT, and the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least the current version number supported by the ONT and the upgrade target version number;
  • the ONT checks the upgrade check parameter, and obtains a check result of the ONT for the upgrade check parameter.
  • the ONT reports the verification result to the EMS through the OLT, so that the triggering EMS determines that the verification result is the verification pass, and the upgrade start command is sent to the ONT by the OLT.
  • the EMS when the EMS determines that the verification result is a verification pass, it indicates that the ONT supports the version upgrade, and the EMS may send an upgrade start command to the ONT via the OLT.
  • the foregoing target XML configuration file may be added with a unique CRC check value, and the CRC check value is used to compare whether the versions are consistent.
  • the target XML configuration file sent by the ONT to receive the EMS by the OLT includes:
  • the ONT adds the CRC check value added by the remote XML configuration file to the EMS through the OLT;
  • the remote XML configuration file is used to load a remote mapping relationship, where the remote mapping relationship is a mapping relationship between a current version number supported by the ONT type and a storage address of a multicast program encapsulated in the current version.
  • the ONT receiving EMS compares the CRC check value added by the remote XML configuration file with the CRC check value added by the target XML configuration file, and then sends the protocol message including the target XML configuration file by the OLT.
  • the ONT can report the CRC check value added by the local XML configuration file of the ONT to the EMS after being powered on, and compare the CRC check value added by the remote XML configuration file with the EMS.
  • the EMS can learn that the multicast version encapsulated by the current version supported by the ONT is different from the multicast program encapsulated by the upgrade version supported by the ONT.
  • the EMS can target The XML configuration file is delivered to the ONT via the OLT.
  • the ONT may update the remote mapping relationship by using the version address mapping relationship, and the ONT may use the version address mapping relationship as the new remote mapping relationship.
  • the ONT may perform the following steps:
  • the ONT determines whether the preset ONT upgrade policy is met. If the preset ONT upgrade policy is met, go to step 103.
  • the ONT can receive the ONT upgrade policy delivered by the OLT.
  • the ONT upgrade policy can include one or a combination of the following situations, namely:
  • the ONT does not currently have on-demand services or voice services
  • the current load of the ONT is less than the preset load value
  • the ONT finds the corresponding multicast program according to the upgraded version storage address.
  • the ONT has not been upgraded to the upgraded version.
  • the manner in which the ONT performs the version upgrade operation according to the multicast program in the foregoing step 105 may be specifically:
  • the ONT extracts, according to the received multicast program, each multicast packet included in the multicast program, where the multicast packet includes an upgrade target version subfile and a control header;
  • the ONT combines the upgrade target version sub-files included in each multicast packet according to the control header included in each multicast packet to obtain an upgrade target version file supported by the ONT type.
  • the ONT performs a version upgrade operation according to the upgrade target version file.
  • the ONT can perform the version upgrade operation on the ONT according to the upgrade target version file and the state machine mode.
  • the version upgrade operation of the ONT in the state machine mode ensures a complete upgrade of the version, and can also avoid repeated upgrades of the same upgrade version.
  • the multicast server can periodically deliver multicast programs. When the ONT detects that the upgrade fails, the ONT can perform the upgrade operation again according to the next multicast program delivered by the multicast server until the upgrade is complete. After the ONT detects the upgrade, the ONT is complete.
  • the multicast server can be notified to stop delivering multicast programs, thus ensuring a complete upgrade of the version, and avoiding repeated upgrades of the same upgrade version.
  • FIG. 11 is a schematic flowchart of another optical terminal upgrading method according to an embodiment of the present invention. The method described in FIG. 11 is described from multiple perspectives of EMS, multicast server, OLT, and ONT. As shown in FIG. 11, the method may include the following steps:
  • the EMS encapsulates the upgrade version file supported by the ONT type under the OLT into a multicast program.
  • the EMS uploads the multicast program encapsulated by the upgrade version file supported by the ONT type to the multicast program.
  • Multicast server storage
  • the EMS establishes a mapping relationship between the upgrade version number supported by the ONT type and the version address of the multicast program storage address.
  • the EMS loads the local mapping relationship into the XML configuration file to obtain the target XML configuration file.
  • the EMS delivers the target XML configuration file to the ONT via the OLT.
  • the EMS sends the upgrade test command to the ONT by using the OLT.
  • the upgrade test command includes an upgrade check parameter, where the upgrade check parameter includes at least a current version number supported by the ONT and an upgrade target version number.
  • the ONT verifies the upgrade check parameter, and obtains a check result of the ONT for the upgrade check parameter.
  • the ONT reports the verification result to the EMS by using the OLT.
  • the EMS determines whether the verification result is a check pass. If the check is passed, the EMS determines whether the preset EMS upgrade policy is met. If the preset EMS upgrade policy is met, the upgrade start command is sent to the OLT through the OLT. ONT.
  • the ONT determines whether the preset ONT upgrade policy is met. If the preset ONT upgrade policy is met, the ONT responds to the upgrade start command, and sends a multicast program on demand request to the multicast server according to the multicast program storage address in the version address mapping relationship. .
  • the ONT can implement adaptive control of the version upgrade, which can effectively prevent the version upgrade from affecting the service used by the user (such as causing the HD video on demand service to be unsmooth), and/or can effectively prevent the version.
  • the upgrade exacerbates the current load on the ONT and prevents the ONT from crashing.
  • the ONT receives the multicast program stored in the multicast program storage address sent by the multicast server. 121. The ONT performs a version upgrade operation according to the multicast program.
  • the ONT can be used as the control body of the upgrade operation, so that the upgrade operation control of the ONT by the OLT can be omitted, so that the OLT can only be used as a transmission channel during the version upgrade process of the ONT, thereby effectively Reduce the workload of the OLT;
  • the ONT performs multicast program on demand to implement version upgrade, which can realize parallel version upgrade operation of massive ONT. This can improve the upgrade efficiency of the ONT.
  • the ONT can obtain the version upgrade file required for the ONT upgrade through the multicast server.
  • the ONT obtains the upgrade version file from the OLT and obtains the upgrade version file from the multicast server. Therefore, the upgrade tasks of different vendors and different types of terminals can be concurrently performed. Limited by the processing power of the OLT.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种终端升级方法及相关设备,该方法为:EMS将终端类型支持的升级版本文件封装成组播节目并存储至组播服务器,或将终端类型支持的升级版本文件发送至组播服务器,以使组播服务器将升级版本文件封装成组播节目;EMS建立版本地址映射关系,版本地址映射关系包括升级版本号与组播节目存储地址的映射关系;EMS将版本地址映射关系下发至终端;将升级启动指令下发至终端,以触发终端根据版本地址映射关系中的组播节目存储地址向组播服务器发送组播节目点播请求,以及由终端接收组播服务器发送的终端的组播节目存储地址存储的组播节目,并由终端依据接收到的组播节目执行版本升级操作。能够有效降低OLT的工作负荷以及提升终端的升级效率。

Description

一种终端升级方法及相关设备 技术领域
本发明涉及光网络技术领域, 尤其涉及一种终端升级方法及相关设备。 背景技术
在无源光纤网络( Passive Optical Network, PON )中,随着光纤到户( Fiber To The Home , FTTH ) 的大规模商用, 光线路终端 ( Optical Line Terminal, OLT )所辖的光网络终端(Optical network terminal, ONT )的功能需要不断增 强, 因此常常需要对 OLT所辖的 ONT进行版本升级操作。
在实践中, 对 ONT 进行升级操作的过程可以概述为: 网元管理系统 ( Element Management System, EMS )接收经 OLT上报的各类 ONT的版本号, 并将各类 ONT上报的版本号分别与 EMS保存的各类 ONT的版本号进行比较, 依据比较结果确定出待升级的各类 ONT, 由 OLT依次对待升级的各类 ONT 进行版本升级操作, 即对于待升级的每一类 ONT, OLT判断是否首次进行该 类 ONT的升级操作, 若是首次进行该类 ONT的升级操作, OLT可以从 EMS 获取该类 ONT的升级版本文件, 并下发至该类 ONT, 以使该类 ONT进行版 本升级操作; 若不是首次进行该类 ONT的升级操作, 则 OLT的 flash中已经 保存了该类 ONT的升级版本文件, 则 OLT可以直接从 flash中提取该类 ONT 的升级版本文件, 并下发至该类 ONT, 以使该类 ONT进行版本升级操作。
在实践中发现,在上述的对各类 ONT进行升级操作的过程中,对各类 ONT 进行升级操作的控制主体是 OLT, 在待升级的各类 ONT的数量较大时会加剧 OLT的工作负荷, 从而会影响 OLT的业务开通、 用户状态监测、 用户带宽分 配等业务性能。 另外, 在上述的对各类 ONT进行升级操作的过程中, OLT对 待升级的各类 ONT 进行升级操作是串行处理的, 这往往导致待升级的各类 ONT的升级时间很长, 从而影响 ONT的升级效率。 发明内容
本发明实施例公开了一种终端升级方法及相关设备, 能够有效降低 OLT 的工作负荷以及提升终端的升级效率。
本发明实施例第一方面公开了一种终端升级方法, 包括:
网元管理系统 EMS将终端类型支持的升级版本文件封装成组播节目并存 储至组播服务器; 或者, 网元管理系统 EMS将终端类型支持的升级版本文件 发送至组播服务器, 以使所述组播服务器将所述升级版本文件封装成组播节 ¾ ;
所述 EMS建立版本地址映射关系, 所述版本地址映射关系包括升级版本 号与组播节目存储地址的映射关系;
所述 EMS将所述版本地址映射关系下发至终端;
所述 EMS将升级启动指令下发至所述终端, 以触发所述终端根据所述版 本地址映射关系中的组播节目存储地址向所述组播服务器发送组播节目点播 请求,以及由所述终端接收所述组播服务器发送的所述终端的组播节目存储地 址存储的组播节目,并由所述终端依据接收到的所述组播节目执行版本升级操 作
在本发明实施例第一方面的第一种可能的实现方式中,所述将终端类型支 持的升级版本文件封装成组播节目包括:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息; 结合本发明实施例第一方面或本发明实施例第一方面的第一种可能的实 现方式, 在本发明实施例第一方面的第二种可能的实现方式中, 所述 EMS将 所述版本地址映射关系下发至所述终端包括:
所述 EMS 将所述版本地址映射关系加载至 XML 配置文件, 获得目标 XML配置文件;
所述 EMS将所述目标 XML配置文件下发至所述终端。
结合本发明实施例第一方面的第二种可能的实现方式,在本发明实施例第 一方面的第三种可能的实现方式中, 所述 EMS将所述目标 XML配置文件下 发至所述终端之后, 以及所述 EMS将升级启动指令下发至所述终端之前, 所 述方法还包括:
所述 EMS将升级测试指令下发至所述终端, 所述升级测试指令包括升级 校验参数,所述升级校验参数至少包括所述终端类型支持的当前版本号以及升 级版本号;
所述 EMS接收所述终端上报的所述终端针对所述升级校验参数的校验结 果;
所述 EMS判断所述校验结果是否为校验通过, 若校验通过, 执行所述的 将升级启动指令下发至所述终端的步骤。
本发明实施例第二方面公开了一种终端升级方法, 包括:
终端接收网元管理系统 EMS下发的版本地址映射关系, 所述版本地址映 射关系包括升级版本号与组播节目存储地址的映射关系; 其中, 所述组播节目 存储地址存储的组播节目是由所述终端类型支持的升级版本文件封装成的组 播节目;
所述终端接收所述 EMS下发的升级启动指令;
所述终端响应所述升级启动指令,根据所述版本地址映射关系中的组播节 目存储地址向组播服务器发送组播节目点播请求;
所述终端接收所述组播服务器发送的所述组播节目存储地址存储的组播 节目;
所述终端依据接收到的所述组播节目执行版本升级操作。
在本发明实施例第二方面的第一种可能的实现方式中,所述终端依据接收 到的所述组播节目执行版本升级操作包括:
所述终端从接收到的所述组播节目中提取各个升级版本子文件,所述升级 版本子文件包括控制头, 所述控制头包括所述终端升级所需的信息;
级版本子文件进行组合, 获得所述终端类型支持的升级版本文件; 在本发明实施例第二方面的第二种可能的实现方式中,所述终端接收网元 管理系统 EMS下发的版本地址映射关系系包括:
终端接收 EMS下发的目标 XML配置文件, 其中, 所述目标 XML配置文 件加载有版本地址映射关系。
结合本发明实施例第二方面的第二种可能的实现方式,在本发明实施例第 二方面的第三种可能的实现方式中, 所述终端接收 EMS发的目标 XML配置 文件之后, 以及所述终端接收所述 EMS下发的升级启动指令之前, 所述方法 还包括:
所述终端接收所述 EMS下发的升级测试指令, 所述升级测试指令包括升 级校验参数,所述升级校验参数至少包括所述终端类型支持的当前版本号以及 升级版本号;
所述终端对所述升级校验参数进行校验,获得所述终端针对所述升级校验 参数的校验结果;
所述终端将所述校验结果上报给所述 EMS, 以使触发所述 EMS判断出所 述校验结果为校验通过时, 下发升级启动指令给所述终端。
本发明实施例第三方面公开了一种网元管理系统, 包括:
封装单元,用于将终端类型支持的升级版本文件封装成组播节目并存储至 组播服务器; 或者, 将终端类型支持的升级版本文件发送至组播服务器, 以使 所述组播服务器将所述升级版本文件封装成组播节目;
建立单元, 用于建立版本地址映射关系, 所述版本地址映射关系包括升级 版本号与组播节目存储地址的映射关系;
第一通讯单元, 用于将所述版本地址映射关系下发至所述终端, 并启动第 二通讯单元;
所述第二通讯单元,用于将升级启动指令下发至所述终端, 以触发所述终 端根据所述版本地址映射关系中的组播节目存储地址向所述组播服务器发送 组播节目点播请求,以及由所述终端接收所述组播服务器发送的所述终端的组 播节目存储地址存储的组播节目,并由所述终端依据接收到的所述组播节目执 行版本升级操作。
在本发明实施例第三方面的第一种可能的实现方式中,所述将终端类型支 持的升级版本文件封装成组播节目的方式具体为:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息; 结合本发明实施例第三方面或本发明实施例第三方面的第一种可能的实 现方式,在本发明实施例第三方面的第二种可能的实现方式中, 第一通讯单元 包括:
加载子单元, 用于将所述版本地址映射关系加载至 XML配置文件, 获得 目标 XML配置文件;
通讯子单元, 用于将所述目标 XML配置文件下发至所述终端, 并启动第 二通讯单元。
结合本发明实施例第三方面的第二种可能的实现方式,在本发明实施例第 三方面的第三种可能的实现方式中, 所述通讯子单元还用于在将所述目标 XML配置文件下发至所述终端之后, 将升级测试指令下发至所述终端, 所述 升级测试指令包括升级校验参数,所述升级校验参数至少包括所述终端类型支 持的当前版本号以及升级版本号;
所述通讯子单元还用于接收所述终端上报的所述终端针对所述升级校验 参数的校验结果;
所述网元管理系统还包括第一判断单元,用于判断所述校验结果是否为校 验通过, 若校验通过,触发所述第二通讯单元执行所述的将升级启动指令下发 至所述终端执行的操作。
本发明实施例第四方面公开了一种终端, 包括:
第一交互单元, 用于接收网元管理系统 EMS下发的版本地址映射关系, 所述版本地址映射关系包括升级版本号与组播节目存储地址的映射关系; 其 中,所述组播节目存储地址存储的组播节目是由所述终端类型支持的升级版本 文件封装成的组播节目;
第二交互单元, 用于接收所述 EMS下发的升级启动指令;
节目点播单元, 用于响应所述升级启动指令,根据所述版本地址映射关系 中的组播节目存储地址向组播服务器发送组播节目点播请求;
所述节目点播单元,还用于接收所述组播服务器发送的所述组播节目存储 地址存储的组播节目; 升级操作单元, 用于依据接收到的所述组播节目执行版本升级操作。 在本发明实施例第四方面的第一种可能的实现方式中,所述升级操作单元 包括:
第一提取子单元, 用于从接收到的组播节目中提取各个升级版本子文件, 升级版本子文件包括控制头, 控制头包括终端升级所需的信息;
文件组合子单元, 用于根据各个升级版本子文件包括的控制头,将各个升 级版本子文件进行组合, 获得终端类型支持的升级版本文件;
版本升级子单元, 用于依据升级版本文件执行版本升级操作。
在本发明实施例第四方面的第二种可能的实现方式中,所述第一交互单元 用于接收 EMS发的目标 XML配置文件, 其中, 所述目标 XML配置文件加载 有所述终端类型支持的升级目标版本号与组播节目存储地址的版本地址映射 关系。
结合本发明实施例第四方面的第二种可能的实现方式,在本发明实施例第 四方面的第三种可能的实现方式中, 所述第一交互单元还用于在接收 EMS下 发的目标 XML配置文件之后, 接收所述 EMS下发的升级测试指令, 所述升 级测试指令包括升级校验参数,所述升级校验参数至少包括所述终端类型支持 的当前版本号以及升级版本号;
所述终端还包括参数校验单元, 用于对所述升级校验参数进行校验, 获得 所述终端针对所述升级校验参数的校验结果;
所述第一交互单元还用于将所述校验结果上报给所述 EMS, 以使触发所 述 EMS判断出所述校验结果为校验通过时, 下发升级启动指令给所述终端。
本发明实施例第五方面公开了一种网元管理系统, 包括接收器、 处理器、 存储器以及发射器, 所述接收器、 处理器、 存储器以及发射器分别连接总线, 其中, 所述存储器中存储一组终端升级程序代码,且所述处理器用于调用所述 存储器中存储的终端升级程序代码, 用于执行以下操作:
通过所述接收器接收终端类型支持的升级版本文件;
将所述终端类型支持的升级版本文件封装成组播节目并通过所述发射器 传输至组播服务器存储, 或者,通过所述发射器将终端类型支持的升级版本文 件发送至组播服务器,以使所述组播服务器将所述升级版本文件封装成组播节 η ·,
建立版本地址映射关系,所述版本地址映射关系包括升级版本号与组播节 目存储地址的映射关系;
通过所述发射器将所述版本地址映射关系下发至所述终端;
通过所述发射器将升级启动指令下发至所述终端,以触发所述终端根据所 述版本地址映射关系中的组播节目存储地址向所述组播服务器发送组播节目 点播请求,以及由所述终端接收所述组播服务器发送的所述终端的组播节目存 储地址存储的组播节目,并由所述终端依据接收到的所述组播节目执行版本升 级操作。
在本发明实施例第五方面的第一种可能的实现方式中,所述将终端类型支 持的升级版本文件封装成组播节目的方式具体为:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息; 结合本发明实施例第五方面或本发明实施例第五方面的第一种可能的实 施方式,在本发明实施例第五方面的第二种可能的实施方式中, 所述处理器通 过所述发射器将所述版本地址映射关系下发至所述终端的方式具体为:
所述处理器将所述版本地址映射关系加载至 XML 配置文件, 获得目标 XML配置文件;
以及, 所述处理器通过所述发射器将所述目标 XML配置文件下发至所述 终端。
结合本发明实施例第五方面的第二种可能的实施方式,在本发明实施例第 五方面的第三种可能的实施方式中, 所述处理器通过所述发射器将所述目标 XML配置文件下发至所述终端之后, 以及所述处理器通过所述发射器将升级 启动指令下发至所述终端之前, 所述处理器还执行以下操作:
所述处理器通过所述发射器将升级测试指令下发至所述终端,所述升级测 试指令包括升级校验参数,所述升级校验参数至少包括所述终端的类型支持的 当前版本号以及升级版本号;
所述处理器通过所述接收器接收所述终端上报的所述终端针对所述升级 校验参数的校验结果;
所述处理器判断所述校验结果是否为校验通过,若校验通过,执行所述的 通过所述发射器将升级启动指令下发至所述终端的操作。
本发明实施例第六方面公开了一种终端, 包括接收器、 处理器、 存储器以 及发射器, 所述接收器、 处理器、 存储器以及发射器分别连接总线, 其中, 所 述存储器中存储一组终端升级程序代码,且所述处理器用于调用所述存储器中 存储的终端升级程序代码, 用于执行以下操作:
通过所述接收器接收网元管理系统 EMS下发的版本地址映射关系, 所述 版本地址映射关系包括升级版本号与组播节目存储地址的映射关系; 其中, 所 述组播节目存储地址存储的组播节目是由所述终端类型支持的升级版本文件 封装成的组播节目;
通过所述接收器接收所述 EMS下发的升级启动指令;
响应所述升级启动指令,根据所述版本地址映射关系中的组播节目存储地 址通过所述发射器向组播服务器发送组播节目点播请求;
通过所述接收器接收所述组播服务器发送的所述组播节目存储地址存储 的组播节目;
依据接收到的所述组播节目执行版本升级操作。
在本发明实施例第六方面的第一种可能的实现方式中,所述处理器依据接 收到的所述组播节目执行版本升级操作的方式具体为:
从接收到的所述组播节目中提取各个升级版本子文件,所述升级版本子文 件包括控制头, 所述控制头包括所述终端升级所需的信息;
根据所述各个升级版本子文件包括的所述控制头,将所述各个升级版本子 文件进行组合, 获得所述终端类型支持的升级版本文件;
依据所述升级版本文件执行版本升级操作。
在本发明实施例第六方面的第二种可能的实现方式中,所述处理器通过所 述接收器接收 EMS下发的版本地址映射关系系的方式具体为:
所述处理器通过所述接收器接收 EMS下发的目标 XML配置文件, 其中, 所述目标 XML配置文件加载有版本地址映射关系。
结合本发明实施例第六方面的第二种可能的实施方式,在本发明实施例第 六方面的第三种可能的实施方式中, 所述处理器通过所述接收器接收 EMS下 发的目标 XML配置文件之后,以及所述处理器通过所述接收器接收所述 EMS 下发的升级启动指令之前, 所述处理器还执行以下操作:
所述处理器通过所述接收器接收所述 EMS下发的升级测试指令, 所述升 级测试指令包括升级校验参数,所述升级校验参数至少包括所述终端的类型支 持的当前版本号以及升级版本号;
所述处理器对所述升级校验参数进行校验,获得所述终端针对所述升级校 验参数的校验结果;
所述处理器通过所述发射器将所述校验结果上报给所述 EMS, 以使触发 所述 EMS判断出所述校验结果为校验通过时,下发升级启动指令给所述终端。
与现有技术相比, 本发明实施例具有以下有益效果:
本发明实施例中,可以将终端(如 ONT )进行升级操作的控制主体由 OLT 下降至终端,即终端可以根据版本地址映射关系中的组播节目存储地址向组播 服务器发送组播节目点播请求,以及接收组播服务器发送的该组播节目存储地 址存储的组播节目, 并依据接收到的该组播节目执行版本升级操作,从而可以 省去由 OLT对终端 (如 ONT )进行升级操作控制, 使得在对终端进行版本升 级过程中 OLT只作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另外, 本发明实施例中由终端进行组播节目点播来实现版本升级, 可以实现海 量终端的并行的版本升级操作, 从而可以提升终端的升级效率。 附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例中所需要 使用的附图作简单地介绍,显而易见地, 下面描述中的附图仅仅是本发明的一 些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还 可以根据这些附图获得其他的附图。
图 1是本发明实施例公开的一种终端升级系统的结构示意图;
图 2为本发明实施例公开的一种 EMS的结构示意图;
图 3 为本发明实施例公开的另一种 EMS的结构示意图;
图 4 为本发明实施例公开的又一种 EMS的结构示意图; 图 5为本发明实施例公开的又一种 EMS的结构示意图;
图 6 为本发明实施例公开的一种终端的结构示意图;
图 7 为本发明实施例公开的另一种终端的结构示意图;
图 8 为本发明实施例公开的又一种终端的结构示意图;
图 9 为本发明实施例公开的一种终端升级方法的流程示意图;
图 10 为本发明实施例公开的另一种终端升级方法的流程示意图; 图 11 为本发明实施例公开的又一种终端升级方法的流程示意图。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅是本发明一部分实施例, 而不是全 部的实施例。基于本发明中的实施例, 本领域普通技术人员在没有作出创造性 劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例公开了一种终端升级方法及相关设备、 系统, 能够有效降低 OLT 的工作负荷以及提升终端的升级效率。 本发明实施例中, 终端既可以是 ONT (包括有源或无源网络单元), 也可以是数字用户线路(DSL )终端, 本 发明实施例不作限定。 当终端为 DSL终端时, DSL终端可以通过铜线连接 OLT。 以下分别进行详细说明。
请参阅图 1, 图 1是本发明实施例公开的一种光网络终端升级系统的结构 示意图。 其中, 图 1所示的光网络终端升级系统可以包括:
EMS10、 组播服务器 11、 OLT12以及 OLT12所辖的终端 13, 其中, 终端 13通常安装在用户侧, 终端 13下面可以接入用户终端, 例如电话、 电脑、 交 互式网络电视(IPTV )等。 需要说明的是, 在图 1 所示的终端升级系统中, OLT12所辖的终端 13数量可以是一个或者多个, 当 OLT12所辖的终端 13数 量为多个时, 多个终端 13的类型可以相同, 也可以不相同, 多个终端 13也可 以是不同厂商的终端, 本发明实施例不作限定。
在图 1所示的终端升级系统中, EMS 10可以通过有线网络(如光纤网络) 或无线网络(如无线局域网 )与组播服务器 11相连; EMS10和 OLT12之间 可以釆用简单网络管理协议( Simple Network Management Protocol, SNMP ) 进行通信; 组播服务器 11可以通过有线网络(如光纤网络)或无线网络(如 无线局域网)与 OLT12相连; 可选地, 组播服务器 11还可以通过专用组播通 道(釆用私有协议)与终端 13相连; OLT12和终端 13之间可以釆用光纤或铜
FTP协议或 TR069协议进行通信。
在图 1所示的终端升级系统中:
EMS10将终端 13类型支持的升级版本文件封装成组播节目并存储至组播 服务器 11; 或者, EMS将终端 13类型支持的升级版本文件发送至组播服务器 11, 以使组播服务器 11将升级版本文件封装成组播节目并存储;
以及, EMS10建立版本地址映射关系, 该建立版本地址映射关系包括升 级版本号与组播节目存储地址的映射关系; 其中,升级本版号是指升级版本文 件的版本号,该组播节目存储地址是指升级版本文件封装成的组播节目在组播 服务器 11中的存储地址; 可选地, 该组播节目存储地址可以由组播服务器 11 返回给 EMS10, 或者, 该组播节目存储地址也可以由 EMS10指定;
以及, EMS10用于将版本地址映射关系由经 OLT12下发至终端 13; 以及 将升级启动指令由经 OLT12下发至终端 13;
相应地, 终端 13接收 EMS10由 OLT12下发的版本地址映射关系, 以及 接收 EMS10由经 OLT12下发的升级启动指令, 并响应该升级启动指令, 并根 据版本地址映射关系中的组播节目存储地址向组播服务器 11发送组播节目点 播请求; 可选地, 终端 13可以由经 OLT12向组播服务器 11发送组播节目点 播请求, 或者, 终端 13也可以通过与组播服务器 11之间的专用组播通道向组 播服务器 11发送组播节目点播请求, 本发明实施例不作限定;
相应地,组播服务器 11向终端 13发送的组播节目存储地址存储的组播节 目; 可选地, 组播服务器 11可以由经 OLT12向终端 13发送组播节目存储地 址存储的组播节目, 或者, 组播服务器 11也可以通过与终端 13之间的专用组 播通道向终端 13发送组播节目存储地址存储的组播节目, 本发明实施例不作 限定;
相应地,终端 13还接收组播服务器 11发送的组播节目存储地址存储的组 播节目, 并依据该组播节目执行版本升级操作。
作为一种可选的实施方式, EMS10或组播服务器 11将终端 13类型支持 的升级版本文件封装成组播节目的方式可以为:
将终端 13类型支持的升级版本文件划分为至少一个升级版本子文件; 其 中, EMS10将终端 13类型支持的升级版本文件划分为至少一个升级版本子文 以及, 为升级版本子文件分配控制头, 控制头包括终端升级所需的信息; 需要说明的是,上述的控制头中包括的终端升级所需的信息可以包括软件 升级包有效标志位、 包头 CRC、 升级包内文件数目、 升级版本号、 组播服务 器 IP、 组播服务器端口号, 以及升级控制的描述信息等。
相应地, 本发明实施例中, 终端 13依据该组播节目执行版本升级操作的 方式可以为:
终端 13从接收到的组播节目中提取各个升级版本子文件, 升级版本子文 件包括控制头, 控制头包括终端升级所需的信息;
终端 13根据各个升级版本子文件包括的控制头, 将各个升级版本子文件 进行组合, 获得终端类型支持的升级版本文件;
以及, 终端 13依据该升级版本文件执行版本升级操作。
作为一种可选的实施方式, EMS 10将版本地址映射关系由经 OLT12下发 至终端 13的方式具体可以为:
EMS 10用于将版本地址映射关系加载至 XML配置文件, 获得目标 XML 配置文件;
以及, EMS10还用于将该目标 XML配置文件由经 OLT12下发至终端 13。 相应地, 终端 13接收 EMS10由 OLT12下发的版本地址映射关系的方式 可以为: 终端 13用于接收 EMS10由 OLT12下发的加载有版本地址映射关系的 目标 XML配置文件, 从而实现接收 EMS 10由 OLT12下发的终端 13类型 支持的升级版本号与组播节目存储地址的对应关系的目的。
举例来说, 当 OLT12所辖的终端 13为 n ( n为大于 1的自然数)个时, EMS10可以将包括终端 13类型支持的升级版本号与组播节目存储地址的映射 关系的版本地址映射关系加载 XML配置文件, 获得目标 XML配置文件, 也 即是说, 目标 XML配置文件中可以加载有 n个版本地址映射关系; 更进一步 地, EMS10可以将目标 XML配置文件由经 OLT12下发至 n个终端 13。 本发 明实施例中, 为了尽可能地降低目标 XML配置文件对终端 13的内存占用, 每一个终端 13在接收到 EMS 10由经 OLT12下发的目标 XML配置文件之后, 可以仅保留目标 XML配置文件中加载的包括该终端 13类型支持的升级版本 号与组播节目存储地址的映射关系的版本地址映射关系,而过滤掉其余的版本 地址映射关系。 例如, 第 n个终端 13在接收到 EMS10由经 OLT12下发的目 标 XML配置文件之后,第 n个终端 13可以仅保留目标 XML配置文件中加载 的包括第 n个终端 13类型支持的升级版本号与组播节目存储地址的映射关系 的版本地址映射关系, 而过滤掉其余版本地址映射关系。
作为一种可选的实施方式, 在图 1所示的终端升级系统中, EMS10在将 目标 XML配置文件由经 OLT12下发至终端 13之后, EMS 10可以先测试终端 13是否支持版本升级操作, 当测试终端 13支持版本升级操作时, EMS10才启 动终端 13的版本升级操作。 具体方式为:
EMS 10还在将目标 XML配置文件由经 OLT12下发至终端 13之后,将升 级测试指令由经 OLT12下发至终端 13, 该升级测试指令包括升级校验参数, 该升级校验参数至少包括该终端 13类型支持的当前版本号以及升级版本号; 更进一步地, 该升级校验参数还可以包括该终端 13类型支持的制造商信息等 信息;
相应地, 终端 13还接收 EMS10由经 OLT12下发的升级测试指令, 并对 升级测试指令包括的升级校验参数进行校验, 获得该终端 13针对升级校验参 数的校验结果; 以及将校验结果由经 OLT12上报给 EMS10; 举例来说, 当升 级校验参数包括该终端 13类型支持的当前版本号、 升级版本号以及制造商信 息时, 该终端 13可以校验支持的当前版本的版本号是否与该升级校验参数包 括该终端 13支持的当前版本号相同,以及该终端 13可以校验该升级校验参数 包括的升级版本号是否合法,以及该终端可以校验是否支持该升级校验参数包 括的制造商信息, 并将校验结果由经 OLT12上报给 EMS10;
相应地, EMS10还用于接收终端 13由经 OLT12上报的该终端 13针对升 级校验参数的校验结果; 以及判断该校验结果是否为校验通过, 若校验通过, 则表示该终端 13 支持版本升级操作, EMS10 可以执行将升级启动指令由经 OLT12下发至该终端 13的操作; 举例来说, 当该终端 13校验支持的当前版本 的版本号与该升级校验参数包括该终端 13支持的当前版本号相同, 以及该终 端 13校验该升级校验参数包括的升级版本号合法,以及该终端 13校验支持该 升级校验参数包括的制造商信息时, 该终端 13可以将用于表示校验通过的校 验结果由经 OLT12上报给 EMS10, 以使得 EMS 10判断该校验结果为校验通 过时,表示终端 13支持版本升级操作, EMS 10执行将升级启动指令由经 OLT12 下发至该终端 13的操作。
作为另一种可选的实施方式, 在图 1所示的终端升级系统中, EMS10在 判断出终端 13针对升级校验参数的校验结果为校验通过之后, EMS10可以先 判断是否满足 EMS升级策略,当满足 EMS升级策略时才执行将升级启动指令 由经 OLT12下发至终端 13的操作, 否则, EMS10可以暂緩执行将升级启动 指令由经 OLT12下发至终端 13的操作。 需要说明的是, 该 EMS升级策略可 以是预设在终端中的升级策略; 也可以是由 EMS下发的升级策略。 本发明不 做具体限定。
EMS 10还用于在判断出终端 13针对升级校验参数的校验结果为校验通过 之后, 判断是否满足预设的 EMS升级策略, 如果满足预设的 EMS升级策略, 执行将升级启动指令由经 OLT12下发至终端 13的操作;
其中, EMS升级策略可以包括以下任意一种或几种策略组合:
1、 到达指定的升级时间; 2、 终端 13为指定类型的终端;
3、 终端 13支持的升级目标版本为指定厂商的升级目标版本。
作为另一种可选的实施方式,在图 1所示的终端升级系统中, 上述的目标 XML配置文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是 否一致。 相应地, 上述的 EMS10将目标 XML配置文件由经 OLT12下发至终 端 13的方式具体可以为:
终端 13用于将远端 XML配置文件添加的 CRC校验值由经 OLT12上报给 EMS 10; 其中, 该远端 XML配置文件用于加载远端映射关系, 该远端映射关 系为终端 13类型支持的当前版本号与当前版本封装成的组播节目的存储地址 的映射关系;
相应地, EMS 10用于接收终端 13由经 OLT12上报的远端 XML配置文件 添加的 CRC校验值; 以及将远端 XML配置文件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值进行比较, 若比较不一致, 由经 OLT12下 发包括目标 XML配置文件的协议消息给终端 13。
本发明实施例中,终端 13可以在上电时将远端 XML配置文件添加的 CRC 校验值由经 OLT12上报给 EMS10,当 EMS10比较远端 XML配置文件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致时, EMS 10可以 获悉终端 13支持的当前版本封装成的组播节目与终端 13支持的升级目标版本 封装成的组播节目不同, 此时, EMS10可以将目标 XML配置文件(该目标 XML配置文件加载有终端 13支持的升级版本号与组播节目存储地址的版本地 址映射关系)由经 OLT12下发至终端 13, 以便后续启动终端 13的版本升级操 作。
作为另一种可选的实施方式, 在图 1所示的终端升级系统中, 终端 13还 用于在接收 EMS10由经 OLT12下发的升级启动指令之后,先判断是否满足预 设的终端升级策略,如果满足预设的终端升级策略, 才执行的响应升级启动指 令, 根据版本地址映射关系中的组播节目存储地址向组播服务器 11发送组播 节目点播请求的操作; 其中, 终端升级策略可以包括终端当前不存在点播业务、语音业务或终端 当前负荷小于预设负荷值中的任意一种或几种的组合。
其中, 点播业务可以包括高清视频点播业务, 终端当前负荷是指终端的处 理器当前负荷。
在一个实施例中,终端升级策略还可以包括终端确定组播节目存储地址中 存储有组播节目。具体地, 终端可以根据组播节目存储地址向组播服务器发送 组播节目查询请求, 以及接收组播服务器发送查询响应, 并根据该查询响应确 定组播节目存储地址中是否存储有组播节目。
本发明实施例中, 当终端 13在判断出满足预设的终端升级策略时, 才执 行响应升级启动指令,根据版本地址映射关系中的组播节目存储地址向组播服 务器 11发送组播节目点播请求的操作,可以实现终端 13版本升级操作的自适 应控制, 可以有效地防止版本升级对用户所使用的业务造成影响(如造成高清 视频点播业务播放不流畅), 和 /或, 可以有效地防止版本升级加剧终端当前负 荷, 防止终端崩溃。 由于终端可以通过组播服务器获取终端升级所需的版本升 级文件,终端从 OLT获取升级版本文件改成从组播服务器获取升级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力 的限制。
作为另一种可选的实施方式, 在图 1所示的终端升级系统中, 终端 13依 据该升级版本文件执行版本升级操作的方式具体可以为:
终端 13用于依据该升级版本文件,并釆用状态机方式对终端 13执行版本 升级操作。其中, 釆用状态机方式对终端执行版本升级操作可以确保版本的完 整升级, 而且还可以避免造成同一升级版本的反复升级。
在图 1所示的终端升级系统中, 可以将终端 (如 ONT )进行升级操作的 控制主体由 OLT下降至终端 (如 ONT ), 即终端 (如 ONT )可以根据版本地 址映射关系中的组播节目存储地址向组播服务器发送组播节目点播请求,以及 接收组播服务器发送的该组播节目存储地址存储的组播节目,并依据该组播节 目执行版本升级操作, 从而可以省去由 OLT对终端 (如 ONT )进行升级操作 控制, 使得在对终端 (如 ONT )进行版本升级过程中 OLT只作为传输通道使 用, 从而可以有效地降低 OLT的工作负荷; 另外, 在图 1所示的终端升级系 统中, 由终端 (如 ONT )进行组播节目点播来实现版本升级, 可以实现海量 终端 (如 ONT ) 的并行的版本升级操作, 从而可以提升终端 (如 ONT ) 的升 级效率。
前面已对本发明实施例公开的一种终端升级系统进行了介绍,下面进一步 对本发明实施例公开的终端升级系统中的 EMS进行介绍。
请参阅图 2, 图 2为本发明实施例公开的一种 EMS的结构示意图。 其中, 图 2所示的 EMS可以包括:
封装元 21, 用于将 OLT所辖的终端(如 ONT )类型支持的升级版本文件 封装成组播节目并存储至组播服务器; 或者,将终端类型支持的升级版本文件 发送至组播服务器,以使组播服务器将所述升级版本文件封装成组播节目并存 储;
建立单元 22, 用于建立版本地址映射关系, 该版本地址映射关系包括升 级版本号与组播节目存储地址的映射关系; 可选地,该组播节目存储地址可以 由组播服务器返回给封装单元 21, 或者, 该组播节目存储地址也可以由封装 单元 21指定;
第一通讯单元 23, 用于将版本地址映射关系由经 OLT下发至该终端, 并 启动第二通讯单元 24;
第二通讯单元 24, 用于将升级启动指令由经 OLT下发至该终端, 以触发 该终端根据版本地址映射关系中的组播节目存储地址向组播服务器发送组播 节目点播请求,以及由该终端接收组播服务器发送的该组播节目存储地址存储 的组播节目, 并由该终端依据接收到的该组播节目执行版本升级操作。
请一并参阅图 3, 图 3为本发明实施例公开的另一种 EMS的结构示意图。 其中, 图 3所示的 EMS是由图 2所示的 EMS进行优化得到的。
在图 3所示的 EMS中, 封装单元 21可以包括:
文件划分子单元 211, 用于将终端类型支持的升级目标版本文件划分为至 少一个升级目标版本子文件; 控制头分配子单元 212, 用于为升级版本子文件分配控制头, 控制头包括 终端升级所需的信息; 节目并存储至组播服务器。
可选地, 该组播节目存储地址可以由组播服务器返回给封装单元 21的报 文组合子单元 213, 或者, 该组播节目存储地址也可以由封装单元 21 的报文 组合子单元 213指定。
在图 3所示的 EMS中, 第一通讯单元 23可以包括:
加载子单元 231, 用于将版本地址映射关系加载至 XML配置文件, 获得 目标 XML配置文件;
通讯子单元 232, 用于将目标 XML配置文件由经 OLT下发至该终端, 并 启动第二通讯单元 24。
作为一种可选的实施方式, 在图 3所示的 EMS中, 通讯子单元 232还用 于在将目标 XML配置文件由经 OLT下发至该终端之后,将升级测试指令由经 OLT下发至该终端, 其中, 该升级测试指令可以包括升级校验参数, 该升级校 验参数至少可以包括该终端类型支持的当前版本号以及升级版本号;更进一步 地, 该升级校验参数还可以包括该终端支持的制造商信息;
相应地, 通讯子单元 232还用于接收该终端由经 OLT上报的该终端针对 升级校验参数的校验结果; 举例来说, 当升级校验参数包括该终端类型支持的 当前版本号、升级版本号以及制造商信息时,该终端可以校验支持的当前版本 的版本号是否与该升级校验参数包括该终端支持的当前版本号相同,以及该终 端可以校验该升级校验参数包括的升级版本号是否合法,以及该终端可以校验 是否支持该升级校验参数包括的制造商信息,并将校验结果由经 OLT1上报给 EMS;
相应地, 图 3所示的 EMS还可以包括第一判断单元 25, 用于判断该校验 结果是否为校验通过, 若校验通过, 触发第二通讯单元 24执行的将升级启动 指令由经 OLT下发至该终端的操作。 举例来说, 当该终端校验支持的当前版 本的版本号与该升级校验参数包括该终端支持的当前版本号相同,以及该终端 校验该升级校验参数包括的升级版本号合法,以及该终端校验支持该升级校验 参数包括的制造商信息时, 该终端可以将用于表示校验通过的校验结果由经 OLT上报给 EMS, 以使得 EMS的第一判断单元 25判断该校验结果为校验通 过时, 表示该终端支持目标版本升级, 第一判断单元 25可以触发第二通讯单 元 24执行的将升级启动指令由经 OLT下发至该终端的操作。
请一并参阅图 4, 图 4为本发明实施例公开的另一种 EMS的结构示意图。 其中, 图 4所示的 EMS是由图 3所示的 EMS进行优化得到的。在图 4所示的 EMS中, 还包括:
第二判断单元 26, 用于在第一判断单元 25判断该校验结果为校验通过之 后, 判断是否满足 EMS升级策略, 如果满足 EMS升级策略, 触发第二通讯单 元 24执行的将升级启动指令由经 OLT下发至该终端的操作;
其中, EMS升级策略可以包括以下任意一种或几种策略组合:
1、 到达指定的升级时间;
2、 终端为指定类型的终端;
3、 终端支持的升级目标版本为指定厂商的升级目标版本。
作为一种可选的实施方式,在图 3~图 4所示的 EMS中,上述的目标 XML 配置文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相应地,上述的通讯子单元 232将目标 XML配置文件由经 OLT下发至该终端 的方式具体可以为:
通讯子单元 232用于接收该终端由经 OLT上报的远端 XML配置文件添加 的 CRC校验值; 其中, 该远端 XML配置文件用于加载远端映射关系, 该远 端映射关系为该终端类型支持的当前版本号与当前版本封装成的组播节目的 存储地址的映射关系;
以及, 通讯子单元 232用于将该远端 XML配置文件添加的 CRC校验值 与目标 XML配置文件添加的 CRC校验值进行比较;
以及,通讯子单元 232用于在比较模块的比较结果为不一致时, 由经 OLT 下发包括目标 XML配置文件的协议消息给该终端。
本发明实施例中, 该终端可以在上电时将该远端 XML 配置文件添加的 CRC校验值由经 OLT上报给 EMS, 当通讯子单元 232比较该远端 XML配置 文件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致时, 通讯子单元 232 可以获悉该终端支持的当前版本封装成的组播节目与该终端 支持的升级目标版本封装成的组播节目不同, 此时,通讯子单元 232可以将目 标 XML配置文件由经 OLT下发至该终端,以便后续启动该终端的版本升级操 作。
本发明实施例中, 上述的协议消息包括但不限于 OMCI/OAM协议消息、 FTP协议消息或 TR069协议消息。
其中, 通过实施图 2~图 4所示的 EMS, 可以将终端(如 ONT )进行升级 操作的控制主体由 OLT下降至终端, 从而可以省去由 OLT对终端进行升级操 作控制, 使得在对终端进行版本升级过程中 OLT只作为传输通道使用, 从而 可以有效地降低 OLT的工作负荷; 另夕卜, 通过实施图 2~图 4所示的 EMS, 由 终端进行组播节目点播来实现版本升级,可以实现海量终端的并行的版本升级 操作,从而可以提升终端的升级效率。 由于终端可以通过组播服务器获取终端 升级所需的版本升级文件, 终端从 OLT获取升级版本文件改成从组播服务器 获取升级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力的限制。 请参阅图 5, 图 5为本发明实施例公开的另一种 EMS的结构示意图。 其 中, 图 5所示的网元管理系统 EMS可以包括接收器 50、 处理器 51、 存储器 52 以及发射器 53, 其中, 接收器 50、 处理器 51、 存储器 52 以及发射器 53 分别连接总线 54连接, 其中, 存储器 52中存储一组终端升级程序代码, 且处 理器 51用于调用存储器 52中存储的终端升级程序代码, 用于执行以下操作: 通过接收器 50接收终端类型支持的升级版本文件;
将 OLT所辖的终端类型支持的升级版本文件封装成组播节目并通过发射 器 53传输至组播服务器存储; 或者,通过发射器 53将终端类型支持的升级版 本文件发送至组播服务器,以使组播服务器将升级版本文件封装成组播节目并 存储;
建立版本地址映射关系,版本地址映射关系包括升级版本号与组播节目存 储地址的映射关系; 可选地, 该组播节目存储地址可以由组播服务器通过接收 器 50返回给处理器 51, 或者, 该组播节目存储地址也可以由处理器 51指定; 通过发射器 53将该版本地址映射关系由经 OLT下发至该终端;
通过发射器 53将升级启动指令由经 OLT下发至该终端, 以触发该终端根 据版本地址映射关系中的组播节目存储地址向组播服务器发送组播节目点播 请求,以及由该终端接收组播服务器发送的该组播节目存储地址存储的组播节 目, 并由该终端依据接收到的该组播节目执行版本升级操作。
作为一种可选的实施方式,在图 5所示的 EMS中,处理器 51将终端类型 支持的升级版本文件封装成组播节目的方式具体为:
将终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为升级版本子文件分配控制头, 控制头包括终端升级所需的信息; 作为一种可选的实施方式,在图 5所示的 EMS中,处理器 51通过发射器 53将版本地址映射关系下发至终端的方式具体可以为:
处理器 51将版本地址映射关系加载至 XML配置文件,获得目标 XML配 置文件;
以及,处理器 51通过发射器 53将目标 XML配置文件由经 OLT下发至该 终端。
作为一种可选的实施方式,在图 5所示的 EMS中,处理器 51通过发射器 53将目标 XML配置文件由经 OLT下发至该终端之后, 以及处理器 51通过发 射器 53将升级启动指令由经 OLT下发至该终端之前, 处理器 51还执行以下 操作:
处理器 51通过发射器 53将升级测试指令由经 OLT下发至该终端, 该升 级测试指令包括升级校验参数,该升级校验参数至少包括该终端类型支持的当 前版本号以及升级版本号; 更进一步地, 该升级校验参数还可以包括该终端支 持的制造商信息;
处理器 51通过接收器 50接收该终端由经 OLT上报的该终端针对升级校 验参数的校验结果; 举例来说, 当升级校验参数包括该终端类型支持的当前版 本号、升级目标版本号以及制造商信息时, 该终端可以校验支持的当前版本的 版本号是否与该升级校验参数包括该终端支持的当前版本号相同, 以及该 ONT可以校验该升级校验参数包括的升级版本号是否合法, 以及该终端可以 校验是否支持该升级校验参数包括的制造商信息,并将校验结果由经 OLT1上 报给 EMS;
处理器 51判断该校验结果是否为校验通过, 若校验通过, 执行通过发射 器 53将升级启动指令由经 OLT下发至该终端的操作。 举例来说, 当该终端校 验类型支持的当前版本的版本号与该升级校验参数包括的该终端类型支持的 当前版本号相同, 以及该终端校验该升级校验参数包括的升级版本号合法, 以 及该终端校验支持该升级校验参数包括的制造商信息时,该终端可以将用于表 示校验通过的校验结果由经 OLT上报给 EMS, 以使得 EMS的处理器 51判断 该校验结果为校验通过时, 表示该终端支持版本升级, 处理器 51可以执行的 将升级启动指令由经 OLT下发至该终端的操作。
作为一种可选的实施方式,在图 5所示的 EMS中,处理器 51判断校验结 果为校验通过之后, 以及处理器 51通过发射器 53将升级启动指令由经 OLT 下发至该终端之前, 处理器 51还执行以下操作:
处理器 51判断是否满足 EMS升级策略, 如果满足 EMS升级策略, 执行 通过发射器 53将升级启动指令由经 OLT下发至该终端的操作;
其中, EMS升级策略可以包括以下任意一种或几种策略组合:
1、 到达指定的升级时间;
2、 终端为指定类型的终端;
3、 终端支持的升级目标版本为指定厂商的升级目标版本。
作为一种可选的实施方式, 在图 5所示的 EMS中, 上述的目标 XML配 置文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相应地,处理器 51通过发射器 53将目标 XML配置文件由经 OLT下发至该终 端的方式具体可以为:
处理器 51通过接收器 50接收该终端由经 OLT上报的远端 XML配置文件 添加的 CRC校验值; 其中, 该远端 XML配置文件用于加载远端映射关系, 该远端映射关系为该终端类型支持的当前版本号与当前版本封装成的组播节 目的存储地址的映射关系; 处理器 51将该远端 XML配置文件添加的 CRC校验值与目标 XML配置 文件添加的 CRC校验值进行比较, 若比较不一致, 通过发射器 53由经 OLT 下发包括目标 XML配置文件的协议消息给该终端。
本发明实施例中, 该终端可以在上电时将该远端 XML 配置文件添加的 CRC校验值由经 OLT上报给 EMS, 当处理器 51比较该远端 XML配置文件 添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致时, 处理 器 51可以获悉该终端支持的当前版本封装成的组播节目与该终端支持的升级 目标版本封装成的组播节目不同, 此时, 处理器 51可以将目标 XML配置文 件由经 OLT下发至该终端, 以便后续启动该终端的版本升级操作。
本发明实施例中, 上述的协议消息包括但不限于 OMCI/OAM协议消息、 FTP协议消息或 TR069协议消息。
其中, 通过实施图 5所示的 EMS, 可以将终端进行升级操作的控制主体 由 OLT下降至终端, 从而可以省去由 OLT对终端进行升级操作控制, 使得在 对终端进行版本升级过程中 OLT只作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另外, 通过实施图 5所示的 EMS, 由终端进行组播节目点 播来实现版本升级, 可以实现海量终端的并行的版本升级操作,从而可以提升 终端的升级效率。由于终端可以通过组播服务器获取终端升级所需的版本升级 文件, 终端从 OLT获取升级版本文件改成从组播服务器获取升级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力 的限制。 下面进一步对本发明实施例公开的光终端升级系统中的终端进行介绍。请 参阅图 6, 图 6为本发明实施例公开的一种终端的结构示意图。 如图 6所示, 该终端可以包括:
第一交互单元 61, 用于接收 EMS下发的版本地址映射关系, 版本地址映 射关系包括升级版本号与组播节目存储地址的映射关系; 其中,组播节目存储 地址存储的组播节目是由终端类型支持的升级版本文件封装成的组播节目;其 中, 升级版本号是指升级版本文件的版本号; 第二交互单元 62, 用于接收 EMS由经 OLT下发的升级启动指令; 节目点播单元 63, 用于响应升级启动指令, 根据版本地址映射关系中的 组播节目存储地址向组播服务器发送组播节目点播请求;
上述的节目点播单元 63, 还用于接收组播服务器发送的该组播节目存储 地址存储的组播节目;
升级操作单元 64, 用于依据接收到的该组播节目执行版本升级操作。 作为一种可选的实施方式, 在图 6所示的终端中, 升级操作单元 64可以 包括:
第一提取子单元 641, 用从接收到的组播节目中提取各个升级版本子文 件, 升级版本子文件包括控制头, 控制头包括终端升级所需的信息;
文件组合子单元 642, 用于根据各个升级版本子文件包括的控制头, 将各 个升级版本子文件进行组合, 获得终端类型支持的升级版本文件;
版本升级子单元 643, 用于依据升级版本文件执行版本升级操作。
作为一种可选的实施方式, 在图 6所示的终端中, 第一交互单元 61可以 用于接收 EMS由经 OLT下发的目标 XML配置文件, 其中, 该目标 XML配 置文件加载有版本地址映射关系, 从而可以实现第一交互单元 61 接收 EMS 由经 OLT下发的该终端类型支持的升级版本号与组播节目存储地址的版本地 址映射关系的目的。
作为一种可选的实施方式, 在图 6所示的终端中, 第一交互单元 61还用 于在接收 EMS由经 OLT下发的目标 XML配置文件之后,接收 EMS由经 OLT 下发的升级测试指令, 该升级测试指令包括升级校验参数, 该升级校验参数至 少包括该终端类型支持的当前版本号以及升级版本号; 更进一步地, 该升级校 验参数还可以包括该终端支持的制造商信息;
相应地, 图 6所示的终端还可以包括参数校验单元 65, 用于对该升级校 验参数进行校验, 获得该终端针对升级校验参数的校验结果; 举例来说, 当升 级校验参数包括该终端类型支持的当前版本号、 升级版本号以及制造商信息 时, 参数校验单元 65可以校验该终端类型支持的当前版本的版本号是否与该 升级校验参数包括的该终端支持的当前版本号相同,以及可以校验该升级校验 参数包括的升级版本号是否合法,以及可以校验该终端是否支持该升级校验参 数包括的制造商信息, 并将校验结果由经 OLT上报给 EMS;
相应地, 第一交互单元 61还用于将校验结果由经 OLT上报给 EMS, 以 使触发 EMS判断出校验结果为校验通过时,由经 OLT下发升级启动指令给该 终端。举例来说, 当该终端校验支持的当前版本的版本号与该升级校验参数包 括的该终端支持的当前版本号相同,以及该终端校验该升级校验参数包括的升 级版本号合法, 以及该终端校验支持该升级校验参数包括的制造商信息时, 第 一交互单元 61可以将用于表示校验通过的校验结果由经 OLT上报给 EMS, 以使得 EMS判断该校验结果为校验通过时, 表示该终端支持目标版本升级, EMS可以执行的将升级启动指令由经 OLT下发至该终端的操作。
作为一种可选的实施方式, 在图 6所示的终端中, 上述的目标 XML配置 文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相 应地, 第一交互单元 61接收 EMS由经 OLT下发的目标 XML配置文件的方 式具体可以为:
第一交互单元 61用于将远端 XML配置文件添加的 CRC校验值由经 OLT 上报给 EMS; 其中, 该远端 XML配置文件用于加载远端映射关系, 该远端映 射关系为该终端类型支持的当前版本号与当前版本封装成的组播节目的存储 地址的映射关系;
第一交互单元 61还用于接收 EMS比较该远端 XML配置文件添加的 CRC 校验值与目标 XML配置文件添加的 CRC校验值不一致之后, 由经 OLT下发 的包括目标 XML配置文件的协议消息。
本发明实施例中, 第一交互单元 61可以在该终端上电时将远端 XML配 置文件添加的 CRC校验值由经 OLT上报给 EMS, 当 EMS比较该远端 XML 配置文件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致 时, EMS 可以获悉该终端支持的当前版本封装成的组播节目与该终端支持的 升级目标版本封装成的组播节目不同,此时, EMS可以将目标 XML配置文件 由经 OLT下发至该终端, 以便后续启动该终端的版本升级操作。
本发明实施例中, 上述的协议消息包括但不限于 OMCI/OAM协议消息、 FTP协议消息或 TR069协议消息。
请一并参阅图 7, 图 7为本发明实施例公开的另一种终端的结构示意图。 其中, 图 7所示的终端是由图 6所示的终端进行优化得到的。 与图 6所示的终 端相比, 图 7所示的终端还可以包括:
判断单元 66, 用于在第二交互单元 62接收 EMS由经所述 OLT下发的升 级启动指令之后,判断是否满足预设的终端升级策略,如果满足预设的终端升 级策略, 触发节目点播单元 64执行的响应升级启动指令, 根据版本地址映射 关系中的组播节目存储地址向组播服务器发送组播节目点播请求的操作;
其中, 终端升级策略可以包括终端当前不存在点播业务、语音业务或终端 当前负荷小于预设负荷值中的任意一种或几种的组合。
其中, 点播业务可以包括高清视频点播业务, 终端当前负荷是指终端的处 理器当前负荷。
本发明实施例中, 当判断单元 66判断出满足预设的终端升级策略时, 才 触发节目点播单元 64执行响应升级启动指令, 根据版本地址映射关系中的组 播节目存储地址向组播服务器发送组播节目点播请求的操作,可以实现终端版 本升级的自适应控制,可以有效地防止版本升级对用户所使用的业务造成影响 (如造成高清视频点播业务播放不流畅), 和 /或, 可以有效地防止版本升级加 剧终端当前负荷, 防止终端崩溃。
作为另一种可选的实施方式, 在图 6所示的终端中, 版本升级子单元 643 依据该升级版本文件执行版本升级操作的方式具体可以为:
版本升级子单元 643用于依据该升级版文件,并釆用状态机方式对该终端 执行版本升级操作。其中, 釆用状态机方式对该终端执行版本升级操作可以确 保版本的完整升级, 而且还可以避免造成同一升级版本的反复升级。
在图 6~图 7所示的终端中, 终端可以作为升级操作的控制主体, 从而可 以省去由 OLT对终端进行升级操作控制, 使得在对终端进行版本升级过程中 OLT只作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另外, 由 终端进行组播节目点播来实现版本升级,可以实现海量终端的并行的版本升级 操作,从而可以提升终端的升级效率。 由于终端可以通过组播服务器获取终端 升级所需的版本升级文件, 终端从 OLT获取升级版本文件改成从组播服务器 获取升级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力的限制。 请参阅图 8,图 8为本发明实施例公开的另一种终端的结构示意图。其中, 图 8所示的终端可以包括接收器 80、 处理器 81、 存储器 82以及发射器 83, 接收器 80、 处理器 81、 存储器 82以及发射器 83分别连接总线 84, 其中, 存 储器 82中存储一组终端升级程序代码, 且处理器 81用于调用存储器 82中存 储的终端升级程序代码, 用于执行以下操作:
通过接收器 80接收 EMS由经 OLT下发的版本地址映射关系, 版本地址 映射关系包括升级版本号与组播节目存储地址的映射关系; 其中,组播节目存 储地址存储的组播节目是由终端类型支持的升级版本文件封装成的组播节目; 通过接收器 80接收 EMS由经 OLT下发的升级启动指令;
响应升级启动指令,根据版本地址映射关系中的组播节目存储地址通过发 射器 83向组播服务器发送组播节目点播请求;
通过接收器 80接收组播服务器发送的该组播节目存储地址存储的组播节
¾ ;
依据接收到的该组播节目执行版本升级操作。
作为一种可选的实施方式, 在图 8所示的终端中, 处理器 81依据接收到 的该组播节目执行版本升级操作的方式具体为:
从接收到的组播节目中提取各个升级版本子文件,升级版本子文件包括控 制头, 控制头包括所述终端升级所需的信息;
根据各个升级版本子文件包括的控制头, 将各个升级版本子文件进行组 合, 获得终端类型支持的升级版本文件;
依据升级版本文件执行版本升级操作。
作为一种可选的实施方式, 在图 8所示的终端中, 处理器 81通过接收器 80接收 EMS下发的版本地址映射关系的方式具体可以为:
处理器 81通过接收器 80接收 EMS由经 OLT下发的目标 XML配置文件, 其中, 该目标 XML配置文件加载有版本地址映射关系, 从而可以实现处理器 81接收 EMS由经 OLT下发的该终端类型支持的升级版本号与组播节目存储 地址的版本地址映射关系的目的。
作为一种可选的实施方式, 在图 8所示的终端中, 处理器 81通过接收器 80接收 EMS由经 OLT下发的目标 XML配置文件之后, 以及处理器 81通过 接收器 80接收 EMS由经 OLT下发的升级启动指令之前,处理器 81还执行以 下操作:
处理器 81通过接收器 80接收 EMS由经 OLT下发的升级测试指令,该升 级测试指令包括升级校验参数,该升级校验参数至少包括该终端类型支持的当 前版本号以及升级版本号; 更进一步地, 该升级校验参数还可以包括该终端支 持的制造商信息;
处理器 81对升级校验参数进行校验, 获得该终端针对所述升级校验参数 的校验结果;
处理器 81通过发射器 83将校验结果由经 OLT上报给 EMS,以使触发 EMS 判断出校验结果为校验通过时, 由经 OLT下发升级启动指令给该终端。
举例来说, 当升级校验参数包括该终端支持的当前版本号、升级版本号以 及制造商信息时, 处理器 81可以校验该终端支持的当前版本的版本号是否与 该升级校验参数包括的该终端支持的当前版本号相同,以及可以校验该升级校 验参数包括的升级版本号是否合法,以及可以校验该终端是否支持该升级校验 参数包括的制造商信息, 并将校验结果由经 OLT上报给 EMS;
当该终端校验支持的当前版本的版本号与该升级校验参数包括的该终端 支持的当前版本号相同,以及该终端校验该升级校验参数包括的升级版本号合 法, 以及该终端校验支持该升级校验参数包括的制造商信息时, 处理器 81可 以将用于表示校验通过的校验结果由经 OLT上报给 EMS, 以使得 EMS判断 该校验结果为校验通过时, 表示该终端支持版本升级, EMS 可以执行的将升 级启动指令由经 OLT下发至该终端的操作。
作为一种可选的实施方式, 在图 8所示的终端中, 上述的目标 XML配置 文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相 应地, 处理器 81通过接收器 80接收 EMS由经 OLT下发的目标 XML配置文 件的方式具体可以为:
处理器 81通过发射器 83将远端 XML配置文件添加的 CRC校验值由经 OLT上报给 EMS; 其中, 该远端 XML配置文件用于远端映射关系, 该远端 映射关系为该终端类型支持的当前版本号与该当前版本封装成的组播节目的 存储地址的映射关系;
处理器 81通过接收器 80接收 EMS比较该远端 XML配置文件添加的 CRC 校验值与目标 XML配置文件添加的 CRC校验值不一致之后, 由经 OLT下发 的包括目标 XML配置文件的协议消息。
本发明实施例中, 处理器 81可以在该终端上电时将该远端 XML配置文 件添加的 CRC校验值由经 OLT上报给 EMS, 当 EMS比较该远端 XML配置 文件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致时, EMS 可以获悉该终端支持的当前版本封装成的组播节目与该终端支持的升级 版本封装成的组播节目不同,此时, EMS可以将目标 XML配置文件由经 OLT 下发至该终端, 以便后续启动该终端的版本升级操作。
本发明实施例中, 上述的协议消息包括但不限于 OMCI/OAM协议消息、 FTP协议消息或 TR069协议消息。
作为一种可选的实施方式, 在图 8所示的终端中, 处理器 81通过接收器 80接收 EMS由经 OLT下发的升级启动指令之后, 以及处理器 81响应升级启 动指令, 根据版本地址映射关系中的组播节目存储地址通过发射器 83向组播 服务器发送组播节目点播请求之前, 处理器 81还执行以下操作:
处理器 81判断是否满足预设的终端升级策略, 如果满足预设的终端升级 策略,执行的响应升级启动指令,根据版本地址映射关系中的组播节目存储地 址通过发射器 83向组播服务器发送组播节目点播请求的操作;
其中, 终端升级策略可以包括终端当前不存在点播业务、语音业务或终端 当前负荷小于预设负荷值中的任意一种或几种的组合。
其中, 点播业务可以包括高清视频点播业务, 终端当前负荷是指终端的处 理器当前负荷。
本发明实施例中, 当处理器 81判断出满足预设的终端升级策略时, 才执 行响应升级启动指令,根据版本地址映射关系中的组播节目存储地址向组播服 务器发送组播节目点播请求的操作, 可以实现终端版本升级的自适应控制, 可 以有效地防止版本升级对用户所使用的业务造成影响(如造成高清视频点播业 务播放不流畅), 和 /或, 可以有效地防止版本升级加剧终端当前负荷, 防止终 端崩溃。
作为另一种可选的实施方式, 在图 8所示的终端中, 处理器 81依据该升 级版本文件执行版本升级操作的方式具体可以为:
处理器 81用于依据该升级版本文件, 并釆用状态机方式对该终端执行版 本升级操作。其中,釆用状态机方式对该终端执行版本升级操作可以确保版本 的完整升级, 而且还可以避免造成同一升级版本的反复升级。
在图 8所示的终端中, 终端可以作为升级操作的控制主体,从而可以省去 由 OLT对终端进行升级操作控制, 使得在对终端进行版本升级过程中 OLT只 作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另外, 由终端进 行组播节目点播来实现版本升级, 可以实现海量终端的并行的版本升级操作, 从而可以提升终端的升级效率。由于终端可以通过组播服务器获取终端升级所 需的版本升级文件, 终端从 OLT获取升级版本文件改成从组播服务器获取升 级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力的限制。
以上对本发明实施例公开的光终端升级系统及 EMS、 终端进行了介绍, 下面进一步介绍本发明实施例公开的光终端升级方法。
请参阅图 9,图 9是本发明实施例公开的一种终端升级方法的流程示意图。 其中, 图 9所描述的方法是从 EMS的角度来进行描述的。 如图 9所示, 该方 法可以包括以下步骤:
91、 EMS将 OLT所辖的终端类型支持的升级版本文件封装成组播节目并 存储至组播服务器。 92、 EMS 建立该终端类型支持的升级版本号与组播节目存储地址的版本 地址映射关系。
93、 EMS将版本地址映射关系由经 OLT下发至该终端。
94、 EMS将升级启动指令由经 OLT下发至该终端, 以触发该终端根据版 本地址映射关系中的组播节目存储地址向组播服务器发送组播节目点播请求, 以及由该终端接收组播服务器发送的该组播节目存储地址存储的组播节目,并 由该终端依据该组播节目执行版本升级操作。
本发明实施例中,上述步骤 92中 EMS建立的该终端类型支持的升级目标 版本号与该终端的组播节目存储地址的版本地址映射关系中,可以包括以下表
1所示的关键参数, 即:
表 1 版本地址映射关系包括的关键参数
名称 名称中文描述 类型 取值范围
InternetGatewayDevice.Devicelnfo. 通用设备信息 object -
Manufacturer 制造商 string [0:64]
ManufacturerOUI 制造商 OUI string [0:6]
ModelName 设备名称 string [0:64]
Description 设备描述 string [0:256]
ProductClass 产品类别 string [0:64]
Software Version 升级版本号 string [0:64]
附加升级版本号
AdditionalSoftw are Version 描述 string [0:64] SpecVersion 升级版本标记 string [0: 16]
IGMP V4组播节
Igmp Program V4 目存储地址 string [0:4]
IGMP V6组播节
Igmp Program V6 目存储地址 string [0: 16]
本发明实施例中, 上述步骤 93中 EMS将版本地址映射关系由经 OLT下 发至该终端的方式具体可以为:
EMS将版本地址映射关系加载至 XML配置文件, 获得目标 XML配置文 件, 以及 EMS将目标 XML配置文件由经 OLT下发至该终端。
本发明实施例中, EMS可以由经 OLT下发包括目标 XML配置文件的协 议消息给该终端,从而实现将目标 XML配置文件由经 OLT下发至该终端的目 的。 其中, 该协议消息可以包括但不限于 OMCI/OAM协议消息、 FTP协议消 息或 TR069协议消息。
本发明实施例中,当 OLT下发包括目标 XML配置文件的协议消息给该终 端失败时, 该终端会通知 OLT, 以使得 OLT重新下发包括目标 XML配置文 件的协议消息。
作为另一种可选的实施方式,在图 9所描述的方法中, EMS在将目标 XML 配置文件由经 OLT下发至该终端之后, 以及 EMS在执行步骤 94之前, EMS 还可以执行以下步骤:
EMS将升级测试指令由经 OLT下发至该终端, 该升级测试指令包括升级 校验参数,该升级校验参数至少包括该终端类型支持的当前版本号以及升级版 本号;
以及, EMS接收 ONT由经 OLT上报的该终端针对所述升级校验参数的 校验结果;
以及, EMS判断该校验结果是否为校验通过,若校验通过,执行步骤 S904。 本发明实施例中, 当 EMS判断该校验结果为校验通过时, 表示该终端支 持版本升级, EMS即可执行步骤 904, 从而启动该终端的版本升级操作。 作为另一种可选的实施方式, 在图 9所描述的方法中, EMS判断该校验 结果为校验通过之后, 以及 EMS执行步骤 94之前, EMS还可以执行以下步 骤:
EMS判断是否满足预设的 EMS升级策略, 如果满足预设的 EMS升级策 略, 执行 EMS执行步骤 94。
作为一种可选的实施方式, 在图 9所描述的方法中, 上述的目标 XML配 置文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相应地,上述的 EMS将目标 XML配置文件由经 OLT下发至该终端可以包括:
EMS接收该终端由经 OLT上报的远端 XML配置文件添加的 CRC校验值; 其中, 该远端 XML配置文件用于加载远端映射关系, 该远端映射关系为该终 端类型支持的当前版本号与当前版本封装成的组播节目的存储地址的映射关 系;
以及, EMS将该远端 XML配置文件添加的 CRC校验值与目标 XML配 置文件添加的 CRC校验值进行比较, 若比较不一致, 由经 OLT下发包括目标 XML配置文件的协议消息给该终端。
在图 9所描述的方法中, 可以将终端进行升级操作的控制主体由 OLT下 降至终端, 从而可以省去由 OLT对终端进行升级操作控制, 使得在对终端进 行版本升级过程中 OLT只作为传输通道使用, 从而可以有效地降低 OLT的工 作负荷; 另外, 在图 9所描述的方法中, 终端进行组播节目点播来实现版本升 级,可以实现海量终端的并行的版本升级操作,从而可以提升终端的升级效率。 请参阅图 10, 图 10是本发明实施例公开的另一种终端升级方法的流程示 意图。 其中, 图 10所描述的方法是从 ONT的角度来进行描述的。 如图 10所 示, 该方法可以包括以下步骤:
101、 ONT接收 EMS由经 OLT下发的该 ONT类型支持的升级版本号与 组播节目存储地址的版本地址映射关系; 其中, 该组播节目存储地址存储的组 播节目是由该 ONT类型支持的升级版本封装成的组播节目。 102、 ONT接收 EMS由经 OLT下发的升级启动指令。
103、 ONT响应升级启动指令, 根据版本地址映射关系中的组播节目存储 地址向组播服务器发送组播节目点播请求。
104、 ONT接收组播服务器发送的该组播节目存储地址存储的组播节目。 105、 ONT依据该组播节目执行版本升级操作。
作为一种可选的实施方式,在图 10所描述的方法中,上述步骤 101中 ONT 接收 EMS由经 OLT下发的该 ONT类型支持的升级版本号与组播节目存储地 址的版本地址映射关系可以包括:
ONT接收 EMS由经 OLT下发的目标 XML配置文件, 其中, 目标 XML 配置文件加载有该 ONT类型支持的升级版本号与组播节目存储地址的版本地 址映射关系。
作为一种可选的实施方式, 在图 10所描述的方法中, ONT接收 EMS由 经 OLT下发的目标 XML配置文件之后, 以及 ONT执行上述的步骤 102中的 接收 EMS由经 OLT下发的升级启动指令之前, ONT还可以执行以下步骤:
ONT接收 EMS由经 OLT下发的升级测试指令, 该升级测试指令包括升 级校验参数, 该升级校验参数至少包括该 ONT支持的当前版本号以及升级目 标版本号;
以及, ONT对升级校验参数进行校验, 获得该 ONT针对升级校验参数的 校验结果;
ONT将校验结果由经 OLT上报给 EMS, 以使触发 EMS判断出校验结果 为校验通过时, 由经 OLT下发升级启动指令给该 ONT。
本发明实施例中, 当 EMS 判断该校验结果为校验通过时, 表示该 ONT 支持版本升级, EMS可以由经 OLT下发升级启动指令给该 ONT作。
作为一种可选的实施方式, 在图 10所描述的方法中, 上述的目标 XML 配置文件可以添加有唯一的 CRC校验值, CRC校验值用于比较版本是否一致。 相应地, 上述的 ONT接收 EMS由经 OLT下发的目标 XML配置文件包括:
ONT将远端 XML配置文件添加的 CRC校验值由经 OLT上报给 EMS; 其中, 该远端 XML 配置文件用于加载远端映射关系, 该远端映射关系为该 ONT类型支持的当前版本号与当前版本封装成的组播节目的存储地址的映射 关系;
以及, ONT接收 EMS比较该远端 XML配置文件添加的 CRC校验值与目 标 XML配置文件添加的 CRC校验值不一致之后, 由经 OLT下发的包括目标 XML配置文件的协议消息。
本发明实施例中,该 ONT可以在上电时将该 ONT的本地 XML配置文件 添加的 CRC校验值由经 OLT上报给 EMS, 当 EMS比较该远端 XML配置文 件添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致时, EMS 可以获悉该 ONT支持的当前版本封装成的组播节目与该 ONT支持的升级版本 封装成的组播节目不同, 此时, EMS可以将目标 XML配置文件由经 OLT下 发至该 ONT。
本发明实施例中, ONT依据该组播节目执行版本升级操作之后, ONT可 以利用上述的版本地址映射关系更新远端映射关系, 将 ONT可以将上述的版 本地址映射关系作为新的远端映射关系。
作为一种可选的实施方式, 在图 10所描述的方法中, ONT执行步骤 102 之后, 以及 ONT执行步骤 103之前, ONT还可以执行以下步骤:
ONT判断是否满足预设的 ONT升级策略, 如果满足预设的 ONT升级策 略, 执行步骤 103。
举例来说, ONT可以接收 OLT下发的 ONT升级策略, 该 ONT升级策略 可以包括以下一种或几种情形的组合, 即:
1、 ONT当前不存在点播业务或语音业务;
2、 ONT当前负荷小于预设负荷值;
3、 升级版本信息完善;
4、 ONT根据升级版本存储地址找到对应的组播节目;
5、 升级版本号与组播节目的对应关系表存在;
6、 ONT当前不存在版本升级操作; 7、 ONT内存充足, 可以进行版本升级任务;
8、 ONT尚未升级至升级版本。
作为另一种可选的实施方式, 在图 10所描述的方法中, 上述步骤 105中 ONT依据该组播节目执行版本升级操作的方式具体可以为:
ONT从接收到的组播节目中提取出所述组播节目包括的各个组播报文, 其中, 组播报文包括升级目标版本子文件和控制头;
ONT根据各个组播报文包括的控制头, 将各个组播报文包括的升级目标 版本子文件进行组合, 获得 ONT类型支持的升级目标版本文件;
ONT依据升级目标版本文件执行版本升级操作。
其中, ONT可以依据升级目标版本文件, 并釆用状态机方式对该 ONT 执行版本升级操作。 其中, 釆用状态机方式对该 ONT执行版本升级操作可以 确保版本的完整升级, 而且还可以避免造成同一升级版本的反复升级。 组播服务器可以循环下发组播节目, 当 ONT检测到升级失败时, ONT可以依 据组播服务器下一次下发的组播节目重新执行升级操作, 直至升级完成; 当 ONT检测升级完成之后, ONT可以通知组播服务器停止下发组播节目, 从而 可以确保版本的完整升级, 而且还可以避免造成同一升级版本的反复升级。
在图 10所描述的方法, ONT可以作为升级操作的控制主体, 从而可以省 去由 OLT对 ONT进行升级操作控制,使得在对 ONT进行版本升级过程中 OLT 只作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另夕卜, 由 ONT 进行组播节目点播来实现版本升级, 可以实现海量 ONT的并行的版本升级操 作, 从而可以提升 ONT的升级效率。 请参阅图 11, 图 11是本发明实施例公开的另一种光终端升级方法的流程 示意图。 其中, 图 11所描述的方法是从 EMS、 组播服务器、 OLT以及 ONT 多个角度来进行描述的。 如图 11所示, 该方法可以包括以下步骤:
110, EMS将 OLT所辖的 ONT类型支持的升级版本文件封装成组播节目。
111、 EMS将该 ONT类型支持的升级版本文件封装成的组播节目上传至 组播服务器存储。
112、 EMS建立该 ONT类型支持的升级版本号与组播节目存储地址的版 本地址映射关系。
113、 EMS将本地映射关系加载至 XML配置文件, 获得目标 XML配置 文件。
114、 EMS将目标 XML配置文件由经 OLT下发至该 ONT。
115、 EMS将升级测试指令由经 OLT下发至该 ONT, 该升级测试指令包 括升级校验参数, 该升级校验参数至少包括该 ONT支持的当前版本号以及升 级目标版本号。
116、 ONT对升级校验参数进行校验, 获得该 ONT针对升级校验参数的 校验结果。
117、 ONT将校验结果由经 OLT上报给所述 EMS。
118、 EMS判断该校验结果是否为校验通过, 若校验通过, EMS判断是否 满足预设的 EMS升级策略,如果满足预设的 EMS升级策略,将升级启动指令 由经 OLT下发至该 ONT。
119、 ONT判断是否满足预设的 ONT升级策略, 如果满足预设的 ONT升 级策略, ONT 响应升级启动指令, 根据版本地址映射关系中的组播节目存储 地址向组播服务器发送组播节目点播请求。
本发明实施例 , ONT可以实现版本升级的自适应控制, 可以有效地防止 版本升级对用户所使用的业务造成影响 (如造成高清视频点播业务播放不流 畅), 和 /或, 可以有效地防止版本升级加剧 ONT当前负荷, 防止 ONT崩溃。
120、 ONT接收组播服务器发送的该组播节目存储地址存储的组播节目。 121、 ONT依据该组播节目执行版本升级操作。
在图 11所描述的方法, ONT可以作为升级操作的控制主体, 从而可以省 去由 OLT对 ONT进行升级操作控制,使得在对 ONT进行版本升级过程中 OLT 只作为传输通道使用, 从而可以有效地降低 OLT的工作负荷; 另夕卜, 由 ONT 进行组播节目点播来实现版本升级, 可以实现海量 ONT的并行的版本升级操 作,从而可以提升 ONT的升级效率。由于 ONT可以通过组播服务器获取 ONT 升级所需的版本升级文件, ONT从 OLT获取升级版本文件改成从组播服务器 获取升级版本文件, 因此不同厂商、 不同类型终端的升级任务可以并发进行, 不受 OLT处理能力的限制。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可 以通过程序指令相关的硬件来完成,前述的程序可以存储于一计算机可读取存 储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储 介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
以上对本发明实施例公开的一种终端升级方法及相关设备、系统进行了详 实施例的说明只是用于帮助理解本发明的方法及其核心思想; 同时,对于本领 域的一般技术人员,依据本发明的思想,在具体实施方式及应用范围上均会有 改变之处, 综上所述, 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种终端升级方法, 其特征在于, 包括:
网元管理系统 EMS将终端类型支持的升级版本文件封装成组播节目并存 储至组播服务器; 或者, 网元管理系统 EMS将终端类型支持的升级版本文件 发送至组播服务器,以使所述组播服务器将所述升级版本文件封装成组播节目 并存储;
所述 EMS建立版本地址映射关系, 所述版本地址映射关系包括升级版本 号与组播节目存储地址的映射关系;
所述 EMS将所述版本地址映射关系下发至终端;
所述 EMS将升级启动指令下发至所述终端, 以触发所述终端根据所述版 本地址映射关系中的组播节目存储地址向所述组播服务器发送组播节目点播 请求,以及由所述终端接收所述组播服务器发送的所述终端的组播节目存储地 址存储的组播节目,并由所述终端依据接收到的所述组播节目执行版本升级操 作。
2、 根据权利要求 1所述的方法, 其特征在于, 所述将终端类型支持的升 级版本文件封装成组播节目包括:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息;
3、根据权利要求 1或 2所述的方法, 其特征在于, 所述 EMS将所述版本 地址映射关系下发至所述终端包括:
所述 EMS 将所述版本地址映射关系加载至 XML 配置文件, 获得目标 XML配置文件;
所述 EMS将所述目标 XML配置文件下发至所述终端。
4、根据权利要求 3所述的方法,其特征在于,所述 EMS将所述目标 XML 配置文件下发至所述终端之后, 以及所述 EMS将升级启动指令下发至所述终 端之前, 所述方法还包括:
所述 EMS将升级测试指令下发至所述终端, 所述升级测试指令包括升级 校验参数,所述升级校验参数至少包括所述终端类型支持的当前版本号以及升 级版本号;
所述 EMS接收所述终端上报的所述终端针对所述升级校验参数的校验结 果;
所述 EMS判断所述校验结果是否为校验通过, 若校验通过, 执行所述的 将升级启动指令下发至所述终端的步骤。
5、 根据权利要求 3~4任一项所述的方法, 其特征在于, 所述目标 XML 配置文件添加有 CRC校验值, 所述 EMS将所述目标 XML配置文件下发至所 述终端包括:
所述 EMS接收所述终端上报的远端 XML配置文件添加的 CRC校验值; 其中, 所述远端 XML配置文件用于加载远端映射关系, 所述远端映射关系为 所述终端类型支持的当前版本号与当前版本封装成的组播节目的存储地址的 映射关系;
所述 EMS将所述远端 XML配置文件添加的 CRC校验值与所述目标 XML 配置文件添加的 CRC校验值进行比较,若比较不一致,下发包括所述目标 XML 配置文件的协议消息给所述终端。
6、 一种终端升级方法, 其特征在于, 包括:
终端接收网元管理系统 EMS下发的版本地址映射关系, 所述版本地址映 射关系包括升级版本号与组播节目存储地址的映射关系; 其中, 所述组播节目 存储地址存储的组播节目是由所述终端类型支持的升级版本文件封装成的组 播节目;
所述终端接收所述 EMS下发的升级启动指令;
所述终端响应所述升级启动指令,根据所述版本地址映射关系中的组播节 目存储地址向组播服务器发送组播节目点播请求;
所述终端接收所述组播服务器发送的所述组播节目存储地址存储的组播 节目;
所述终端依据接收到的所述组播节目执行版本升级操作。
7、 根据权利要求 6所述的方法, 其特征在于, 所述终端依据接收到的所 述组播节目执行版本升级操作包括:
所述终端从接收到的所述组播节目中提取各个升级版本子文件,所述升级 版本子文件包括控制头, 所述控制头包括所述终端升级所需的信息; 级版本子文件进行组合, 获得所述终端类型支持的升级版本文件;
8、 根据权利要求 6所述的方法, 其特征在于, 所述终端接收网元管理系 统 EMS下发的版本地址映射关系系包括:
终端接收 EMS下发的目标 XML配置文件,其中, 所述目标 XML配置文 件加载有版本地址映射关系。
9、根据权利要求 8所述的方法, 其特征在于, 所述终端接收 EMS发的目 标 XML配置文件之后, 以及所述终端接收所述 EMS下发的升级启动指令之 前, 所述方法还包括:
所述终端接收所述 EMS下发的升级测试指令, 所述升级测试指令包括升 级校验参数,所述升级校验参数至少包括所述终端类型支持的当前版本号以及 升级版本号;
所述终端对所述升级校验参数进行校验,获得所述终端针对所述升级校验 参数的校验结果;
所述终端将所述校验结果上报给所述 EMS, 以使触发所述 EMS判断出所 述校验结果为校验通过时, 下发升级启动指令给所述终端。
10、 根据权利要求 8或 9所述的方法, 其特征在于, 所述目标 XML配置 文件添加有 CRC校验值,所述终端接收 EMS下发的目标 XML配置文件包括: 所述终端将远端 XML配置文件添加的 CRC校验值上报给所述 EMS; 其 中, 所述远端 XML配置文件用于加载远端映射关系, 所述远端映射关系为所 述终端类型支持的当前版本号与当前版本封装成的组播节目的存储地址的映 射关系;
所述终端接收所述 EMS比较所述远端 XML配置文件添加的 CRC校验值 与目标 XML配置文件添加的 CRC校验值不一致之后, 下发的包括所述目标 XML配置文件的协议消息。
11、 根据权利要求 6~10任一项所述的方法, 其特征在于, 所述终端接收 所述 EMS下发的升级启动指令之后, 以及所述终端响应所述升级启动指令, 根据所述版本地址映射关系中的组播节目存储地址向组播服务器发送组播节 目点播请求之前, 所述方法还包括:
终端判断是否满足终端升级策略,如果满足所述终端升级策略,执行所述 的响应所述升级启动指令,根据所述版本地址映射关系中的组播节目存储地址 向组播服务器发送组播节目点播请求的步骤;
其中, 所述终端升级策略包括所述终端当前不存在点播业务、语音业务或 所述终端当前负荷小于预设负荷值中的任意一种或几种的组合。
12、 一种网元管理系统, 其特征在于, 包括:
封装单元,用于将终端类型支持的升级版本文件封装成组播节目并存储至 组播服务器; 或者, 将终端类型支持的升级版本文件发送至组播服务器, 以使 所述组播服务器将所述升级版本文件封装成组播节目并存储;
建立单元, 用于建立版本地址映射关系, 所述版本地址映射关系包括升级 版本号与组播节目存储地址的映射关系;
第一通讯单元, 用于将所述版本地址映射关系下发至所述终端, 并启动第 二通讯单元;
所述第二通讯单元,用于将升级启动指令下发至所述终端, 以触发所述终 端根据所述版本地址映射关系中的组播节目存储地址向所述组播服务器发送 组播节目点播请求,以及由所述终端接收所述组播服务器发送的所述终端的组 播节目存储地址存储的组播节目,并由所述终端依据接收到的所述组播节目执 行版本升级操作。
13、 根据权利要求 12所述的网元管理系统, 其特征在于, 所述将终端类 型支持的升级版本文件封装成组播节目的方式具体为:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息;
14、 根据权利要求 12或 13所述的网元管理系统, 其特征在于, 第一通讯 单元包括:
加载子单元, 用于将所述版本地址映射关系加载至 XML配置文件, 获得 目标 XML配置文件;
通讯子单元, 用于将所述目标 XML配置文件下发至所述终端, 并启动第 二通讯单元。
15、 根据权利要求 14所述的网元管理系统, 其特征在于, 所述通讯子单 元还用于在将所述目标 XML配置文件下发至所述终端之后, 将升级测试指令 下发至所述终端, 所述升级测试指令包括升级校验参数, 所述升级校验参数至 少包括所述终端类型支持的当前版本号以及升级版本号;
所述通讯子单元还用于接收所述终端上报的所述终端针对所述升级校验 参数的校验结果;
所述网元管理系统还包括第一判断单元,用于判断所述校验结果是否为校 验通过, 若校验通过, 触发所述第二通讯单元执行所述的将升级启动指令下发 至所述终端执行的操作。
16、根据权利要求 14~15任一所述的网元管理系统, 其特征在于, 所述目 标 XML配置文件添加有 CRC校验值,所述通讯子单元将所述目标 XML配置 文件发至所述终端的方式具体为:
所述通讯子单元用于接收所述终端上报的远端 XML配置文件添加的 CRC 校验值; 其中, 所述远端 XML配置文件用于加载远端映射关系, 所述远端映 射关系为所述终端类型支持的当前版本号与当前版本封装成的组播节目的存 储地址的映射关系;
以及, 所述通讯子单元用于将所述远端 XML配置文件添加的 CRC校验 值与所述目标 XML配置文件添加的 CRC校验值进行比较, 若比较不一致, 下发包括所述目标 XML配置文件的协议消息给所述终端。
17、 一种终端, 其特征在于, 包括:
第一交互单元, 用于接收网元管理系统 EMS下发的版本地址映射关系, 所述版本地址映射关系包括升级版本号与组播节目存储地址的映射关系; 其 中,所述组播节目存储地址存储的组播节目是由所述终端类型支持的升级版本 文件封装成的组播节目;
第二交互单元, 用于接收所述 EMS下发的升级启动指令;
节目点播单元, 用于响应所述升级启动指令,根据所述版本地址映射关系 中的组播节目存储地址向组播服务器发送组播节目点播请求;
所述节目点播单元,还用于接收所述组播服务器发送的所述组播节目存储 地址存储的组播节目;
升级操作单元, 用于依据接收到的所述组播节目执行版本升级操作。
18、 根据权利要求 17所述的终端, 其特征在于, 所述升级操作单元包括: 第一提取子单元, 用于从接收到的组播节目中提取各个升级版本子文件, 升级版本子文件包括控制头, 控制头包括终端升级所需的信息;
文件组合子单元, 用于根据各个升级版本子文件包括的控制头,将各个升 级版本子文件进行组合, 获得终端类型支持的升级版本文件;
版本升级子单元, 用于依据升级版本文件执行版本升级操作。
19、 根据权利要求 17所述的终端, 其特征在于, 所述第一交互单元用于 接收 EMS发的目标 XML配置文件,其中, 所述目标 XML配置文件加载有所 述终端类型支持的升级目标版本号与组播节目存储地址的版本地址映射关系。
20、 根据权利要求 19所述的终端, 其特征在于, 所述第一交互单元还用 于在接收 EMS下发的目标 XML配置文件之后,接收所述 EMS下发的升级测 试指令, 所述升级测试指令包括升级校验参数, 所述升级校验参数至少包括所 述终端类型支持的当前版本号以及升级版本号;
所述终端还包括参数校验单元, 用于对所述升级校验参数进行校验, 获得 所述终端针对所述升级校验参数的校验结果;
所述第一交互单元还用于将所述校验结果上报给所述 EMS, 以使触发所 述 EMS判断出所述校验结果为校验通过时, 下发升级启动指令给所述终端。
21、 根据权利要求 20或 21所述的终端, 其特征在于, 所述目标 XML配 置文件添加有 CRC校验值, 所述第一交互单元接收 EMS下发的目标 XML配 置文件的方式具体为:
所述第一交互单元用于将远端 XML配置文件添加的 CRC校验值上报给 所述 EMS; 其中, 所述远端 XML配置文件用于加载远端映射关系, 所述远端 映射关系为所述终端类型支持的当前版本号与当前版本封装成的组播节目的 存储地址的映射关系;
所述第一交互单元还用于接收所述 EMS比较所述远端 XML配置文件添 加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致之后, 下发 的包括所述目标 XML配置文件的协议消息。
22、根据权利要求 17~21任一项所述的终端, 其特征在于, 所述终端还包 括:
判断单元, 用于在所述第二交互单元接收所述 EMS下发的升级启动指令 之后, 判断是否满足预设的终端升级策略, 如果满足预设的终端升级策略, 触 发所述节目点播单元执行所述的响应所述升级启动指令,根据所述版本地址映 射关系中的组播节目存储地址向组播服务器发送组播节目点播请求的操作; 其中, 所述终端升级策略包括所述终端当前不存在点播业务、语音业务或 所述终端当前负荷小于预设负荷值中的任意一种或几种的组合。
23、 一种网元管理系统, 其特征在于, 包括接收器、 处理器、 存储器以及 发射器, 所述接收器、 处理器、 存储器以及发射器分别连接总线, 其中, 所述 存储器中存储一组终端升级程序代码,且所述处理器用于调用所述存储器中存 储的终端升级程序代码, 用于执行以下操作: 通过所述接收器接收终端类型支持的升级版本文件;
将所述终端类型支持的升级版本文件封装成组播节目并通过所述发射器 传输至组播服务器存储, 或者,通过所述发射器将终端类型支持的升级版本文 件发送至组播服务器,以使所述组播服务器将所述升级版本文件封装成组播节 目并存储;
建立版本地址映射关系,所述版本地址映射关系包括升级版本号与组播节 目存储地址的映射关系;
通过所述发射器将所述版本地址映射关系下发至所述终端;
通过所述发射器将升级启动指令下发至所述终端,以触发所述终端根据所 述版本地址映射关系中的组播节目存储地址向所述组播服务器发送组播节目 点播请求,以及由所述终端接收所述组播服务器发送的所述终端的组播节目存 储地址存储的组播节目,并由所述终端依据接收到的所述组播节目执行版本升 级操作。
24、 根据权利要求 23所述的网元管理系统, 其特征在于, 所述将终端类 型支持的升级版本文件封装成组播节目的方式具体为:
将所述终端类型支持的升级版本文件划分为至少一个升级版本子文件; 为所述升级版本子文件分配控制头;所述控制头包括所述终端升级所需的 信息;
25、 根据权利要求 23或 24所述的网元管理系统, 其特征在于, 所述处理 器通过所述发射器将所述版本地址映射关系下发至所述终端的方式具体为: 所述处理器将所述版本地址映射关系加载至 XML 配置文件, 获得目标 XML配置文件;
以及, 所述处理器通过所述发射器将所述目标 XML配置文件下发至所述 终端。
26、 根据权利要求 25所述的网元管理系统, 其特征在于, 所述处理器通 过所述发射器将所述目标 XML配置文件下发至所述终端之后, 以及所述处理 器通过所述发射器将升级启动指令下发至所述终端之前,所述处理器还执行以 下操作:
所述处理器通过所述发射器将升级测试指令下发至所述终端,所述升级测 试指令包括升级校验参数,所述升级校验参数至少包括所述终端的类型支持的 当前版本号以及升级版本号;
所述处理器通过所述接收器接收所述终端上报的所述终端针对所述升级 校验参数的校验结果;
所述处理器判断所述校验结果是否为校验通过, 若校验通过,执行所述的 通过所述发射器将升级启动指令下发至所述终端的操作。
27、根据权利要求 25~26任一所述的网元管理系统, 其特征在于, 所述目 标 XML配置文件添加有 CRC校验值, 所述处理器通过所述发射器将所述目 标 XML配置文件下发至所述终端的方式具体为:
所述处理器通过所述接收器接收所述终端上报的远端 XML配置文件添加 的 CRC校验值; 其中, 所述远端 XML配置文件用于加载远端映射关系, 所 述远端映射关系为所述终端的类型支持的当前版本号与当前版本封装成的组 播节目的存储地址的映射关系;
所述处理器将所述远端 XML 配置文件添加的 CRC校验值与所述目标 XML配置文件添加的 CRC校验值进行比较, 若比较不一致, 通过所述发射器 下发包括所述目标 XML配置文件的协议消息给所述终端。
28、 一种终端, 其特征在于, 包括接收器、 处理器、 存储器以及发射器, 所述接收器、 处理器、 存储器以及发射器分别连接总线, 其中, 所述存储器中 存储一组终端升级程序代码,且所述处理器用于调用所述存储器中存储的终端 升级程序代码, 用于执行以下操作:
通过所述接收器接收网元管理系统 EMS下发的版本地址映射关系, 所述 版本地址映射关系包括升级版本号与组播节目存储地址的映射关系; 其中, 所 述组播节目存储地址存储的组播节目是由所述终端类型支持的升级版本文件 封装成的组播节目; 通过所述接收器接收所述 EMS下发的升级启动指令;
响应所述升级启动指令,根据所述版本地址映射关系中的组播节目存储地 址通过所述发射器向组播服务器发送组播节目点播请求;
通过所述接收器接收所述组播服务器发送的所述组播节目存储地址存储 的组播节目;
依据接收到的所述组播节目执行版本升级操作。
29、 根据权利要求 28所述的终端, 其特征在于, 所述处理器依据接收到 的所述组播节目执行版本升级操作的方式具体为:
从接收到的所述组播节目中提取各个升级版本子文件,所述升级版本子文 件包括控制头, 所述控制头包括所述终端升级所需的信息;
根据所述各个升级版本子文件包括的所述控制头,将所述各个升级版本子 文件进行组合, 获得所述终端类型支持的升级版本文件;
依据所述升级版本文件执行版本升级操作。
30、 根据权利要求 28所述的终端, 其特征在于, 所述处理器通过所述接 收器接收 EMS下发的版本地址映射关系的方式具体为:
所述处理器通过所述接收器接收 EMS下发的目标 XML配置文件, 其中, 所述目标 XML配置文件加载有版本地址映射关系。
31、 根据权利要求 30所述的终端, 其特征在于, 所述处理器通过所述接 收器接收 EMS下发的目标 XML配置文件之后, 以及所述处理器通过所述接 收器接收所述 EMS下发的升级启动指令之前, 所述处理器还执行以下操作: 所述处理器通过所述接收器接收所述 EMS下发的升级测试指令, 所述升 级测试指令包括升级校验参数,所述升级校验参数至少包括所述终端的类型支 持的当前版本号以及升级版本号;
所述处理器对所述升级校验参数进行校验,获得所述终端针对所述升级校 验参数的校验结果;
所述处理器通过所述发射器将所述校验结果上报给所述 EMS, 以使触发 所述 EMS判断出所述校验结果为校验通过时,下发升级启动指令给所述终端。
32、 根据权利要求 30或 31所述的终端, 其特征在于, 所述目标 XML配 置文件添加有 CRC校验值,所述处理器通过所述接收器接收 EMS下发的目标 XML配置文件包括:
所述处理器通过所述发射器将远端 XML配置文件添加的 CRC校验值上 报给所述 EMS; 其中, 所述远端 XML配置文件用于加载远端映射关系, 所述 远端映射关系为所述终端类型支持的当前版本号与当前版本封装成的组播节 目的存储地址的映射关系;
所述处理器通过所述接收器接收所述 EMS比较所述远端 XML配置文件 添加的 CRC校验值与目标 XML配置文件添加的 CRC校验值不一致之后, 下 发的包括所述目标 XML配置文件的协议消息。
33、 根据权利要求 28~32任一项所述的 ONT, 其特征在于, 所述处理器 通过所述接收器接收所述 EMS下发的升级启动指令之后, 以及所述处理器响 应所述升级启动指令,根据所述版本地址映射关系中的组播节目存储地址通过 所述发射器向组播服务器发送组播节目点播请求之前,所述处理器还执行以下 操作:
所述处理器判断是否满足终端升级策略,如果满足所述终端升级策略,执 行所述的响应所述升级启动指令,根据所述版本地址映射关系中的组播节目存 储地址通过所述发射器向组播服务器发送组播节目点播请求的操作;
其中, 所述终端升级策略包括所述终端当前不存在点播业务、语音业务或 所述终端当前负荷小于预设负荷值中的任意一种或几种的组合。
PCT/CN2014/082779 2014-07-23 2014-07-23 一种终端升级方法及相关设备 WO2016011607A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2014/082779 WO2016011607A1 (zh) 2014-07-23 2014-07-23 一种终端升级方法及相关设备
CN201480065652.1A CN105993147B (zh) 2014-07-23 2014-07-23 一种终端升级方法及相关设备
EP14898250.7A EP3163796B1 (en) 2014-07-23 2014-07-23 Terminal upgrade method and related device
US15/328,417 US10419291B2 (en) 2014-07-23 2014-07-23 Terminal upgrade method and related device with multicast program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/082779 WO2016011607A1 (zh) 2014-07-23 2014-07-23 一种终端升级方法及相关设备

Publications (1)

Publication Number Publication Date
WO2016011607A1 true WO2016011607A1 (zh) 2016-01-28

Family

ID=55162411

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/082779 WO2016011607A1 (zh) 2014-07-23 2014-07-23 一种终端升级方法及相关设备

Country Status (4)

Country Link
US (1) US10419291B2 (zh)
EP (1) EP3163796B1 (zh)
CN (1) CN105993147B (zh)
WO (1) WO2016011607A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324169A (zh) * 2018-03-30 2019-10-11 北京京东尚科信息技术有限公司 一种接口管理的方法和装置
CN110532006A (zh) * 2019-08-21 2019-12-03 杭州趣链科技有限公司 一种基于状态机的复杂配置文件升级方法
CN110740045A (zh) * 2019-10-28 2020-01-31 支付宝(杭州)信息技术有限公司 指令的组播方法及其系统
CN113050976A (zh) * 2019-12-28 2021-06-29 浙江宇视科技有限公司 基于PCIe总线的FPGA并行升级方法、装置、介质及电子设备
CN116088926A (zh) * 2023-01-10 2023-05-09 睿智合创(北京)科技有限公司 一种决策组件版本管理方法

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108196962B (zh) * 2017-12-29 2020-09-08 杭州迪普科技股份有限公司 一种实现不同版本接口调用的方法及装置
CN111385105B (zh) * 2018-12-27 2022-07-12 中国电信股份有限公司 数据的传输方法、装置、系统、组播管理设备和用户设备
CN110045972B (zh) * 2019-03-25 2022-03-25 深圳市友华通信技术有限公司 Onu在线升级方法和系统
CN110290429B (zh) * 2019-05-14 2021-09-14 聚好看科技股份有限公司 一种栏目下发方法及装置
CN110621011B (zh) * 2019-09-12 2022-11-04 北京方研矩行科技有限公司 一种基于蓝牙设备端的ota固件升级方法及系统
CN111078256B (zh) * 2019-12-20 2024-02-02 广州品唯软件有限公司 自动化测试环境的升级方法、终端及可读存储介质
CN113448596A (zh) * 2020-03-24 2021-09-28 上海汽车集团股份有限公司 一种车辆控制器刷写系统、方法及相关设备
CN111857772B (zh) * 2020-06-29 2023-06-09 湖南中联重科智能技术有限公司 终端边缘应用程序远程传输及动态加载方法及设备
CN113965461B (zh) * 2020-07-02 2022-09-27 大唐移动通信设备有限公司 一种有源天线单元升级方法和装置
CN112104487B (zh) * 2020-08-31 2023-06-20 北京智芯微电子科技有限公司 物联网终端的远程升级方法、物联网主站及存储介质
CN112203170B (zh) * 2020-09-27 2022-10-11 上海欣诺通信技术股份有限公司 一种光网络单元的升级方法、装置、介质及设备
CN112559349B (zh) * 2020-12-16 2024-04-09 合安科技技术有限公司 一种程序的运行方法及运行装置
CN112737847B (zh) * 2020-12-28 2023-02-03 青岛海尔科技有限公司 节点升级方法及装置、存储介质及电子装置
CN113596087A (zh) * 2021-06-25 2021-11-02 海南视联大健康智慧医疗科技有限公司 应用升级方法、装置及计算机可读存储介质
CN114401449A (zh) * 2021-12-27 2022-04-26 中国电信股份有限公司 一种版本的升级方法、装置及可读存储介质
CN114760200A (zh) * 2022-06-15 2022-07-15 深圳市华迅光通信有限公司 无源光网络设备的业务配置方法、装置、设备及存储介质
CN115052252B (zh) * 2022-08-10 2022-11-04 广州世炬网络科技有限公司 一种ota升级方法、系统及装置
CN117573181A (zh) * 2024-01-17 2024-02-20 北京智芯微电子科技有限公司 配电终端升级方法、装置、存储介质及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355454A (zh) * 2008-09-09 2009-01-28 中兴通讯股份有限公司 一种自动升级分布式网络管理服务器的系统与方法
CN101877650A (zh) * 2010-05-20 2010-11-03 中兴通讯股份有限公司 一种自动更新软件版本的方法及系统
CN102098590A (zh) * 2009-12-15 2011-06-15 中兴通讯股份有限公司 光网络单元固件版本自动升级方法及系统
CN102118260A (zh) * 2009-12-30 2011-07-06 中兴通讯股份有限公司 一种网元版本自动化管理的方法及其网络系统
CN103209362A (zh) * 2013-04-12 2013-07-17 深圳市共进电子股份有限公司 一种无源光网络设备间多设备之间升级的方法

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694546A (en) * 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US6009274A (en) * 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
JP2001273122A (ja) * 2000-03-23 2001-10-05 Hitachi Ltd 並列計算システムのプログラムインストール方法及び装置
US7526762B1 (en) * 2000-06-30 2009-04-28 Nokia Corporation Network with mobile terminals as browsers having wireless access to the internet and method for using same
US7720903B1 (en) * 2000-08-31 2010-05-18 Intel Corporation Client messaging in multicast networks
US7308491B2 (en) * 2002-03-18 2007-12-11 Samsung Electronics Co., Ltd. System and method for on-line upgrade of call processing software using group services in a telecommunication system
US7219344B2 (en) * 2002-04-30 2007-05-15 Accenture Global Services Gmbh Method and apparatus for deploying programs and computing platforms to selected computers
US9609003B1 (en) * 2007-06-12 2017-03-28 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US7844721B2 (en) * 2005-11-23 2010-11-30 Qualcomm Incorporated Method for delivery of software upgrade notification to devices in communication systems
JP4741022B2 (ja) * 2007-07-13 2011-08-03 富士通株式会社 マルチキャスト配信システム及び方法
CN101217412B (zh) 2008-01-03 2011-07-27 烽火通信科技股份有限公司 一种吉比特无源光网络系统中批量升级光网络终端的方法
CN101686139B (zh) 2008-09-22 2012-05-23 华为终端有限公司 一种组播升级的方法、装置和系统
CN101686458B (zh) 2008-09-28 2013-06-12 华为技术有限公司 一种终端配置和管理方法及终端装置
KR101596510B1 (ko) * 2009-09-04 2016-02-22 엘지전자 주식회사 네트워크 tv의 펌웨어 분할 업데이트 방법
US9596305B2 (en) * 2013-04-06 2017-03-14 Citrix Systems, Inc. Systems and methods for distributed hash table contract renewal
US9621668B2 (en) * 2013-04-06 2017-04-11 Citrix Systems, Inc. Systems and methods for application-state, distributed replication table cache poisoning
US9294482B2 (en) * 2013-07-25 2016-03-22 Oracle International Corporation External platform extensions in a multi-tenant environment
US9270529B2 (en) * 2013-10-22 2016-02-23 Landis+Gyr Innovations, Inc. Distributed data transmission in data networks
US9904535B2 (en) * 2015-09-14 2018-02-27 At&T Intellectual Property I, L.P. Method and apparatus for distributing software
US10122872B1 (en) * 2017-05-31 2018-11-06 Xerox Corporation Automatic configuration of network devices in remote managed print service applications utilizing groups of historical device data
US10243651B1 (en) * 2018-01-17 2019-03-26 Vt Idirect, Inc. Mesh satellite terminal accessing multiple time division carriers

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355454A (zh) * 2008-09-09 2009-01-28 中兴通讯股份有限公司 一种自动升级分布式网络管理服务器的系统与方法
CN102098590A (zh) * 2009-12-15 2011-06-15 中兴通讯股份有限公司 光网络单元固件版本自动升级方法及系统
CN102118260A (zh) * 2009-12-30 2011-07-06 中兴通讯股份有限公司 一种网元版本自动化管理的方法及其网络系统
CN101877650A (zh) * 2010-05-20 2010-11-03 中兴通讯股份有限公司 一种自动更新软件版本的方法及系统
CN103209362A (zh) * 2013-04-12 2013-07-17 深圳市共进电子股份有限公司 一种无源光网络设备间多设备之间升级的方法

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324169A (zh) * 2018-03-30 2019-10-11 北京京东尚科信息技术有限公司 一种接口管理的方法和装置
CN110532006A (zh) * 2019-08-21 2019-12-03 杭州趣链科技有限公司 一种基于状态机的复杂配置文件升级方法
CN110532006B (zh) * 2019-08-21 2022-11-18 杭州趣链科技有限公司 一种基于状态机的复杂配置文件升级方法
CN110740045A (zh) * 2019-10-28 2020-01-31 支付宝(杭州)信息技术有限公司 指令的组播方法及其系统
CN113050976A (zh) * 2019-12-28 2021-06-29 浙江宇视科技有限公司 基于PCIe总线的FPGA并行升级方法、装置、介质及电子设备
CN113050976B (zh) * 2019-12-28 2023-06-20 浙江宇视科技有限公司 基于PCIe总线的FPGA并行升级方法、装置、介质及电子设备
CN116088926A (zh) * 2023-01-10 2023-05-09 睿智合创(北京)科技有限公司 一种决策组件版本管理方法
CN116088926B (zh) * 2023-01-10 2023-10-20 睿智合创(北京)科技有限公司 一种决策组件版本管理方法

Also Published As

Publication number Publication date
EP3163796B1 (en) 2019-04-03
CN105993147A (zh) 2016-10-05
EP3163796A4 (en) 2017-06-07
US10419291B2 (en) 2019-09-17
EP3163796A1 (en) 2017-05-03
US20170214568A1 (en) 2017-07-27
CN105993147B (zh) 2019-03-05

Similar Documents

Publication Publication Date Title
WO2016011607A1 (zh) 一种终端升级方法及相关设备
KR101273201B1 (ko) 통신 시스템에서 단말 소프트웨어의 동시 업데이트 방법 및 장치
US8352569B2 (en) Full mesh rates transaction in a network
US8782181B2 (en) Method and system for upgrading network device
US9125003B2 (en) Machine to machine service management device, network device, and method processing service system
US20160286380A1 (en) Management method for embedded universal integrated circuit card, related device, and system
WO2021082715A1 (zh) 直接通信的处理方法、装置、中继终端及远端终端
CN102307390B (zh) 管理数据链路资源使用的方法和设备
EP3205134B1 (en) Auto-configuration of wireless network extender
CN113259309A (zh) 一种通信方法、设备及存储介质
WO2012000251A1 (zh) 一种以太网无源光网络中光节点的软件升级方法及系统
US20180026715A1 (en) Message transmission method, apparatus, and system
WO2015139359A1 (zh) 无线网络维护方法、装置和系统
WO2012092818A1 (zh) 终端的文件下载方法及系统
US10212021B2 (en) Network protocol configuration method and apparatus
WO2014177111A1 (zh) 光网络单元onu数据处理方法、装置及系统
CN107968725B (zh) 家庭网关单元型终端设备配置信息返回及配置方法、设备
EP3059907B1 (en) Network packet forwarding method and device
CN113396600B (zh) 信息验证方法、装置、设备及存储介质
WO2017215438A1 (zh) 一种业务开通方法、设备、系统及存储介质
CN108683598B (zh) 一种非对称网络流量处理方法和处理装置
WO2015096058A1 (zh) 一种数据包处理方法和装置
WO2013095488A1 (en) Implementing an inter-pal pass-through
WO2015117294A1 (zh) 信息的绑定方法及装置
CN106332179B (zh) 一种报文压缩方法及移动终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14898250

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15328417

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2014898250

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014898250

Country of ref document: EP