Method for managing software maintenance tasks of personnel conveyor system and software maintenance task management system

Abstract

The invention relates to a method for managing software maintenance tasks of a personnel conveyor system (100, 200). The method comprises: obtaining (410) a predefined sequence of software maintenance tasks of the personnel conveyor system (100, 200); activating (420) a digital lock associated with the predefined sequence of software maintenance tasks, wherein the digital lock prevents execution of software maintenance tasks associated with the personnel conveyor system (100, 200) initiated by the unauthenticated user; receiving (430) a software maintenance task execution command from the user device (302), where the software maintenance task execution command is generated by the user device (302) in response to an interaction with the authenticated user (306) through the user device (302); and initiating (440) execution of the predefined sequence of software maintenance tasks in response to receiving the software maintenance task execution command. The invention also relates to a software maintenance task management system (120) of a personnel conveyor system (100, 200).

Description

Technical Field

[0001] This invention generally relates to the technical field of personnel conveyor systems. In particular, this invention relates to managing the software maintenance tasks of personnel conveyor systems. Background Technology

[0002] Personnel conveyor systems, such as elevator systems, typically require several maintenance tasks, including software maintenance. Conveyor systems comprise various components, each equipped with a processor running component-specific application software. During the lifespan of a personnel conveyor system, new features and / or corrections to existing features may be provided in the form of new software versions. To utilize these new features and / or corrected existing features, the application software of one or more components of the personnel conveyor system needs to be updated.

[0003] Software maintenance tasks, such as software updates, can be performed manually on-site, for example, by service technicians. Typically, during a manual update, a maintenance technician enters the personnel conveyor field, removes the personnel conveyor system from normal operation, connects a computing device (such as a laptop) to the personnel conveyor control system, and updates the software. After the update process, the maintenance technician restores the personnel conveyor system to normal operation and checks for correct operation. Software maintenance tasks can also be performed remotely, enabling automation. Remote update processes may require interrupting normal operation of the personnel conveyor system during the update process. However, solutions for managing software maintenance tasks on personnel conveyor systems need to be developed. Summary of the Invention

[0004] The following is a simplified summary of the invention to provide a basic understanding of some aspects of various embodiments of the invention. This summary is not a broad overview of the invention. It is neither intended to identify key or essential elements of the invention nor to depict its scope. The following summary presents only some concepts of the invention in a simplified form, serving as a prelude to a more detailed description of exemplary embodiments of the invention.

[0005] The purpose of this invention is to provide a method and a software maintenance task management system for managing software maintenance tasks of personnel conveyor systems. Another purpose of this invention is to improve the management of software maintenance tasks in personnel conveyor systems.

[0006] The objective of this invention is achieved by the method and software maintenance task management system as defined by the respective independent claims.

[0007] According to a first aspect, a method is provided for managing software maintenance tasks of a personnel conveyor system, the method comprising: acquiring a predefined sequence of software maintenance tasks for the personnel conveyor system; activating a digital lock associated with the predefined sequence of software maintenance tasks, wherein the digital lock prevents execution of software maintenance tasks related to the personnel conveyor system initiated by an unauthenticated user; receiving a software maintenance task execution command from a user device, wherein the software maintenance task execution command is generated by the user device in response to an interaction between the user device and an authenticated user; and in response to receiving the software maintenance task execution command, initiating execution of the predefined sequence of software maintenance tasks.

[0008] The method may further include storing execution status and log data related to the execution of each software maintenance task in a predefined sequence of software maintenance tasks.

[0009] Software maintenance tasks can be arranged into a predefined sequence based on the priority assigned to them.

[0010] One or more software maintenance tasks in a predefined sequence of software maintenance tasks may include at least one subtask.

[0011] Alternatively or additionally, the method may further include: receiving an interrupt command before all software maintenance tasks in a predefined sequence of software maintenance tasks are executed, wherein unexecuted software maintenance tasks in the predefined sequence of software maintenance tasks are set as pending software maintenance tasks; interrupting the execution of pending software maintenance tasks; and preventing the execution of new software maintenance tasks of the personnel conveyor system before executing pending software maintenance tasks.

[0012] The method may further include: receiving an execution continue command from a user equipment to continue executing a pending software maintenance task, wherein the execution continue command is generated by the user equipment in response to an interaction between the user equipment and an authenticated user; and continuing to execute the pending software maintenance task in response to receiving the execution continue command.

[0013] Multiple software maintenance tasks for the personnel conveyor system may include: one or more software update tasks, one or more software subcomponent addition tasks, one or more parameter modification tasks, one or more setting modification tasks, one or more feature implementation tasks, one or more service implementation tasks, and / or one or more service integration tasks.

[0014] According to a second aspect, a software maintenance task management system for a personnel conveyor system is provided, wherein the software maintenance task management system includes: a user device and a control system configured to: acquire a predefined sequence of software maintenance tasks for the personnel conveyor system; activate a digital lock associated with the predefined sequence of software maintenance tasks, wherein the digital lock prevents the execution of software maintenance tasks related to the personnel conveyor system initiated by an unauthenticated user; receive a software maintenance task execution command from the user device, wherein the software maintenance task execution command is generated by the user device in response to an interaction between the user device and an authenticated user; and in response to receiving the software maintenance task execution command, initiate the execution of the predefined sequence of software maintenance tasks.

