Method and device for automatically updating and synchronizing component package production environment based on medical platform software

Abstract

The invention discloses a method and a device for automatically updating and synchronizing a component package production environment based on medical platform software, and relates to the technical field of computers. Comprising the steps that after a component package uploading request of a developer is received, verification operation is carried out on the developer to obtain a verification result; if yes, receiving a current component package uploaded by the developer, and judging whether a historical component package corresponding to the current component package exists in a cloud component package warehouse or not; if yes, determining a total storage folder corresponding to the historical component package, and storing the current component package to a corresponding subdirectory in the total storage folder; and generating an updated link address of the current component package based on the subdirectory and sending the updated link address to the user. According to the method and the device, only authorized developers can update the component package in the updating process, and the component package is acquired through the link address, so that related medical personnel or systems can conveniently acquire the latest component package, and the performance and the safety of a medical software system are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for automatically updating and synchronizing a component package production environment based on medical platform software. Background Art

[0002] In the field of medical and health care, numerous complex software systems are widely used in key links such as medical data management, medical image processing, telemedicine services, and hospital information management. These software systems are usually composed of multiple interrelated components or modules, which are highly consistent with the concept of component packages in the present invention.

[0003] Taking medical image processing software as an example, it may include multiple key parts such as image acquisition component packages, image enhancement component packages, and disease diagnosis auxiliary component packages. With the continuous advancement of medical technology and the increasing requirements for disease diagnosis accuracy, these component packages must be continuously updated and optimized. Otherwise, a series of security risks will be caused by untimely updates or incorrect references of component packages, such as medical data leakage may lead to damage to patient privacy, or incorrect image enhancement processing may affect disease diagnosis results and other serious problems. At the same time, in the hospital information management system, important components such as patient information management component packages and medical resource scheduling component packages need to be updated in a timely manner to adapt to new medical regulations or improve data management efficiency. However, there is currently no automatic update and synchronization of the production environment of component packages. Patient information leakage or management chaos often occur due to errors in the update process. Therefore, automatic update and synchronization of the production environment of component packages has become a major pain point. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide a method and device for automatically updating and synchronizing a component package production environment based on medical platform software. The component package update method of the present invention has important application value in this scenario. Specifically, when developers conduct research and development on image enhancement algorithms and obtain new results, they can operate through the component package update process of the present invention. First, the developer sends a component package upload request, and the system performs strict preset verification operations on the developer based on this request. Only authorized developers can continue the subsequent process. After the verification is passed, the developer uploads the updated image enhancement component package. At this time, the system will determine whether there is a historical component package corresponding to the current component package in the cloud component package warehouse. If it exists, the system will determine the total storage folder corresponding to the historical component package according to the established rules, and accurately store the new component package in the corresponding subdirectory of the total storage folder. Subsequently, the updated link address of the current component package is generated based on this subdirectory, and the link address is sent to the relevant medical personnel or other related systems using the medical image processing software. In this way, medical personnel can easily obtain the latest component package through the link address, which greatly simplifies the reference process of the component package and significantly improves the update efficiency of the medical image processing software. This not only helps to improve the accuracy and efficiency of medical diagnosis, but also effectively reduces security risks caused by untimely updates or incorrect references of component packages, such as medical data leakage that may lead to damage to patient privacy, or incorrect image enhancement processing that may affect disease diagnosis results and other serious problems.

[0005] Similarly, in the hospital information management system, important components include patient information management component packages, medical resource scheduling component packages, etc. The method of the present invention can ensure that these component packages are updated in a timely, safe and efficient manner, thereby ensuring the stable operation of the hospital information management system and providing patients with better medical services. For example, when the patient information management component package needs to be updated to adapt to new medical regulations or improve data management efficiency, developers can follow the update process of the present invention to ensure that the update process of the component package meets safety and regulatory requirements, and avoid problems such as patient information leakage or management chaos caused by mistakes during the update process. Therefore, automatic update synchronization of the production environment of the component package has become a major pain point. The specific plan is as follows:

[0006] In a first aspect, the present invention discloses a method for automatically updating and synchronizing a component package production environment based on medical platform software, which is applied to a cloud component package warehouse, comprising:

[0007] Receive a component package upload request sent by a developer, and perform a preset verification operation on the developer based on the component package upload request to obtain a verification result;

[0008] If the verification result is that the verification is passed, receiving the current component package uploaded by the developer, and determining whether there is a historical component package corresponding to the current component package in the cloud component package repository;

[0009] If the historical component package corresponding to the current component package exists in the cloud component package warehouse, determining a total storage folder corresponding to the historical component package, and storing the current component package in a corresponding subdirectory in the total storage folder;

[0010] An updated link address of the current component package is generated based on the sub-directory, and the updated link address is sent to the user.

