System updating method, product, equipment and medium

Abstract

The invention relates to the technical field of software updating, in particular to a system updating method, a product, equipment and a medium. The method comprises the steps that when an updating instruction triggered by a user is received, idle systems at the current moment are determined, a system to be updated is determined from the idle systems, and system updating is triggered; in the system updating process, an error signal sent by the error monitoring module when the error event is monitored is captured, and the error signal is analyzed to obtain an error system and an error reason associated with the error event; unloading the error system, and executing a repair operation based on an error reason; when it is monitored that unloading and repairing are both completed, the error system is updated again. According to the invention, a complete updating and repairing closed loop can be formed, and the updating efficiency of the hotel system is improved.

Description

Technical Field

[0001] The present application relates to the field of software update technology, and in particular to a system update method, product, device and medium based on hotel television. Background Art

[0002] Batch system updates are often plagued by issues like unstable networks and fluctuating power supplies, which can lead to corruption of critical files like .so files during the update process. Currently, several approaches are used to address these challenges: pre-downloading update packages to reduce network reliance, performing batch updates to alleviate system pressure, manually repairing corrupted files, and implementing rollback mechanisms. However, these methods have limitations. In particular, after an update fails, manual repair often requires the experience and skills of technicians, which not only increases operational complexity but also significantly reduces update efficiency. Summary of the Invention

[0003] In order to improve the efficiency of hotel system updates, this application provides a system update method, product, device and medium.

[0004] In the first aspect, the present application provides a system update method, which adopts the following technical solutions: A system updating method, comprising: When receiving an update instruction triggered by a user, obtaining the total network bandwidth and determining the idle systems at the current moment, determining the system to be updated from the idle systems based on the total network bandwidth, and triggering the system update; During the system update process, the error monitoring module captures the error signal sent when an error event is detected, and analyzes the error signal to obtain the error system and error cause associated with the error event; Uninstalling the faulty system and performing a repair operation based on the cause of the error; When it is detected that the uninstallation and the repair are completed, the faulty system is updated again.

[0005] By adopting the above technical solution, when the user triggers an update instruction, the update process will be started immediately in response, and the current idle system will be determined. The system can intelligently choose to update when the network load is low and the system is idle, avoiding the impact on the normal operation of the hotel. Determining the system to be updated from the idle system can ensure that the update process is carried out when network resources are sufficient, thereby improving the update efficiency. Parsing the error signal to obtain the error system and the cause of the error can accurately locate the problem, providing strong support for subsequent repair operations. Uninstalling the error system can quickly cut off the source of the fault and avoid the spread of the fault. Executing repair operations based on the cause of the error can accurately solve the problem and improve the repair efficiency. Through rapid uninstallation and repair, the impact of the fault on hotel operations and customer experience can be minimized. Re-updating the error system can ensure that the system is restored to the latest state, improving the stability and reliability of the system. From receiving the update instruction to re-updating the error system, a complete update and repair closed loop is formed, which improves the standardization and efficiency of system management.

[0006] In a preferred example, the present application may be further configured as follows: before the error monitoring module captures the error signal sent when an error event is detected, the method further includes: During the system update process, real-time monitoring of system performance; When there is an abnormal performance indicator in the system performance, obtaining the update progress of the system, determining the system that has not completed the update as an error system based on the update progress, and marking the preset error event type corresponding to the abnormal performance indicator as the error cause; Create an Intent object, set the Action of the Intent object, add the error cause and the ID of the error system into the Intent object to obtain a configured system error signal; The Action of the system error signal is matched with the predefined Action of the error monitoring module. If the match is successful, the error monitoring module is controlled to receive the system error signal.

[0007] By adopting the above technical solution, the steps of real-time monitoring of system performance, determining the faulty system and the cause of the error, creating and configuring system error signals, and matching and receiving system error signals during the system update process together constitute a complete fault monitoring and reporting mechanism. By matching the Action of the system error signal with the predefined Action of the error monitoring module, it can be ensured that the received error signal is valid, avoiding interference from invalid error signals. This mechanism can promptly detect and report abnormal conditions in the system during the update process, providing strong support for subsequent repair operations, thereby improving the stability and reliability of the system and reducing the impact of faults on hotel operations and customer experience.

