Pressure steam sterilizer based on internet of things and remote control management system thereof

Abstract

The application relates to the technical field of medical devices, and provides a pressure steam sterilizer based on Internet of Things and a remote control management system thereof. The sterilizer comprises a sterilizer body, an Internet of Things communication unit and a cloud platform. A local controller of the sterilizer body binds sterilization program parameters issued by the cloud platform and a traceable number of this cycle to generate a parameter contract when a sterilization process is started. A freezing request is sent to the cloud platform before entering a non-backtracking stage, and the sterilization program parameters bound in the cycle are set to a freezing state. In the non-backtracking stage, parameter updates issued by the cloud platform are rejected, and the parameter contract is executed. The application has a unique version belonging in time sequence for parameters executed in each sterilization cycle, solves a time sequence race problem between remote parameter issuing and a local sterilization process, and enables semantic consistency of sterilization cycle records across communication breakpoints to be verified.

Description

Technical Field

[0001] This application relates to the field of medical device technology, and in particular to an Internet of Things-based pressure steam sterilizer and its remote control and management system. Background Technology

[0002] Pressure steam sterilizers are core equipment for sterilizing instruments in medical institutions, laboratories, and the pharmaceutical industry. They utilize the latent heat of saturated pressurized steam to denature and inactivate microbial proteins, thereby achieving sterilization. Based on the sterilization principle, the sterilization process of a pulsed vacuum pressure steam sterilizer typically includes a preheating stage, a pulsed vacuum stage, a heating stage, a sterilization maintenance stage, an exhaust stage, and a drying stage. Among these, the pulsed vacuum stage gradually dilutes and removes the air from the sterilization chamber and the packaging of the items being sterilized through repeated vacuuming and steam injection.