[0011] Optionally, the receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result, includes:

[0012] Receive a component package upload request sent by a developer, and obtain the developer ID information in the component package upload request;

[0013] Performing a preset verification operation on the developer based on the developer ID information;

[0014] If the same developer ID information is found in both the developer ID set and the authorized ID set, the verification result is determined to be verification passed;

[0015] Correspondingly, if the verification result is that the verification is passed, receiving the current component package uploaded by the developer includes:

[0016] If the verification result is that the verification is passed, the warehouse key corresponding to the cloud component package warehouse is obtained, so as to use the warehouse key to decrypt and obtain the decrypted cloud component package warehouse;

[0017] The current component package uploaded by the developer is received through the decrypted cloud-based component package warehouse.

[0018] Optionally, sending the updated link address to the user includes:

[0019] Receiving a current component package acquisition request sent by the user, and acquiring user ID information contained in the current component package acquisition request;

[0020] Performing the preset verification operation on the user based on the user ID information;

[0021] If the same user ID information is found in both the user ID set and the authorized ID set, the updated link address sent by the cloud component package repository is received.

[0022] Optionally, after storing the current component package in a corresponding subdirectory in the total storage folder, the method further includes:

[0023] Monitoring key indicators corresponding to the current component package; wherein the key indicators include the frequency of access to the cloud component package warehouse, the speed of component package downloading, and the frequency of component package update;

[0024] When the key indicator meets the preset alarm rule, the preset alarm processing operation is triggered, and an alarm message is generated to notify the developer; the preset alarm processing operation includes a script repair operation.

[0025] Optionally, after generating the updated link address of the current component package based on the subdirectory and sending the updated link address to the user, the method further includes:

[0026] Monitoring the cloud component package warehouse and determining whether an error occurs based on a preset error handling mechanism; wherein the error includes a network connection error, a component package download failure, and a component package version mismatch;

[0027] If the error occurs, a corresponding error log message is generated.

[0028] Optionally, if the error occurs, after generating corresponding error log information, the method further includes:

[0029] Obtaining all the historical component packages corresponding to the current component package, and determining whether there is a version-locked component package among all the historical component packages;

[0030] If the version-locked component package exists in all the historical component packages, obtaining a version-locked link address corresponding to the version-locked component package, and sending the version-locked link address to the user;

[0031] If the version-locked component package does not exist in all the historical component packages, determining the latest historical component package from all the historical component packages;

[0032] An automatic rollback operation is triggered based on the latest historical component package to obtain the latest historical link address corresponding to the latest historical component package, and the latest historical link address is sent to the user.

[0033] Optionally, generating the updated link address of the current component package based on the sub-directory includes:

[0034] Obtaining a preset warehouse link address corresponding to the cloud component package warehouse;

[0035] Determine a total storage link address based on the preset warehouse link address and the total storage folder;

[0036] The updated link address is generated based on the total storage link address and the subdirectory of the current component package.

[0037] In a second aspect, the present invention discloses an automatic update synchronization device for a component package production environment based on medical platform software, which is applied to a cloud component package warehouse, comprising:

[0038] A verification module, used for receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result;

[0039] A component package determination module, for receiving the current component package uploaded by the developer if the verification result is verification passed, and determining whether there is a historical component package corresponding to the current component package in the cloud component package repository;

[0040] A component package storage module, configured to determine a total storage folder corresponding to the historical component package if the historical component package corresponding to the current component package exists in the cloud component package warehouse, and store the current component package in a corresponding subdirectory in the total storage folder;

[0041] The link address generating module is used to generate an updated link address of the current component package based on the sub-directory, and send the updated link address to the user.

[0042] It can be seen that the present invention provides a method for automatically updating and synchronizing a component package production environment based on medical platform software, including: receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result; if the verification result is a verification pass, receiving the current component package uploaded by the developer, and judging whether there is a historical component package corresponding to the current component package in the cloud component package warehouse; if there is a historical component package corresponding to the current component package in the cloud component package warehouse, determining the total storage folder corresponding to the historical component package, and storing the current component package in the corresponding subdirectory in the total storage folder; generating an updated link address of the current component package based on the subdirectory, and sending the updated link address to the user. It can be seen that the present invention uniformly replaces the way of obtaining component packages with obtaining through link addresses, one component package corresponds to a link address of a component package, and when receiving a component package acquisition request from a user, the corresponding component package link address is sent to the user for direct call, which simplifies the reference process of component packages, improves production efficiency, and reduces security risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0044] Figure 1 A flowchart of an automatic update and synchronization method for a component package production environment based on medical platform software disclosed in the present invention;

[0045] Figure 2 A schematic diagram of establishing a component package warehouse content in the cloud disclosed by the present invention;

[0046] Figure 3 A schematic diagram of the flow of using the hook function disclosed in the present invention;