[0008] In a preferred example, the present application may be further configured as follows: determining the system to be updated from the idle systems based on the total network bandwidth includes: Get the total network bandwidth and update package information for system updates; Acquire storage space information of the idle system, the storage space information including the occupied storage space of the old system and the currently available storage space of each system; Determining whether the target system meets the storage requirement based on the occupied storage space, currently available storage space, and the update package information of the target system, where the target system is any system in the idle system; Determine a system that meets the storage requirement from the idle systems as an intermediate system; The network requirement of the intermediate system during the update process is determined, and if the total network bandwidth can meet the network requirement, the intermediate system is used as a system to be updated.

[0009] By adopting the above technical solution, the system's storage space information and network requirements during the update process are comprehensively considered, and the systems that meet the storage requirements and can be updated within the total network bandwidth are intelligently screened out from the idle systems as the objects to be updated, thereby improving the efficiency and success rate of the system update and ensuring the stable update and smooth operation of the hotel system.

[0010] In a preferred example, the present application may be further configured as follows: determining the network requirements of the intermediate system during the update process includes: Collecting historical update data, the historical update data including first bandwidth data before updating and historical update system information and second bandwidth data during a historical system update process; Determine network bandwidth usage information caused by historical system updates based on the first bandwidth data and the second bandwidth data; estimating the update network demand of the intermediate system based on the historical update system information and the network bandwidth occupancy information; Obtain historical bandwidth data for a period of time before the current moment, and estimate future bandwidth requirements of the system load based on the historical bandwidth data; The sum of the future bandwidth requirement and the updated network requirement is used as the network requirement of the intermediate system during the update process.

[0011] By adopting the above technical solution, historical update data is collected and network bandwidth usage information is analyzed to estimate the update network requirements of the intermediate system. The historical bandwidth data before the current moment is combined to estimate the future bandwidth requirements of the system load. The sum of the two is used as the network requirement during the update process, thereby accurately evaluating the network resource requirements of the system update, ensuring the reasonable allocation of resources within the total network bandwidth, and improving the reliability of the system update and the utilization of network resources.

[0012] In a preferred example, the present application may be further configured as follows: if the total network bandwidth cannot meet the network demand, the method further includes: determining the number of updateable systems based on the total network bandwidth, the future bandwidth requirement, and the update network requirement; Obtaining the last update time of the intermediate system, and arranging the intermediate systems from earliest to latest according to the last update time to obtain a system list; Starting from the first one in the system list, systems corresponding to the number of updateable systems are determined as systems to be updated.

[0013] By adopting the above technical solution, if the total network bandwidth cannot meet the network update requirements, the number of updateable systems is accurately calculated and sorted according to the last update time of the system. Systems that have not been updated for a long time are updated first. This ensures the efficient use of network resources and balances the update requirements of each system, thereby improving the overall efficiency and fairness of system updates.

[0014] In a preferred example, the present application may be further configured as follows: determining the idle system at the current moment includes: Obtaining the current occupancy status of the room, and classifying the room into occupied rooms and unoccupied rooms based on the room occupancy status; Send reminders of upcoming updates to every room with guests staying; The systems in the rooms with guests that have not received any update feedback from the guests within a preset time period or have received update permission feedback from the guests within the preset time period and the systems in the rooms without guests are combined into an idle system.

[0015] By adopting the above technical solution, combined with the room occupancy situation, update reminders are intelligently sent to rooms with guests staying. Based on the feedback from guests, the systems of rooms with guests staying in the hotel that have not received any objections or permission to update within the specified time and rooms without guests staying in the hotel are integrated into an idle system. This ensures the guest experience while effectively utilizing hotel resources and improving the flexibility and efficiency of system updates.

[0016] In a preferred example, the present application may be further configured as follows: after re-updating the erroneous system, the method further includes: Get the non-updated system; monitoring room occupancy and storage space information of the unupdated system in real time, determining whether the unupdated system is in an idle state based on the room occupancy, and determining whether the unupdated system meets update requirements based on the total network bandwidth and the storage space information; When the non-updated system is in an idle state and the non-updated system meets the update requirement, the non-updated system is updated.