[0003] The physical nature of the sterilization process dictates its irreversibility. On one hand, the process state of sterilization is irreversible: at the end of the pulsating vacuum phase, the air in the sterilization chamber and the packaging of the sterilized items has been substantially expelled, and saturated vapor has entered and penetrated the packaging. This state is a prerequisite for subsequent sterilization; once broken, it cannot be restored through subsequent operations. On the other hand, the sterilization intensity of the sterilization process is irreversible: the sterilization intensity of the sterilization maintenance phase is characterized by the combination of sterilization temperature and maintenance time, and its sterilization effect is measured by the F0 control management system value (i.e., the equivalent sterilization time at the control management system's reference temperature of 121℃); once the sterilization maintenance phase begins, the accumulated sterilization intensity becomes a fait accompli of that sterilization cycle and cannot be supplemented or reversed through subsequent operations. Therefore, the interval from the start of the heating phase to the end of the sterilization maintenance phase constitutes the irreversible interval of the sterilization process.

[0004] To improve the reliability and traceability of the sterilization process, existing technologies combine pressure steam sterilizers with Internet of Things (IoT) technology. These solutions typically incorporate data acquisition and communication modules on the sterilizer itself, uploading parameters such as temperature and pressure during sterilization to a cloud platform. The cloud platform then provides user clients with remote monitoring, data storage, fault diagnosis, and traceability reports. Simultaneously, the cloud platform can also send sterilization program parameters to the sterilizer, allowing medical institutions to adjust the sterilization intensity based on the type of items being sterilized.

[0005] However, the aforementioned prior art has the following technical problems: First, there is a timing race condition between the sterilization program parameters remotely issued and the sterilization process being executed locally. The issuance of sterilization program parameters by the cloud platform and the execution of the sterilization process by the sterilizer are two parallel processes coupled through a communication link. In actual use in medical institutions, users may adjust the sterilization program parameters via a client during sterilizer operation, but the timing of this parameter issuance is not related to the stage of the sterilization process. When the issuance time of the sterilization program parameters falls within the irreversible interval from the start of the heating phase to the end of the sterilization maintenance phase, if the local controller executes the parameter update, the sterilization cycle will exhibit a situation where "some stages are executed with the old parameters, and some stages are executed with the new parameters," resulting in the sterilization intensity of this sterilization cycle being unable to be characterized by any single parameter version. The consequence of this is that the sterilization program parameters displayed to the user by the client, the sterilization program parameters actually executed by the local controller, and the sterilization program parameters recorded in the traceability report may be inconsistent, thereby rendering the traceability record of the sterilization process ineffective as evidence of sterilization quality.

[0006] Secondly, existing technologies fail to address the timing decision-making issue in sterilization processes under communication interruption conditions. Current technologies primarily handle communication interruptions through data caching and retransmission. This involves a local cache module temporarily storing sterilization process parameters collected during the network outage, which are then retransmitted to the cloud platform in chronological order after communication is restored. However, the sterilization process itself is an unskippable and incompressible physical process: temperature and pressure within the sterilization chamber progress according to a predetermined process curve, steam is continuously injected and discharged, and the process objectives corresponding to each stage cannot be deleted or compressed on the timeline. Once a stage is skipped, its corresponding process objective cannot be compensated for by subsequent stages. Therefore, when a communication interruption occurs, the core issue facing the local controller is not "whether data needs to be cached," but rather "whether the sterilization process should continue, be delayed, or be terminated," and, if it continues, which parameter version should be used as the execution basis. Existing caching and retransmission solutions do not address this decision-making problem.

[0007] Third, existing technologies fail to address the semantic consistency issue in sterilization cycle records across communication interruptions. When the parameter upload process of a sterilization cycle is split into a pre-interruption and post-interruption segment due to a communication interruption, existing technologies can only guarantee that the two data segments have not been tampered with at the content level, but cannot prove that the two data segments correspond to the same sterilization procedure parameter version. If the two data segments correspond to different sterilization procedure parameter versions, even if the data content is complete and unaltered, the records of the sterilization cycle are still semantically inconsistent, and existing technologies cannot identify this situation afterward.

[0008] It should be noted that the aforementioned technical problems are not caused by the mechanical structure or thermal parameters of the sterilizer itself, but rather by the coupling of the time rigidity of the sterilization process and the time uncertainty of the communication link during the evolution of the sterilizer from local independent operation to cloud-based collaborative control. Existing dual-mode redundant transmission schemes aim to solve the availability problem of the communication link, and load identification and parameter adaptation schemes aim to solve the selection problem of sterilization program parameters; neither of these addresses the issue of defining the effective boundaries of the sterilization program parameters in terms of timing. Summary of the Invention

[0009] This application provides an IoT-based pressure steam sterilizer and its remote control and management system to solve the technical problems in the prior art, such as the existence of timing race between the sterilization program parameters remotely issued and the sterilization process executed locally, the lack of timing decision-making mechanism for the sterilization process under communication interruption conditions, and the inability to verify the semantic consistency of sterilization cycle records across communication breakpoints.

[0010] To achieve the above objectives, this application provides the following technical solution: Firstly, this application proposes a remote control and management system for a pressure steam sterilizer based on the Internet of Things, comprising: A local controller is used to control the sterilization process, wherein the sterilization process includes a preheating stage, a pulsed vacuum stage, a heating stage, a sterilization maintenance stage, an exhaust stage, and a drying stage. An Internet of Things (IoT) communication unit, connected to the local controller, is used to collect sterilization process parameters; The cloud platform communicates with the IoT communication unit and with the client, and is used to store sterilization program parameters and distribute them. When the sterilization process is started, the local controller binds the sterilization program parameters issued by the cloud platform with the traceability number of the current sterilization cycle to generate a parameter contract for the current sterilization cycle. The local controller sends a freeze request to the cloud platform before the sterilization process enters the irreversible stage; The irreversible phase is the period from the start of the heating phase to the end of the sterilization maintenance phase; In response to the freeze request, the cloud platform sets the sterilization program parameters bound to this sterilization cycle to a frozen state. During the irreversible phase, the local controller refuses to apply the sterilization program parameter updates issued by the cloud platform and executes the irreversible phase in accordance with the parameter contract.

[0011] Optionally, in one possible implementation, the local controller maintains a time budget at the boundaries of each stage of the sterilization process; wherein, The time budget is the estimated remaining time for the current stage minus the minimum execution time for the current stage; The estimated remaining time is the duration from the current moment until the end of the current phase; The minimum execution time is the shortest time required from the current moment to enable the current stage to achieve its technological objective. When the local controller detects a communication interruption, it performs the following decision: If a communication interruption occurs during a rollback phase and the time budget is greater than zero, the local controller waits for the communication link to be restored within the time budget, and continues the sterilization process according to the parameter contract after a timeout; wherein... The reversible phase includes the preheating phase, the pulsating vacuum phase, the exhaust phase, and the drying phase; the waiting is achieved by extending the execution duration of the current phase, and the extended duration does not exceed the time budget; When a communication interruption occurs during the irreversible phase, the local controller does not wait for the communication link to be restored and directly continues to execute the sterilization process according to the parameter contract; When the time budget is less than or equal to zero, the local controller continues to execute the sterilization process directly according to the parameter contract.

[0012] Optionally, in one possible implementation, the IoT communication unit includes a local cache module; wherein, The local cache module caches the sterilization process parameters on a sterilization cycle basis. The local cache module records the collection timestamps and corresponding sterilization process stage markers for the cached sterilization process parameters. After communication is restored, the IoT communication unit retransmits the cached sterilization process parameters to the cloud platform in the order of the collected timestamps, and deletes the corresponding cached sterilization process parameters after the cloud platform confirms receipt. When the communication is interrupted again during the retransmission of the sterilization process parameters, the local cache module records the retransmission breakpoint and resumes retransmission from the breakpoint after communication is restored.

[0013] Optionally, in one possible implementation, the IoT communication unit further includes a dual-mode communication module and an encryption module; The dual-mode communication module supports communication with the cloud platform via a first communication network and a second communication network; wherein... The first communication network is a wireless local area network, and the second communication network is a cellular communication network; When the dual-mode communication module detects that the signal quality of the current communication network is lower than a preset threshold, it switches from the current communication network to another communication network. The dual-mode communication module records the communication network before the switch as the network to be switched back, and switches back to the network to be switched back when it detects that the signal quality of the network to be switched back is higher than the preset threshold and remains stable for a preset time. The encryption module uses the AES-256 control management system encryption algorithm to encrypt and transmit the sterilization process parameters and the sterilization program parameters, and rotates the encryption key according to a preset period.

[0014] Optionally, in one possible implementation, the IoT communication unit and the cloud platform transmit the sterilization process parameters through the MQTT control management system protocol and the sterilization program parameters through the HTTPS control management system protocol. The freeze request sent by the IoT communication unit to the cloud platform is transmitted through an instant control channel; wherein, the transmission priority of the instant control channel is higher than that of the data transmission channel for the sterilization process parameters. Each sterilization program parameter package issued by the cloud platform carries a issuance timestamp and the sterilization cycle number for this period. When the local controller receives the sterilization program parameter package, it compares the sterilization cycle number carried in the sterilization program parameter package with the current sterilization cycle number. If the sterilization cycle number carried in the sterilization program parameter package is less than the current sterilization cycle number, the local controller discards the sterilization program parameter package and sends an expiration information to the cloud platform.

[0015] Optionally, in one possible implementation, the cloud platform includes a parameter management module; wherein, The parameter management module is used to maintain the version chain of sterilization procedure parameters; When the parameter management module receives an editing operation on the sterilization program parameters that are in the frozen state, it generates a new version of the sterilization program parameters and marks the effective sterilization cycle number of the new version of the sterilization program parameters, without overwriting the sterilization program parameters that are in the frozen state. After the sterilization process is completed, the parameter management module releases the frozen state of the sterilization program parameters bound to this sterilization cycle based on the parameter version receipt.

[0016] Optionally, in one possible implementation, the IoT communication unit further includes a local cache module, which caches the sterilization process parameters on a per-sterilization-cycle basis and retransmits the cached sterilization process parameters to the cloud platform after communication is restored. If a communication interruption occurs during the retransmission process, a cross-breakpoint marker is added to the sterilization process parameters of the sterilization cycle in which the communication interruption occurred. The cloud platform also includes a traceability reporting module; The traceability reporting module is used to identify sterilization cycles marked as crossing breakpoints by the local cache module, and compare the parameter contract corresponding to the sterilization process parameters before the breakpoint with the parameter contract corresponding to the sterilization process parameters after the breakpoint of the sterilization cycle. When the parameter contract corresponding to the pre-break segment is inconsistent with the parameter contract corresponding to the post-break segment, the traceability reporting module marks the cross-break point sterilization cycle as a record anomaly and generates a record anomaly warning message which is pushed to the client.

[0017] Optionally, in one possible implementation, the parameter management module is further configured to record changes to the sterilization procedure parameters; wherein, The change record includes the changer's identifier, the change time, and the effective sterilization cycle number; The traceability report module is used to generate traceability reports according to the sterilization cycle; wherein, the traceability report includes sterilization process parameters for each stage of the sterilization process, the parameter contract, and the parameter version receipt; The change record and the traceability report are stored independently in the cloud platform. The traceability report module performs consistency verification based on the effective sterilization cycle number in the change record and the parameter contract in the traceability report.

[0018] Optionally, in one possible implementation, when the local controller detects that the sterilization process parameters in the non-reversible phase exceed the safety range corresponding to the parameter contract, it generates a loop termination instruction and terminates the sterilization process, and simultaneously writes the termination time corresponding to the loop termination instruction, the sterilization process parameters of the termination phase, and the parameter contract into the record corresponding to the traceability number. After the sterilization process is stopped, the local controller sends the record to the cloud platform and requests the release of the frozen state. After the cloud platform unfreezes the process, it marks the traceability number of this sterilization cycle as sterilization incomplete and generates release restriction information for the traceability number, which is then pushed to the client.

[0019] Secondly, this application also proposes an IoT-based pressure steam sterilizer, adapted to the remote control and management system of the aforementioned IoT-based pressure steam sterilizer, wherein the pressure steam sterilizer includes a sterilizer body; wherein the sterilizer body is internally equipped with the local controller and the IoT communication unit.

[0020] The beneficial effects of this invention are as follows: By generating a parameter contract on the local controller side, initiating a freeze request before the irreversible phase arrives, and refusing to apply sterilization program parameter updates during the irreversible phase, the sterilization program parameters executed in each sterilization cycle have a uniquely determined version attribution in terms of timing. Therefore, the sterilization program parameters displayed on the client, the sterilization program parameters actually executed by the local controller, and the sterilization program parameters recorded in the traceability report are necessarily consistent within the same sterilization cycle, solving the problem of unclear sterilization cycle parameter version attribution caused by the uncertain timing of remote parameter distribution. Simultaneously, since the local controller uses the parameter contract as the sole basis for execution during the irreversible phase, communication interruptions no longer interfere with the execution of the sterilization process. The local controller can perform limited waiting during the reversible phase based on time budget and directly continue execution during the irreversible phase, thus ensuring that the sterilization process maintains predictable timing behavior even under unreliable communication conditions. Furthermore, since the parameter contract is uploaded along with the traceability data, for sterilization cycles that are divided into pre-break and post-break segments due to communication interruption, it can be determined whether they correspond to the same parameter version by comparing the parameter contracts corresponding to the two segments. This solves the problem of the inability to verify the semantic consistency of sterilization cycle records across breakpoints. Attached Figure Description

[0021] Figure 1 A schematic diagram of the overall architecture of the IoT-based pressure steam sterilizer and its remote control and management system provided in the embodiments of this application; Figure 2 This is a schematic diagram of the structure of the sterilizer body provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of an IoT communication unit provided in an embodiment of this application; Figure 4 This is a schematic diagram of the functional modules of the cloud platform provided in the embodiments of this application; Figure 5 A schematic diagram illustrating the workflow of the remote control management system provided in this application embodiment; Figure 6 This application provides a schematic diagram of parameter contracts and frozen state timing for embodiments of the present application. Figure 7 A schematic diagram of the time budget decision-making process provided for embodiments of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0023] The terms “first,” “second” (if any), etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion.