[0047] Figure 4 A schematic diagram of the automatic update and synchronization process of the component package production environment disclosed in the present invention;

[0048] Figure 5 A flowchart of a specific automatic update synchronization method for a component package production environment based on medical platform software disclosed in the present invention;

[0049] Figure 6 A schematic diagram of establishing a component package warehouse in the cloud disclosed by the present invention;

[0050] Figure 7 A schematic diagram of the structure of an automatic update synchronization device for a component package production environment based on medical platform software provided by the present invention. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0052] At present, in the process of software development, various businesses and methods are often extracted into various components or packages. These components or packages are used to solve the same part of the business and logic in different projects. However, the component package has its own life cycle, including creation and development debugging, update release and automatic synchronization, etc. Each update and release will re-acquire and release the project corresponding to the use of the component package, which is a repetitive assembly line work. As the number of software development projects increases, repeated component package references reduce production efficiency, so the automatic update and synchronization of the production environment of the component package has become a major pain point. To this end, the present invention provides a method for automatically updating and synchronizing the production environment of a component package based on medical platform software, which can simplify the reference process of the component package, improve production efficiency, and reduce safety risks.

[0053] The embodiment of the present invention discloses a method for automatically updating and synchronizing a component package production environment based on medical platform software, see Figure 1 As shown, applied to a cloud component package warehouse, the method includes:

[0054] Step S11: receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result.

[0055] In this embodiment, a component package upload request sent by a developer is received, and a preset verification operation is performed on the developer based on the component package upload request to obtain a verification result. Specifically, a component package upload request sent by a developer is received, and the developer ID information in the component package upload request is obtained; a preset verification operation is performed on the developer based on the developer ID information; if the same developer ID information is found in both the developer ID set and the authorized ID set, the verification result is determined to be verification passed.

[0056] It is understandable that the present invention establishes a centralized cloud component package warehouse in a cloud environment for storing component packages of various versions. The cloud component package warehouse is a storage system based on cloud storage or a server to ensure that the component packages are safely and reliably stored in the warehouse. A version management mechanism is implemented for each component package, for example, using a standard version control system (such as Git) to ensure that each component package version is properly recorded, managed and tracked. When a component package is updated, the developer publishes the component package upload request to the cloud component package warehouse, and through the automated process equipped in the warehouse, the link address is automatically updated and the relevant team is notified when a new version is released.

[0057] The present invention uses identity authentication, authorization mechanism, access permission mechanism, data transmission encryption mechanism, warehouse isolation, version control, and log recording to improve security. It should be pointed out that operations such as identity authentication, authorization mechanism, and access permission mechanism are automatically verified when the visitor accesses in order to determine the identity of the visitor. Strict access control is set on the cloud component package warehouse to ensure that only authorized users can access the warehouse and component packages, and use identity authentication and authorization mechanisms such as role-based access control (RBAC) or access tokens to limit access rights. Among them, warehouse isolation refers to isolating different component package warehouses to ensure that each project or team can only access the warehouse it needs, reducing the risk of misoperation or accidental access.

[0058] In addition, update the project configuration, obtain the configuration file location and add the cloud warehouse information, for example:

[0059] {

[0060] "componentRepo": "https: / / component-repo.com / packages / "

[0061] }.

[0062] Furthermore, replace the existing acquisition logic and obtain the cloud warehouse component package version URL (Uniform Resource Locator). For example, convert the code import ". / table / 1.0.0" into the following code through the production environment:

[0063] import "https: / / component-repo.com / packages / table / 1.0.0".

[0064] Step S12: If the verification result is that the verification is passed, the current component package uploaded by the developer is received, and it is determined whether there is a historical component package corresponding to the current component package in the cloud component package repository.

[0065] In this embodiment, a preset verification operation is performed on the developer based on the component package upload request to obtain a verification result. If the verification result is a passed verification, the current component package uploaded by the developer is received, and it is determined whether there is a historical component package corresponding to the current component package in the cloud component package warehouse. Specifically, if the verification result is a passed verification, the warehouse key corresponding to the cloud component package warehouse is obtained so that the warehouse key can be used for decryption to obtain the decrypted cloud component package warehouse; the current component package uploaded by the developer is received through the decrypted cloud component package warehouse. It can be understood that the cloud component package warehouse is encrypted using HTTPS (Hyper Text Transfer Protocol over Secure Socket Layer) to protect the security of data transmission and prevent man-in-the-middle attacks and data leakage. After the visitor passes the verification, the cloud component package warehouse can be decrypted and accessed.

[0066] Step S13: If the historical component package corresponding to the current component package exists in the cloud component package warehouse, a general storage folder corresponding to the historical component package is determined, and the current component package is stored in a corresponding subdirectory in the general storage folder.