[0017] By adopting the above technical solution, after re-updating the erroneous system, the unupdated systems will continue to be monitored and updated. By comprehensively considering room occupancy, storage space information and total network bandwidth, the unupdated systems that are idle and meet the update requirements will be intelligently judged and updated, thereby ensuring that all systems can be updated in a timely and effective manner, thereby improving the overall quality and efficiency of hotel services.

[0018] In a second aspect, the present application provides a computer program product that employs the following technical solution: A computer program product includes a computer program. When the computer program is executed by a processor, it implements the system update method as described in any one of the first aspects.

[0019] In a third aspect, the present application provides an electronic device, which adopts the following technical solution: one or more processors; Memory; At least one system, wherein the at least one system is stored in a memory and configured to be executed by at least one processor, and the at least one system is configured to: execute the system update method as described in any one of the first aspects.

[0020] In a fourth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solution: A computer-readable storage medium stores a computer program thereon, which, when executed in a computer, causes the computer to execute the system updating method as described in any one of the first aspects.

[0021] In summary, this application has the following beneficial technical effects: In this application, when the user triggers an update instruction, the update process is started immediately in response, and the current idle system is determined. The system can intelligently choose to update when the network load is low and the system is idle, avoiding the impact on the normal operation of the hotel. Determining the system to be updated from the idle system can ensure that the update process is carried out when network resources are sufficient, thereby improving the update efficiency. Parsing the error signal to obtain the error system and the cause of the error can accurately locate the problem, providing strong support for subsequent repair operations. Uninstalling the error system can quickly cut off the source of the fault and avoid the spread of the fault. Executing repair operations based on the cause of the error can accurately solve the problem and improve repair efficiency. Through rapid uninstallation and repair, the impact of the fault on hotel operations and customer experience can be minimized. Re-updating the error system can ensure that the system is restored to the latest state, improving the stability and reliability of the system. From receiving the update instruction to re-updating the error system, a complete update and repair closed loop is formed, which improves the standardization and efficiency of system management. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 This is a flowchart of a system update method provided in an embodiment of the present application; Figure 2 This is a flowchart of a system updating method provided by another embodiment of the present application; Figure 3 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The following is combined with Figure 1 -Attached Figure 3 This application is described in further detail.

[0024] This specific embodiment is merely an explanation of the present application and is not a limitation of the present application. After reading this specification, those skilled in the art may make non-creative modifications to the present embodiment as needed, but as long as they are within the scope of the claims of the present application, they are protected by the patent law.

[0025] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0026] In this document, the term "and / or" simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document, unless otherwise specified, generally indicates an "or" relationship between the related objects.

[0027] It should be noted that in the optional embodiments of the present application, the object information and other related data involved, when the embodiments in the present application are applied to specific products or technologies, need to obtain the permission or consent of the object, and the collection, use and processing of the relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions. In other words, if the embodiments of the present application involve data related to the object, it needs to be obtained through the authorization and consent of the object, the authorization and consent of the relevant departments, and in compliance with the relevant laws, regulations and standards of the country and region. If personal information is involved in the embodiments, the acquisition of all personal information requires the consent of the individual. If sensitive information is involved, the separate consent of the information subject needs to be obtained. The embodiments also need to be implemented with the authorization and consent of the object.

[0028] The present application embodiment provides a system update method, such as Figure 1 As shown, the method provided in the embodiment of the present application is performed by an electronic device, which can be a server or a terminal device, wherein the server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can be a smartphone, a tablet computer, a laptop computer, a desktop computer, etc., but is not limited thereto. The terminal device and the server can be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiment of the present application. The method includes steps S101 to S104, wherein: S101. When an update instruction triggered by a user is received, an idle system at the current moment is determined, a system to be updated is determined from the idle systems, and a system update is triggered.

[0029] Specifically, the electronic device is provided with an interactive interface, through which the administrator triggers a system update command. The currently idle system indicates a system that is currently idle and can be updated immediately. The system type can be a television system, a wireless network system, a smart door lock system, etc.