[0024] The embodiments of this application will now be described in detail with reference to the accompanying drawings. Example 1

[0025] like Figure 1 The diagram shows a system framework of an IoT-based pressure steam sterilizer provided in this application embodiment. The remote control management system comprises two parts. The first part is the hardware components of the pressure steam sterilizer, including the sterilizer body 1, a local controller 12, and an IoT communication unit 13. The second part is the remote control component, including a cloud platform 2 and a client 3. The client 3 is not limited to the control terminal on the customer's side, but also includes a management client, i.e., a remote control terminal.

[0026] The sterilizer body 1 is the main device for achieving sterilization, containing a sterilization chamber 11 and a local controller 12 for controlling the sterilization process. An IoT communication unit 13 is connected to the local controller 12 to collect sterilization process parameters and communicate with the cloud platform 2. The cloud platform 2 is connected to the IoT communication unit 13 to store and distribute sterilization program parameters, as well as to store sterilization process parameters and generate traceability reports. A client 3 is connected to the cloud platform 2, including but not limited to mobile application terminals and SMS terminals, for users to view sterilization process parameters, adjust sterilization program parameters, and receive warning information.

[0027] like Figure 2As shown, in this embodiment, the sterilizer body 1 includes a sterilization chamber 11, a local controller 12, a client 21, a water tank 14, a steam generator 15, a steam storage tank 16, a vacuum pump 17, a quick-opening door 18, an electric door lock 19, and an exhaust valve and a drain valve 20. The sterilization chamber 11 has a volume of 5L and is made of 304 stainless steel. The client 21 is located on the outer wall of the sterilization chamber 11. The steam generator 15 is connected to the steam storage tank 16 and is used to provide saturated steam to the sterilization chamber 11. The vacuum pump 17 is connected to the sterilization chamber 11 and is used to evacuate the sterilization chamber 11. The quick-opening door 18 is located on one side of the sterilization chamber 11 and is locked by the electric door lock 19. The exhaust valve and drain valve 20 are located at the bottom of the sterilization chamber 11 and are used to discharge steam during the exhaust phase and condensate during the drying phase. The local controller 12 is electrically connected to the client 21, the steam generator 15, the vacuum pump 17, the electric door lock 19, and the exhaust valve and drain valve 20, respectively, and is used to control the operation of the above components according to the sterilization program parameters.

[0028] In this embodiment, the sterilization process of the sterilizer body 1 includes a preheating stage, a pulsating vacuum stage, a heating stage, a sterilization maintenance stage, an exhaust stage, and a drying stage. Specifically, the preheating stage is used to preheat the wall temperature of the sterilization chamber 11 to near the sterilization temperature; the pulsating vacuum stage is used to repeatedly evacuate the chamber using a vacuum pump 17 and inject steam through a steam generator 15 to gradually dilute and expel the air from the sterilization chamber 11 and the packaging of the items to be sterilized; the heating stage is used to raise the temperature inside the sterilization chamber 11 from the end temperature of the pulsating vacuum stage to the sterilization maintenance temperature; the sterilization maintenance stage is used to maintain the temperature inside the sterilization chamber 11 at the sterilization maintenance temperature for a preset duration; the exhaust stage is used to expel the steam from the sterilization chamber 11; and the drying stage is used to evacuate the sterilization chamber 11 to evaporate residual condensate on the surface of the items to be sterilized.

[0029] like Figure 3 As shown, in this embodiment, the IoT communication unit 13 includes a data acquisition module 131, a dual-mode communication module 132, a local cache module 133, and an encryption module 134. The data acquisition module 131 is connected to various sensors within the sterilizer body 1 to collect sterilization process parameters; the local cache module 133 is used to cache sterilization process parameters during communication interruptions; the encryption module 134 is located between the data acquisition module 131 and the dual-mode communication module 132 to encrypt the data to be transmitted and to decrypt the received data; the dual-mode communication module 132 supports data transmission under two communication networks and sends the data encrypted by the encryption module 134 to the cloud platform 2, and receives data sent from the cloud platform 2 and decrypted by the encryption module 134.

[0030] like Figure 4As shown, in this embodiment, the cloud platform 2 includes a monitoring and early warning module 21, a parameter management module 22, a permission management module 23, a traceability report module 24, and a control and management system. The monitoring and early warning module 21 is used to monitor the uploaded sterilization process parameters in real time and generate early warnings when parameters are abnormal; the parameter management module 22 is used to store, maintain, and distribute sterilization program parameters; the permission management module 23 is used to manage user operation permissions hierarchically; the traceability report module 24 is used to generate traceability reports for the sterilization cycle; and the control and management system is used to manage registered sterilizer equipment. Example 2