[0067] In this embodiment, after determining whether there is a historical component package corresponding to the current component package in the cloud component package warehouse, if there is a historical component package corresponding to the current component package in the cloud component package warehouse, the total storage folder corresponding to the historical component package is determined, and the current component package is stored in the corresponding subdirectory in the total storage folder. It can be understood that each component package in the warehouse corresponds to a unique file directory, that is, the total storage folder. Each update of the component package will generate a corresponding subdirectory in the total storage folder for storage according to the updated component package version number. For example, for the table component, the address of the corresponding total storage folder is as follows: https: / / component-repo.com / packages / table. Each time the component package releases a version, a corresponding subdirectory is generated. For example, the storage address of the subdirectory corresponding to the component package of version 1.0.0 is https: / / component-repo.com / packages / table / 1.0.0; when a version 1.0.1 is released, the storage address of the subdirectory is https: / / component-repo.com / packages / table / 1.0.1. In the production environment, the URL address with the component package version is used, for example:

[0068] https: / / component-repo.com / packages / table / 1.0.1;

[0069] When only the content of component package 1.0.1 is modified, the version is not upgraded. The places where the component package is used in the production environment will be automatically updated because the address of the component package is an address with a unique version tag. The naming of the component package should be descriptive, easy to understand and follow certain naming rules so that developers can easily identify and use it. You can use the agreed naming prefix or suffix, use standard version control methods to manage different versions of the component package, track and record changes to the component package, and ensure that only authorized personnel can release new component package versions. Each version number of the component package is named according to the preset naming convention. The version number is used to identify the uniqueness of the current version. A unique version number is assigned to each component package version, such as 1.0.0, 2.1.3, etc. The version number naming convention and update rules ensure that changes in the version number reflect the functions and changes of the component package. The preset naming conventions are as follows: The standard version number uses the format of VX.YZ, such as V5.3.2; V (version number) represents the version number, abbreviated as V; X, Y, and Z are non-negative integers, X is the major version number, Y is the minor version number, and Z is the revision number. The first released version is named V1.0.0, and the version number is updated once each time a version is updated. The update rules for the version number are as follows: When modifying bugs and optimizing functions, modify the third digit, that is, Z+1, and the rest remains unchanged. For example: V1.0.0 is updated to V1.0.1. When adding a small function, modify the second digit, that is, Y+1, and the rest remains unchanged, for example: V1.0.0 is updated to V1.1.0. When adding a large function or making major changes to the original function, modify the first digit, that is, X+1, and the rest remains unchanged, for example: V1.0.0 is updated to V2.0.0. It should be noted that after the previous digits are added, the following digits are counted from zero. For example Figure 2 As shown, the cloud component package warehouse contains storage subdirectories corresponding to multiple version numbers of each component package. In the storage subdirectories, you can obtain the code files and description information of the component package; the description information, such as this component package is used for table-related, this component package is used for button-related or other descriptions. Each component package should have clear documentation and descriptions so that developers can understand its functions, usage and precautions.

[0070] Step S14: Generate an updated link address of the current component package based on the sub-directory, and send the updated link address to the user.

[0071] In this embodiment, after the current component package is stored in the corresponding subdirectory in the total storage folder, an updated link address of the current component package is generated based on the subdirectory, and the updated link address is sent to the user. Specifically, the preset warehouse link address corresponding to the cloud component package warehouse is obtained; the total storage link address is determined based on the preset warehouse link address and the total storage folder; the updated link address is generated based on the total storage link address and the subdirectory of the current component package. The current component package acquisition request sent by the user is received, and the user ID information contained in the current component package acquisition request is obtained; the preset verification operation is performed on the user based on the user ID information; if the same user ID information is found in both the user ID set and the authorized ID set, the updated link address sent by the cloud component package warehouse is received.

[0072] It is understandable that the link address generated in the present invention is a URL address, and the preset warehouse link address corresponding to the cloud component package warehouse is obtained, that is, the basic URL address, such as the following address: https: / / component-repo.com / packages / . Then, the basic URL and the version number of the component package are used to construct a complete component package version URL address, and the version number is added to the end of the basic URL to form a final URL link address, such as https: / / component-repo.com / packages / table / 1.0.0.

[0073] Write hook functions to detect whether a new version of a component package is available and whether to roll back the component package. Hook functions can be implemented in a variety of programming languages, such as Python, JavaScript, etc., depending on the application technology stack, and ensure that the environment supports writing and running these scripts. Determine when to trigger the hook function based on demand, such as in periodic tasks (such as daily, hourly) or when specific events occur (such as new version releases, error detection). Write logic in the hook function, including tasks such as version detection, downloading new versions, and rollback. According to the automatic update synchronization solution, write code to interact with the cloud component package repository to obtain the latest version of the component package, check the version number, handle errors, etc. Implement error handling and rollback logic in the hook function. If an error occurs, write code to roll back the system to the previous stable version to ensure that it does not affect the production environment.