[0030] Then, the total network bandwidth is obtained. The total network bandwidth represents the network bandwidth utilization threshold. The total network bandwidth can be set by technical personnel based on actual experience and is not specifically limited in this embodiment. The update requirements of each idle system are determined. The update requirements include storage requirements and network requirements. The storage requirement represents the available storage space that will not be exceeded after the system update package is installed. The network requirement represents the network bandwidth that can meet the update during the update process. Systems that meet both storage requirements and network requirements are selected from the idle systems as the systems to be updated. The electronic device sends an update instruction to the selected system to be updated, and the system begins downloading and installing the update package.

[0031] S102 . During the system update process, the error signal sent by the error monitoring module when an error event is monitored is captured, and the error signal is analyzed to obtain the error system and error cause associated with the error event.

[0032] During the update process, the electronic device's built-in error monitoring module continuously monitors error signal messages from various systems. When a system encounters an error during the update process, the system sends an error signal containing the system ID and the cause of the error. By analyzing the received error signals, the faulty system and the cause of the error can be determined. The cause of the error can include power outage, network anomaly, or insufficient storage space. Optionally, the error monitoring module can be a broadcast receiver or other monitoring module customized by technical personnel, and the error signal can be broadcast.

[0033] S103: Uninstall the faulty system and perform a repair operation based on the cause of the error.

[0034] Based on the received ID of the faulty system, the electronic device remotely uninstalls the current version of the faulty system, wherein user data and user settings can be retained during the uninstallation process. A corresponding repair operation can be preset for each type of error cause. Optionally, the repair operation corresponding to a power outage error cause can include sending a prompt signal to prompt a technician to inspect the error. The repair operation corresponding to a network anomaly error cause can include restarting the router. The repair operation corresponding to an insufficient storage space error cause can include clearing unused files. The specific error cause and corresponding repair operation can be set by the technician based on actual experience and are not specifically limited in this embodiment.

[0035] S104: When it is detected that the uninstallation and repair are completed, the faulty system is updated again.

[0036] When the faulty system is uninstalled or repaired, a corresponding error signal may be sent. When the electronic device receives the uninstallation and repair completion error signal, it initiates a re-update process to ensure that the faulty system can be updated to the latest version.

[0037] In this embodiment, when the user triggers an update instruction, the update process is immediately responded to and started. By obtaining the total network bandwidth and determining the current idle system, the system can intelligently choose to update when the network load is low and the system is idle, avoiding the impact on the normal operation of the hotel. The system to be updated is determined from the idle system based on the total network bandwidth, which can ensure that the update process is carried out when network resources are sufficient, thereby improving the update efficiency. The error signal is parsed to obtain the error system and the cause of the error, which can accurately locate the problem and provide strong support for subsequent repair operations. Uninstalling the error system can quickly cut off the source of the fault and avoid the spread of the fault. Executing the repair operation based on the cause of the error can accurately solve the problem and improve the repair efficiency. Through rapid uninstallation and repair, the impact of the fault on hotel operations and customer experience can be minimized. Re-updating the error system can ensure that the system is restored to the latest state, thereby improving the stability and reliability of the system. From receiving the update instruction to re-updating the error system, a complete update and repair closed loop is formed, which improves the standardization and efficiency of system management.

[0038] A possible implementation of the embodiment of the present application is to determine an idle system at a current moment, including: Get the current room occupancy status, and classify the rooms into occupied rooms and unoccupied rooms based on the room occupancy status; Send reminders of upcoming updates to every room with guests staying; The systems in the rooms with guests that have not received any update feedback from the guests within a preset time period or have received the guest's permission to update feedback within a preset time period and the systems in the rooms without guests are combined into an idle system.

[0039] In this embodiment, the electronic device is connected to the hotel management system to obtain the current occupancy status of all rooms. "Guests in" means that there are guests staying in the room at the current moment, and "no guests in" means that there are no guests staying in the room at the current moment.

