TW201917570A - Firmware management server and firmware upgrading method - Google Patents
Firmware management server and firmware upgrading method Download PDFInfo
- Publication number
- TW201917570A TW201917570A TW106136091A TW106136091A TW201917570A TW 201917570 A TW201917570 A TW 201917570A TW 106136091 A TW106136091 A TW 106136091A TW 106136091 A TW106136091 A TW 106136091A TW 201917570 A TW201917570 A TW 201917570A
- Authority
- TW
- Taiwan
- Prior art keywords
- upgrade
- user terminal
- firmware
- terminal devices
- version
- Prior art date
Links
Abstract
Description
本發明是有關於一種韌體管理，且特別是有關於一種用於用戶終端設備(Customer Premise Equipment，CPE)之韌體管理伺服器及其韌體升版方法。The present invention relates to a firmware management, and in particular to a firmware management server for a Customer Premise Equipment (CPE) and a firmware enhancement method thereof.
由於用戶終端設備種類繁多，而不同種類的韌體版本可能有差異，長期下來通常會存在許多關於用戶終端設備的韌體管控問題。當發現用戶終端設備可能有資安問題時，設備商必須針對弱點或漏洞快速進行防堵、修復，而網路服務供應商(Internet Service Provider，ISP)則需在短時間內大量進行用戶終端設備之韌體升版，以避免遭受有心人士攻擊，從而提升資訊安全防護等級。相較於設備商，網路服務供應商更需要面臨下列問題：(1)公司內部不同時期所採購之網路設備型號相異，用戶終端設備之韌體版本眾多，升版方式也大相逕庭，故無法使用單一方式進行韌體升版(2)不同客戶所申請的服務層級協議(Service Level Agreement，SLA)可能不同，而進行韌體升版作業時需要重新啟動，恐造成電路瞬斷，從而影響高等級用戶的使用(3)用戶終端設備的數量相當龐大，且大量程序同時執行韌體升版作業恐影響升版伺服器的負擔。由此可知，現有的韌體管控系統仍有待改進。Due to the wide variety of user terminal devices and the different types of firmware versions, there are often many firmware issues related to user terminal devices in the long run. When it is found that the user terminal device may have a security problem, the device vendor must quickly prevent and fix the vulnerability or vulnerability, and the Internet Service Provider (ISP) needs to perform a large number of user terminal devices in a short time. The firmware is upgraded to avoid attacks by people who are interested in it, thus improving the level of information security protection. Compared with equipment vendors, network service providers need to face the following problems: (1) The types of network equipment purchased in different periods of the company are different, and the firmware versions of user terminal equipment are numerous, and the upgrade methods are also very different. It is not possible to use a single way for firmware upgrades. (2) Different service level agreements (SLAs) may be different for different customers, and need to be restarted when performing firmware upgrades, which may cause circuit breaks and thus affect The use of high-level users (3) The number of user terminal devices is quite large, and a large number of programs simultaneously performing firmware upgrade operations may affect the burden of the upgrade server. It can be seen that the existing firmware control system still needs to be improved.
本發明提供一種韌體管理伺服器及其韌體升版方法，針對不同等級用戶分類成不同升版方式，並分別提供對應的升版排程，使高等級用戶的無感升版，更方便伺服器管控。The invention provides a firmware management server and a firmware upgrading method thereof, which are classified into different upgrade modes for different levels of users, and respectively provide corresponding upgrade schedules, so that high-level users have no sense of promotion and are more convenient. Server management.
本發明的韌體管理伺服器，其包括輸入單元、儲存單元及處理單元。輸入單元取得客戶所申請的服務層級及韌體版本資訊。儲存單元記錄模組。處理單元耦接輸入單元及儲存單元，且存取並執行儲存單元所儲存的那些模組。而那些模組包括升版排程模組及升版執行模組。升版排程模組依據用戶終端設備的服務品質等級分類為主動升版及被動升版的升版方式。升版執行模組依據各韌體版本資訊分別對主動升版及被動升版的用戶終端設備執行升版作業。The firmware management server of the present invention includes an input unit, a storage unit, and a processing unit. The input unit obtains the service level and firmware version information requested by the customer. Storage unit record module. The processing unit is coupled to the input unit and the storage unit, and accesses and executes those modules stored by the storage unit. Those modules include an upgraded scheduling module and an upgraded execution module. The upgrade schedule module is classified into an upgrade mode of active promotion and passive upgrade according to the service quality level of the user terminal device. The upgraded execution module performs an upgrade operation on the actively upgraded and passively upgraded user terminal devices according to the firmware version information.
本發明的韌體升版方法，其包括下列步驟。取得客戶所申請的服務層級及韌體版本資訊。依據客戶所申請的服務層級及訊務流量資訊，將CPE分類為主動升版及被動升版的升版方式。依據各韌體版本資訊分別對主動升版及被動升版之那些用戶終端設備執行升版作業。The firmware upgrading method of the present invention comprises the following steps. Get the service level and firmware version information requested by the customer. According to the service level and traffic flow information requested by customers, CPE is classified into an upgrade mode of active promotion and passive promotion. According to the firmware version information, the user equipments of the active and passive upgrades are respectively upgraded.
基於上述，本發明實施例針對不同等級用戶分別採用被動升版及主動升版兩種升版方式，並對不同升版方式提供對應且合適的排程。藉此，可有效且快速地強化用戶終端設備的資安防護能力，並解決用戶終端設備種類繁多、升版技術相異或管控不易等問題。Based on the above, the embodiment of the present invention adopts two upgrade modes of passive upgrade and active upgrade for different grade users, and provides corresponding and suitable schedules for different upgrade modes. Thereby, the security protection capability of the user terminal equipment can be effectively and quickly enhanced, and the problems of various types of user terminal equipment, different upgrading technologies or difficult management and control are solved.
為讓本發明的上述特徵和優點能更明顯易懂，下文特舉實施例，並配合所附圖式作詳細說明如下。The above described features and advantages of the invention will be apparent from the following description.
圖1是依據本發明一實施例說明一種管理系統1的示意圖。請參照圖1，管理系統1包括韌體管理伺服器100及網路管理伺服器200。韌體管理伺服器100及網路管理伺服器200可能係任何類型伺服器、個人電腦、主機、工作站等電子裝置。1 is a schematic diagram of a management system 1 in accordance with an embodiment of the present invention. Referring to FIG. 1, the management system 1 includes a firmware management server 100 and a network management server 200. The firmware management server 100 and the network management server 200 may be electronic devices of any type of server, personal computer, host, workstation, and the like.
韌體管理伺服器100包括輸入單元110、儲存單元及處理單元。輸入單元110可以係無線或有線通訊處理器(例如，支援藍芽、第4代行動通訊(4G)、WiFi、光纖、乙太網路(Ethernet)等)、匯流排介面等可接收用戶申請的服務層級、韌體版本資訊、訊務流量資訊及對應局端設備相關資訊的硬體單元。The firmware management server 100 includes an input unit 110, a storage unit, and a processing unit. The input unit 110 can be a wireless or wired communication processor (for example, supporting Bluetooth, 4th generation mobile communication (4G), WiFi, optical fiber, Ethernet, etc.), a bus interface, etc., can receive user applications. Service level, firmware version information, traffic flow information, and hardware unit corresponding to the information about the central office equipment.
儲存單元可以係任何型態的固定或可移動隨機存取記憶體(RAM)、唯讀記憶體(ROM)、快閃記憶體(flash memory)、傳統硬碟(hard disk drive)、固態硬碟(solid-state drive)或類似元件或上述元件的組合，並用以記錄韌體管理模組120、升版排程模組130、用戶分群子模組131、升版執行模組140、主動升版執行子模組141及被動升版執行子模組142等軟體程式，儲存資料內容包含服務品質等級、韌體版本資訊及對應局端設備相關資訊、韌體升版規則、升版工作排程、升版方法、分時分數、用量分數、訊務流量資訊等相關資訊。前述模組、參數、檔案及資料待後續實施例再詳細說明。The storage unit can be any type of fixed or removable random access memory (RAM), read only memory (ROM), flash memory, hard disk drive, solid state drive. (solid-state drive) or the like or a combination of the above components, and used to record the firmware management module 120, the upgrade scheduling module 130, the user clustering sub-module 131, the upgrade execution module 140, and the active upgrade The software program such as the execution sub-module 141 and the passive upgrade execution sub-module 142 stores the data content including the service quality level, the firmware version information, the corresponding information about the central office equipment, the firmware upgrade rule, the upgrade work schedule, Upgrading methods, time-sharing scores, usage scores, traffic flow information, and more. The foregoing modules, parameters, files and materials will be described in detail in the following embodiments.
處理單元與輸入單元110及儲存單元連接，並可以是中央處理單元(CPU)，或是其他可程式化之一般用途或特殊用途的微處理器(Microprocessor)、數位信號處理器(DSP)、可程式化控制器、特殊應用積體電路(ASIC)或其他類似元件或上述元件的組合。在本發明實施例中，處理單元用以執行韌體管理伺服器100的所有作業，且可存取並執行輸入單元110及上述儲存單元所記錄的軟體模組。The processing unit is connected to the input unit 110 and the storage unit, and may be a central processing unit (CPU), or other programmable general purpose or special purpose microprocessor (Microprocessor), digital signal processor (DSP), A stylized controller, special application integrated circuit (ASIC) or other similar component or a combination of the above. In the embodiment of the present invention, the processing unit is configured to execute all the operations of the firmware management server 100, and can access and execute the software modules recorded by the input unit 110 and the storage unit.
於本發明實施例中，為韌體管理伺服器100提供用戶終端設備及局端設備相關資訊的裝置係網路管理伺服器200。此網路管理伺服器200可能與一個或更多個局端設備及/或用戶終端設備連接，並取得前述資訊。此外，網路管理伺服器200包括用戶資訊管理模組210、資訊蒐集監控模組220、用戶訊務蒐集子模組221、韌體版本蒐集子模組222、及通知接收模組230(這些軟體模組儲存在網路管理伺服器200的儲存單元中且由其處理單元存取並載入，儲存單元及處理單元的實施態樣可參照前述說明)。In the embodiment of the present invention, the device management network 200 for providing the firmware management server 100 with information about the user terminal device and the central office device is provided. The network management server 200 may be connected to one or more central office devices and/or user terminal devices and obtain the aforementioned information. In addition, the network management server 200 includes a user information management module 210, a information collection monitoring module 220, a user information collection sub-module 221, a firmware version collection sub-module 222, and a notification receiving module 230 (these softwares) The modules are stored in the storage unit of the network management server 200 and accessed and loaded by the processing unit. The implementation of the storage unit and the processing unit can be referred to the foregoing description.
用戶資訊管理模組210負責紀錄用戶終端設備之設備資訊(例如，型號等)及客戶所申請的服務層級(以下稱服務品質等級或用戶類別，於本實施例分為SLA及盡力而為(Best Effort))及對應局端設備資訊(例如，型號、網際網路協定(Internet Protocol，IP)位址、埠號等)。資訊蒐集監控模組220中的用戶訊務蒐集子模組221及韌體版本蒐集子模組222分別負責定期蒐集用戶終端設備之訊務流量資訊及韌體版本資訊，以產生用戶訊務報表，並定期追蹤當前韌體版本資訊。而通知接收模組230則負責接收局端設備所傳送出來的各式通知或告警(Trap)，例如，喚起連結通知(Link Up Trap)表示用戶終端設備正進行重新開機，而網路管理伺服器200會對收到的通知進行對應處理或轉送。網路管理伺服器200所蒐集並儲存的資料可整理成如圖3所示之表格。The user information management module 210 is responsible for recording the device information (for example, model number, etc.) of the user terminal device and the service level (hereinafter referred to as the service quality level or user category) requested by the customer. In this embodiment, the SLA is divided into best-effort (Best). Effort)) and corresponding office equipment information (for example, model number, Internet Protocol (IP) address, nickname, etc.). The user information collection sub-module 221 and the firmware version collection sub-module 222 of the information collection and monitoring module 220 are respectively responsible for periodically collecting the traffic flow information and the firmware version information of the user terminal device to generate a user service report. And regularly track the current firmware version information. The notification receiving module 230 is responsible for receiving various notifications or traps transmitted by the central office device. For example, a Link Up Trap indicates that the user terminal device is being restarted, and the network management server is 200 will process or forward the received notification. The data collected and stored by the network management server 200 can be organized into a table as shown in FIG.
需說明的是，於其他實施例中，韌體管理伺服器100亦可能透過輸入單元110直接對局端設備及/或用戶終端設備取得前述資訊(例如，設備型號、韌體版本資訊等)，更可能透過隨身碟、資料上傳、光碟等方式輸入前述資訊，本發明不加以限制。It should be noted that, in other embodiments, the firmware management server 100 may directly obtain the foregoing information (for example, device model, firmware version information, etc.) on the central office device and/or the user terminal device through the input unit 110. It is more likely that the aforementioned information is input through a flash drive, a data upload, a compact disc, etc., and the present invention is not limited.
為了方便理解本發明實施例的操作流程，以下將舉諸多實施例詳細說明本發明實施例中韌體管理伺服器100的韌體升版方法。下文中，將搭配韌體管理伺服器100的各項元件及模組說明本發明實施例所述之方法。本方法的各個流程可依照實施情形而隨之調整，且並不僅限於此。In order to facilitate the understanding of the operation flow of the embodiment of the present invention, a firmware upgrading method of the firmware management server 100 in the embodiment of the present invention will be described in detail below. Hereinafter, the methods and embodiments of the firmware management server 100 will be described with reference to the methods described in the embodiments of the present invention. The various processes of the method can be adjusted accordingly according to the implementation situation, and are not limited thereto.
本發明實施例基本上分為三個主要步驟：The embodiment of the invention is basically divided into three main steps:
韌體管理步驟：Firmware management steps:
韌體管理模組120(透過諸如LCD、LED等顯示器)提供使用者介面給使用者或管理人員進行韌體檔案管理(例如，輸入韌體版本及韌體檔名等)及制定韌體升版規則(包括局端設備型號、用戶終端設備型號、用戶終端設備來源版本、目標版本及中間版本)。韌體管理模組所儲存的資料可整理成如圖4所示之表格。而中間版本主要是註記於當用戶終端設備版本過舊、與新版韌體版本間有差異，導致不能直接更版至最新版本(或最終版本)的情形，此時可先設定成中間版本，並依序升版直到最終版本。The firmware management module 120 (through displays such as LCDs, LEDs, etc.) provides a user interface for firmware management of users or administrators (for example, input firmware version and firmware file name) and develop firmware upgrades. Rules (including the central office device model, user terminal device model, user terminal device source version, target version, and intermediate version). The data stored in the firmware management module can be organized into a table as shown in FIG. The intermediate version is mainly noted when the user terminal device version is too old and there is a difference between the new version and the firmware version, which may not be directly changed to the latest version (or the final version). In this case, the intermediate version may be set first. Upgrade to the final version.
升版排程步驟：Upgrade schedule steps:
圖2是依據本發明一實施例說明一種升版排程之流程圖。請參照圖2，升版排程模組130根據符合韌體升版規則(記錄有局端設備型號、用戶終端設備型號以及用戶終端設備之韌體版本資訊)的局端設備IP位址、用戶介面(埠號)、用戶類型(即，服務品質等級)等用戶資訊篩選出候選用戶(步驟S210-S230)，並於用戶分群子模組131進行用戶分群。2 is a flow chart showing an upgrade schedule according to an embodiment of the invention. Referring to FIG. 2, the upgrade schedule module 130 is based on the IP address and user of the central office device according to the firmware upgrade rule (the information of the central office device model, the user terminal device model, and the firmware version of the user terminal device). The user information such as the interface (nickname) and the user type (ie, the service quality level) filters out the candidate users (steps S210-S230), and performs user grouping in the user grouping sub-module 131.
當用戶類型為Best Effort用戶時，可依據網路管理伺服器200所監控之用戶前一天(亦可採用過去一段固定時間)的訊務用量(記錄在訊務流量資訊中)統計各用戶終端設備的分時分數(A)及用量分數(B)(步驟S240)。用戶分群子模組131計算某一用戶終端設備每小時分時分數(A)，計算分時分數(A)的方式以高訊務2分/中訊務1分/低訊務0分為權重值，註記此用戶終端設備採用主動升版之升版方式，並記錄可進行升版的時間(例如，低訊務時段)(步驟S245)，以有效降低Best Effort用戶斷線的影響。同時或接續，用戶分群子模組131計算單一用戶終端設備之用量分數(B)，當用量分數(B)大於門檻值N(正整數)或用戶類型為SLA用戶時，表示用戶終端設備一直處於高流量使用狀態、高訊務或為高優先(或高服務品質等級)用戶，則註記或更改成此用戶終端設備採用被動升版之升版方式(步驟S250)。When the user type is a Best Effort user, each user terminal device can be counted according to the traffic usage (recorded in the traffic flow information) of the user monitored by the network management server 200 the previous day (which can also be used in a fixed period of time). The time-sharing score (A) and the usage score (B) (step S240). The user grouping sub-module 131 calculates the hourly time-shared score (A) of a certain user terminal device, and calculates the time-sharing score (A) by dividing the high-traffic 2 points/middle-communication 1 points/low-traffic 0 into weights. Value, note that the user terminal device adopts an upgrade mode of active promotion, and records the time when the upgrade can be performed (for example, a low traffic period) (step S245), so as to effectively reduce the influence of the Best Effort user disconnection. Simultaneously or continuously, the user grouping sub-module 131 calculates the usage score (B) of the single user terminal device. When the usage score (B) is greater than the threshold value N (positive integer) or the user type is the SLA user, the user terminal device is always in the A high-traffic usage state, a high-traffic service, or a high-priority (or high quality of service level) user is noted or changed to the user terminal device adopting a passive upgrade upgrade mode (step S250).
以圖5為例，用戶分群子模組131統計前一天晚間12時至6時之分時分數(A)與用量分數(B)，得到計算結果埠(Port) 1與Port 3可於2-4時進行主動升版，而Port 2由於用量分數大於N(本實施例之N為8)，則註記為被動升版。Taking FIG. 5 as an example, the user grouping sub-module 131 counts the time-division score (A) and the usage score (B) from 12:00 to 6:00 in the evening of the previous day, and obtains the calculation result Port(Port) 1 and Port 3 can be 2- Active promotion is performed at 4 o'clock, and Port 2 is marked as passive upgrade because the usage score is greater than N (N in this embodiment is 8).
此外，升版排程模組130需檢查韌體升版規則中是否還存在中間版本尚未新增至升版工作排程中(步驟S260)。若存在中間版本(如圖4所記錄型號CPEModel_B具有中間版本)，則設定中間版本為目標版本(步驟S270)，並新增至升版工作排程(步驟S280)，重複進行升版作業直到不存在中間版本(即目標版本為最終版本)時，即完成韌體升版排程作業(步驟S290)。以圖7為例，升版排程模組130可依據前述作業得知各用戶介面、用戶類型及型號的升版方式。In addition, the upgrade schedule module 130 needs to check whether there is still an intermediate version in the firmware upgrade rule that has not been added to the upgrade work schedule (step S260). If there is an intermediate version (the intermediate version is recorded in the model CPEModel_B as shown in FIG. 4), the intermediate version is set as the target version (step S270), and is added to the upgrade work schedule (step S280), and the upgrade operation is repeated until no When there is an intermediate version (ie, the target version is the final version), the firmware upgrade schedule job is completed (step S290). Taking FIG. 7 as an example, the upgrade scheduling module 130 can learn the upgrade mode of each user interface, user type, and model according to the foregoing operation.
需說明的是，服務品質等級(即，用戶類別)還可能有很多種，但基本上係訊務用量、服務需求、要求服務等級等因素來分類成被動及主動升版。例如，訊務用量相對大及服務品質等級相對高的歸類為被動升版，反之則設為主動升版。It should be noted that there may be many types of service quality (ie, user categories), but basically classified into passive and active upgrades due to factors such as traffic usage, service requirements, and service level requirements. For example, a relatively large amount of traffic and a relatively high level of service quality are classified as passive upgrades, and vice versa.
韌體升版執行步驟：Firmware upgrade steps:
圖6是依據本發明一實施例說明一種升版執行之流程圖。請參照圖6，本步驟分別由主動升版執行子模組141及被動升版執行子模組142執行。主動升版執行子模組141採用定時啟動至升版執行模組140取得韌體升版排程，每一台局端設備使用獨立執行緒執行升版作業(步驟S610)。每一獨立執行緒需對此台局端設備下註記升版方式為主動升版以及符合升版時間的用戶終端設備進行韌體版本確認(步驟S620)。當設備之韌體版本資訊與韌體升版排程記錄的來源版本相同(步驟S625)時，所有符合條件(某一局端設備同時有數個用戶埠需要升版至同一韌體版本)的用戶即可進行『合併升版』，並通知升版執行模組140註記升版執行中(步驟S630)。反之，若未符合，則暫不執行升版作業(步驟S627)。而待完成升版後，即將此完成升版之排程自韌體升版排程中移除(步驟S635)。主動升版執行子模組141仍需檢查單一局端設備是否仍有升版排程待處理(步驟S640)，若存在其他升版排程則需持續進行升版作業，若未存在即可完成主動升版工作(步驟S690)。此外，當用戶終端設備的韌體版本資訊與最終版本間有差異、存在中間版本、無法直接進行更新時，可透過設定中間版本為目標版本而進行單一用戶之『連續升版』，以使韌體升版能一次到位。FIG. 6 is a flow chart showing an implementation of an upgrade according to an embodiment of the invention. Referring to FIG. 6, this step is performed by the active upgrade execution sub-module 141 and the passive upgrade execution sub-module 142, respectively. The active upgrade execution sub-module 141 adopts the timing start-to-upgrade execution module 140 to obtain the firmware upgrade schedule, and each of the central office devices performs the upgrade operation using the independent thread (step S610). Each independent thread needs to perform a firmware version confirmation for the client device that is in the upgrade mode and the user terminal device that meets the upgrade time (step S620). When the firmware version information of the device is the same as the source version of the firmware upgrade schedule record (step S625), all users who meet the conditions (a certain terminal device has several users at the same time need to be upgraded to the same firmware version) The "merging upgrade" can be performed, and the upgrade execution module 140 is notified to perform the upgrade (step S630). On the other hand, if it is not met, the upgrade operation is not performed yet (step S627). After the upgrade is completed, the schedule for completing the upgrade is removed from the firmware upgrade schedule (step S635). The active upgrade execution sub-module 141 still needs to check whether a single central office device still has an upgrade schedule to be processed (step S640). If there are other upgrade schedules, the upgrade operation needs to be continued, and if not, the upgrade operation can be completed. Active upgrade work (step S690). In addition, when there is a difference between the firmware version information of the user terminal device and the final version, there is an intermediate version, and the update cannot be directly performed, the "continuous upgrade" of the single user can be performed by setting the intermediate version to the target version, so as to be tough. The body upgrade can be in place at one time.
而被動升版執行子模組142等候接收網路管理伺服器200通知用戶已發出喚起連結(網路管理伺服器200可透過接收局端設備的用戶終端設備 Link Up Trap得知)，此通知表示用戶終端設備正在進行重新開機(步驟S650)。被動升版執行子模組142至升版執行模組140查詢此重開機之用戶終端設備的升版工作排程(步驟S660)，確認某一用戶終端設備是否有升版工作排程待執行(步驟S670)且對應局端設備是否正在執行升版作業(步驟S675)。若此局端設備正在執行主動韌體升版作業，則升版執行模組140停止此局端設備之主動韌體升版程序(步驟S680)，再進行升版作業(步驟S683)，並待完成被動升版作業後移除此用戶終端設備的工作排程(步驟S685)。而若未存在待執行之升版工作排程，則表示無需升版(步驟S677)。藉此，可達到利用重新開機的時間點進行高SLA用戶韌體升版之目的。The passive upgrade execution sub-module 142 waits for the receiving network management server 200 to notify the user that an aroused connection has been issued (the network management server 200 can learn from the user terminal device Link Up Trap of the receiving central office device), and the notification indicates The user terminal device is restarting (step S650). The passive upgrade execution sub-module 142 to the upgrade execution module 140 queries the upgrade work schedule of the restarted user terminal device (step S660), and confirms whether a user terminal device has an upgrade work schedule to be executed ( Step S670) and whether the corresponding central office device is performing an upgrade operation (step S675). If the central office device is performing the active firmware upgrade operation, the upgrade execution module 140 stops the active firmware upgrade process of the central office device (step S680), and then performs the upgrade operation (step S683), and waits The work schedule of this user terminal device is removed after the passive upgrade job is completed (step S685). If there is no upgrade work schedule to be executed, it means that no upgrade is required (step S677). In this way, the purpose of upgrading the high SLA user firmware can be achieved by using the time point of rebooting.
綜上所述，本發明實施例依據用戶服務等級、設備特性，合理地對大量用戶終端設備進行升版排程，使各用戶終端設備能適時地升版。不僅統一管控用戶終端設備之韌體檔案，亦掌控每個用戶終端設備之正確升版順序性，讓後續進行韌體升版排程時可以依序升版，有效減少因升版順序不正確而導致設備當機之問題，從而避免用戶終端設備無法上網的狀況。經篩選符合韌體升版規則之用戶資訊，依服務品質等級將用戶終端設備分群標記主動及被動升版方式，可依照用戶特性採取對應升版方式。而採用訊務分時用量分析排定升版時間，有效降低Best Effort用戶斷線的影響。網路管理伺服器通知用戶終端設備係正在進行重新開機時，同步進行韌體升版作業，可避免因主動升版造成SLA用戶無預警斷線，達到SLA用戶無感升版。此外，主動升版及被動升版執行作業可同步執行，從而提升流暢性並加速韌體升版作業，其效益與貢獻十分卓著。藉此，可有效強化終端設備資安防護能力，解決用戶終端設備種類繁多且升版技術各異、管控不易問題。In summary, the embodiment of the present invention reasonably upgrades a large number of user terminal devices according to user service levels and device characteristics, so that each user terminal device can be upgraded in a timely manner. Not only the management and control of the firmware file of the user terminal equipment, but also the correct upgrade order of each user terminal equipment, so that the subsequent firmware upgrade schedule can be upgraded in order, effectively reducing the order of the upgrade is not correct. This causes the device to crash, thus preventing the user terminal device from being able to access the Internet. After screening the user information that meets the firmware upgrade rules, the user terminal equipment is grouped into an active and passive upgrade mode according to the service quality level, and the corresponding upgrade mode can be adopted according to the user characteristics. The use of traffic time-sharing analysis to schedule the upgrade time, effectively reducing the impact of Best Effort users disconnection. The network management server notifies the user that the terminal device is in the process of restarting the firmware, and the firmware upgrade is performed synchronously, so as to prevent the SLA user from being disconnected from the alarm due to the active upgrade, and the SLA user does not feel the upgrade. In addition, active upgrades and passive upgrades can be performed simultaneously, improving fluency and accelerating firmware upgrades, with outstanding benefits and contributions. Thereby, the terminal equipment security protection capability can be effectively strengthened, and the variety of user terminal equipments can be solved, and the upgrading technology is different, and the control is not easy.
雖然本發明已以實施例揭露如上，然其並非用以限定本發明，任何所屬技術領域中具有通常知識者，在不脫離本發明的精神和範圍內，當可作些許的更動與潤飾，故本發明的保護範圍當視後附的申請專利範圍所界定者為準。Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.
1‧‧‧管理系統1‧‧‧Management system
100‧‧‧韌體管理伺服器100‧‧‧ Firmware Management Server
110‧‧‧輸入單元110‧‧‧Input unit
120‧‧‧韌體管理模組120‧‧‧ Firmware Management Module
130‧‧‧升版排程模組130‧‧‧Upgraded scheduling module
131‧‧‧用戶分群子模組131‧‧‧User Grouping Submodules
140‧‧‧升版執行模組140‧‧‧Upgraded Execution Module
141‧‧‧主動升版執行子模組141‧‧‧Active upgraded execution sub-module
142‧‧‧被動升版執行子模組142‧‧‧ Passive upgrade execution sub-module
200‧‧‧網路管理伺服器200‧‧‧Network Management Server
210‧‧‧用戶資訊管理模組210‧‧‧User Information Management Module
220‧‧‧資訊蒐集監控模組220‧‧‧Information Collection Monitoring Module
221‧‧‧用戶訊務蒐集子模組221‧‧‧User Traffic Collection Sub-module
222‧‧‧韌體版本蒐集子模組222‧‧‧ firmware version collection sub-module
230‧‧‧通知接收模組230‧‧‧Notice receiving module
S210~S290、S610~S690‧‧‧步驟S210~S290, S610~S690‧‧‧ steps
圖1是依據本發明一實施例說明一種管理系統的示意圖。 圖2是依據本發明一實施例的升版排程流程圖。 圖3是一範例說明局端設備/用戶終端設備/韌體版本資訊。 圖4是一範例說明韌體管理模組所儲存的資訊。 圖5是一範例說明分時及用量分數之統計結果。 圖6是依據本發明一實施例的升版執行的流程圖。 圖7是一範例說明升版排程紀錄。1 is a schematic diagram of a management system in accordance with an embodiment of the invention. 2 is a flow chart of an upgrade schedule according to an embodiment of the invention. FIG. 3 is an example of a central office device/user terminal device/firmware version information. FIG. 4 is an example of information stored in a firmware management module. Figure 5 is a graphical illustration of the statistical results of time sharing and usage scores. 6 is a flow chart of an upgrade implementation in accordance with an embodiment of the present invention. Figure 7 is an illustration of an upgrade schedule record.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW106136091A TWI644258B (en) | 2017-10-20 | 2017-10-20 | Firmware management server and firmware upgrading method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW106136091A TWI644258B (en) | 2017-10-20 | 2017-10-20 | Firmware management server and firmware upgrading method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| TWI644258B TWI644258B (en) | 2018-12-11 |
| TW201917570A true TW201917570A (en) | 2019-05-01 |
Family
ID=65432104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW106136091A TWI644258B (en) | 2017-10-20 | 2017-10-20 | Firmware management server and firmware upgrading method |
Country Status (1)
| Country | Link |
|---|---|
| TW (1) | TWI644258B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI719746B (en) * | 2019-12-10 | 2021-02-21 | 中華電信股份有限公司 | System and method for network service provisioning |
| TWI728637B (en) * | 2020-01-02 | 2021-05-21 | 中華電信股份有限公司 | Information security protection method and computer-readable medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699399B (en) * | 2009-11-03 | 2014-04-30 | 中兴通讯股份有限公司 | Software update system and method |
| US8924778B2 (en) * | 2010-12-29 | 2014-12-30 | Lsi Corporation | Method to synchronize a replacement controller's firmware version to the native configuration database version on a simplex array |
| KR101976397B1 (en) * | 2012-11-27 | 2019-05-09 | 에이치피프린팅코리아 유한회사 | Method and Apparatus for service level agreement management |
| CN104965736B (en) * | 2015-06-19 | 2018-04-27 | 青岛海信移动通信技术股份有限公司 | A kind of method and device continuously upgraded |
-
2017
- 2017-10-20 TW TW106136091A patent/TWI644258B/en active
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI719746B (en) * | 2019-12-10 | 2021-02-21 | 中華電信股份有限公司 | System and method for network service provisioning |
| TWI728637B (en) * | 2020-01-02 | 2021-05-21 | 中華電信股份有限公司 | Information security protection method and computer-readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI644258B (en) | 2018-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11372669B2 (en) | System and method of cross-silo discovery and mapping of storage, hypervisors and other network objects | |
| US10521324B2 (en) | Programmatically classifying alarms from distributed applications | |
| US10637737B2 (en) | Managing alarms from distributed applications | |
| US20210184947A1 (en) | Automatic capture of detailed analysis information based on remote server analysis | |
| EP3000040B1 (en) | Determining and monitoring performance capabilities of a computer resource service | |
| US9384114B2 (en) | Group server performance correction via actions to server subset | |
| US10552247B2 (en) | Real-time monitoring alert chaining, root cause analysis, and optimization | |
| US9128792B2 (en) | Systems and methods for installing, managing, and provisioning applications | |
| US9537962B2 (en) | Method, device and system for processing client environment data | |
| US8627147B2 (en) | Method and computer program product for system tuning based on performance measurements and historical problem data and system thereof | |
| US8606905B1 (en) | Automated determination of system scalability and scalability constraint factors | |
| EP2595084A2 (en) | Program analyzing system and method | |
| US20140095694A1 (en) | Systems and methods for installing, managing, and provisioning applications | |
| WO2014075599A1 (en) | Method, device and system for processing client environment data | |
| US20160094392A1 (en) | Evaluating Configuration Changes Based on Aggregate Activity Level | |
| TWI644258B (en) | Firmware management server and firmware upgrading method | |
| US8949824B2 (en) | Systems and methods for installing, managing, and provisioning applications | |
| CN113760677A (en) | Abnormal link analysis method, device, equipment and storage medium | |
| CN115051867A (en) | Detection method and device for illegal external connection behaviors, electronic equipment and medium | |
| US10958509B2 (en) | Providing a new server alarm configuration based on the correlation of server alarms for varying metrics of monitored servers | |
| TW201928747A (en) | Server and monitoring method thereof | |
| JP5974905B2 (en) | Response time monitoring program, method, and response time monitoring apparatus | |
| US20190090120A1 (en) | Highly scalable home subscriber server | |
| RU2797263C1 (en) | Active information delivery system, method and device, device and data carrier | |
| WO2023098476A1 (en) | Poor network quality user determination method and apparatus, electronic device, and storage medium |