[0074] If a new version is available, the latest component package will be automatically downloaded from the cloud component package warehouse; if the component package needs to be rolled back, it will be automatically rolled back to the corresponding component package from the cloud component package warehouse. In the automatic update process, the new version of the component package is obtained from the cloud component package warehouse. HTTPS encryption is used to ensure the security of data transmission, effectively preventing the risk of man-in-the-middle attacks and information leakage, thereby ensuring the confidentiality and integrity of the download process.

[0075] like Figure 3 As shown in the figure, after the component package releases a new version, the hook function introduces each project, processes the release of the new version of the component package, obtains the corresponding new version number, and uses the new version number to update the URL address of the component package to achieve automatic update of the project component package. Figure 4 As shown, the developer creates a component package and manages the component package based on the component package version management rules, performs local development and debugging on the component package, and uses it as a local project development after development and debugging. The debugged component package is updated to the cloud component repository, and the component version URL address is constructed and exposed to facilitate operations such as upgrading and rolling back the component package.

[0076] In the creation and development and debugging stage of the component package, for example, when the developer is developing and debugging on the local machine, the present invention replaces the way of obtaining the component package when publishing online after the development and debugging is completed with obtaining it through the URL, and one component package corresponds to the URL of one component package. A global component package warehouse is established in the cloud, and the URL link address of each component package is exposed. When the component package passes the development and debugging, each component package is updated or rolled back and then published in the global component package warehouse in the cloud, so as to achieve the effect of automatic update synchronization without the need to re-acquire and publish the project.

[0077] It can be seen that the present invention provides a method for automatically updating and synchronizing a component package production environment based on medical platform software, including: receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result; if the verification result is a verification pass, receiving the current component package uploaded by the developer, and judging whether there is a historical component package corresponding to the current component package in the cloud component package warehouse; if there is a historical component package corresponding to the current component package in the cloud component package warehouse, determining the total storage folder corresponding to the historical component package, and storing the current component package in the corresponding subdirectory in the total storage folder; generating an updated link address of the current component package based on the subdirectory, and sending the updated link address to the user. It can be seen that the present invention uniformly replaces the way of obtaining component packages with obtaining through link addresses, one component package corresponds to a link address of a component package, and when receiving a component package acquisition request from a user, the corresponding component package link address is sent to the user for direct call, which simplifies the reference process of component packages, improves production efficiency, and reduces security risks.

[0078] See also Figure 5 As shown, an embodiment of the present invention discloses an automatic update synchronization method for a component package production environment based on medical platform software. Compared with the previous embodiment, this embodiment further illustrates and optimizes the technical solution.

[0079] Step S21: receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result.

[0080] Step S22: If the verification result is that the verification is passed, the current component package uploaded by the developer is received, and it is determined whether there is a historical component package corresponding to the current component package in the cloud component package repository.

[0081] Step S23: If the historical component package corresponding to the current component package exists in the cloud component package warehouse, a general storage folder corresponding to the historical component package is determined, and the current component package is stored in a corresponding subdirectory in the general storage folder.

[0082] Step S24: Generate an updated link address of the current component package based on the sub-directory, and send the updated link address to the user.

[0083] In this embodiment, Figure 6As shown in the figure, each time a new component package version is released, the URL link address of the corresponding version is automatically generated. These URL link addresses will point to the corresponding version in the cloud component package warehouse, and these URL addresses are exposed so that users can access the corresponding component package based on the URL address. The process of changing the way to obtain the component package from the local version to the corresponding version of the component package through the URL involves changes in the project configuration file or other related settings.

[0084] Step S25: monitor the cloud component package repository and determine whether an error occurs based on a preset error handling mechanism.

[0085] In this embodiment, after generating the updated link address of the current component package based on the subdirectory and sending the updated link address to the user, the cloud component package warehouse is monitored to determine whether an error occurs based on a preset error handling mechanism. The error conditions include network connection errors, component package download failures, and component package version mismatches; a robust error handling mechanism is implemented in the automatic update process to capture and handle possible error conditions, including network connection errors, download failures, and version mismatches.

[0086] It is understandable that the key indicators corresponding to the current component package are monitored; wherein the key indicators include the frequency of access to the cloud component package warehouse, the speed of component package downloading, and the frequency of component package updating; when the key indicators meet the preset alarm rules, the preset alarm processing operation is triggered, and an alarm message is generated to notify the developer; the preset alarm processing operation includes a script repair operation. The present invention notifies channels and automates alarms by defining key indicators and setting alarm rules. Among them, whether to trigger an alarm is determined based on key indicators and pre-set alarm rules. For example, if the download speed of the component package exceeds a certain threshold or the update of the component package fails, an alarm is triggered. Configure the alarm notification channel to ensure that relevant personnel can be notified in time when a problem occurs. The notification channel may include email, text message, Slack notification, etc. Configure automated response alarm measures so that predefined actions are automatically taken when an alarm is triggered, which can achieve the effects of automatically executing certain repair scripts and reducing system load.