[0031] This embodiment provides a detailed description of the process of generating and binding parameter contracts.

[0032] In medical institutions, the sterilizer body 1 is independently controlled by the local controller 12. The cloud platform 2 sends sterilization program parameters to the local controller 12 through the Internet of Things communication unit 13, so that the medical institution can adjust the sterilization intensity according to the type and loading method of the items to be sterilized.

[0033] In this embodiment, when a user initiates a sterilization process through client 3, the local controller 12 sends a sterilization program parameter request to the cloud platform 2 at the start of the sterilization process. The parameter management module 22 of the cloud platform 2 responds to the request, determines the currently effective version from the version chain of sterilization program parameters, and sends the sterilization program parameters of that version along with its version identifier to the local controller 12 via the IoT communication unit 13.

[0034] After receiving the sterilization program parameters, the local controller 12 assigns a unique traceability number to this sterilization cycle and binds the version identifier of the sterilization program parameters with the traceability number to generate a parameter contract for this sterilization cycle.

[0035] In this embodiment, the data structure of the parameter contract includes at least: a traceability number, a sterilization procedure parameter version identifier, a binding time, and a content digest of the sterilization procedure parameters. The content digest of the sterilization procedure parameters is calculated using a preset hash algorithm to quickly verify whether the parameter content has changed in subsequent steps.

[0036] It should be noted that the parameter contract is generated only when the sterilization process begins, thus fixing the execution basis of the sterilization cycle before the sterilization process starts. Therefore, any sterilization program parameters that arrive after the sterilization process has started, regardless of whether their content is the same as the bound version, will not change the execution basis of this sterilization cycle.

[0037] In a specific embodiment of this application, the traceability number is preferably set to the format of equipment number - date - daily serial number. For example: if the equipment number is SGL-001, the date is the year, month, and day of implementation, and the number of sterilization cycles on that day is specified, then the traceability number is SGL-001 - year, month, and day of implementation - number of sterilization cycles. In this process, the sterilization procedure parameter version identifier can be in the form of a version serial number. Example 3

[0038] In one embodiment of this application, the process of initiating a freeze request, setting a freeze state, and rejecting parameter updates is described in detail below.

[0039] In the specific implementation of this application, the interval from the start of the heating phase to the end of the sterilization maintenance phase in the sterilization process is defined as the non-reversible phase.

[0040] The irreversible stage is primarily characterized by the irreversibility of the process state: When the pulsating vacuum stage ends, the air in the sterilization chamber 11 and the packaging of the items being sterilized has been substantially expelled, and saturated vapor has entered and penetrated the packaging. This state is a prerequisite for subsequent heating and sterilization to be maintained. Once the heating phase begins, the temperature inside sterilization chamber 11 starts to rise continuously, and the items being sterilized begin to acquire an irreversible heating history, with the distribution of steam and condensate inside the packaging also changing accordingly.

[0041] At this point, if the process is interrupted for any reason and an attempt is made to continue from a later stage, the heat history of the sterilized items and the phase distribution within the packaging cannot be restored. The entire cycle must be restarted from the pulsating vacuum stage. Therefore, the starting moment of the heating stage constitutes a point of no return in the process.

[0042] The sterilization intensity during the irreversible phase is irreversible: The sterilization intensity during the sterilization maintenance phase is characterized by the combination of sterilization temperature and maintenance time, and its cumulative sterilization effect is measured by the F0 value. The physical meaning of the F0 value is: the equivalent sterilization time at a reference temperature of 121℃, which is calculated by integrating the equivalent coefficient corresponding to the sterilization temperature at each moment within the sterilization phase over time. The integral begins to accumulate from the heating phase as the temperature inside sterilization chamber 11 rises and stops accumulating at the end of the sterilization maintenance phase. Once this integration process begins, the accumulated result becomes a fait accompli, and no subsequent operation can reduce or reverse the accumulated F0 value. Therefore, from the start of the heating phase to the end of the sterilization maintenance phase, the process state and sterilization intensity within the corresponding interval cannot be reversed.

[0043] In contrast to the non-reversible stages, the preheating stage, pulsating vacuum stage, exhaust stage, and drying stage in the sterilization process constitute the reversible stages.

[0044] This application addresses reversible stages. None of the aforementioned stages involve the cumulative effect of sterilization intensity; their execution results only affect the residual air level, temperature conditions, or surface dryness of the items within sterilization chamber 11. If any stage needs to be re-executed due to communication issues, it will not lead to an uncontrollable additional accumulation of sterilization intensity. For example, if the pulsating vacuum stage is repeated, it will only further reduce the residual air level within sterilization chamber 11, without producing any negative impact.

[0045] In one specific embodiment of this application, the local controller 12 sends a freeze request to the cloud platform 2 just before entering the heating phase, within the interval between the end of the last pulse of the pulsating vacuum phase and the start of the heating phase. The parameter management module 22 of the cloud platform 2 responds to the freeze request by setting the sterilization program parameters bound to this sterilization cycle, i.e., the version specified in the parameter contract, to a frozen state.

[0046] In one specific embodiment of this application, the "frozen state" refers to a state in which the sterilization program parameters of this version are prohibited from being overwritten or modified by any editing operation before being unfrozen. It should be noted that the frozen state does not prohibit editing of sterilization program parameters other than this version. When the cloud platform 2 receives an editing operation on the sterilization program parameters in the frozen state, it will generate a new version of the sterilization program parameters and mark the effective sterilization cycle number of the new version, without overwriting the sterilization program parameters in the frozen state.

[0047] In one specific embodiment of this application, after the sterilization process enters the irreversible stage, the local controller 12 refuses to apply the sterilization program parameter updates issued by the cloud platform 2. Specifically, during the irreversible stage, the local controller 12 receives the sterilization program parameters issued by the cloud platform 2 but does not perform any application operations on the sterilization program parameters. Instead, it uses the parameter contract of this sterilization cycle as the sole basis for stage advancement.

[0048] Therefore, during the irreversible phase, the sterilization cycle is always executed based on the parameter version bound to the parameter contract, and there will be no situation where some phases are executed according to one parameter version and some phases are executed according to another parameter version.

[0049] Combination Figure 6 As shown, in this embodiment, the timing relationship between the parameter contract and the frozen state is as follows: The time control management system t0 starts the sterilization process and generates the parameter contract for this sterilization cycle; At time t1, the warm-up phase begins; t2, the pulsating vacuum phase begins; t3, Local controller 12 sends a freeze request, and cloud platform 2 sets the sterilization program parameters bound to this sterilization cycle to a frozen state; t4, the heating phase begins (the irreversible phase begins); t5, the sterilization maintenance phase begins; t6, End of sterilization maintenance phase (end of irreversible phase); t7, exhaust phase begins; t8, the drying stage begins; t9, sterilization process complete, local controller 12 generates parameter version receipt and uploads it, cloud platform 2 unfreezes.