[0040] For each guest staying in a room, a reminder of an upcoming system update will be sent to the guest via the system, room phone, or text message. This notification should include the time, purpose, possible impact (such as a brief service interruption), and the guest's feedback (allow or decline the update). A preset time period can be set based on actual needs to wait for guest feedback. During this time, the electronic device continuously monitors the guest's feedback, which can include allowing the update, declining the update, or no response (i.e., no feedback within the preset time period). For rooms that receive a guest's "allow update" response within the preset time period, their system will be considered as part of the idle system. For rooms that do not receive a guest response within the preset time period (i.e., no response), it can be assumed that the guest has agreed to the update and the system will be considered as part of the idle system. For rooms that receive a guest's "decline update" response within the preset time period, the system will be considered as not being updated.

[0041] This embodiment intelligently sends update reminders to rooms with guests by combining room occupancy status, and based on guest feedback, integrates the systems of occupied rooms that have not received any objections or permission to update within the specified time with those of rooms without guests into an idle system. This ensures the guest experience while effectively utilizing hotel resources and improving the flexibility and efficiency of system updates.

[0042] A possible implementation of the embodiment of the present application is shown in Figure 2 , determining a system to be updated from idle systems based on the total network bandwidth, including steps S201 to S205, wherein: S201, obtaining total network bandwidth and update package information for system update; S202, obtaining storage space information of idle systems, the storage space information including the occupied storage space of the old system and the currently available storage space of each system; S203, based on the occupied storage space of the target system, the currently available storage space, and the update package information, determining whether the target system meets the storage requirements, the target system being any system in the idle system; S204, determining a system that meets the storage requirements from the idle systems as an intermediate system; S205: Determine the network requirements of the intermediate system during the update process. If the total network bandwidth can meet the network requirements, the intermediate system is used as the system to be updated.

[0043] In this embodiment, the update package information is the data size of the update package. The storage space information can be obtained by querying the configuration information of the idle system. The occupied storage space of the old system is the storage space occupied by the system installed before the update.

[0044] For the target system, the sum of the occupied storage space and the available storage space is calculated as the total available storage space, and the total available storage space is compared with the update package size in the update package information. If the total available storage space is not less than the update package size, it is determined that the target system meets the storage requirements. If the total available storage space is less than the update package size, it is determined that the target system does not meet the storage requirements.

[0045] If the total network bandwidth cannot meet the network requirements of the intermediate systems, a subset of these systems will be selected for update. Both the total network bandwidth and the network requirement represent network bandwidth utilization. The total network bandwidth represents the maximum allowed network bandwidth utilization, while the network requirement represents the estimated network bandwidth utilization for the system update. If the total network bandwidth is not less than the network requirement, it is considered to meet the network requirements. If the total network bandwidth is less than the network requirement, it is considered to not meet the network requirements.

[0046] This embodiment comprehensively considers the system's storage space information and the network requirements during the update process, and intelligently selects systems from idle systems that both meet the storage requirements and can be updated within the total network bandwidth as the objects to be updated, thereby improving the efficiency and success rate of system updates and ensuring the stable update and smooth operation of the hotel system.

[0047] A possible implementation of the embodiment of the present application, determining the network requirements of the intermediate system during the update process, includes: Collecting historical update data, the historical update data including first bandwidth data before updating and historical update system information and second bandwidth data during a historical system update process; Determine network bandwidth usage information caused by historical system updates based on the first bandwidth data and the second bandwidth data; Estimate the update network requirements of the intermediate system based on historical update system information and network bandwidth usage information; Obtain historical bandwidth data for a period of time before the current moment and estimate the future bandwidth demand of the system load based on the historical bandwidth data; The sum of future bandwidth requirements and update network requirements is used as the network requirements of the intermediate system during the update process.

[0048] In this embodiment, the first bandwidth data in the historical update data represents bandwidth usage changes when no system update occurs, and the first average bandwidth usage is obtained by determining the average value of the first bandwidth data. The second bandwidth data represents bandwidth usage changes when a system update occurs, and the second average bandwidth usage is obtained by determining the average value of the second bandwidth data. The first and second bandwidth data correspond to adjacent time periods.

[0049] The difference between the second average bandwidth usage and the first average bandwidth usage is calculated as the network bandwidth usage information corresponding to the historical system update. The historical update system information includes the number of system updates in the historical update (expressed as a historical number) and historical update package information. The number of system updates in the current historical update is expressed as a historical number, and the historical update package information includes the size of the historical update package.