[0087] Step S26: If the error occurs, a corresponding error log message is generated to trigger a component package rollback operation.

[0088] In this embodiment, detailed error logs are recorded at each stage of the automatic update, which is helpful for troubleshooting and understanding the causes of errors. In addition, the log statistics function can also record the access and operation records of the warehouse, which is conducive to tracking and monitoring the activities of users.

[0089] Furthermore, all the historical component packages corresponding to the current component package are obtained, and it is determined whether there is a version-locked component package among all the historical component packages; if the version-locked component package exists among all the historical component packages, the version-locked link address corresponding to the version-locked component package is obtained, and the version-locked link address is sent to the user; if the version-locked component package does not exist among all the historical component packages, the latest historical component package is determined from all the historical component packages; an automatic rollback operation is triggered based on the latest historical component package to obtain the latest historical link address corresponding to the latest historical component package, and the latest historical link address is sent to the user.

[0090] It is understandable that the automatic rollback strategy, that is, when a critical error occurs, automatically rolls the system back to the previous stable state, involves a backup and recovery mechanism to ensure that it can be quickly restored to a safe state. Consider implementing a version locking strategy to ensure that only pre-tested stable versions of locked component packages can be used during the update process to prevent untested component packages from affecting the production environment.

[0091] The production environment in this invention refers to an environment that includes all functions. The environment used by any project is based on this environment, and then adjusted or modified according to the personalized needs of the customer. Component package refers to component design, which is formed by disassembling, summarizing, and reorganizing the elements in the functions and visual expressions, and based on the purpose of being reused, forming standardized components, and constructing the entire design plan through multi-dimensional combinations, and organizing these components together to form a component package. The cloud is a software platform that uses application virtualization technology, integrating multiple functions such as software search, download, use, management, and backup.

[0092] The present invention establishes a cloud component package warehouse so that the component package versions are centrally managed. Developers can easily obtain the required component packages through URL links, reducing the complexity of manual downloading and management; component package version management ensures that each version is tracked and recorded, and the development team can accurately understand the change history of the component package; the automatic generation of URL link addresses provides a stable and consistent acquisition method, simplifies the reference process of the component package, and makes update synchronization easier and controllable; the realization of automatic component package updates eliminates the tediousness of manual operations, improves production efficiency, and ensures that the component package is always up to date and rollback; enhanced security and permission control protect the access and data transmission of the component package, reducing security risks; the monitoring and alarm system realizes real-time monitoring and rapid response, helps identify and solve problems, and improves the stability of the component package; error handling and automatic rollback strategies ensure reliability during the update process and reduce the potential impact of the component package. The present invention is more efficient, safe, and flexible for component package management and automatic update solutions, reduces the risk of human errors, and brings a better development experience and reliability of the production environment to the team.

[0093] For the specific contents of the above steps S21 to S23, reference may be made to the corresponding contents disclosed in the above embodiments, which will not be repeated here.

[0094] It can be seen that the embodiment of the present application receives a component package upload request sent by a developer, and performs a preset verification operation on the developer based on the component package upload request to obtain a verification result; if the verification result is verification passed, the current component package uploaded by the developer is received, and it is determined whether there is a historical component package corresponding to the current component package in the cloud component package warehouse; if the historical component package corresponding to the current component package exists in the cloud component package warehouse, the total storage folder corresponding to the historical component package is determined, and the current component package is stored in the corresponding subdirectory of the total storage folder; an updated link address of the current component package is generated based on the subdirectory, and the updated link address is sent to the user; the cloud component package warehouse is monitored to determine whether an error occurs based on a preset error handling mechanism; if the error occurs, corresponding error log information is generated to trigger a component package rollback operation, thereby simplifying the component package reference process, improving production efficiency, and reducing security risks.

[0095] See also Figure 7 As shown, the embodiment of the present invention also discloses a component package production environment automatic update synchronization device based on medical platform software, which is applied to a cloud component package warehouse, including:

[0096] The verification module 11 is used to receive a component package upload request sent by a developer, and perform a preset verification operation on the developer based on the component package upload request to obtain a verification result;

[0097] The component package determination module 12 is used for receiving the current component package uploaded by the developer if the verification result is verification passed, and determining whether there is a historical component package corresponding to the current component package in the cloud component package repository;

[0098] The component package storage module 13 is used to determine the total storage folder corresponding to the historical component package if the historical component package corresponding to the current component package exists in the cloud component package warehouse, and store the current component package in the corresponding subdirectory in the total storage folder;