[0050] As a specific implementation of this embodiment, the local controller 12 can also send a freeze request at the same time as the sterilization process starts. At this time, the freeze request and the generation of the parameter contract are completed at the same time, which can also achieve the technical effect of having a unique execution basis in the irreversible stage. Example 4

[0051] In one embodiment of this application, the maintenance of the time budget and the decision-making process in the event of communication interruption are described in detail.

[0052] In this embodiment, the local controller 12 maintains a time budget at the boundaries of each stage of the sterilization process. The time budget is calculated as follows: The estimated remaining time for the current stage minus the minimum guaranteed execution time for the current stage.

[0053] The estimated remaining time refers to the time required from the current moment to the end of the current stage according to the sterilization procedure parameters bound in the parameter contract; the minimum execution time refers to the shortest remaining execution time required from the current moment to ensure that the current stage achieves its process objective.

[0054] Both parameters are calculated from the current moment, and the difference between them is the remaining waiting time for the current stage without affecting its process objective. The minimum execution time can be predetermined and stored in the local controller 12 based on the specifications of the sterilizer body 1, the type of items to be sterilized, and the loading method.

[0055] Combination Figure 7 As shown, in this embodiment, when the local controller 12 detects a communication interruption, it makes a decision according to the following rules: First, the stage at which the communication interruption occurred is determined. If the communication interruption occurs in a reversible stage, namely the preheating stage, the pulsed vacuum stage, the exhaust stage, and the drying stage, and the time budget is greater than zero, the local controller 12 waits for the communication link to be restored within the time budget limit, and continues to execute the sterilization process according to the parameter contract after the waiting timeout. This waiting is achieved by extending the execution duration of the current stage, and the extended duration does not exceed the time budget. If the communication link is restored within the time budget, the local controller 12 ends the waiting, continues to execute the sterilization process according to the parameter contract, and records the start and end times of this waiting in the record corresponding to the traceability number.

[0056] Secondly, if the communication interruption occurs in the irreversible phase, that is, the interval from the start of the heating phase to the end of the sterilization maintenance phase, the local controller 12 will not wait for the communication link to be restored and will directly continue to execute the sterilization process according to the parameter contract.

[0057] Third, if the time budget is less than or equal to zero, meaning there is no redundant time available to wait in the current stage, the local controller 12 will directly continue to execute the sterilization process according to the parameter contract.

[0058] The above decision is made because the rollback phase has time redundancy in the process, and its execution time can be adjusted within a certain range without affecting the sterilization intensity. Therefore, a limited wait can be made in this phase, which is achieved by extending the execution time of the current phase, and the extended time does not exceed the time budget. The duration of the non-rollback phase directly determines the size of the F0 value. Extending the duration of this phase will cause the sterilization intensity to exceed the range agreed upon in the parameter contract. Therefore, waiting is not allowed in this phase. Example 5

[0059] This embodiment provides a detailed description of the caching and retransmission process of sterilization parameters.

[0060] In this embodiment, the local caching module 133 caches sterilization process parameters on a per-sterilization-cycle basis. Specifically, the local caching module 133 records the collection timestamp and the corresponding sterilization process stage marker for each cached sterilization process parameter, and aggregates the sterilization process parameters of the same sterilization cycle according to the traceability number.

[0061] In this embodiment, after communication is restored, the IoT communication unit 13 retransmits the cached sterilization process parameters to the cloud platform 2 according to the order of the collected timestamps. If the communication is interrupted again during the retransmission of sterilization process parameters for a certain sterilization cycle, the local cache module 133 records the retransmission breakpoint and continues the retransmission from the breakpoint after communication is restored, without having to retransmit the part of the sterilization cycle that has already been retransmitted.

[0062] In this embodiment, for sterilization cycles where communication is interrupted during retransmission, the sterilization process parameters are divided into a pre-interruption segment and a post-interruption segment. The local cache module 133 adds cross-interruption markers to the sterilization process parameters of the sterilization cycle so that the cloud platform 2 can identify the sterilization cycle as a cross-interruption sterilization cycle.

[0063] After identifying a sterilization cycle that crosses a breakpoint, the traceability reporting module 24 of the cloud platform 2 compares the parameter contract corresponding to the sterilization process parameters before the breakpoint with the parameter contract corresponding to the sterilization process parameters after the breakpoint.

[0064] When the parameter contract corresponding to the pre-break segment is consistent with the parameter contract corresponding to the post-break segment, the traceability report module 24 confirms that the sterilization cycle across the breakpoint is semantically complete, that is, the pre-break segment and the post-break segment correspond to the same sterilization program parameter version.

[0065] When the parameter contract corresponding to the pre-break segment is inconsistent with the parameter contract corresponding to the post-break segment, the traceability report module 24 marks the sterilization cycle that crosses the break point as a record abnormality and generates a record abnormality warning message to push to the client 3.

[0066] It should be noted that the object of comparison in this embodiment is the parameter contract, not the content of the sterilization process parameters themselves. When this application is executed, even if the data content of the pre- and post-fracture segments is complete and has not been tampered with, if the sterilization program parameter versions corresponding to the two are different, the record of the sterilization cycle is still inconsistent at the semantic level; and this inconsistency cannot be detected by content-level integrity verification, but can only be identified by comparing the parameter contract.

[0067] In this embodiment, the communication protocol between the IoT communication unit 13 and the cloud platform 2 adopts a layered design: sterilization process parameters are uploaded to the cloud platform 2 via the MQTT protocol, and sterilization program parameters are sent from the cloud platform 2 to the local controller 12 via the HTTPS protocol. The reason for using the MQTT protocol to transmit sterilization process parameters is that sterilization process parameters are characterized by large data volume and high transmission frequency, and the lightweight nature of the MQTT protocol helps to reduce transmission overhead; the reason for using the HTTPS protocol to transmit sterilization program parameters is that sterilization program parameters directly affect sterilization intensity and have high requirements for transmission security, and the transmission layer encryption provided by the HTTPS protocol helps to ensure its security.

[0068] In this embodiment, the data acquisition module 131 sets its acquisition cycle according to parameter type: the temperature and pressure in the sterilization chamber 11 are acquired at a cycle of 1 second; the drying status during the drying stage and the water level and water conductivity in the water tank 14 are acquired at a cycle of 5 seconds; the on / off status of the electric door lock 19 and the fault codes generated by the local controller 12 are acquired via event triggering. The reason for using a tiered acquisition cycle is that the temperature and pressure change rapidly and have a direct impact on the sterilization intensity determination, so a higher acquisition frequency is used; while the water level, water quality, and door lock status change slowly, so a lower acquisition frequency or event triggering method is beneficial to reduce the amount of data. Example 6

[0069] This embodiment provides a detailed description of the switching and reverting process of the dual-mode communication module 132.