[0050] Furthermore, based on the historical update system information and network bandwidth usage information, the update network requirements of the intermediate system are estimated, including: obtaining the update package information of this update, that is, the update package size, determining the number of intermediate systems as the current number, and the update network requirement = (network bandwidth usage information × update package size × current number) / (historical update package size × historical number).

[0051] Historical bandwidth data from the time period preceding the current moment represents changes in bandwidth usage by loads other than the system. Statistical or machine learning models are used to estimate future bandwidth requirements for these loads during the update process. This future bandwidth requirement is expressed as bandwidth utilization. Technical staff can estimate the duration of this update based on experience; the predicted duration of future bandwidth requirements can be equivalent to the duration of the current update.

[0052] This embodiment collects historical update data and analyzes network bandwidth usage information to estimate the update network requirements of the intermediate system. It also estimates the future bandwidth requirements of the system load in combination with historical bandwidth data before the current moment, and uses the sum of the two as the network requirements during the update process. This accurately assesses the network resource requirements of the system update, ensures the reasonable allocation of resources within the total network bandwidth, and improves the reliability of the system update and the utilization of network resources.

[0053] In one possible implementation of the embodiment of the present application, if the total network bandwidth cannot meet the network demand, the method further includes: Determine the number of systems that can be updated based on total network bandwidth, future bandwidth requirements, and network requirements for updates; Obtain the last update time of the intermediate system, and sort the intermediate systems from earliest to latest according to the last update time to obtain a system list; Starting from the first system in the system list, determine the systems corresponding to the number of updateable systems as the systems to be updated.

[0054] The number of updateable systems = (total network bandwidth - future bandwidth demand) × current number / update network demand. The current number is the number of systems in the intermediate system, ensuring that the network bandwidth occupied by updating the updateable systems is within the total network bandwidth.

[0055] In this embodiment, if the total network bandwidth cannot meet the update network demand, the number of updateable systems is accurately calculated and sorted according to the last update time of the system, and the systems that have not been updated for a long time are updated first. This ensures the efficient use of network resources and balances the update needs of each system, thereby improving the overall efficiency and fairness of system updates.

[0056] In one possible implementation of the embodiment of the present application, before capturing the error signal sent by the error monitoring module when an error event is detected, the method further includes: During the system update process, real-time monitoring of system performance; When there are abnormal performance indicators in the system performance, the system update progress is obtained, and the system that has not completed the update is determined as an error system based on the update progress, and the preset error event type corresponding to the abnormal performance indicator is marked as the error cause; Create an Intent object, set the Action of the Intent object, add the error cause and the ID of the error system into the Intent object to obtain the configured system error signal; The action of the system error signal is matched with the predefined action of the error monitoring module. If the match is successful, the error monitoring module is controlled to receive the system error signal.

[0057] In this embodiment, when the system starts to update, a monitoring process or thread is started to monitor the system performance in real time. The system performance indicators include power status, network connection status and storage space status. The power status can be achieved by monitoring the voltage or current, and the network connection status can be achieved by monitoring whether the connection is interrupted or the network speed. When the voltage or current is interrupted, the power status is used as an abnormal performance indicator. When the network connection is disconnected or the network speed drops sharply, the network connection status is used as an abnormal performance indicator. When the storage space is exceeded, the storage space status is used as an abnormal performance indicator. The correspondence between the abnormal performance indicators and the preset error event types is pre-set, and the correspondence includes: the preset error event type corresponding to the power status is power interruption, the preset error event type corresponding to the network status is network abnormality, and the preset error event type corresponding to the storage space status is insufficient storage space.

[0058] Furthermore, an Intent object is created to send a system error signal. A unique Action identifier is set for the Intent to distinguish different types of system error signals. The error cause and the system ID (such as the device serial number or MAC address) are added to the Intent object as string data.