[0099] The link address generating module 14 is used to generate an updated link address of the current component package based on the sub-directory, and send the updated link address to the user.

[0100] It can be seen that the present invention includes: receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result; if the verification result is a verification pass, receiving the current component package uploaded by the developer, and judging whether there is a historical component package corresponding to the current component package in the cloud component package warehouse; if there is a historical component package corresponding to the current component package in the cloud component package warehouse, determining the total storage folder corresponding to the historical component package, and storing the current component package in the corresponding subdirectory in the total storage folder; generating an updated link address of the current component package based on the subdirectory, and sending the updated link address to the user. It can be seen that the present invention uniformly replaces the way of obtaining component packages with obtaining through link addresses, one component package corresponds to a link address of a component package, and when receiving a component package acquisition request from a user, the corresponding component package link address is sent to the user for direct call, which simplifies the reference process of component packages, improves production efficiency, and reduces security risks.

[0101] In some specific embodiments, the verification module 11 specifically includes:

[0102] A component package upload request receiving unit, used for receiving a component package upload request sent by a developer;

[0103] A developer ID information acquisition unit, used to acquire the developer ID information in the component package upload request;

[0104] A first verification unit, configured to perform a preset verification operation on the developer based on the developer ID information;

[0105] The verification determination unit is used to determine that the verification result is verification passed if the same developer ID information is found in both the developer ID set and the authorized ID set.

[0106] In some specific embodiments, the component package determination module 12 specifically includes:

[0107] A warehouse key acquisition unit, configured to acquire a warehouse key corresponding to the cloud component package warehouse if the verification result is that the verification is passed;

[0108] A warehouse decryption unit, used to use the warehouse key to decrypt and obtain a decrypted cloud component package warehouse;

[0109] A current component package receiving unit, configured to receive the current component package uploaded by the developer through the decrypted cloud component package repository;

[0110] The historical component package existence determination unit is used to determine whether there is a historical component package corresponding to the current component package in the cloud component package repository.

[0111] In some specific embodiments, the component package storage module 13 specifically includes:

[0112] a total storage folder determining unit, configured to determine a total storage folder corresponding to the historical component package if the historical component package corresponding to the current component package exists in the cloud component package warehouse;

[0113] A current component package storage unit, used to store the current component package in a corresponding subdirectory of the total storage folder;

[0114] A key indicator monitoring unit, used to monitor the key indicators corresponding to the current component package; wherein the key indicators include the frequency of access to the cloud component package warehouse, the speed of component package downloading, and the frequency of component package updating;

[0115] An alarm unit, used to trigger a preset alarm processing operation when the key indicator meets the preset alarm rule; the preset alarm processing operation includes a script repair operation;

[0116] The alarm message generating unit is used to generate an alarm message to notify the developer.

[0117] In some specific embodiments, the link address generation module 14 specifically includes:

[0118] A preset warehouse link address acquisition unit, used to acquire the preset warehouse link address corresponding to the cloud component package warehouse;

[0119] A total storage link address determining unit, configured to determine a total storage link address based on the preset warehouse link address and the total storage folder;

[0120] An updated link address generating unit, configured to generate the updated link address based on the total storage link address and the subdirectory of the current component package;

[0121] A current component package acquisition request receiving unit, configured to receive a current component package acquisition request sent by the user;

[0122] A user ID information acquisition unit, used to acquire the user ID information included in the current component package acquisition request;

[0123] A second verification unit, configured to perform the preset verification operation on the user based on the user ID information;

[0124] The updated link address receiving unit is used to receive the updated link address sent by the cloud component package repository if the same user ID information is found in both the user ID set and the authorized ID set.

[0125] In some specific embodiments, after the link address generation module 14, it further includes:

[0126] A warehouse monitoring unit, used to monitor the cloud component package warehouse;

[0127] An error condition judgment unit, used to judge whether an error condition occurs based on a preset error handling mechanism; wherein the error condition includes a network connection error, a component package download failure, and a component package version mismatch;

[0128] An error log information generating unit, used for generating corresponding error log information if the error situation occurs;

[0129] A historical component package acquisition unit, used to acquire all the historical component packages corresponding to the current component package;

[0130] A version-locked component package determination unit, used to determine whether there is a version-locked component package in all the historical component packages;

[0131] a version lock link address determining unit, configured to obtain a version lock link address corresponding to the version lock component package if the version lock component package exists in all the historical component packages;

[0132] A version lock link address sending unit, used for sending the version lock link address to the user;

[0133] The latest historical component package determining unit is used to determine the latest historical component package from all the historical component packages if the version-locked component package does not exist in all the historical component packages;

[0134] A rollback operation triggering unit, used to trigger an automatic rollback operation based on the latest historical component package to obtain the latest historical link address corresponding to the latest historical component package;