[0070] In this embodiment, the dual-mode communication module 132 supports communication with the cloud platform 2 through a first communication network and a second communication network. In a specific implementation of this application, the first communication network is a wireless local area network, for example: a Wi-Fi network in the 2.4GHz or 5GHz band; the second communication network is a cellular communication network, for example: an LTE Cat-1 network.

[0071] In one specific embodiment of this application, if the dual-mode communication module 132 detects that the signal quality of the current communication network is lower than a preset threshold, it will switch from the current communication network to another communication network. The preset threshold is when the wireless local area network signal strength is lower than a preset minimum value, or the packet loss rate is higher than a preset maximum value.

[0072] In one specific embodiment of this application, after completing the switch, the dual-mode communication module 132 does not immediately meet the conditions for switching back. Instead, it records the communication network before the switch as the network to be switched back and determines whether the signal quality of the network to be switched back is higher than a preset threshold and remains stable for a preset duration. Only when the above conditions are met simultaneously will the dual-mode communication module 132 switch back to the network to be switched back.

[0073] In some real-world sterilization environments, the signal quality of a wireless LAN can fluctuate briefly due to factors such as personnel movement and equipment startup / shutdown. If an immediate switchback strategy is used in such situations, the dual-mode communication module 132 will frequently switch between the two communication networks, requiring the re-establishment of the communication connection each time, which in turn reduces the continuity of sterilization process parameter transmission. By setting a preset stable duration as the switchback condition, frequent switching caused by short-term signal quality fluctuations can be avoided in the above-mentioned situations. It should be noted that the switchback condition is based on the signal quality of the network to be switched back to, not the signal quality of the currently used communication network.

[0074] In some actual sterilization environments, the encryption module 134 uses the AES-256 encryption algorithm to encrypt and transmit sterilization process parameters and sterilization program parameters, and rotates the encryption key according to a preset period.

[0075] In this embodiment, the freeze request sent by the IoT communication unit 13 to the cloud platform 2 is transmitted through the real-time control channel, which has a higher transmission priority than the data transmission channel for sterilization process parameters.

[0076] This application establishes a priority channel. The purpose of freezing requests is to ensure that cloud platform 2 promptly freezes the sterilization program parameters bound to the current sterilization cycle. The timeliness requirement for freezing requests is higher than that for transmitting sterilization process parameters. If freezing requests and sterilization process parameters share the same transmission channel, the freezing request may be queued and delayed when the amount of data uploaded for the sterilization process parameters is large. This could result in the freezing request being processed by cloud platform 2 only after the sterilization process has entered an irreversible stage, weakening the technical effectiveness of the freezing mechanism. By setting up a separate real-time control channel for freezing requests and assigning them a higher transmission priority, timely delivery of freezing requests can be guaranteed.

[0077] In this embodiment, each sterilization program parameter package issued by the cloud platform 2 carries a issuance timestamp and the current sterilization cycle number. When the local controller 12 receives the sterilization program parameter package, it compares the sterilization cycle number carried in the parameter package with the current sterilization cycle number. If the sterilization cycle number carried in the parameter package is less than the current sterilization cycle number, the local controller 12 discards the parameter package and sends an expiration message to the cloud platform 2. If the sterilization cycle number carried in the parameter package is equal to the current sterilization cycle number, the local controller 12 receives the parameter package. If the parameter contract for the current sterilization cycle has not yet been generated, the local controller 12 generates the parameter contract for the current sterilization cycle according to the parameter package. If the parameter contract for the current sterilization cycle has already been generated, the local controller 12 does not change the execution basis of the current sterilization cycle due to receiving the parameter package.

[0078] The technical significance of the aforementioned comparison rule lies in the fact that, in scenarios where communication delays exist, a parameter package issued for a previous sterilization cycle may only arrive at the local controller 12 during the current sterilization cycle. If the local controller 12 applies this parameter package without judgment, it will lead to an error in the execution basis of the sterilization process. By comparing the sterilization cycle number carried in the parameter package with the current sterilization cycle number, expired parameter packages can be identified and discarded. For parameter packages whose sterilization cycle number is equal to the current sterilization cycle number, since their corresponding sterilization program parameters have been fixed by the parameter contract at the start of the current sterilization cycle, the local controller 12 will only apply the generated contract if the parameter contract for the current sterilization cycle has not yet been generated; otherwise, it will not be applied. Example 7

[0079] This embodiment provides a detailed explanation of the parameter version generation management and dual-chain mutual verification process on the cloud platform 2 side.

[0080] In this embodiment, the parameter management module 22 is used to maintain the version chain of sterilization procedure parameters. When a medical institution needs to adjust the sterilization procedure parameters, the parameter management module 22 does not overwrite the original parameters, but generates a new version of the sterilization procedure parameters and marks the effective sterilization cycle number on the new version.

[0081] It should be noted that the meaning of the effective sterilization cycle number is: the new version of the sterilization procedure parameters takes effect from the marked sterilization cycle number, while sterilization cycles started before this date will still be executed based on their bound parameter contracts. Therefore, the evolution of parameter versions has a clear temporal boundary.

[0082] In this embodiment, the parameter management module 22 is used to record changes to sterilization procedure parameters. The change record includes the changer's identifier, the change time, and the effective sterilization cycle number. The traceability report module 24 is used to generate traceability reports according to the sterilization cycle. The traceability report includes sterilization process parameters, parameter contracts, and parameter version receipts for each stage of the sterilization process.

[0083] In this embodiment, the change record and the traceability report are stored independently in the cloud platform 2. The traceability report module 24 performs consistency verification based on the effective sterilization cycle number in the change record and the parameter contract in the traceability report.

[0084] The technical significance of storing change records and traceability reports separately lies in the fact that change records document the actions performed by "people" on parameters, while traceability reports record the parameters actually executed by "equipment." These belong to different record subjects. If they are stored together, it becomes difficult to distinguish whether a parameter was incorrectly changed or the equipment executed incorrect parameters in the event of a record dispute. By storing them separately and establishing cross-verification, the two can be mutually verified: the effective sterilization cycle number in the change record should match the version pointed to by the parameter contract for the corresponding sterilization cycle in the traceability report; if they do not match, it indicates an anomaly in the parameter change process or the sterilization process execution stage.

[0085] In one optional embodiment of this application, the permission management module 23 of the cloud platform 2 manages user operation permissions in three levels, specifically operator level, administrator level, and regulatory agency level. Operator-level permissions allow the initiation and termination of the sterilization process; administrator-level permissions allow the adjustment of sterilization program parameters; and regulatory agency-level permissions allow the viewing of traceability reports.