[0015] The control system can also be configured to store execution status and log data related to the execution of each software maintenance task in a predefined sequence of software maintenance tasks.

[0016] Software maintenance tasks can be arranged into a predefined sequence based on the priority assigned to them.

[0017] One or more software maintenance tasks in a predefined sequence of software maintenance tasks may include at least one subtask.

[0018] Alternatively or additionally, the control system may also be configured to: receive an interrupt command before all software maintenance tasks in a predefined sequence of software maintenance tasks are executed, wherein unexecuted software maintenance tasks in the predefined sequence of software maintenance tasks are set as pending software maintenance tasks; interrupt the execution of pending software maintenance tasks; and prevent the execution of new software maintenance tasks of the personnel conveyor system before executing pending software maintenance tasks.

[0019] The control system can also be configured to: receive an execution continue command from the user equipment to continue the execution of the pending software maintenance task, wherein the execution continue command is generated by the user equipment in response to an interaction between the user equipment and an authenticated user; and in response to receiving the execution continue command, continue the execution of the pending software maintenance task.

[0020] Multiple software maintenance tasks for the personnel conveyor system may include: one or more software update tasks, one or more software subcomponent addition tasks, one or more parameter modification tasks, one or more setting modification tasks, one or more feature implementation tasks, one or more service implementation tasks, and / or one or more service integration tasks.

[0021] Various exemplary and non-limiting embodiments of the invention (with regard to structure and operation) and their additional objects and advantages will be best understood from the following description of specific exemplary and non-limiting embodiments when read in conjunction with the accompanying drawings.

[0022] The verbs “comprising” and “including” are used herein as open-ended restrictions, neither excluding nor requiring the presence of any unlisted features. Unless otherwise expressly stated, the features recited in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of “a” or “an,” i.e., the singular form, throughout the document does not exclude a plurality. Attached Figure Description

[0023] The embodiments of the invention are illustrated in the accompanying drawings by way of example and not limitation.

[0024] Figure 1 An example of a personnel conveyor system is schematically shown, where the personnel conveyor system is an elevator system.

[0025] Figure 2 Another example of a people conveyor system is illustrated schematically, where the people conveyor system is an escalator system.

[0026] Figure 3 An example of a software maintenance task management system for managing software maintenance tasks of a conveyor system is illustrated.

[0027] Figure 4 An example of a method for managing software maintenance tasks on a conveyor system is illustrated.

[0028] Figure 5 This illustration shows another example of a method for managing software maintenance tasks on a conveyor system.

[0029] Figure 6 An example scenario is illustrated, in which the software maintenance task management system also includes at least one other user device.

[0030] Figure 7 An exemplary method for verifying the integration of a personnel conveyor system with a field system is illustrated schematically.

[0031] Figure 8 An example of the components of the control system of a software maintenance task management system is illustrated schematically. Detailed Implementation