[0135] The latest historical link address sending unit is used to send the latest historical link address to the user.

[0136] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0137] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0138] The above is a detailed introduction to the automatic update and synchronization method and device for the component package production environment based on the medical platform software provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for automatically updating and synchronizing a component package production environment based on medical platform software, characterized in that: Applied to cloud component package repositories, including: Receive a component package upload request sent by a developer, and perform a preset verification operation on the developer based on the component package upload request to obtain a verification result; If the verification result is that the verification is passed, receiving the current component package uploaded by the developer, and determining whether there is a historical component package corresponding to the current component package in the cloud component package repository; If the historical component package corresponding to the current component package exists in the cloud component package warehouse, determining a total storage folder corresponding to the historical component package, and storing the current component package in a corresponding subdirectory in the total storage folder; An updated link address of the current component package is generated based on the sub-directory, and the updated link address is sent to the user.

2. The method for automatically updating and synchronizing a component package production environment based on medical platform software according to claim 1, characterized in that: The receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result, includes: Receive a component package upload request sent by a developer, and obtain the developer ID information in the component package upload request; Performing a preset verification operation on the developer based on the developer ID information; If the same developer ID information is found in both the developer ID set and the authorized ID set, the verification result is determined to be verification passed; Correspondingly, if the verification result is that the verification is passed, receiving the current component package uploaded by the developer includes: If the verification result is that the verification is passed, the warehouse key corresponding to the cloud component package warehouse is obtained, so as to use the warehouse key to decrypt and obtain the decrypted cloud component package warehouse; The current component package uploaded by the developer is received through the decrypted cloud-based component package warehouse.

3. The automatic update synchronization method for component package production environment based on medical platform software according to claim 2, characterized in that: The sending the updated link address to the user comprises: Receiving a current component package acquisition request sent by the user, and acquiring user ID information contained in the current component package acquisition request; Performing the preset verification operation on the user based on the user ID information; If the same user ID information is found in both the user ID set and the authorized ID set, the updated link address sent by the cloud component package repository is received.

4. The method for automatically updating and synchronizing a component package production environment based on medical platform software according to claim 1, characterized in that: After storing the current component package in the corresponding subdirectory of the total storage folder, the method further includes: Monitoring key indicators corresponding to the current component package; wherein the key indicators include the frequency of access to the cloud component package warehouse, the speed of component package downloading, and the frequency of component package update; When the key indicator meets the preset alarm rule, the preset alarm processing operation is triggered, and an alarm message is generated to notify the developer; the preset alarm processing operation includes a script repair operation.

5. The method for automatically updating and synchronizing a component package production environment based on medical platform software according to claim 1, characterized in that: Also includes: Monitoring the cloud component package warehouse and determining whether an error occurs based on a preset error handling mechanism; wherein the error includes a network connection error, a component package download failure, and a component package version mismatch; If the error occurs, a corresponding error log message is generated.

6. The method for automatically updating and synchronizing a component package production environment based on medical platform software according to claim 5, characterized in that: If the error occurs, after generating the corresponding error log information, the method further includes: Obtaining all the historical component packages corresponding to the current component package, and determining whether there is a version-locked component package among all the historical component packages; If the version-locked component package exists in all the historical component packages, obtaining a version-locked link address corresponding to the version-locked component package, and sending the version-locked link address to the user; If the version-locked component package does not exist in all the historical component packages, determining the latest historical component package from all the historical component packages; An automatic rollback operation is triggered based on the latest historical component package to obtain the latest historical link address corresponding to the latest historical component package, and the latest historical link address is sent to the user.

7. The automatic update and synchronization method for component package production environment based on medical platform software according to any one of claims 1 to 6, characterized in that: The step of generating the updated link address of the current component package based on the sub-directory includes: Obtaining a preset warehouse link address corresponding to the cloud component package warehouse; Determine a total storage link address based on the preset warehouse link address and the total storage folder; The updated link address is generated based on the total storage link address and the subdirectory of the current component package.

8. An automatic update synchronization device for a component package production environment based on medical platform software, characterized in that: Applied to cloud component package repositories, including: A verification module, used for receiving a component package upload request sent by a developer, and performing a preset verification operation on the developer based on the component package upload request to obtain a verification result; A component package determination module, for receiving the current component package uploaded by the developer if the verification result is verification passed, and determining whether there is a historical component package corresponding to the current component package in the cloud component package repository; A component package storage module, configured to determine a total storage folder corresponding to the historical component package if the historical component package corresponding to the current component package exists in the cloud component package warehouse, and store the current component package in a corresponding subdirectory in the total storage folder; The link address generating module is used to generate an updated link address of the current component package based on the sub-directory, and send the updated link address to the user.

Images