[0059] The error monitoring module predefines one or more action identifiers, which are matched with the action of the system error signal (i.e., the action of the Intent object). The error signal action is matched with the predefined actions of the error monitoring module. If a match is successful, the error monitoring module is triggered to receive and process the system error signal. In the error monitoring module's onReceive method, data in the Intent object (such as the error cause and the error system ID) can be read and appropriate error handling operations can be performed, such as logging, displaying an error message, or attempting to resume the update process. If the match fails, the error monitoring module ignores the system error signal.

[0060] This embodiment includes the steps of real-time monitoring of system performance, determining the faulty system and the cause of the error, creating and configuring system error signals, and matching and receiving system error signals during the system update process, which together constitute a complete fault monitoring and reporting mechanism. By matching the Action of the system error signal with the predefined Action of the error monitoring module, it can ensure that the received error signal is valid and avoid interference from invalid error signals. This mechanism can promptly detect and report abnormal conditions of the system during the update process, providing strong support for subsequent repair operations, thereby improving the stability and reliability of the system and reducing the impact of faults on hotel operations and customer experience.

[0061] In one possible implementation of the embodiment of the present application, after re-updating the erroneous system, the method further includes: Get the non-updated system; Monitor the room occupancy and storage space information of the unupdated system in real time, determine whether the unupdated system is idle based on the room occupancy, and determine whether the unupdated system meets the update requirements based on the total network bandwidth and storage space information; When the non-updated system is in an idle state and the non-updated system meets an update requirement, the non-updated system is updated.

[0062] In this embodiment, an unupdated system is a system that has not been updated between the time period from when the user-triggered update instruction was received to the current moment. Determining whether any unupdated system is in an idle state includes: obtaining the occupancy status of the room corresponding to the unupdated system, determining the room as occupied or unoccupied based on the occupancy status, determining the unupdated system as idle if the room is unoccupied, and sending an upcoming update reminder to the occupied room if the room is occupied. If no update feedback is received from the guest within a preset time period, or if a guest's permission to update is received within a preset time period, determining the unupdated system as idle.

[0063] Update requirements include storage space requirements and network bandwidth requirements. If a non-updated system meets both requirements, the non-updated system is considered to meet the update requirements. For any non-updated system's storage space requirements, the sum of the old system's occupied storage space and available storage space is calculated as the total available storage space. The total available storage space is then compared with the update package size in the update package information. If the total available storage space is not less than the update package size, the non-updated system is considered to meet the storage requirements. If the total available storage space is less than the update package size, the non-updated system is considered to not meet the storage space requirements.

[0064] For the network requirements of the non-updated systems, the same process as determining the network requirements of the intermediate systems during the update process can be used to determine the systems that meet the storage space requirements. Ultimately, the systems that meet both the storage space and network requirements are selected from the non-updated systems and are idle for the update.

[0065] After re-updating the erroneous system, this embodiment continues to monitor and update the unupdated systems. By comprehensively considering room occupancy, storage space information, and total network bandwidth, it intelligently determines and updates the unupdated systems that are idle and meet the update requirements, thereby ensuring that all systems can be updated in a timely and effective manner, thereby improving the overall quality and efficiency of hotel services.

[0066] An embodiment of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, the contents shown in the aforementioned system update method embodiment are implemented.

[0067] An electronic device is provided in an embodiment of the present application, such as Figure 3 As shown, Figure 3 The electronic device 300 shown includes a processor 301 and a memory 303. The processor 301 and the memory 303 are connected, for example, via a bus 302. Optionally, the electronic device 300 may further include a transceiver 304. It should be noted that in actual applications, the number of transceivers 304 is not limited to one, and the structure of the electronic device 300 does not constitute a limitation on the embodiments of the present application.

[0068] Processor 301 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 301 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0069] Bus 302 may include a path for transmitting information between the above components. Bus 302 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. Bus 302 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 3 Only one thick line is used in the diagram, but it does not mean that there is only one bus or one type of bus.

[0070] The memory 303 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0071] The memory 303 is used to store application code for executing the solution of the present application, and is controlled by the processor 301. The processor 301 is used to execute the application code stored in the memory 303 to implement the content shown in the above system update method embodiment.

[0072] Figure 3 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0073] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer-readable storage medium is run on a computer, the computer can execute the contents shown in the aforementioned system update method embodiment.