[0032] Figure 1Examples of personnel conveyor systems 100 and 200 are schematically shown, wherein the personnel conveyor systems 100 and 200 are elevator systems 100. Elevator system 100 includes at least one elevator car 102, a counterweight 106, and an elevator control system 108. The at least one elevator car 102 is configured to travel along a respective elevator shaft 104 between multiple floors (i.e., landings) 105a-105n. Elevator system 100 can also form elevator groups, i.e., groups of two or more elevator cars 102, each elevator car 102 traveling along a separate elevator shaft 104, the elevator shaft 104 being configured as a unit operation serving the same landings 105a-105n. Elevator system 100 also includes a lifting mechanism system configured to drive at least one elevator car 102 along the respective elevator shaft 104 between floors. The elevator lifting mechanism may include, for example, a motor and traction pulleys 110 for lifting the elevator car 102. For illustrative purposes, Figure 1 Only the traction pulley 110 is shown. The elevator car 102, the hoisting mechanism, and the counterweight 106 are interconnected via the hoisting rope device 112, which is wired via the traction pulley 110 and a plurality of pulleys, which are shown in [the image / description]. Figure 1 Not shown in the diagram. When the traction sheave 110 rotates, the elevator car 102 and counterweight 106 are in motion. The lifting rope device 112 includes at least one lifting rope. In the elevator implementation of the personnel conveyor systems 100, 200, the elevator control system 108 is a conveyor control system. The elevator control system 108 is configured to at least control the operation of the elevator system 100. The elevator control system 108 may be located in the machine room 114 (e.g., Figure 1 (as shown in the example) or located on one of the floors, such as in a machine-room-less elevator system. The elevator control system 108 is communicatively connected to other entities of the elevator system 100. Communication between the elevator control system 108 and other entities of the elevator system 100 can be based on one or more known wired or wireless communication technologies. The implementation of the elevator control system 108 can be accomplished as a standalone control entity or as a distributed control environment among multiple standalone control entities (e.g., multiple servers), thereby providing distributed control resources. The elevator system 100 may also include one or more known elevator-related entities, such as user interface devices, elevator doors, safety circuits and devices, and / or elevator brakes, etc., which are not explicitly shown in the examples. Figure 1 As shown in the image.

[0033] Figure 2Another example of a personnel conveyor system 100, 200 is schematically shown, wherein the personnel conveyor system 100, 200 is an escalator system 200. The escalator system 200 includes a step chain 202 and an escalator control system 204, the step chain 202 being arranged to an endless conveyor band carried by a truss. For illustrative purposes, Figure 2 Only the step chain and escalator control system 204 are shown. However, the escalator system 200 may also include one or more other known escalator-related entities, such as a drive unit including at least one motor, etc. Figure 2 Not shown. The step chain 202 is coupled to at least one motor via a transmission device including at least one chain or belt or the like. The motor can generate rotational force via the transmission device, thereby moving the step chain 202 in a desired direction of travel. In the escalator embodiments of the personnel conveyor systems 100, 200, the escalator control system 204 is a conveyor control system. The escalator control system 204 can be configured to at least partially control the operation of the escalator system 200, for example, to control the movement of the step chain 202. The escalator control system 204 can, for example, be arranged in one of the platforms of the escalator system 200. Figure 2 In the example, the escalator control system 204 is positioned on the bottom platform of the escalator system 200. Alternatively, the escalator control system 204 may be positioned, for example, on the top platform of the escalator system 200. The escalator control system 204 is communicatively connected to other entities of the escalator system 200. Communication between the escalator control system 204 and other entities of the escalator system 200 may be based on one or more known wired or wireless communication technologies. The implementation of the escalator control system 204 may be accomplished as a standalone control entity or as a distributed control environment among multiple standalone control entities (such as multiple servers), thereby providing distributed control resources. The expression "escalator system" as used in this patent application also covers moving walkway systems. Moving walkway systems are otherwise similar to those referenced above. Figure 2 The escalator system 200 is described, but instead of the step chain 202, the moving walk system includes a pallet chain arranged to a circular conveyor belt. Therefore, everything disclosed above with reference to the escalator system 200 also applies to the moving walk system. The moving walk system can be an inclined moving walk system, i.e., a moving walk system configured to transport people and / or goods across an inclined plane, for example, between two platforms. Alternatively, the moving walk system can be a horizontal moving walk system, i.e., a moving walk system configured to transport people and / or goods on a horizontal plane (e.g., between two platforms).

[0034] Conveyor control systems 108 and 204 are communicatively connected to a software maintenance task management system 120 of personnel conveyor systems 100 and 200. The software maintenance task management system 120 is configured to manage software maintenance tasks for personnel conveyor systems 100 and 200. The software maintenance task management system 120 includes user equipment 302 and a control system 304. Conveyor control systems 108 and 204 can, for example, be communicatively connected to the control system 304 of the software task management system 120. Communication between the conveyor control systems 108 and 204 and the control system 304 of the software task management system 120 can be based on one or more known communication technologies, wired or wireless. For example, in Figure 1 In one example, the elevator control system 108 is communicatively connected to the software maintenance task management system 120 (e.g., connected to the control system 304). According to another example, in... Figure 2 In the example, the escalator control system 204 is communicatively connected to the software maintenance task management system 120 (e.g., connected to the control system 304). Figure 3 An example of a software maintenance task management system 120 for managing software maintenance tasks of personnel conveyor systems 100, 200 is schematically shown. Control system 304 can be a local control system and / or a remote control system. The local control system (i.e., the field control system) is located at personnel conveyor systems 100, 200. The remote control system (i.e., the off-site control system) is located away from personnel conveyor systems 100, 200. The implementation of control system 304 can be accomplished as an independent control entity or as a distributed control environment among multiple independent control entities (such as multiple servers), thereby providing distributed control resources. Control system 304 can be, for example, a cloud server, personnel conveyor control system 108, 204, building management control system, local server, service center, maintenance center, or data center. User equipment 302 is communicatively connected to control system 304. Communication between user equipment 302 and control system 304 can be based on one or more known wired or wireless communication technologies. User equipment 302 can be, for example, a personnel conveyor system user interface device or a mobile terminal device. Figure 3In the example, user equipment 302 is a mobile terminal device, but this is only a non-limiting example, and user equipment 302 could also be a user interface device for a personnel conveyor system. A mobile terminal device could be, for example, a mobile phone or a tablet computer. In an elevator system implementation, the personnel conveyor system user interface device could be, for example, an elevator call device or a maintenance panel. An elevator call device could be, for example, a destination call device, such as a destination operation panel (DOP), for providing a destination call from the floor where the destination call device is located to the desired destination floor; a car call device, such as a car operation panel (COP), for providing an elevator car call to drive the elevator car 102 to the desired destination floor; or a floor call device, such as a floor call station (LCS), for providing a floor call to drive the elevator car 102 to the floor where the floor call device is located. In an escalator system implementation, the personnel conveyor system user interface device could be, for example, a maintenance panel. The software maintenance task management system 120 may also include at least one other user device 602a-602d, as will be described later in this application. All the information disclosed above regarding user equipment 302 also applies to at least one other user equipment 602a-602d.

[0035] Next, through reference Figure 4 An example is provided to describe a method for managing software maintenance tasks of conveyor systems 100 and 200 through a software maintenance task management system 120. Figure 4 An example of this method is illustrated in a flowchart.

[0036] At step 410, the control system 304 acquires a predefined sequence of software maintenance tasks for the personnel conveyor systems 100 and 200. This predefined sequence of software maintenance tasks for the personnel conveyor systems 100 and 200 may be defined, for example, by a maintenance task planner unit. The maintenance task planner unit may be part of the control system 304. Alternatively, the maintenance task planner unit may be a separate entity configured to provide the control system 304 with the predefined sequence of software maintenance tasks. The predefined sequence of software maintenance tasks is assigned to a specific user 306, such as a maintenance technician, who is certified to initiate the execution of the predefined sequence of software maintenance tasks. In other words, only uncertified users 306 (e.g., certified maintenance technicians assigned a predefined sequence of software maintenance tasks) are allowed to initiate the predefined sequence of software maintenance tasks for the personnel conveyor systems 100 and 200. Before an certified user 306 can initiate the execution of the predefined sequence of software maintenance tasks for the personnel conveyor systems 100 and 200, the certified user 306 needs to be identified, as described later in this application. The term "software maintenance task" refers throughout this application to editing tasks related to the software of the personnel conveyor systems 100 and 200. However, in this application, internal software tasks of the personnel conveyor software are not considered software maintenance tasks of the personnel conveyor systems 100 and 200. A predefined sequence of software maintenance tasks for the personnel conveyor systems 100 and 200 may include, for example, one or more software update tasks, one or more software subcomponent addition tasks, one or more parameter modification tasks, one or more setting modification tasks, one or more feature implementation tasks, one or more service implementation tasks, and / or one or more service integration tasks. Software maintenance tasks may be arranged into a predefined sequence, for example, based on a priority assigned to the software maintenance tasks. Alternatively or additionally, software maintenance tasks may be arranged into a predefined sequence, for example, based on some other execution order. According to an example, one or more software maintenance tasks in a predefined sequence may include at least one subtask.

[0037] At step 420, control system 304 activates a digital lock associated with a predefined sequence of software maintenance tasks. The digital lock prevents the execution of software maintenance tasks related to personnel conveyor systems 100 and 200 initiated by unauthenticated users (i.e., any user other than authenticated user 306) until the digital lock is deactivated. Therefore, the digital lock prevents any changes to the software of personnel conveyor systems 100 and 200. While the digital lock prevents the execution of software maintenance tasks initiated by unauthenticated users, it allows the execution of a predefined sequence of software maintenance tasks initiated by authenticated user 306, who has been assigned a predefined sequence of software maintenance tasks. Each software maintenance task in the predefined sequence of software maintenance tasks may have a separate digital lock. Alternatively, some software maintenance tasks in the predefined sequence of software maintenance tasks may have a common digital lock, and the remaining software maintenance tasks in the predefined sequence of software maintenance tasks may each have a separate digital lock. According to the example, personnel conveyor control systems 108 and 204 can be digitally locked to prevent unauthorized users from performing software maintenance tasks associated with personnel conveyor control systems 108 and 204 until the digital lock on personnel conveyor control systems 108 and 204 is deactivated. According to another example, one or more functions of personnel conveyor systems 100 and 200 can be digitally locked to prevent unauthorized users from performing software maintenance tasks associated with said one or more functions of personnel conveyor systems 100 and 200 until the digital lock on one or more functions of the personnel conveyor systems is deactivated. If a software maintenance task (referred to as a “main task”) includes one or more subtasks, a separate digital lock can be established for each subtask of the main task. Alternatively, a common digital lock can be established for all subtasks of the main task. Separate digital locks can be established for the main task and its one or more subtasks, where each subtask can have a separate digital lock, all subtasks can have a common digital lock, or some subtasks can each have separate digital locks and some subtasks can have a common digital lock. Alternatively, a common digital lock can be established for the main task and its one or more subtasks.

[0038] At step 430, the control system 304 receives a software maintenance task execution command from the user equipment 302. The software maintenance task execution command is generated by the user equipment 302 in response to an interaction between the user equipment 302 and an authenticated user 306 assigned a predefined sequence of software maintenance tasks. For example, the user equipment 302 may generate the software maintenance task execution command in response to user input received by the authenticated user 306, for example, via a user interface of the user equipment 302. The user equipment 302 may include, for example, a display, such as a touchscreen, showing a list of predefined sequences of software maintenance tasks. The authenticated user 306 can select a software maintenance task to be performed from the list. In response to the selection of a maintenance task to be performed by the authenticated user 306, the user equipment 302 can generate the software maintenance task execution command. The authenticated user 306 can select all software maintenance tasks in the predefined sequence of software maintenance tasks to be performed at once. In this case, the generated software maintenance task execution command includes commands for performing all software maintenance tasks in the predefined sequence of software maintenance tasks. Alternatively, the authenticated user 306 can select one or more software maintenance tasks from a predefined sequence of software maintenance tasks to be executed at once. In this case, the generated software maintenance task execution command includes a command to execute the selected software maintenance task from the predefined sequence of software maintenance tasks, and after executing the selected software maintenance task, the authenticated user 306 can again select one or more software maintenance tasks from the predefined sequence of software maintenance tasks to be executed, until all predefined sequences of software maintenance tasks have been executed. Identification of the authenticated user 306 is required before user input can be entered. Identification can be based, for example, using a key card, tag, and / or identification code, such as a personal identification number (PIN) or ID number. Identification of the authenticated user 306 can be performed, for example, via user equipment 302.

[0039] At step 440, the control system 304 initiates the execution of a predefined sequence of software maintenance tasks in response to receiving a software maintenance task execution command from the user equipment 302. During at least a portion of the execution of the predefined sequence of software maintenance tasks, the personnel conveyor systems 100 and 200 may need to cease service, i.e., the operation of the personnel conveyor systems 100 and 200 may need to be interrupted. Whether the personnel conveyor systems 100 and 200 need to cease service during at least a portion of the execution of the predefined sequence of software maintenance tasks may depend, for example, on the criticality level of the software maintenance task to be performed. For example, if the software maintenance task belonging to the predefined sequence of software maintenance tasks involves a security-related part of the software, then the personnel conveyor systems 100 and 200 need to cease service at least during the execution of the software maintenance task. However, if the software maintenance task belonging to the predefined sequence of software maintenance tasks (e.g., a container software approach) is independent of the software, then it is not necessary to cease service of the personnel conveyor systems 100 and 200 during the execution of the software maintenance task. It is also possible that the security-related parts of the software cannot be modified, for example, by regulations, and that software maintenance tasks involving the security-related parts of the software (such as adding features) need to be performed as additional software parts that do not affect the operation of the security-related parts of the software.

[0040] According to the example, the control system 304 may also store execution status and log data related to the execution of each software maintenance task in a predefined sequence of software maintenance tasks. The execution status and log data may include, for example, data representing the status of the personnel conveyor systems 100, 200 before the execution of the software maintenance task (e.g., the version of the previous software maintenance task, process status, who started the execution, what software maintenance task will be executed, the start time and / or end time of the software maintenance task, etc.) and / or the status of the personnel conveyor systems 100, 200 after the execution of the software maintenance task (e.g., the version and / or process status of the subsequent software maintenance task, etc.). The execution status and log data may be stored, for example, in the memory unit 820 of the control system 304 and / or in an external memory unit (e.g., a database). The storage of the execution status and log data enables subsequent inspection of the executed software maintenance tasks. For example, the stored execution status and log data may be used for simulation and / or playback purposes in a digital twin implementation, as described later in this application.

[0041] Figure 5 Another example of a method for managing software maintenance tasks of conveyor systems 100 and 200 is illustrated schematically. According to... Figure 5The example method also includes a software maintenance task execution interruption function. If a predefined sequence of software maintenance tasks cannot be completed in one go, the software maintenance task execution interruption function allows the execution of the predefined sequence of software maintenance tasks to be interrupted and resumed later. The resumption of the predefined sequence of software maintenance tasks after interruption can be initiated by the same authenticated user 306 from whom the initial software maintenance task execution command was received in step 430, or by another authenticated user 604, as described later.

[0042] At step 510, the control system 304 may receive an interrupt command before all software maintenance tasks in a predefined sequence of software maintenance tasks are executed. Unexecuted software maintenance tasks in the predefined sequence are set as pending software maintenance tasks. The interrupt command may be received, for example, from user equipment 302. The interrupt command may be generated by user equipment 302 in response to interaction between user equipment 302 and authenticated user 306. For example, user equipment 302 may generate a software maintenance task execution command in response to user input received by authenticated user 306, for example, via user interface of user equipment 302. Alternatively, the interrupt command may be generated, for example, by the control system 304 itself when encountering an unsolvable problem. In this case, the execution of software maintenance tasks in the predefined sequence of software maintenance tasks needs to be stopped to a safe state, where the software maintenance tasks already executed are known to be functioning correctly with the personnel conveyor systems 100, 200. These safety conditions (i.e., safety steps) may be predefined, for example, by the maintenance task planner unit.

[0043] At step 520, the control system 304 may interrupt the execution of the pending software maintenance task in response to receiving an interrupt command. Operation of the personnel conveyor systems 100 and 200 may continue during the interruption of the pending software maintenance task. For example, the personnel conveyor systems 100 and 200 may operate in a compatibility mode.

[0044] At step 530, in response to receiving an interrupt command, the control system 304 further prevents the execution of new software maintenance tasks for the personnel conveyor systems 100 and 200 before executing pending software maintenance tasks. The execution of new software maintenance tasks for the personnel conveyor systems 100 and 200 can be digitally prevented until the pending software maintenance tasks are executed. For example, if there is a pending software maintenance task related to an entity or function of the personnel conveyor systems 100 and 200, and it is known that this entity or function interacts with another entity or function of the personnel conveyor systems 100 and 200, and the software maintenance task is suspended to a state known not to be final, then new software maintenance tasks for the dependent entity or function can be digitally prevented until the pending software maintenance tasks are completed.

[0045] At step 540, the control system 304 may receive an execution continue command from user equipments 302, 602a-602d to continue executing the pending software maintenance task. The execution continue command is generated by user equipment 302 in response to interaction between user equipments 302, 602a-602d and authenticated users 306, 604. For example, user equipments 302, 602a-602d may generate the software maintenance task execution command in response to user input received by authenticated users 306, 604, for example, via the user interface of user equipments 302, 602a-602d. Identification of authenticated users 306, 604 is required before user input can be input. Identification of authenticated users 306, 604 can be performed as described above with reference to step 430. The user equipments 302, 602a-602d from which the execution continue command is received at step 540 may be the same user equipment 302 from which the initial software maintenance task execution command was received at step 430 discussed above. Alternatively, the user devices 302, 602a-602d that receive the execute continue command from them at step 540 may be another user device 602a-602d, different from the user device 302 that receives the initial software maintenance task execution command from them at step 430 discussed above. The authenticated users 306, 604 that interact with user devices 302, 602a-602d to generate the execute continue command may be the same authenticated user 306 that interacted with user device 302 at step 430 discussed above to generate the initial software maintenance task execution command. Alternatively, the authenticated users 306, 604 that interact with user devices 302, 602a-602d to generate the execute continue command may be another authenticated user 604, different from the authenticated user 306 that interacted with user device 302 at step 430 discussed above to generate the initial software maintenance task execution command. In order for other certified users 604 to continue performing pending software maintenance tasks, it may be necessary to reassign the pending software maintenance tasks to other certified users 604. The possibility of transferring pending software maintenance tasks from the initial uncertified user 306 to another uncertified user 604 allows the pending software maintenance tasks to continue even if the initial uncertified user 306 is unable or unwilling to continue performing the pending software maintenance tasks.

[0046] Figure 6 An example scenario is shown where, in addition to user equipment 302, the software maintenance task management system 120 also includes at least one other user equipment 602a-602d. Figure 6In the example, the software maintenance task management system 120 includes user equipment 302 (e.g., a first user equipment) and four other user equipments 602a-602d. However, the software maintenance task management system 120 is not limited to this, and it may include any other number of other user equipments 602a-602d. Figure 6 In the example, the first user equipment 302 is a mobile device, and the other user equipment 602a-602d are DOPs. However, at least one or all of the other user equipment 602a-602d can also be mobile devices or other conveyor system user interface devices. Figure 6 In an example scenario, the software maintenance task execution command (step 430) is generated by the first user equipment 302 in response to interaction with an authenticated user 306 (e.g., the first authenticated user) to whom a predefined sequence of software maintenance tasks has been assigned via the user equipment 302, and transmitted to the control system 304 as described above. Furthermore, in Figure 6 In an example scenario, in response to receiving the interrupt command as described above, the execution of the pending software maintenance task is interrupted, and in response to the interaction between the second user equipment 602a and another authenticated user 604 (e.g., the second authenticated user), the other user equipment 602a-602d (e.g., the second user equipment 602a) generates an execution continue command.

[0047] At step 550, the control system 304 may continue to perform the pending software maintenance task in response to receiving the execute continue command.

[0048] After each software maintenance task in a predefined sequence of software maintenance tasks, authenticated users 306 and 604 can observe the status of personnel conveyor systems 100 and 200. If the status of personnel conveyor systems 100 and 200 is not nominal, i.e., the behavior of personnel conveyor systems 100 and 200 does not conform to expectations or plans, authenticated users 306 and 604 can interact with the corresponding user devices 302 and 602a-602d to generate a rollback start command to the control system 304 to initiate at least a partial rollback process of the executed software maintenance task to restore the previous version of the software maintenance task, wherein the behavior of the personnel conveyor system conformed to expectations or plans. In response to receiving the rollback start command, the control system 304 can initiate at least a partial rollback process. After the at least partial rollback process, authenticated users 306 and 604 can attempt to restart the execution of the software maintenance task, similar to what is described above with reference to steps 430-440. Alternatively, authenticated users 306 and 604 can interact with the corresponding user devices 302 and 602a-602d to generate an execution completion command to the control system 304. If the software maintenance task includes at least one subtask, the state of the personnel conveyor system 100 and 200 can be observed after the entire software maintenance task is executed, or after one or more subtasks of at least one subtask of the software maintenance task, or after each subtask of at least one subtask of the software maintenance task. According to the example, if the execution of the next software maintenance task in the predefined sequence of the software maintenance task is not nominal, the execution of the next software maintenance task in the predefined sequence of the software maintenance task may not be allowed. If the state of the personnel conveyor 100 and 200 is nominal, authenticated users 306 and 604 can accept the execution of the software maintenance task by interacting with the corresponding user devices 302 and 602a-602d to generate an execution completion command to the control system 304. In response to receiving an execution completion command from user equipment 302, 602a-602d, if the maintenance task has a separate digital lock, the control system 304 may release (i.e., deactivate) the digital lock associated with the software maintenance task. Otherwise, in response to receiving an execution completion command from user equipment 302, 602a for each software maintenance task belonging to a common digital lock, the control system 304 may release the common digital lock.

[0049] The present invention has been described above, enabling a predefined sequence of software maintenance tasks to be executed directly within personnel conveyor systems 100 and 200. However, during the execution of the predefined sequence of software maintenance tasks as described above, personnel conveyor systems 100 and 200 may need to stop service. According to an example, before actually executing the predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200, the predefined sequence of software maintenance tasks can first be executed in a digital twin of personnel conveyor systems 100 and 200. The digital twin of personnel conveyor systems 100 and 200 represents a digital representation of personnel conveyor systems 100 and 200. The digital twin enables the simulation and testing of personnel conveyor systems 100 and 200. When a predefined sequence of software maintenance tasks is executed in the digital twins of personnel conveyor systems 100 and 200, personnel conveyor systems 100 and 200 remain operational, and a digital lock activated at step 420 prevents the execution of new software maintenance tasks for personnel conveyor systems 100 and 200, and thus prevents any changes to the software of personnel conveyor systems 100 and 200.

[0050] An authenticated user 306 can initiate the execution of a predefined sequence of software maintenance tasks in the digital twin, similar to the execution of the predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200 described above (steps 430-440). After executing the predefined sequence of software maintenance tasks in the digital twin, the authenticated user 306 can observe the state of the digital twin. If the state of the digital twin is not ideal after executing the predefined sequence of software maintenance tasks, the executed software maintenance task can be cancelled without interfering with the operation of personnel conveyor systems 100 and 200. If the state of the digital twin is ideal after executing the predefined sequence of software maintenance tasks, the authenticated user 306 can interact with user equipment 302 to generate a software maintenance task execution command for control system 304, as described above in step 430. In response to receiving the software maintenance task execution command from user equipment 302, control system 304 initiates the execution of the predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200, as described above in step 440. Before starting the execution of a predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200, the operation of personnel conveyor systems 100 and 200 needs to be stopped during the execution of the predefined sequence of software maintenance tasks, as described above. One or more of the additional method steps described above can also be applied to this embodiment, wherein the predefined sequence of software maintenance tasks is first executed in a digital twin of personnel conveyor systems 100 and 200 before the actual execution of the predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200. Testing using a digital twin allows verification of the correct operation of personnel conveyor systems 100 and 200 after the execution of the predefined sequence of software maintenance tasks and before the actual execution of the predefined sequence of software maintenance tasks in personnel conveyor systems 100 and 200. This also minimizes the downtime of personnel conveyor systems 100 and 200 due to the execution of the predefined sequence of software maintenance tasks. Where applicable, digital twins can also be used to simulate the operation of the actual software of the actual personnel conveyor systems 100 and 200 in use by utilizing sensor data from the actual personnel conveyor systems 100 and 200. For example, by utilizing sensor data from the actual personnel conveyor systems 100 and 200 in the digital twin, the functionality of the software can be tested after a predefined sequence of software maintenance tasks is performed. The functionality of the software in the digital twin can be tested in parallel with the functionality of the actual software of the personnel conveyor systems 100 and 200. Differences between the functionality of the software in the digital twin and the functionality of the actual software during certain events can be reported to, for example, user interface device 302 and / or a cloud server for further analysis.

[0051] The digital twins of personnel conveyor systems 100 and 200 can also be used for simulation and / or playback purposes. Simulation and / or playback can be used, for example, for training purposes of maintenance personnel. For example, stored execution status and log data related to the software maintenance tasks performed can be used in the simulation and / or playback. Alternatively or additionally, the digital twins of personnel conveyor systems 100 and 200 can also be used to test integration with field systems (e.g., third-party field systems), such as application programming interface (API) integration, before applying the integration to the actual personnel conveyor systems 100 and 200, without affecting the operation of personnel conveyor systems 100 and 200. Some non-limiting examples of third-party field system integration include building management system (BMS) integration, access control system integration, fire service integration, and / or evacuation system integration. Figure 7 An exemplary method for verifying the integration of personnel conveyor systems 100, 200 with field systems is shown.

[0052] At step 710, the control system 304 obtains an integration test request. The integration test request may be obtained, for example, from a field system (e.g., a third-party field system).

[0053] At step 720, control system 304 applies the integration with the field system in the digital twin of personnel conveyor systems 100 and 200 to test and verify the operation of the integration. Since the testing is performed in the digital twin, the testing does not affect the operation of personnel conveyor systems 100 and 200. If applicable, legacy integrations can remain in use in personnel conveyor systems 100 and 200 during testing and verification. The use of digital twins enables testing of integrations without building separate field test setups and taking personnel conveyor systems 100 and 200 out of service. This also minimizes downtime for personnel conveyor systems 100 and 200.

[0054] At step 730, after testing and verifying in the digital twin that the integration with the field system operates as expected, the control system 304 can activate the digital lock associated with the integration with the field system in the personnel conveyor systems 100, 200.

[0055] At step 740, the control system 304 can apply integration with field systems in the personnel conveyor systems 100 and 200, while digital lockout prevents any changes to the personnel conveyor systems 100 and 200. This is particularly useful when applying critical integrations, such as access control system integration.

[0056] Figure 8An example of components of the control system 304 of a software maintenance task management system 120 is schematically shown. The control system 304 may include: a processing unit 810 including one or more processors, a memory unit 820 including one or more memories, a communication unit 830 including one or more communication devices, and a possible user interface (UI) unit 840. The aforementioned components may be communicatively connected to each other, for example, via a communication bus. The memory unit 820 may store and maintain portions of a computer program (code) 825, as well as data such as a predefined sequence of software maintenance tasks, pending software maintenance tasks, execution status and log data, or any other data. The computer program 825 may include instructions that, when executed by the processing unit 810 of the control system 304, cause the processing unit 810 and thus the control system 304 to perform desired tasks, such as one or more of the method steps described above. Therefore, the processing unit 810 may be arranged to access the memory unit 820 and retrieve any information from and store any information in the memory unit 820. For clarity, the term "processor" herein refers to any unit suitable for processing information and controlling the operation of the control system 304, as well as other tasks. These operations can also be implemented using a microcontroller solution with embedded software. Similarly, memory unit 820 is not limited to a particular type of memory, but any type of memory suitable for storing the described multiple pieces of information can be applied within the context of this invention. Communication unit 830 provides one or more communication interfaces for communicating with any other unit (e.g., user equipment 302, at least one other user equipment 602a-602d, personnel conveyor control systems 108, 204, one or more databases) and / or with any other unit. User interface unit 840 may include one or more input / output (I / O) devices for receiving user input and output information, such as buttons, keyboards, touchscreens, microphones, speakers, displays, etc. Computer program 825 may be a computer program product that can be included in a tangible non-volatile (non-transitory) computer-readable medium carrying the computer program code 825 embodied therein for use with the computer (i.e., control system 304).

[0057] The specific examples provided in the description above should not be construed as limiting the applicability and / or interpretation of the appended claims. Unless otherwise expressly stated, the list and groups of examples provided in the description above are not exhaustive.

Claims

1. A method for managing software maintenance tasks of a conveyor system (100, 200), the method comprising: Obtain a predefined sequence of software maintenance tasks for the personnel conveyor system (100, 200) described in (410); Activate (420) a digital lock associated with a predefined sequence of the software maintenance tasks, wherein the digital lock prevents the execution of software maintenance tasks associated with the personnel conveyor systems (100, 200) initiated by unauthenticated users; Receive (430) a software maintenance task execution command from user equipment (302), wherein the software maintenance task execution command is generated by user equipment (302) in response to an interaction between user equipment (302) and an authenticated user (306); and In response to receiving the software maintenance task execution command, (440) the execution of the predefined sequence of the software maintenance task is initiated.

2. The method according to claim 1, further comprising: After each software maintenance task in the predefined sequence of the software maintenance tasks is executed, the execution status and log data related to the execution of the software maintenance task are stored.

3. The method according to any one of the preceding claims, wherein, The software maintenance tasks are arranged into the predefined sequence based on the priority assigned to them.

4. The method according to any one of the preceding claims, wherein, One or more software maintenance tasks in the predefined sequence of the software maintenance tasks include at least one subtask.

5. The method according to any one of the preceding claims further comprises: Receive (510) interrupt command before all software maintenance tasks in the predefined sequence of the software maintenance tasks are executed, wherein unexecuted software maintenance tasks in the predefined sequence of the software maintenance tasks are set as pending software maintenance tasks. Interrupt (520) the execution of the pending software maintenance task; and Prevent (530) from executing a new software maintenance task for the personnel conveyor system before executing the pending software maintenance task.

6. The method according to claim 6, further comprising: Receive (540) an execution continue command from user equipment (302, 602a-602d) to continue executing the pending software maintenance task, wherein the execution continue command is generated by the user equipment (302, 602a-602d) in response to an interaction between the user equipment (302, 602a-602d) and an authenticated user (306, 604); and In response to receiving the execution continue command, the execution of the pending software maintenance task continues (550).

7. The method according to any one of the preceding claims, wherein, The multiple software maintenance tasks of the personnel conveyor system (100, 200) include: one or more software update tasks, one or more software sub-component addition tasks, one or more parameter modification tasks, one or more setting modification tasks, one or more feature implementation tasks, one or more service implementation tasks, and / or one or more service integration tasks.

8. A software maintenance task management system (120) for a personnel conveyor system (100, 200), the software maintenance task management system (120) comprising: User equipment (302), and The control system (304) is configured as follows: Obtain a predefined sequence of software maintenance tasks for the personnel conveyor systems (100, 200); Activate a digital lock associated with a predefined sequence of the software maintenance tasks, wherein the digital lock prevents the execution of software maintenance tasks associated with the personnel conveyor systems (100, 200) initiated by unauthenticated users; Receive a software maintenance task execution command from the user equipment (302), wherein the software maintenance task execution command is generated by the user equipment (302) in response to an interaction between the user equipment (302) and an authenticated user (306); and In response to receiving the software maintenance task execution command, the execution of a predefined sequence of the software maintenance task is initiated.

9. The software maintenance task management system (120) according to claim 8, wherein, The control system (304) is further configured to store execution status and log data related to the execution of the software maintenance task after each software maintenance task in a predefined sequence of software maintenance tasks is executed.

10. The software maintenance task management system (120) according to claim 8 or 9, wherein, The software maintenance tasks are arranged into the predefined sequence based on the priority assigned to them.

11. The software maintenance task management system (120) according to any one of claims 8 to 10, wherein, One or more software maintenance tasks in the predefined sequence of the software maintenance tasks include at least one subtask.

12. The software maintenance task management system (120) according to any one of claims 8 to 11, wherein, The control system (304) is also configured to: An interrupt command is received before all software maintenance tasks in a predefined sequence of the software maintenance tasks are executed, wherein unexecuted software maintenance tasks in the predefined sequence of the software maintenance tasks are set as pending software maintenance tasks. Interrupt the execution of the pending software maintenance task; and Before executing the pending software maintenance task, prevent the execution of new software maintenance tasks for the personnel conveyor systems (100, 200).

13. The software maintenance task management system (120) according to claim 12, wherein, The control system (304) is also configured to: Receive an execution continue command from user equipment (302, 602a-602d) to continue executing the pending software maintenance task, wherein the execution continue command is generated by the user equipment (302, 602a-602d) in response to an interaction between the user equipment (302, 602a-602d) and an authenticated user (306, 604); and In response to receiving the execution continue command, the execution of the pending software maintenance task continues.

14. The software maintenance task management system (120) according to any one of claims 8 to 13, wherein, The multiple software maintenance tasks of the personnel conveyor system (100, 200) include: one or more software update tasks, one or more software sub-component addition tasks, one or more parameter modification tasks, one or more setting modification tasks, one or more feature implementation tasks, one or more service implementation tasks, and / or one or more service integration tasks.

Images