[0086] In a specific application scenario, a sterilization supply center has multiple sterilizers, such as six pressure steam sterilizers. The sterilization supply center administrator adjusts the sterilization maintenance phase temperature in the sterilization program parameters from 132℃ to 134℃ via client 3. The parameter management module 22 does not overwrite the original parameters but instead generates a new version of the parameters for the effective sterilization cycle number using a labeling method. If, at this point, a sterilizer numbered 1 is in the sterilization maintenance phase of a sterilization cycle, and the parameter contract bound to this cycle points to the previous parameter version, which is already frozen, then this sterilization cycle will still be executed at 132℃ until completion; while subsequent sterilization cycles started by another sterilizer numbered 1 will be executed at 134℃. When generating two traceability reports, the traceability report module 24 of the cloud platform 2 records the corresponding parameter contracts for each, thus accurately reflecting the actual parameter differences executed by the two devices at the record level.

[0087] In another specific application scenario, the wireless LAN signal quality of the pressure steam sterilizer is unstable, and the signal strength of the cellular communication network fluctuates. During the sterilization cycle, a communication interruption occurs during the heating phase. In the non-reversible heating phase, the local controller 12 does not wait for the communication link to be restored and continues to execute the heating and sterilization maintenance phases according to the parameter contract. After communication is restored, the local cache module 133 re-transmits the sterilization process parameters cached during the network outage to the cloud platform 2 in timestamp order. The sterilization process parameters of this sterilization cycle are marked as a cross-breakpoint cycle. The traceability report module 24 compares the parameter contracts corresponding to the pre-break and post-break segments to confirm that they point to the same parameter version, thus confirming that the record of this sterilization cycle is semantically complete. Example 8

[0088] This embodiment provides a detailed description of the termination process during the irreversible phase.

[0089] In this embodiment, the local controller 12 continuously compares the collected sterilization process parameters with the safety range corresponding to the parameter contract during the irreversible phase. This safety range includes the lower and upper limits of the sterilization maintenance temperature, the lower limit of the sterilization maintenance time, and the allowable pressure fluctuation range within the sterilization chamber 11. Specifically, the lower limit of the sterilization maintenance time is determined as follows: if, after the duration represented by this lower limit has elapsed since the start of the sterilization maintenance phase, the temperature within the sterilization chamber 11 has not yet fallen between the lower and upper limits of the sterilization maintenance temperature, then the sterilization process parameters are determined to be outside the safety range.

[0090] When the sterilization process parameters are detected to be outside the safe range, the local controller 12 generates a cycle termination command and terminates the sterilization process. After termination, the local controller 12 writes the termination time corresponding to the cycle termination command, the sterilization process parameters of the termination stage, and the parameter contract into the record corresponding to the traceability number, so that the record can reflect at what time, at what stage, and according to which parameter version the sterilization process was terminated.

[0091] After the sterilization process is terminated, the local controller 12 sends the record to the cloud platform 2 and requests to unfreeze. After unfreezing, the cloud platform 2 marks the traceability number of this sterilization cycle as sterilization incomplete and generates release restriction information for that traceability number, which is then pushed to the client 3.

[0092] The technical significance of generating release restriction information lies in the fact that the termination of the sterilization process means that the sterilization cycle did not reach the sterilization intensity specified in the parameter contract, and the sterilized items did not meet the sterility assurance level. By generating release restriction information for this traceability number and pushing it to client 3, operators can receive clear prompts when handling this batch of sterilized items, preventing items that have not been sterilized from being mistakenly considered to have been sterilized and put into use.

[0093] It should be noted that the improvement of the pressure steam sterilizer provided in this application lies in the timing contract relationship established between the local controller 12 and the cloud platform 2 around the sterilization cycle, rather than the mechanical structure or thermal parameters of the sterilizer body 1. The specifications of the sterilizer body 1, the specific duration and temperature and pressure settings of each stage of the sterilization process, and the selection of sensor types can all be determined according to actual needs, and this application does not impose any limitations. Example 9

[0094] like Figure 5 As shown in the embodiment of this application, a remote control management system for a pressure steam sterilizer based on the Internet of Things is also provided. The system includes a local controller 12 of the sterilizer body 1, an Internet of Things communication unit 13 and a cloud platform 2. The remote control management process is executed collaboratively by the local controller 12 and the cloud platform 2.

[0095] In this embodiment, when the sterilization process of the sterilizer body 1 is started, the local controller 12 binds the sterilization program parameters issued by the cloud platform 2 with the traceability number of this sterilization cycle to generate a parameter contract for this sterilization cycle. The specific process is as described in Embodiment 2 of this application.

[0096] In this embodiment, before the sterilization process enters the irreversible stage, the local controller 12 sends a freeze request to the cloud platform 2 so that the cloud platform 2 sets the sterilization program parameters bound to this sterilization cycle to a frozen state. The irreversible stage is the stage from the start of the heating stage to the end of the sterilization maintenance stage. The timing of the freeze request is as described in Embodiment 3 of this application.

[0097] In this embodiment, the local controller 12 continuously determines whether the sterilization process has entered the irreversible stage during the execution of the sterilization process. Before the sterilization process enters the irreversible stage, the local controller 12 continues to execute the sterilization process according to the parameter contract, and the execution basis of this sterilization cycle is not changed due to the sterilization program parameter update issued by the cloud platform 2. After the sterilization process enters the irreversible stage, the local controller 12 refuses to apply the sterilization program parameter update issued by the cloud platform 2, and executes the irreversible stage according to the parameter contract until the sterilization maintenance stage ends.

[0098] In this embodiment, after the sterilization process is completed, the local controller 12 generates a parameter version receipt carrying the parameter contract, and uploads it to the cloud platform 2 via the Internet of Things communication unit 13. The cloud platform 2 releases the frozen state of the sterilization program parameters bound to this sterilization cycle according to the parameter version receipt.

[0099] It should be noted that in this embodiment, the freezing request is not limited to being sent before entering the irreversible stage. The local controller 12 can also send the freezing request at the same time as the sterilization process starts. In this case, the freezing request and the generation of the parameter contract are completed at the same time, which can also achieve the technical effect of having a unique execution basis in the irreversible stage.

[0100] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0101] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A remote control and management system for a pressure steam sterilizer based on the Internet of Things, applied to a pressure steam sterilizer, characterized in that, include: A local controller is used to control the sterilization process of the pressure steam sterilizer; wherein the sterilization process includes a preheating stage, a pulsating vacuum stage, a heating stage, a sterilization maintenance stage, an exhaust stage, and a drying stage; An Internet of Things (IoT) communication unit, connected to the local controller, is used to collect sterilization process parameters; The cloud platform communicates with the IoT communication unit and with the client, and is used to store sterilization program parameters and distribute them. When the sterilization process is started, the local controller binds the sterilization program parameters issued by the cloud platform with the traceability number of the current sterilization cycle to generate a parameter contract for the current sterilization cycle. The local controller sends a freeze request to the cloud platform before the sterilization process enters the irreversible stage; The irreversible phase is the period from the start of the heating phase to the end of the sterilization maintenance phase; In response to the freeze request, the cloud platform sets the sterilization program parameters bound to this sterilization cycle to a frozen state. During the irreversible phase, the local controller refuses to apply the sterilization program parameter updates issued by the cloud platform and executes the irreversible phase in accordance with the parameter contract.