[0074] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0075] The above are only some of the implementation methods of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A system update method, characterized in that: include: When receiving an update instruction triggered by a user, determining an idle system at the current moment, determining a system to be updated from the idle systems, and triggering the system update; During the system update process, the error monitoring module captures the error signal sent when an error event is detected, and analyzes the error signal to obtain the error system and error cause associated with the error event; Uninstalling the faulty system and performing a repair operation based on the cause of the error; When it is detected that the uninstallation and the repair are completed, the faulty system is updated again.

2. The system updating method according to claim 1, wherein: Before the error monitoring module captures the error signal sent when an error event is detected, the method further includes: During the system update process, real-time monitoring of system performance; When there is an abnormal performance indicator in the system performance, obtaining the update progress of the system, determining the system that has not completed the update as an error system based on the update progress, and marking the preset error event type corresponding to the abnormal performance indicator as the error cause; Create an Intent object, set the Action of the Intent object, add the error cause and the ID of the error system into the Intent object to obtain a configured system error signal; The Action of the system error signal is matched with the predefined Action of the error monitoring module. If the match is successful, the error monitoring module is controlled to receive the system error signal.

3. The system updating method according to claim 1, wherein: Determining the idle system at the current moment includes: Obtaining the current occupancy status of the room, and classifying the room into occupied rooms and unoccupied rooms based on the room occupancy status; Send reminders of upcoming updates to every room with guests staying; The systems in the rooms with guests that have not received any update feedback from the guests within a preset time period or have received update permission feedback from the guests within the preset time period and the systems in the rooms without guests are combined into an idle system.

4. The system updating method according to claim 1, wherein: After re-updating the erroneous system, the method further includes: Get the non-updated system; monitoring room occupancy and storage space information of the unupdated system in real time, determining whether the unupdated system is in an idle state based on the room occupancy, and determining whether the unupdated system meets update requirements based on the total network bandwidth and the storage space information; When the non-updated system is in an idle state and the non-updated system meets the update requirement, the non-updated system is updated.

5. The system updating method according to claim 1, wherein: The determining of the system to be updated from the idle system comprises: Get the total network bandwidth and update package information for system updates; Acquire storage space information of the idle system, the storage space information including the occupied storage space of the old system and the currently available storage space of each system; Determining whether the target system meets the storage requirement based on the occupied storage space, currently available storage space, and the update package information of the target system, where the target system is any system in the idle system; Determine a system that meets the storage requirement from the idle systems as an intermediate system; The network requirement of the intermediate system during the update process is determined, and if the total network bandwidth can meet the network requirement, the intermediate system is used as a system to be updated.

6. The system updating method according to claim 5, characterized in that: Determining the network requirements of the intermediate system during the updating process includes: Collecting historical update data, the historical update data including first bandwidth data before updating and historical update system information and second bandwidth data during a historical system update process; Determine network bandwidth usage information caused by historical system updates based on the first bandwidth data and the second bandwidth data; estimating the update network demand of the intermediate system based on the historical update system information and the network bandwidth occupancy information; Obtain historical bandwidth data for a period of time before the current moment, and estimate future bandwidth requirements of the system load based on the historical bandwidth data; The sum of the future bandwidth requirement and the updated network requirement is used as the network requirement of the intermediate system during the update process.

7. The system updating method according to claim 6, characterized in that: If the total network bandwidth cannot meet the network requirement, the method further includes: determining the number of updateable systems based on the total network bandwidth, the future bandwidth requirement, and the update network requirement; Obtaining the last update time of the intermediate system, and arranging the intermediate systems from earliest to latest according to the last update time to obtain a system list; Starting from the first one in the system list, systems corresponding to the number of updateable systems are determined as systems to be updated.

8. A computer program product, characterized in that The system comprises a computer program, which implements the steps of the system updating method according to any one of claims 1 to 7 when the computer program is executed by a processor.

9. An electronic device, characterized in that: include: at least one processor; Memory; At least one application, wherein the at least one application is stored in a memory and configured to be executed by at least one processor, and the at least one application is configured to: execute the system updating method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed in a computer, the computer is caused to execute the system updating method according to any one of claims 1 to 7.

Images