2. The remote control and management system for a pressure steam sterilizer based on the Internet of Things as described in claim 1, characterized in that, The local controller maintains time budgets at the boundaries of each stage of the sterilization process; wherein, The time budget is the estimated remaining time for the current stage minus the minimum execution time for the current stage; The estimated remaining time is the duration from the current moment until the end of the current phase; The minimum execution time is the shortest time required from the current moment to enable the current stage to achieve its technological objective. When the local controller detects a communication interruption, it performs the following decision: If a communication interruption occurs during a rollback phase and the time budget is greater than zero, the local controller waits for the communication link to be restored within the time budget, and continues the sterilization process according to the parameter contract after a timeout; wherein... The reversible phase includes the preheating phase, the pulsating vacuum phase, the exhaust phase, and the drying phase; the waiting is achieved by extending the execution duration of the current phase, and the extended duration does not exceed the time budget; When a communication interruption occurs during the irreversible phase, the local controller does not wait for the communication link to be restored and directly continues to execute the sterilization process according to the parameter contract; When the time budget is less than or equal to zero, the local controller continues to execute the sterilization process directly according to the parameter contract.

3. The remote control and management system for a pressure steam sterilizer based on the Internet of Things according to claim 2, characterized in that, The IoT communication unit includes a local cache module; wherein... The local cache module caches the sterilization process parameters on a sterilization cycle basis. The local cache module records the collection timestamps and corresponding sterilization process stage markers for the cached sterilization process parameters. After communication is restored, the IoT communication unit retransmits the cached sterilization process parameters to the cloud platform in the order of the collected timestamps, and deletes the corresponding cached sterilization process parameters after the cloud platform confirms receipt. When the communication is interrupted again during the retransmission of the sterilization process parameters, the local cache module records the retransmission breakpoint and resumes retransmission from the breakpoint after communication is restored.

4. The remote control and management system for a pressure steam sterilizer based on the Internet of Things as described in claim 1, characterized in that, The IoT communication unit also includes a dual-mode communication module and an encryption module; The dual-mode communication module supports communication with the cloud platform via a first communication network and a second communication network; wherein... The first communication network is a wireless local area network, and the second communication network is a cellular communication network; When the dual-mode communication module detects that the signal quality of the current communication network is lower than a preset threshold, it switches from the current communication network to another communication network. The dual-mode communication module records the communication network before the switch as the network to be switched back, and switches back to the network to be switched back when it detects that the signal quality of the network to be switched back is higher than the preset threshold and remains stable for a preset time. The encryption module uses the AES-256 encryption algorithm to encrypt and transmit the sterilization process parameters and the sterilization program parameters, and rotates the encryption key according to a preset period.

5. The remote control and management system for an IoT-based pressure steam sterilizer according to claim 4, characterized in that, The IoT communication unit and the cloud platform transmit the sterilization process parameters through the MQTT control management system protocol and the sterilization program parameters through the HTTPS control management system protocol. The freeze request sent by the IoT communication unit to the cloud platform is transmitted through an instant control channel; wherein, the transmission priority of the instant control channel is higher than that of the data transmission channel for the sterilization process parameters. Each sterilization program parameter package issued by the cloud platform carries a issuance timestamp and the sterilization cycle number for this period. When the local controller receives the sterilization program parameter package, it compares the sterilization cycle number carried in the sterilization program parameter package with the current sterilization cycle number. If the sterilization cycle number carried in the sterilization program parameter package is less than the current sterilization cycle number, the local controller discards the sterilization program parameter package and sends an expiration information to the cloud platform.

6. The remote control and management system for a pressure steam sterilizer based on the Internet of Things according to claim 1, characterized in that, The cloud platform includes a parameter management module; wherein... The parameter management module is used to maintain the version chain of sterilization procedure parameters; When the parameter management module receives an editing operation on the sterilization program parameters that are in the frozen state, it generates a new version of the sterilization program parameters and marks the effective sterilization cycle number of the new version of the sterilization program parameters, without overwriting the sterilization program parameters that are in the frozen state. After the sterilization process is completed, the parameter management module releases the frozen state of the sterilization program parameters bound to this sterilization cycle based on the parameter version receipt.

7. The remote control and management system for an IoT-based pressure steam sterilizer according to claim 6, characterized in that, The IoT communication unit also includes a local cache module, which caches the sterilization process parameters in units of sterilization cycles, and retransmits the cached sterilization process parameters to the cloud platform after communication is restored. If a communication interruption occurs during the retransmission process, a cross-breakpoint marker is added to the sterilization process parameters of the sterilization cycle in which the communication interruption occurred. The cloud platform also includes a traceability reporting module; The traceability reporting module is used to identify sterilization cycles marked as crossing breakpoints by the local cache module, and compare the parameter contract corresponding to the sterilization process parameters before the breakpoint with the parameter contract corresponding to the sterilization process parameters after the breakpoint of the sterilization cycle. When the parameter contract corresponding to the pre-break segment is inconsistent with the parameter contract corresponding to the post-break segment, the traceability reporting module marks the cross-break point sterilization cycle as a record anomaly and generates a record anomaly warning message which is pushed to the client.

8. The remote control and management system for an IoT-based pressure steam sterilizer according to claim 7, characterized in that, The parameter management module is also used to record changes to the sterilization procedure parameters; wherein, The change record includes the changer's identifier, the change time, and the effective sterilization cycle number; The traceability report module is used to generate traceability reports according to the sterilization cycle; wherein, the traceability report includes sterilization process parameters for each stage of the sterilization process, the parameter contract, and the parameter version receipt; The change record and the traceability report are stored independently in the cloud platform. The traceability report module performs consistency verification based on the effective sterilization cycle number in the change record and the parameter contract in the traceability report.

9. The remote control and management system for a pressure steam sterilizer based on the Internet of Things according to claim 1, characterized in that, When the local controller detects that the sterilization process parameters in the non-reversible stage exceed the safety range corresponding to the parameter contract, it generates a loop termination command and terminates the sterilization process. At the same time, it writes the termination time corresponding to the loop termination command, the sterilization process parameters of the termination stage, and the parameter contract into the record corresponding to the traceability number. After the sterilization process is stopped, the local controller sends the record to the cloud platform and requests the release of the frozen state. After the cloud platform unfreezes the process, it marks the traceability number of this sterilization cycle as sterilization incomplete and generates release restriction information for the traceability number, which is then pushed to the client.

10. A pressure steam sterilizer based on the Internet of Things (IoT), adapted to the remote control and management system of the pressure steam sterilizer based on the IoT as described in any one of claims 1 to 9, characterized in that, The pressure steam sterilizer includes a sterilizer body; wherein, the sterilizer body is equipped with the local controller and the Internet of Things communication unit.

Images