Ultrasound device configuration synchronization method, system, ultrasound device, and cloud platform

Abstract

The application is suitable for the field of ultrasonic technology, and provides an ultrasonic equipment configuration synchronization method and system, ultrasonic equipment and a cloud platform. The method comprises the following steps: when being a source equipment, in response to an uploading instruction, generating a source configuration data packet containing equipment characteristic information and user personalized configuration data and sending the source configuration data packet to the cloud platform; when being a target equipment, in response to a synchronization instruction, sending a configuration list request containing equipment characteristic information to the cloud platform; receiving a configuration list returned by the cloud platform, the configuration list containing compatibility states between each source configuration data packet and the target equipment under a user account; in response to an operation of a user selecting a selected configuration item from the configuration list, sending a download request for the selected configuration item to the cloud platform; and receiving and applying a target configuration data packet corresponding to the selected configuration item issued by the cloud platform to update a local configuration. The application solves the problem of deficiencies in synchronization of personalized configuration across equipment in existing ultrasonic equipment.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of ultrasound, in particular to an ultrasound device configuration synchronization method and system, an ultrasound device and a cloud platform. BACKGROUND

[0002] Modern ultrasound diagnostic systems are highly complex medical imaging devices. In order to improve diagnostic efficiency and meet the individual work habits of different physicians, the system software usually supports highly personalized configuration. These configurations not only include basic image parameters such as brightness, contrast, gain, dynamic range, etc., but also cover complex diagnostic process preferences, such as commonly used measurement tool combinations, report template formats, shortcut operation modes, etc. These personalized configurations are crucial for optimizing the physician's workflow, ensuring the consistency of diagnostic image quality, and improving the overall user experience.

[0003] However, in current clinical practice, the management and synchronization of these personalized configurations face many challenges. In large hospitals or medical centers, a physician may need to use multiple different ultrasound devices in different examination rooms, or a device may be shared by multiple physicians. In this complex multi-user, multi-device environment, the limitations of existing technologies are increasingly evident:

[0004] Configuration isolation, unable to share: Currently, the personalized configuration information of most ultrasound devices is only stored in the local hard disk of the device. This "information island" mode results in the inability to automatically share configurations between different devices. When a physician switches from one device to another, they must reconfigure manually, which not only greatly reduces work efficiency, but also easily leads to inconsistent configurations due to memory bias, affecting the standardization of diagnosis.

[0005] Poor compatibility, difficult migration: Even if manual migration is attempted, there are serious compatibility issues. Different models, different software versions, and even different batches of ultrasound devices may have differences in hardware architecture and software functions. Simply copying and importing configuration files through external storage media (such as a USB flash drive) often fails due to incompatibility, and may even cause device software errors or system crashes.

[0006] High backup risk, data loss: Relying on local storage means that configuration data is easily lost permanently due to device failure, system reset, or hard disk damage. Due to the lack of reliable and automated cloud backup mechanisms, physicians' carefully tuned personalized configurations face significant security risks.

[0007] Management is rough, and the operation and maintenance cost is high: The existing configuration management method lacks fine-grained, visualized management and analysis of configuration items. When batch configuration updates or problem troubleshooting are needed, the operation and maintenance work becomes very complex and costly.

[0008] Although part of the prior art attempts to load independent image parameter configuration files through user login to solve the problem of multiple people using a single device to some extent. However, such a scheme is usually limited to cloud transmission of image parameters and does not cover more extensive configuration contents such as diagnostic process preferences, nor can it provide a specific technical solution to solve the deep compatibility problem between different devices.

[0009] In summary, the prior art has obvious deficiencies in realizing seamless synchronization, intelligent compatibility and safe backup of personalized configuration of ultrasonic equipment across devices, and there is an urgent need for a more intelligent and comprehensive technical solution that can overcome the above-mentioned defects. SUMMARY

[0010] Therefore, the purpose of the present application is to provide an ultrasonic equipment configuration synchronization method, system, ultrasonic equipment and cloud platform to fundamentally solve the problems existing in the prior art when synchronizing personalized configuration across devices.

[0011] According to an ultrasonic equipment configuration synchronization method according to an embodiment of the present application, applied to an ultrasonic equipment, the method comprises:

[0012] When the ultrasonic equipment performs a configuration upload operation as a source device, in response to an upload instruction, a source configuration data packet containing device characteristic information of itself and user personalized configuration data is generated and sent to a cloud platform for storage and association with a user account by the cloud platform;

[0013] When the ultrasonic equipment performs a configuration synchronization operation as a target device, in response to a synchronization instruction, a configuration list request containing device characteristic information of itself is sent to the cloud platform;

[0014] A configuration list containing the compatibility status between each source configuration data packet under the user account and the target device is received from the cloud platform;

[0015] In response to the user's operation of selecting a selected configuration item from the configuration list, a download request for the selected configuration item is sent to the cloud platform;

[0016] The target configuration data packet corresponding to the selected configuration item issued by the cloud platform is received and applied to update the local configuration.

[0017] In addition, the ultrasonic equipment configuration synchronization method according to the above-mentioned embodiments of the present application can also have the following additional technical features:

[0018] Further, applied to an ultrasonic equipment, the method comprises:

[0019] When the ultrasound device performs a configuration upload operation as a source device, in response to an upload instruction, a source configuration data packet containing device feature information and user personalized configuration data of the ultrasound device is generated and sent to a cloud platform for storage and association with a user account;

[0020] When the ultrasound device performs a configuration synchronization operation as a target device, in response to a synchronization instruction, a configuration list request containing device feature information of the ultrasound device is sent to the cloud platform;

[0021] A configuration list containing compatibility status between each source configuration data packet under a user account and the target device is received from the cloud platform;

[0022] In response to a user selecting a selected configuration item from the configuration list, a download request for the selected configuration item is sent to the cloud platform;

[0023] A target configuration data packet corresponding to the selected configuration item is received and applied from the cloud platform to update the local configuration.

[0024] Further, the step of confirming with the user based on the conversion execution log and applying the target configuration data packet to update the local configuration after obtaining a confirmation instruction from the user comprises:

[0025] The conversion execution log is parsed to extract the operation type, the affected configuration parameter item, and the details of the value or state change before and after the operation of each adaptive operation;

[0026] Based on the extracted details, a visualized change confirmation summary in the form of a highlighted or contrasted list is generated on the user interaction interface;

[0027] A specific instruction input by the user through the change confirmation summary interface is received, the specific instruction being one of confirmation, cancellation, or modification;

[0028] In response to receiving the confirmation instruction input by the user, the target configuration data packet is applied.

[0029] Further, after the step of receiving the specific instruction input by the user through the change confirmation summary interface, the method further comprises:

[0030] In response to receiving the modification instruction input by the user, an interactive option is provided for each modified configuration item to allow the user to select from a set of preset solutions, the preset solutions including at least maintaining the original state of the configuration item in the source configuration data packet, or applying the adapted state of the configuration item set in the target configuration data packet, or reverting to the default state of the factory default value of the device;

[0031] updating the corresponding configuration parameter item in the target configuration data package in response to the target solution selected by the user.

[0032] Further, the method further comprises:

[0033] creating a local snapshot of all personalized configuration data of the target device and storing before applying the target configuration data package to update the local configuration;

[0034] if any error or configuration conflict occurs to interrupt the application, automatically suspending the application process and using the local snapshot to restore the configuration of the target device to the state before the application when applying the target configuration data package to update the local configuration;

[0035] if a user-triggered rollback instruction is received within a preset time after applying the target configuration data package, using the local snapshot to restore the configuration of the target device to the state before the application.

[0036] Further, the step of generating and sending the source configuration data package containing the device feature information and the user personalized configuration data to the cloud platform comprises:

[0037] real-time acquisition of state information of multiple dimensions of the ultrasound device to constitute the device feature information;

[0038] serializing all personalized configuration data of the current activity of the user into a predefined structured data format;

[0039] encapsulating the device feature information and the serialized user personalized configuration data into a structured source configuration data package;

[0040] establishing an encrypted secure communication link with the cloud platform, and sending the source configuration data package to the cloud platform through the secure communication link.

[0041] Another embodiment of the present application also provides an ultrasound device configuration synchronization method applied to a cloud platform, which comprises:

[0042] receiving and storing the source configuration data package containing the device feature information and the user personalized configuration data sent by the ultrasound device as a source device, and establishing the association between the source configuration data package and the corresponding user account;

[0043] receiving the configuration list request containing the device feature information sent by the ultrasound device as a target device;

[0044] According to the device characteristic information of the target device and a preset compatibility rule library, a preliminary compatibility judgment is performed on each source configuration data packet associated with the user account to generate a configuration list containing the compatibility status of each source configuration data packet, and the configuration list is returned to the target device;

[0045] A download request for a selected configuration item in the configuration list is received from the target device;

[0046] In response to the download request, a source configuration data packet corresponding to the selected configuration item is processed to generate a target configuration data packet, which is then delivered to the target device.

[0047] Further, the step of processing the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet and delivering the target configuration data packet to the target device comprises:

[0048] When the compatibility status of the selected configuration item is compatible, the source configuration data packet corresponding to the selected configuration item is directly used as the target configuration data packet and delivered to the target device;

[0049] When the compatibility status of the selected configuration item is conversion required, a configuration conversion engine is started to adaptively process the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet adapted to the target device, a conversion execution log recording the adaptive processing process is synchronously generated, and the target configuration data packet and the conversion execution log are delivered to the target device.

[0050] Further, the step of receiving and storing a source configuration data packet containing device characteristic information and user personalized configuration data from an ultrasound device as a source device and establishing an association between the source configuration data packet and a corresponding user account comprises:

[0051] An encrypted secure communication link is established with the source device, and an upload request containing user authentication credentials and the source configuration data packet is received from the source device through the secure communication link;

[0052] The user authentication credentials are verified to confirm the user's identity and obtain a unique user identifier;

[0053] If the verification is passed, device characteristic information and user personalized configuration data are parsed and extracted from the source configuration data packet;

[0054] According to the extracted device characteristic information, a unique device record corresponding to the source device is queried or created in a device information database, and a corresponding device identifier is obtained;

[0055] create a new configuration record in the configuration storage database, and store the encrypted configuration data of the user personalized configuration data into the configuration record;

[0056] store the configuration record in association with the user identifier and the device identifier into a configuration index database.

[0057] Further, the step of performing preliminary compatibility judgment on each source configuration data package associated with the user account according to the device feature information of the target device and the preset compatibility rule library comprises:

[0058] retrieve index records of all source configuration data packages associated with the user account from the configuration index database according to the user account in the received configuration list request;

[0059] extract the stored device feature information of the source device for each retrieved index record;

[0060] perform multi-level decision tree comparison between the extracted device feature information of the source device and the device feature information of the target device carried in the configuration list request to determine the compatibility state;

[0061] add the determined compatibility state and the corresponding source configuration data package information into the currently constructed configuration list.

[0062] Further, the step of performing multi-level decision tree comparison between the extracted device feature information of the source device and the device feature information of the target device carried in the configuration list request to determine the compatibility state comprises:

[0063] compare the device model and the firmware version in the device feature information of the source device and the target device;

[0064] if the device model and the firmware version in the source device and the target device are consistent, determine that the compatibility state is compatible;

[0065] if the device model in the source device and the target device is consistent but the firmware versions are different, query the configuration difference information between the firmware versions in the compatibility rule library to determine that the compatibility state is compatible or needs conversion;

[0066] if the device model in the source device and the target device is different, query whether there is a cross-model parameter mapping rule in the compatibility rule library to determine that the compatibility state is conversion or incompatible.

[0067] Further, the step of starting the configuration conversion engine to perform adaptive processing on the source configuration data package corresponding to the selected configuration item to generate a target configuration data package adapted to the target device comprises:

[0068] initializing an empty target configuration data structure and loading compatibility rules related to the source device and the target device;

[0069] processing each configuration parameter item parsed from the source configuration data package in an iterative manner;

[0070] for each configuration parameter item, performing a decision flow according to the loaded compatibility rules to determine an adaptive operation, which is one of a filtering operation, a conversion operation or a downgrade operation;

[0071] adding the result after performing the adaptive operation, or the original parameter item if no operation is needed, into the target configuration data structure;

[0072] after all parameter items are processed, encapsulating the target configuration data structure to form the target configuration data package.

[0073] Further, the step of synchronously generating a conversion execution log recording the adaptive processing procedure comprises:

[0074] initializing an empty conversion execution log while processing each configuration parameter item parsed from the source configuration data package in an iterative manner;

[0075] each time an adaptive operation is performed on any configuration parameter item, generating a detailed log record and appending it to the conversion execution log, the log record at least containing the identifier of the operated parameter, the type of the performed operation, the value before the operation and the value after the operation.

[0076] Further, the step of performing a decision flow according to the loaded compatibility rules to determine an adaptive operation comprises:

[0077] when the compatibility rules indicate that the target device does not support the current processing configuration parameter item at all, determining the adaptive operation as a filtering operation and discarding the current processing configuration parameter item;

[0078] when the compatibility rules indicate that the target device supports the current processing configuration parameter item but the value range or unit is different from that in the source configuration data package, determining the adaptive operation as a conversion operation and adjusting the current processing configuration parameter item according to the compatibility rules;

[0079] when the compatibility rules indicate that the target device does not support the advanced function in the source device corresponding to the current processing configuration parameter item but supports an alternative basic function, determining the adaptive operation as a downgrade operation and replacing the current processing configuration parameter item with a parameter item adapted to the basic function according to the compatibility rules.

[0080] The application also aims to provide an ultrasound device configuration synchronization system applied to an ultrasound device, which comprises:

[0081] A source configuration data packet uploading module is configured to generate a source configuration data packet containing device characteristic information and user personalized configuration data and send it to a cloud platform for storage and association with a user account in response to an uploading instruction when the ultrasound device functions as a source device to perform a configuration uploading operation;

[0082] A configuration list request sending module is configured to send a configuration list request containing device characteristic information to the cloud platform in response to a synchronization instruction when the ultrasound device functions as a target device to perform a configuration synchronization operation;

[0083] A configuration list receiving module is configured to receive a configuration list returned by the cloud platform, which contains the compatibility status between each source configuration data packet under a user account and the target device;

[0084] A download request sending module is configured to send a download request for a selected configuration item in the configuration list to the cloud platform in response to a user operation of selecting the selected configuration item from the configuration list;

[0085] A target configuration data packet receiving module is configured to receive and apply a target configuration data packet corresponding to the selected configuration item issued by the cloud platform to update the local configuration.

[0086] The application also aims to provide an ultrasound device configuration synchronization system applied to a cloud platform, which comprises:

[0087] A source configuration data packet receiving module is configured to receive and store a source configuration data packet containing device characteristic information and user personalized configuration data sent by an ultrasound device functioning as a source device and establish an association between the source configuration data packet and a corresponding user account;

[0088] A configuration list request receiving module is configured to receive a configuration list request containing device characteristic information sent by an ultrasound device functioning as a target device;

[0089] A configuration list sending module is configured to perform preliminary compatibility judgment on each source configuration data packet associated with the user account according to the device characteristic information of the target device and a preset compatibility rule library, generate a configuration list containing the compatibility status of each source configuration data packet, and return it to the target device;

[0090] A download request receiving module is configured to receive a download request for a selected configuration item in the configuration list sent by the target device;

[0091] A target configuration data packet sending module is configured to, in response to the download request, process the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet and send the target configuration data packet to the target device.

[0092] The application also provides an ultrasonic device, which comprises a memory, a processor, and a program stored in the memory and capable of running on the processor, and the processor implements the ultrasonic device configuration synchronization method when executing the program.

[0093] The application also provides a cloud platform, which comprises a memory, a processor, and a program stored in the memory and capable of running on the processor, and the processor implements the ultrasonic device configuration synchronization method when executing the program.

[0094] The method for synchronizing the configuration of the ultrasonic equipment provided by the embodiment of the present application realizes the fundamental change from isolated local storage to centralized cloud management by strongly binding the equipment characteristic information of each ultrasonic equipment with the personalized configuration data of the user and uploading to the cloud platform for unified storage and management, solves the problem of low efficiency caused by the need for the doctor to manually repeat the setting or tedious import and export through external media due to the need to switch between different equipment, realizes seamless roaming of the user's personalized working environment; the compatibility rule library is constructed on the cloud platform, and before the configuration synchronization, the multi-level decision tree comparison and preliminary compatibility judgment are performed according to the equipment characteristic information of the source equipment and the target equipment, the intelligent prediction of the feasibility of the configuration migration across types and versions is realized, the compatibility conflict and even the risk of equipment downtime caused by blind migration in the traditional configuration copying method are solved, the clear and safe operation guide is provided for the user, and the invalid operation is fundamentally avoided; the configuration conversion engine is started, the adaptive processing of each parameter based on rules is performed on the source configuration data packet that is not completely compatible, the intelligent and automatic adaptation of the configuration data is realized, the configuration migration barrier problem caused by the difference in equipment hardware and the iteration of software function is solved, the core configuration parameters are ensured to be retained and utilized to the greatest extent, and the smooth transition of the configuration is realized; the detailed conversion execution log is generated in the adaptive processing process, and before the application of the configuration, the confirmation interaction is performed on the target equipment in a visual manner, the complete transparency of the operation process and the guarantee of the user's ultimate control are realized, the black box operation and the clinical safety hidden danger of the unexpected result caused by the automatic processing are solved, the configuration change is ensured to be performed under the full knowledge and explicit authorization of the doctor, and the reliability and safety of the system are enhanced; the local snapshot and the automatic rollback mechanism are introduced before and after the application of the configuration, the atomicity and reversibility of the configuration update process are realized, the system state unrecoverable problem caused by accidental interruption or configuration conflict in the application of the new configuration is solved, and the stable operation of the equipment and the integrity of the data are ensured. The problems in the prior art are solved. BRIEF DESCRIPTION OF DRAWINGS

[0095] Figure 1 The flowchart of the method for synchronizing the configuration of the ultrasonic equipment in the first embodiment of the present application is shown.

[0096] Figure 2 The flowchart of the method for synchronizing the configuration of the ultrasonic equipment in the second embodiment of the present application is shown.

[0097] Figure 3 The structural diagram of the system for synchronizing the configuration of the ultrasonic equipment in the third embodiment of the present application is shown.

[0098] Figure 4Structure diagram of a synchronization system configured for an ultrasonic device in a fourth embodiment of the present application;

[0099] The following detailed description will further describe the present application with reference to the above-mentioned drawings. DETAILED DESCRIPTION

[0100] For the purpose of facilitating the understanding of the present application, the present application will be described more fully below with reference to the accompanying drawings. The accompanying drawings show several embodiments of the present application. However, the present application can be realized in many different forms and is not limited to the embodiments described herein. On the contrary, these embodiments are provided for the purpose of making the disclosure of the present application more thorough and comprehensive.

[0101] It should be noted that when an element is referred to as being "fixedly attached" to another element, it can be directly on the other element or intervening elements can also be present. When an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements can also be present. The terms "vertical", "horizontal", "left", "right" and similar expressions as used herein are for illustrative purposes only.

[0102] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. Embodiment One

[0103] Referring to Figure 1 , a method for configuring synchronization of ultrasonic devices in a first embodiment of the present application is shown. For the purpose of illustration, only parts related to the embodiments of the present application are shown. The method for configuring synchronization of ultrasonic devices provided by the embodiments of the present application is applied to ultrasonic devices. The method comprises the following steps:

[0104] In step S11, when the ultrasonic device performs a configuration upload operation as a source device, a source configuration data packet containing device characteristic information and user personalized configuration data is generated in response to an upload instruction and sent to a cloud platform for storage and association with a user account.

[0105] In one embodiment of the present application, the step of generating a source configuration data packet containing device characteristic information and user personalized configuration data and sending it to a cloud platform comprises the following steps:

[0106] Real-time collection of state information of the ultrasonic device in multiple dimensions to form device characteristic information;

[0107] serializing all the user's current activity personalized configuration data into a predefined structured data format;

[0108] packaging the device feature information and the serialized user personalized configuration data into a structured source configuration data package;

[0109] establishing an encrypted secure communication link with the cloud platform, and sending the source configuration data package to the cloud platform through the secure communication link.

[0110] Specifically, when the user completes his / her personalized parameter calibration on the ultrasound device as the source device, and initiates the upload configuration function on the device interface, the ultrasound device responds to the user's upload instruction immediately. At this time, the processing unit inside the ultrasound device automatically executes the internal process to generate and send a complete and secure source configuration data package.

[0111] Firstly, the processing unit triggers the deep collection of device feature information. The processing unit sends a query instruction to the device bottom layer hardware interface to read and record the product model name and the unique hardware serial number of the ultrasound device, which are the most basic identity of the ultrasound device. Then, the processing unit accesses the system core configuration file or registry to accurately obtain the major version number, minor version number and revision version number of the currently running firmware, which reflect the software status of the ultrasound device. At the same time, the processing unit will actively poll all peripheral ports connected to the device, especially the probe interface, to identify all the probe models supported by the device firmware, software version and their respective internal firmware version, and collect these information into a detailed probe list. Finally, the processing unit will also query the device internal authorization permission manager to confirm all the optional advanced function modules that the user has purchased and activated, such as shear wave elastography, contrast imaging or advanced four-dimensional imaging, etc., and compile the names and versions of these function modules into a function set list.

[0112] Meanwhile, the processing unit performs the structured serialization of the user's personalized configuration data, which is used to organize and convert the user's scattered and functionally diverse setting items into a unified and machine-readable and analyzable structured data format. For image parameters, such as gain, dynamic range, focus position, and other numerical or enumerated settings, the processing unit logically groups them according to their respective clinical applications (e.g., abdomen, heart, superficial) and the type of probe used, and converts each parameter and its current setting value into a key-value pair in the form of "parameter name-parameter value". For more complex diagnostic workflow preference configurations, such as user-defined report templates, measurement toolkits containing specific measurement items and calculation formulas, or personalized shortcut mapping schemes, the processing unit converts the contents of these structured data objects into a universally portable markup language format, such as Extensible Markup Language (XML) or JavaScript Object Notation (JSON). Finally, all converted key-value pairs and markup language format data are integrated under a unified root node to form a logically clear and complete serialized configuration data.

[0113] Next, the processing unit performs the packaging and security preparation of the source configuration data packet. The processing unit encapsulates the aforementioned deeply collected device feature information and the structured serialized user's personalized configuration data into a single data packet entity. In this process, in order to protect the confidentiality of the user's data, the processing unit calls the built-in encryption module to use the public key previously obtained from the cloud platform to perform an asymmetric encryption on the part of the data packet containing the user's personalized configuration data. The part containing the device feature information remains in plaintext so that the cloud platform can quickly read and index without decrypting the core privacy data.

[0114] Finally, the processing unit performs secure communication and data transmission with the cloud platform. The communication module built into the ultrasound device is activated, which first obtains a valid session token from the local secure storage based on the user's login status. Then the communication module initiates a handshake with the specified server address of the cloud platform using the Transport Layer Security (TLS) protocol to establish an end-to-end encrypted secure communication link. Once the link is successfully established, the communication module sends the encapsulated and partially encrypted source configuration data packet along with the user's session token to the cloud platform through the secure link, completing the entire upload operation.

[0115] Step S12, when the ultrasound device as the target device performs the configuration synchronization operation, in response to the synchronization instruction, sends a configuration list request containing its own device feature information to the cloud platform;

[0116] In one embodiment of the present application, when a user logs into his personal account on a new or different ultrasound device as the target device, and initiates the "sync configuration" or "restore settings" function on the device interface, the ultrasound device will immediately respond to the user's sync instruction. At this time, the processing unit inside the ultrasound device will immediately start an automated process to build and send a secure configuration list request to the cloud platform.

[0117] Firstly, the processing unit triggers a real-time collection of the current target device's own device feature information, which is used to ensure that the compatibility judgment to be carried out is based on the most accurate state of the target device at the moment. Similar to the upload operation described above, the processing unit will deeply query the device's underlying hardware interface, system core configuration file, connected peripheral ports, and authorization permission manager, to completely obtain and record the current device's product model name, hardware serial number, firmware version number, probe list, and the list of all authorized optional advanced function modules. This real-time collection process ensures that even if the user has just completed a device firmware upgrade or replaced a probe, the ultrasound device can immediately capture these changes and provide accurate comparison basis for the cloud platform.

[0118] Next, the processing unit constructs the configuration list request message body. The processing unit embeds the complete device feature information collected in real time into a pre-defined structured request message body. The message body is usually in JSON or XML format. In addition to the above-mentioned core device feature information, the message body can also contain some advanced filtering parameters passed through the user interface. For example, the user may have specified on the sync interface that he only wants to see configurations related to "heart application", or wants the list to be sorted in chronological order according to "recent uploads". At this time, the processing unit will encapsulate these filtering parameters and sorting parameters into the request message body to request the cloud platform to return a more accurate and user-friendly configuration list.

[0119] Subsequently, the processing unit performs the encapsulation of the complete network request, which combines the request message body containing the business logic with the network protocol header information for identity verification and communication control. At this time, the processing unit will obtain the valid session token or API key representing the current user's login state from the local secure storage area. Then the processing unit constructs a standard network request based on the Hypertext Transfer Protocol Secure (HTTPS). In this network request, the user's session token is placed in the request's authorization header field to prove the legality of its operation to the cloud platform. The request message body containing the device feature information and optional filtering parameters constructed in the previous step is placed in the request's request body part, and the content type field of the request header is set to inform the cloud platform that the body content is in JSON or XML format.

[0120] Finally, the processing unit sends the encapsulated complete configuration list request to the cloud platform through the built-in communication module via the established secure network connection to the preset API interface address. At this point, the target device initiates the configuration list request action, and the ultrasound device will enter a waiting state to receive the configuration list returned by the cloud platform after intelligent judgment.

[0121] Step S13, receiving a configuration list returned by the cloud platform, containing the compatibility status between each source configuration data packet under the user account and the target device;

[0122] In an embodiment of the present application, after the processing unit of the target device successfully sends the configuration list request to the cloud platform, the communication module built-in the ultrasound device will remain in a listening state, waiting for and receiving network responses from the cloud platform. Once the response is received, the processing unit immediately starts the parsing and presentation process to convert the data returned by the cloud platform into a configuration list interface that users can intuitively understand and interact with.

[0123] First, the processing unit extracts and verifies the returned data from the network response through the communication module. The communication module will first confirm the integrity and security of the network transmission, check the status code of the HTTPS response to ensure that the request has been successfully processed. Then the processing unit extracts the core data load from the response body, which is usually a structured data stream in JSON or XML format. The processing unit will immediately perform format checking on the data stream to ensure its structure is complete and conforms to the predefined interface specification, preventing subsequent processing failures due to data corruption or format errors.

[0124] Next, the processing unit performs in-depth parsing on the verified structured data. The returned configuration list data is essentially an array or list structure, and each element in it represents a source configuration stored under the user account. At this point, the processing unit will iterate through each element in the list and extract multiple key information fields from each element. These key information fields at least include: a unique identifier for a configuration, used for subsequent download requests; a user-readable configuration name or description, such as "Dr. Zhang's abdominal presets"; the original source device model and firmware version; and most importantly, the compatibility status determined by the cloud platform. This compatibility status is an explicit enumeration value, such as "compatible", "needs conversion", or "incompatible".

[0125] Then, the processing unit dynamically constructs and presents the list on the user interface based on the parsed data. The processing unit passes the parsed information to the user interface rendering engine of the ultrasound device. The rendering engine then dynamically generates a visual and interactive configuration list on the display screen of the ultrasound device according to the information. In the list, each row corresponds to a source configuration. In order to intuitively convey the abstract compatibility status to the user, the rendering engine uses specific visual elements to distinguish them. For example, for a configuration item with a status of "compatible", a green check icon can be displayed next to it, and it is displayed in normal font, indicating that it can be used directly. For a configuration item with a status of "conversion required", a yellow warning icon or a gear icon can be displayed, with a brief prompt such as "may need automatic adjustment", to inform the user that the configuration can be applied, but the system will perform some necessary intelligent conversion. For a configuration item with a status of "incompatible", a red prohibition icon is displayed, and it is grayed out or set to an unselectable state, clearly informing the user that the configuration cannot be used on the local machine due to large differences in hardware or software versions.

[0126] Finally, the entire list interface enters a state of waiting for user interaction. At this time, the user can clearly see all the configurations of his cloud backup, and make a choice based on the intuitive compatibility feedback provided by the system. The user can scroll and browse in the list through the touch screen or physical buttons, and finally select a "compatible" or "conversion required" configuration item to trigger the subsequent download and application process. At this point, the step of receiving and presenting the configuration list is complete.

[0127] Step S14, in response to the user's operation of selecting a selected configuration item from the configuration list, a download request for the selected configuration item is sent to the cloud platform;

[0128] In an embodiment of the present application, after the user carefully reviews the configuration list returned by the cloud platform with compatibility status identification on the display interface of the target device, the user selects a specific configuration item that he hopes to apply on the local machine through interaction such as touch or button. Once the processing unit of the ultrasound device detects this selection operation, the system will respond immediately and start a set of processes to build and send a targeted download request.

[0129] First, the processing unit captures the user's selection and extracts the key identifier. When the user interface control is triggered, it passes an event to the processing unit, which contains all the associated information of the list row item selected by the user. The processing unit accurately extracts the unique identifier of the "selected configuration item" from this information. This identifier is specified by the cloud platform for each configuration when receiving the configuration list in the previous step, and it is the only credential for subsequent data retrieval from the cloud platform.

[0130] Then, the processing unit starts to construct the message body of the download request. Unlike the previous sending of the configuration list request, the message body of the download request is more concise and focused. Specifically, the processing unit creates a structured request message body, usually in JSON or XML format. The core content of this message body is the unique identifier of the selected configuration item just extracted. In addition, to ensure that the cloud platform can still be based on the latest state of the target device when performing possible conversion operations, the processing unit also encapsulates the real-time device feature information of the current target device into this request message body again, which is used to prevent potential changes in the state of the ultrasound device during user browsing of the list, thereby ensuring the absolute accuracy of the conversion.

[0131] Subsequently, the processing unit performs the encapsulation of the complete network download request. Similar to the above process of initiating the list request, the processing unit obtains a valid user session token from the local secure storage and constructs a standard network request based on the Hypertext Transfer Protocol Secure (HTTPS) protocol. The user's session token is placed in the authorization header field of the request for authentication. The request message body containing the unique identifier of the selected configuration item and the real-time feature information of the target device is placed in the request body part of the request and its content type is explicitly set.

[0132] Finally, the processing unit sends the encapsulated and well-defined download request to the cloud platform through the built-in communication module to the dedicated API interface for processing download requests through the established secure network connection. After sending is completed, the ultrasound device will again enter a waiting state, ready to receive the specific configuration data issued by the cloud platform after final processing (which may be a directly forwarded compatible configuration package or a new configuration package generated after intelligent conversion).

[0133] Step S15, receiving and applying the target configuration data package corresponding to the selected configuration item issued by the cloud platform to update the local configuration;

[0134] In an embodiment of the present application, the step of receiving and applying the target configuration data package corresponding to the selected configuration item issued by the cloud platform includes:

[0135] When the compatibility status of the selected configuration item is compatible, the source configuration data package corresponding to the selected configuration item issued by the cloud platform is received as the target configuration data package, and the target configuration data package is applied to update the local configuration;

[0136] When the compatibility status of the selected configuration item is compatible, the source configuration data package corresponding to the selected configuration item issued by the cloud platform is received as the target configuration data package, and the target configuration data package is applied to update the local configuration;

[0137] The user is confirmed interactively based on the conversion execution log, and after obtaining the user's confirmation instruction, the target configuration data packet is applied to update the local configuration.

[0138] Specifically, after the processing unit of the target device sends a download request for a specific configuration item to the cloud platform, the communication module built-in the ultrasound device will remain listening, waiting for and receiving the final data response from the cloud. Once the response is received, one of the following two workflows is started according to the compatibility status of the "selected configuration item" previously selected by the user to complete the update of the local configuration.

[0139] Case 1: When the compatibility status of the selected configuration item is "compatible", the network response received by the ultrasound device at this time will only contain the original source configuration data packet corresponding to the selected configuration item, so it is directly identified as the target configuration data packet. At this time, the processing unit first performs integrity verification on this data packet. After verification, since there is no automatic modification, no user confirmation interaction is required, and the application process is directly entered. Subsequently, the processing unit applies the target configuration data packet in an atomic manner. The processing unit starts to write all configuration parameter items in the data packet to the system configuration area of the target device at one time in an indivisible transaction operation. This process ensures that either all original configurations are successfully applied, or the entire application process is immediately aborted in the event of any unexpected errors, and the device configuration is instantly restored to the stable state before application through the local snapshot created previously, thereby completing a safe and direct local update of a known compatible configuration.

[0140] Case two: when the compatibility status of the selected configuration item is "conversion required", the network response received by the ultrasound device will contain two core data: one is the target configuration data package customized for the current target device after intelligent processing by the cloud configuration conversion engine; the other is a structured conversion execution log that records all adaptive processing procedures in detail. At this time, the system will not immediately apply the configuration, but will first start the user confirmation interaction process based on the conversion execution log. The processing unit deeply analyzes this log and extracts the detailed information of each record, including the parameter name being operated, the operation type (such as filtering, conversion, degradation), the value before operation, and the value after operation. Based on these parsed details, the processing unit drives the user interface rendering engine to generate a clear and intuitive change confirmation summary on the device screen. This summary presents all automatic modifications to the user in the form of a highlighted contrast list. At the same time, the summary interface provides explicit interaction options for the user to make a final decision. Only after the user has carefully reviewed all automatic changes and finally input "confirm application" instructions through the interface, will the system continue to perform subsequent steps. Finally, the processing unit also applies the target configuration data package that has been converted and user-confirmed in an atomic manner, writing this customized configuration data to the system configuration area.

[0141] Further, in an embodiment of the present application, the above steps of confirming interaction with the user based on the conversion execution log and applying the target configuration data package to update the local configuration after obtaining the user's confirmation instruction include:

[0142] Parsing the conversion execution log to extract the operation type, affected configuration parameter item, and details of value or state change before and after operation of each adaptive operation;

[0143] Based on the extracted details, generate a visual change confirmation summary in the form of a highlighted or contrast list on the user interaction interface;

[0144] Receiving the exact instruction input by the user through the change confirmation summary interface, the exact instruction being one of confirmation, cancellation, or modification;

[0145] In response to receiving the confirmation instruction input by the user, applying the target configuration data package.

[0146] Specifically, the processing unit first performs a deep parsing and information extraction of the transformation execution log. It invokes a log parsing module that can recognize and process structured log data formats (e.g. JSON or XML). It reads the records in the log one by one, and extracts the core semantic information for each record. This includes: an "operation type" field that identifies the type of operation, such as "filter", "transform", or "degrade"; a "configuration parameter item" field that specifies the object of the operation, such as "image gain" or "report template"; and a "before and after value or state change" field that records the details of the change, such as from one specific value to another, or from an enabled state to a disabled state.

[0147] Next, the processing unit drives a user interface rendering engine to generate a visual and informative change confirmation summary based on the extracted detailed information. This summary is designed as a highly readable user interaction interface, presented on the device's display screen. The rendering engine creates a separate entry on the summary interface for each record in the log. To enable the user to understand the changes at a glance, the interface uses highlighting or contrasting lists to display the information. For example, for a "transformed" numerical parameter, the interface displays "original value: 80 dB" and "suggested value: 210" side by side, and possibly highlights the new suggested value with a prominent color. For a "filtered" function, the interface clearly indicates "function 'composite imaging' will be disabled", and possibly includes a brief explanation such as "due to current device not supporting". The entire summary interface is designed to convert complex technical changes into intuitive information that the clinician can quickly understand.

[0148] Then, the system enters a phase of waiting for and receiving explicit instructions from the user. The change confirmation summary interface is not only a window for displaying information, but also a platform for interactive decision-making. It provides a set of clear function buttons to allow the user to input their exact instructions. These instructions include at least three core options: a "confirm" button, indicating that the user reviews and fully accepts all modifications automatically completed by the system; a "cancel" button, indicating that the user rejects this synchronization operation and wants to keep the current configuration of the device unchanged; and a more advanced "modify" option, indicating that the user accepts most of the results of the synchronization, but wants to manually fine-tune individual automatically adjusted parameters. The processing unit continuously listens for user input events from the interface.

[0149] Finally, the processing unit will respond to the user's instruction and perform the corresponding follow-up operation. If the user inputs the "cancel" instruction, the entire synchronization process will be terminated immediately, all received data packets and logs will be discarded, and the device will return to the state before operation. If the user inputs the "modify" instruction, the system will enter a deeper interactive mode, allowing the user to manually edit individual parameters. And only when the processing unit receives the user's explicit "confirm" instruction will it be considered as the final application authorization. At this time, the system will close the change confirmation summary interface and immediately trigger the final application operation on the target configuration data packet, starting the secure application process including creating a local snapshot and atomic update to complete the update of the local configuration.

[0150] Further, in an embodiment of the present application, the step of receiving the exact instruction input by the user through the change confirmation summary interface further comprises:

[0151] In response to receiving the user's input modification instruction, an interactive option is provided for each modified configuration item to allow the user to select from a set of pre-set solutions, including at least: maintaining the original state of the configuration item in the source configuration data packet, or applying the adapted state set for the configuration item in the target configuration data packet, or restoring to the default state of the factory default value.

[0152] In response to the user's selection of the target solution, the corresponding configuration parameter item in the target configuration data packet is updated.

[0153] Specifically, first, the system responds to the received "modify" instruction and activates the interactive mode of the summary interface. At this time, for each configuration item in the summary list that is automatically "converted" or "downgraded" by the system, an interactive option will be provided next to it, such as a clickable "modify solution" button;

[0154] When the user interacts with the interactive option of a specific configuration item, the system will provide a dedicated selection interface for the item, which is usually a pop-up dialog box listing a set of pre-set solutions for the user to choose from; Among the pre-set solutions, at least include: (1) "maintain original value", which means that the selection of this item will make the parameter maintain its original state in the source configuration data packet when finally applied; (2) "apply suggested value", which means adopting the adapted state set for the configuration item in the target configuration data packet after cloud adaptability processing; (3) "restore factory default value", which means that the selection of this item will make the parameter restore to the default state of the factory default value when finally applied;

[0155] Then, the system receives the explicit selection made by the user from the selection interface, and updates the corresponding configuration parameter item in the target configuration data package currently stored in the memory according to the user's selection. For example, if the user selects "maintain original value" for the "gain" parameter, the value of this parameter in the target configuration data package will be overwritten back to the value in the source configuration. At this time, the user can repeat this process to make scheme selection for multiple configuration items. When all modifications are completed, the user clicks the total "confirm application" button on the summary interface, and the system will execute the subsequent security application process with the final version of the target configuration data package customized by the user. It should be noted that the user's custom value modification of the parameter is performed in the daily actual application of the device, and the modified and saved configuration can be uploaded to the cloud platform as a new source configuration data package in the subsequent process, rather than in the process of this time synchronization update configuration.

[0156] Further, in an embodiment of the present application, the method further comprises:

[0157] Before applying the target configuration data package to update the local configuration, a local snapshot of all personalized configuration data of the target device is created and stored;

[0158] When applying the target configuration data package to update the local configuration, if any error or configuration conflict occurs to cause the application to be interrupted, the application process is automatically suspended, and the target device configuration is restored to the state before application using the local snapshot;

[0159] After applying the target configuration data package, if a user-triggered rollback instruction is received within a preset time, the target device configuration is restored to the state before application using the local snapshot.

[0160] Specifically, in order to ensure the absolute safety and reversibility of the configuration synchronization process, the local snapshot and rollback mechanism is integrated in the method of the embodiment of the present application. The mechanism provides double protection for the user at the key nodes of the entire application process: one is the automatic fault recovery to prevent the device state from being abnormal due to application failure, and the other is the manual revocation ability given to the user after the application is successful.

[0161] First, at the very moment when the final application operation is about to be executed (i.e. either directly applying a "compatible" configuration package, or after the user reviews and clicks "Confirm to apply" for a "conversion-required" configuration package), the processing unit will immediately trigger the pre-application local snapshot creation and storage. The processing unit will send an instruction to the configuration management module of the ultrasound device, asking it to read out all the active personalized configuration data on the device from the volatile working memory completely. These data include all the settings used by the user before this synchronization operation. Then, these data are copied and stored completely to a temporary non-volatile storage area (e.g. a designated area of the internal flash memory of the device), forming a time-stamped local snapshot. This snapshot is a complete digital mirror of the state of the device before the application, and is the basis for all subsequent recovery operations.

[0162] Then, after the local snapshot is successfully created, the system starts the automatic failure recovery during the application process. The processing unit writes the content in the target configuration data package into the system configuration area of the device in an atomized transaction manner. During this process, the system performs real-time monitoring. If any error or configuration conflict occurs, causing the application to be interrupted, for example, due to an underlying file system I / O error causing a write failure, or a logical conflict is found between a parameter and the current mode of the device during the final check, the built-in exception handler of the system will immediately capture this interruption signal. Once captured, the application process is automatically terminated. Immediately after, the configuration management module of the system automatically activates the recovery process, which immediately reads the data in the local snapshot just stored and completely and forcibly overwrites the current system configuration area with this data. This recovery process is extremely fast, and the user can hardly perceive it. As a result, the configuration of the target device is restored to the stable state before the application operation began. At the same time, the system displays a friendly prompt message on the user interface, informing the user that the synchronization failed but the device state has been safely restored.

[0163] Finally, after the target configuration data package is successfully applied and the local configuration is updated, the system will start the post-application manual rollback support. After the application is successful, the system does not immediately delete the local snapshot created before, but retains it for a predetermined period of time (e.g. five minutes), or until the user performs the next significant configuration-related operation. At the same time, on the user interface of the device, a "revoke configuration changes" or similar rollback instruction button appears in a inconspicuous position (such as the status bar or menu). If the user is not satisfied with the new configuration after operation and triggers this rollback instruction within the predetermined time, the processing unit will respond immediately. It will again call the configuration management module to use the data in the still retained local snapshot to restore the device configuration to the state before the application, using the same mechanism as the automatic recovery. Once the manual rollback is successful or the predetermined time is up, the local snapshot is finally cleared.

[0164] In summary, the ultrasonic equipment configuration synchronization method in the above embodiments of the present application realizes a fundamental change from isolated local storage to centralized cloud management by strongly binding the device characteristic information of each ultrasonic equipment with the personalized configuration data of the user and uploading to the cloud platform for unified storage and management, solves the problem of low efficiency caused by the need for the doctor to manually set repeatedly or import and export tediously through external media due to the need to switch between different devices, realizes seamless roaming of the user's personalized working environment; by building a dynamic and extensible compatibility rule library on the cloud platform, and before configuration synchronization, performing multi-level decision tree comparison and preliminary compatibility judgment according to the device characteristic information of the source device and the target device, the intelligent prediction of the feasibility of cross-model and cross-version configuration migration is realized, the compatibility conflict and even the risk of device downtime caused by blind migration in the traditional configuration copying method is solved, and clear and safe operation guidance is provided for the user, which fundamentally avoids invalid operation; by starting the configuration conversion engine, the source configuration data packet that is not fully compatible is adaptively processed item by item based on rules, realizing intelligent and automatic adaptation of the configuration data, solving the configuration migration barrier problem caused by device hardware differences and software function iteration, ensuring that the core configuration parameters can be retained and utilized to the greatest extent, and realizing smooth transition of the configuration; by synchronously generating detailed conversion execution logs during the adaptive processing process, and before applying the configuration, the user is confirmed and interacted with in a visual manner on the target device, the complete transparency of the operation process and the guarantee of the user's ultimate control are realized, the clinical safety hidden danger of black box operation and unintended results caused by automatic processing is solved, ensuring that each configuration change is carried out with the full knowledge and explicit authorization of the doctor, and the reliability and safety of the system are enhanced; by introducing the local snapshot and automatic rollback mechanism before and after applying the configuration, the atomicity and reversibility of the configuration update process are realized, the problem of unrecoverable system state caused by accidental interruption or configuration conflict during the application of the new configuration is solved, and the stable operation of the device and the integrity of the data are ensured. The problems existing in the synchronization of personalized configuration across devices in the existing ultrasonic equipment are solved. Embodiment two

[0165] Please refer to Figure 2 , which is an ultrasonic equipment configuration synchronization method in the second embodiment of the present application, only the parts related to the embodiments of the present application are shown for the convenience of description, and the ultrasonic equipment configuration synchronization method provided by the embodiments of the present application is applied to a cloud platform, the method comprising:

[0166] Step S21, receiving and storing the source configuration data packet containing the device characteristic information and the user's personalized configuration data sent by the ultrasonic equipment as the source device, and establishing the association between the source configuration data packet and the corresponding user account;

[0167] In one embodiment of the present application, the step of receiving and storing the source configuration data packet containing the device characteristic information and the user personalized configuration data from the ultrasound device as the source device, and establishing the association between the source configuration data packet and the corresponding user account comprises:

[0168] establishing an encrypted secure communication link with the source device, and receiving the upload request sent by the source device through the secure communication link, the upload request containing user authentication credentials and the source configuration data packet;

[0169] verifying the user authentication credentials to confirm the user identity and obtain a unique user identifier;

[0170] if the verification is passed, parsing and extracting the device characteristic information and the user personalized configuration data from the source configuration data packet;

[0171] querying or creating a unique device record corresponding to the source device in the device information database according to the extracted device characteristic information, and obtaining the corresponding device identifier;

[0172] creating a new configuration record in the configuration storage database, and storing the configuration data obtained by encrypting the user personalized configuration data in the configuration record;

[0173] storing the configuration record in association with the user identifier and the device identifier in the configuration index database.

[0174] Specifically, when the source device sends the encapsulated source configuration data packet to the cloud platform, the server application of the cloud platform starts an orderly multi-stage processing procedure to ensure the safe reception, compliant storage of data, and efficient indexing for subsequent intelligent synchronization.

[0175] Firstly, the API gateway of the cloud platform performs the establishment of the secure link and the reception of the request. As the entrance of the cloud service, the API gateway requires that all external communications must be carried out through the Transport Layer Security (TLS) protocol. When the source device initiates the connection, an encrypted handshake is performed between the two to establish an encrypted secure communication link. On this secure link, the API gateway receives the upload request from the source device. This request is a structured data packet, which is logically divided into two parts: one is the user authentication credentials in the request header (Header), usually an access token (Access Token) with a time limit; the other is the source configuration data packet containing the device characteristic information and the user personalized configuration data in the request body (Body).

[0176] Next, the identity authentication and authorization service module will immediately perform the verification of the user authentication credentials before the data enters the core business logic. This module will extract the access token in the request header and verify it with the token issuing authority (e.g. OAuth2.0 authorization server) to confirm the authenticity, validity and non-expiration of the token. After verification, the system not only confirms the legal identity of the operator, but also safely parses the unique user identifier (e.g. a string of UUID or digital ID) of the user from the token payload. If the verification fails, the entire request will be immediately rejected and an authentication failure error code will be returned to the source device.

[0177] After the user identity is confirmed, the core business logic begins to parse and extract the source configuration data package in the request body. The data parsing module will parse the source configuration data package according to the predefined format specification (e.g. JSON Schema). It accurately separates the data package into two logical parts: one part is the device feature information describing the device hardware and software status, and the other part is the user personalized configuration data containing all user settings. These two parts of data will be sent to different processing pipelines respectively.

[0178] Subsequently, the system performs the identification and recording of the device identity. The device management service receives the extracted device feature information and uses the unique identification combination (e.g. device model + hardware serial number) in these information as a query key to search in the device information database. If a record is found, it indicates that the device has uploaded configuration before, and the system directly obtains its corresponding, assigned unique device identifier. If no record is found, it indicates that this is a new device, and the system will immediately create a new device record in the device information database, store the complete device feature information, and generate a new and globally unique device identifier. Therefore, the final output of this step is a clear device identifier in both cases.

[0179] At the same time, the configuration storage service begins to process the secure storage of the user personalized configuration data. After receiving the user personalized configuration data, the service calls the cloud key management service (KMS) to obtain a dedicated data encryption key. Then it uses the key to encrypt the entire user personalized configuration data through a high-strength encryption algorithm (such as AES-256-GCM). After encryption, the ciphertext data is stored as an independent and immutable object in a high-availability, high-persistence configuration storage database (usually an object storage service such as AWS S3). After successful storage, the service returns a unique resource locator (URI) pointing to this encrypted data object as its access handle.

[0180] Finally, the index building service performs the establishment of the triadic association index. This service creates a new configuration record in a high-performance, configured index database (typically a relational database such as PostgreSQL). The core of this record is the establishment of a triadic association: it stores the unique user identifier, the unique device identifier, and the unique resource locator pointing to the encrypted configuration data in the same record. In addition, to optimize the performance of subsequent queries, some key fields extracted from the device characteristic information, such as the device model and firmware version, are also stored as redundant fields in the index record and indexed in the database.

[0181] Step S22, receiving a configuration list request containing the device characteristic information of the ultrasound device from the ultrasound device as the target device;

[0182] In one embodiment of the present application, when an ultrasound device as a target device initiates configuration synchronization to the cloud platform, the API gateway of the cloud platform will receive a request specially designed to obtain the configuration list.

[0183] First, the API gateway of the cloud platform receives the network request from the target device through the established encrypted secure communication link. Similar to the above upload request, this configuration list request also follows the pre-defined interface protocol, which is logically divided into two parts: the request header and the request body. The user authentication credentials for identity verification are contained in the request header, while the device characteristic information of the current target device as the compatibility comparison benchmark is encapsulated in the request body.

[0184] Next, before the request enters the core business logic, the identity authentication and authorization service module will immediately perform verification of the user authentication credentials. This module extracts the access token from the request header and performs strict verification to confirm its authenticity, validity, and timeliness. Once the verification is successful, the system confirms the legal identity of the requester and securely parses the unique user identifier of the user from it. This user identifier is the key index for subsequent retrieval of all personal configurations of the user in the database. If the authentication fails, the request will be immediately rejected, thereby preventing any unauthorized data access.

[0185] Wherein, after the user identity is confirmed, the data analysis module starts to process and analyze the content in the request body. The request body contains the device characteristic information collected and structured by the target device in real time. The analysis module will check and analyze this part of data according to the pre-defined format specification, to ensure that the structure is complete and the field is valid. After successful analysis, the system obtains the device characteristic information of the current target device, including its product model name, hardware serial number, firmware version number, probe list and the list of all activated optional advanced function modules. Finally, after successfully verifying the user identity and analyzing the device characteristic information of the target device, the entire request and the key data carried thereby are passed to the core business service responsible for processing the configuration query.

[0186] Step S23, according to the device characteristic information of the target device and the preset compatibility rule library, the preliminary compatibility of each source configuration data packet associated under the user account is judged, and a configuration list containing the compatibility state corresponding to each source configuration data packet is returned to the target device;

[0187] Wherein, in an embodiment of the present application, the step of judging the preliminary compatibility of each source configuration data packet associated under the user account according to the device characteristic information of the target device and the preset compatibility rule library comprises:

[0188] According to the user account in the received configuration list request, the index records of all source configuration data packets associated with the user account are retrieved from the configuration index database;

[0189] For each retrieved index record, the stored device characteristic information of the source device is extracted;

[0190] The extracted device characteristic information of the source device is compared with the device characteristic information of the target device carried in the configuration list request in a multi-level decision tree manner to determine the compatibility state;

[0191] The determined compatibility state is added to the current configuration list together with the corresponding source configuration data packet information.

[0192] Further, the step of comparing the extracted device characteristic information of the source device with the device characteristic information of the target device carried in the configuration list request in a multi-level decision tree manner to determine the compatibility state comprises:

[0193] The device model and firmware version in the device characteristic information of the source device and the target device are compared;

[0194] If the device model and firmware version in the target device and the source device are consistent, it is determined that the compatibility state is compatible;

[0195] If the target device and the source device have the same device model but different firmware versions, the compatibility rule library is queried for configuration difference information between firmware versions to determine the compatibility state as compatible or conversion required.

[0196] If the target device and the source device have different device models, the compatibility rule library is queried for cross-model parameter mapping rules to determine the compatibility state as conversion required or incompatible.

[0197] Specifically, after the cloud platform successfully receives and parses the configuration list request from the target device, the core business logic of the system is activated, and the automated preliminary compatibility judgment process is started to accurately label each cloud backup under the user account with a compatibility label relative to the current target device, and finally generate an intelligent configuration list.

[0198] First, the configuration query service initiates an efficient retrieval operation to the configuration index database according to the unique user identifier obtained from the request. Due to the database index established for the user identifier, the system can quickly query all source configuration data package index records associated with the user account. These records form a preliminary candidate set, each record containing the unique resource locator of the source configuration data in the object storage and the device characteristic information of the source device bound at the time of uploading.

[0199] Next, the system enters an iterative compatibility judgment loop. The processing unit iterates through each index record in the above candidate set. In each iteration, the following key actions are performed:

[0200] Extract source device characteristics: Extract the source device characteristic information stored in the index record currently being processed.

[0201] Perform multi-level decision tree comparison: Compare the source device characteristic information with the target device characteristic information parsed from the request. This comparison process is driven by a specialized compatibility judgment engine, which queries a pre-set, structured compatibility rule library. The comparison logic follows a pre-set decision tree rule:

[0202] First level (complete match judgment): The engine first compares the device model and firmware version of the source device and the target device. If both are completely identical, the compatibility state of the source configuration is immediately determined as "compatible", and the comparison of this iteration ends.

[0203] Second level (version difference judgment): if the device model is consistent but the firmware version is different, the engine will query the version change log in the compatibility rule library which specially records the configuration parameter differences between different firmware versions of the same model device. If the log shows that there is no change in the configuration parameters between the two versions, or all changes have clear conversion rules, the compatibility status is determined as "need conversion".

[0204] Third level (model difference judgment): if the device models are different, the engine will enter the most complex judgment level. It queries the cross-model parameter mapping table in the compatibility rule library which defines the parameter correspondence between different models. The engine will evaluate whether there is an effective conversion path that covers a set of preset "core parameter set" (such as gain, dynamic range, and other key parameters). If there are enough effective mapping rules so that the converted configuration can still guarantee the basic image quality and operation process, the compatibility status is determined as "need conversion". Otherwise, if the key parameters cannot be mapped, the status is determined as "incompatible".

[0205] Then, after the comparison of each iteration is completed, the processing unit combines the determined compatibility status ("compatible", "need conversion", or "incompatible") with some descriptive information of the source configuration (such as user-defined name, upload time, etc.) to construct an entry in the configuration list and add it to a temporary result list being constructed.

[0206] Finally, after all candidate source configuration records are traversed and their compatibility status is determined, the system generates a complete configuration list with intelligent judgment results. The processing unit structures the result list (for example, serializes it into JSON format) and returns it as a response to the previous configuration list request through the API gateway to the target device. At this point, the target device will no longer receive a simple file list, but an interactive list full of intelligent suggestions that can directly guide the user to the next step of operation.

[0207] Step S24, receiving a download request for the selected configuration item in the configuration list sent by the target device;

[0208] In an embodiment of the present application, after the cloud platform successfully returns the configuration list with intelligent compatibility status to the target device, the cloud API gateway will remain on standby, ready to receive the next instruction initiated by the user after reviewing the list. When the user finally selects a specific configuration item on the target device and triggers the download, the cloud platform will receive a clear download request and immediately start a set of verification and analysis processes to prepare for the final data processing and delivery.

[0209] First, the API gateway of the cloud platform receives a brand new network request from the target device through the established encrypted secure communication link. The nature of this request is different from the previous list request, which is a download request for a single, specific resource. As with all interactions, the request header still contains user authentication credentials for identity verification to ensure the security and legality of the operation.

[0210] Next, before the request enters the core business logic, the identity authentication and authorization service module will perform user authentication credential verification again. The system will strictly verify the access token in the request header to confirm its validity and parse the unique user identifier from it. This not only verifies the user's identity but also ensures that subsequent operations will be within the user's permission range, preventing any cross-user illegal data access.

[0211] After the user's identity is confirmed, the data parsing module begins to process and parse the content in the request body. The download request body encapsulates two core pieces of information: one is the unique identifier of the "selected configuration item" that the user selected from the configuration list, which is provided by the cloud when issuing the list previously and is the key to locating a specific source configuration data in the cloud storage; the other is the real-time device feature information of the current target device reported again to ensure the highest accuracy of conversion. The parsing module will verify the format and validity of these two pieces of information to ensure that the request's intent is clear and complete.

[0212] Then, the core business service will perform a permission and existence check. The service will use the parsed user identifier and the unique identifier of the selected configuration item to perform a joint query in the configuration index database. The purpose of this query is to confirm that the configuration item exists and that the ownership of the configuration item belongs to the user who initiated the request. Only when both conditions are met will the subsequent processing flow be allowed to execute. This further strengthens the system's security defenses.

[0213] Finally, after successfully verifying the user's identity, parsing the request content, and confirming the user's ownership of the selected configuration item, the entire request and the key data it carries (i.e., the unique identifier of the selected configuration item and the real-time device feature information of the target device) will be passed to the core business service responsible for processing configuration conversion and issuance.

[0214] Step S25, in response to the download request, processing the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet and issuing it to the target device;

[0215] In one embodiment of the present application, the above-mentioned step of processing the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet and issuing it to the target device includes:

[0216] When the compatibility status of the selected configuration item is compatible, the source configuration data package corresponding to the selected configuration item is directly taken as the target configuration data package and delivered to the target device;

[0217] When the compatibility status of the selected configuration item is compatible, the source configuration data package corresponding to the selected configuration item is directly taken as the target configuration data package and delivered to the target device;

[0218] Specifically, after the cloud platform successfully receives and verifies the download request from the target device, the core business service of the system will respond to this request and intelligently start two different processing and delivery paths according to the compatibility status of the "selected configuration item" determined in advance, to generate and deliver the final target configuration data package.

[0219] Case one: When the compatibility status of the selected configuration item is "compatible", the system determines that there is no known compatibility obstacle between the source configuration and the target device, and it can be directly applied. The business service will perform a direct and efficient data extraction and forwarding process. First, the service will use the unique identifier of the "selected configuration item" specified in the download request to query the exact location of the configuration data in the object storage service in the configuration index database. Then, the service will directly extract the complete, unmodified original source configuration data package from this location. Next, this original source configuration data package is directly taken as the target configuration data package by the system. The business service will build a network response and place this data package in the body of the response. Finally, through the API gateway, along the established secure communication link, the target configuration data package is delivered to the target device. In this response, since no conversion operation is performed, no conversion execution log is included.

[0220] Case two: when the compatibility status of the selected configuration item is "conversion required", the system determines that the source configuration must be intelligently adjusted to adapt to the target device. At this time, the business service will start the configuration conversion engine to perform a complex adaptive processing procedure. First, the configuration conversion engine is activated and the necessary data is loaded. It obtains and decrypts the source configuration data package from the object storage according to the unique identifier of the "selected configuration item", and parses the source configuration data package. At the same time, it loads all related conversion rules from the compatibility rule library according to the device characteristic information of the source device and the target device carried in the request. Then, the engine starts to adaptively process the source configuration data package. It systematically checks each parameter item in the source configuration in an iterative manner. For each item, the engine queries the loaded rules and performs corresponding filtering, conversion or degradation operations. For example, it may scale a value that exceeds the range of the target device according to the parameter mapping rule; or replace a set of advanced imaging function parameters that the target device does not support with an equivalent set of basic function parameters according to the degradation rule. During the processing, the engine will generate a conversion execution log that records the adaptive processing process. Whenever the engine performs an adaptive operation on any parameter item, it will immediately generate a structured log record detailing the parameter being operated, the type of operation performed, and the specific changes before and after the operation, and append this record to a log file being built. After all parameter items have been processed, the engine will recombine all adjusted and unadjusted parameter items to generate a target configuration data package adapted to the target device. Before final encapsulation, a strict architecture verification will be performed on the newly generated data package to ensure that it fully complies with the configuration specification of the target device. Finally, the business service will build a network response and deliver the target configuration data package and the conversion execution log to the target device. Through the API gateway, the two closely related data are sent out together, ensuring that the target device receives the converted configuration at the same time as it obtains all transparent information about the conversion process.

[0221] In an embodiment of the present application, the step of starting the configuration conversion engine to adaptively process the source configuration data package corresponding to the selected configuration item to generate a target configuration data package adapted to the target device comprises:

[0222] Initializing an empty target configuration data structure and loading compatibility rules related to the source device and the target device;

[0223] Processing each configuration parameter item parsed from the source configuration data package in an iterative manner;

[0224] For each configuration parameter item, a decision flow is performed according to the loaded compatibility rules to determine an adaptive operation, which is one of filtering operation, conversion operation or degradation operation;

[0225] The result after performing the adaptive operation, or the original parameter item if no operation is needed, is added into the target configuration data structure;

[0226] After all parameter items are processed, the target configuration data structure is packaged to form the target configuration data package.

[0227] Specifically, when the cloud platform service determines that a selected source configuration needs to be converted, the core configuration conversion engine is woken up and started. First, the configuration conversion engine performs an initialization and preparation phase. It initializes an empty target configuration data structure in memory, and its basic framework strictly follows the configuration specification of the target device. At the same time, the engine initiates an accurate query to the compatibility rule library according to the specific models and firmware versions of the source and target devices involved in the current task, and loads all compatibility rules related to these two devices. These rules are loaded into the engine's cache, ready for fast decision-making later.

[0228] Next, the engine enters the core iterative processing loop. It processes each configuration parameter item parsed from the source configuration data package in an iterative manner. The engine traverses each parameter node in the source configuration data package according to its internal structure, whether it is a simple numerical parameter (such as gain) or a complex structured object (such as a report template). In each iteration, i.e. for each configuration parameter item, the engine performs a quick and accurate decision and operation. It performs a decision flow according to the loaded compatibility rules to determine an adaptive operation. The decision flow determines the support of the current parameter item on the target device. According to the result of the determination, the engine determines a specific adaptive operation, which is one of filtering operation, conversion operation or degradation operation. For example, if the rule library indicates that the target device does not support the function named "composite imaging", the engine determines to perform "filtering operation" on this parameter item; if the rule indicates that the gain range of the target device is different from that of the source device, the engine determines to perform "conversion operation"; if the rule indicates that the target device does not support "shear wave elastography" used by the source device but supports "strain elastography", the engine determines to perform "degradation operation".

[0229] Subsequently, the engine performs the filling and building of the result. After the adaptive operation is determined, the engine immediately performs it. The result of the performance can be a new parameter after numerical mapping, or a new data object after structural reorganization, or being completely discarded (i.e. null). The engine adds the result of the adaptive operation, or the original parameter item itself if the decision flow determines no operation is needed, into the target configuration data structure initialized before, rigorously. With each iteration, the target data structure is filled more completely, and gradually contains the complete configuration of all adapted parameters.

[0230] Finally, after the engine successfully traverses and processes all parameter items in the source configuration data packet, the iteration loop ends. At this time, the engine performs the final packaging and output. After all parameter items are processed, the engine performs a final integrity check and architecture verification on the target configuration data structure. After the verification passes, the data structure containing all adapted parameters is serialized and packaged to form the target configuration data packet. At this time, the target configuration data packet is then returned by the engine to the upper-layer business service, ready to be delivered to the target device together with the synchronously generated conversion execution log.

[0231] In an embodiment of the present application, the step of synchronously generating a conversion execution log recording the adaptive processing process comprises:

[0232] An empty conversion execution log is initialized while processing each configuration parameter item parsed from the source configuration data packet in an iterative manner;

[0233] Detailed log records are generated and appended to the conversion execution log whenever an adaptive operation is performed on any configuration parameter item, and the log records at least contain the identifier of the operated parameter, the type of the performed operation, the value before the operation, and the value after the operation.

[0234] In an embodiment of the present application, the step of performing a decision flow according to the loaded compatibility rules to determine the adaptive operation comprises:

[0235] When the compatibility rules indicate that the target device does not support the current processing configuration parameter item at all, it is determined that the adaptive operation is a filtering operation, and the current processing configuration parameter item is discarded;

[0236] When the compatibility rules indicate that the target device supports the current processing configuration parameter item, but the numerical range or unit is different from that in the source configuration data packet, it is determined that the adaptive operation is a conversion operation, and the current processing configuration parameter item is adjusted according to the compatibility rules;

[0237] When the compatibility rules indicate that the target device does not support the advanced feature in the source device corresponding to the currently processed configuration parameter item, but supports an alternative basic feature, the adaptive operation is determined to be a downgrading operation, and the currently processed configuration parameter item is replaced by a parameter item adapting the basic feature according to the compatibility rules.

[0238] Specifically, before the iteration processing loop of the configuration conversion engine starts, i.e. while processing each configuration parameter item parsed from the source configuration data packet in an iterative manner, the engine initializes an empty conversion execution log. This log is created in memory as a dynamically appendable structured data object, such as a list or an array, ready for recording all subsequent changes.

[0239] Then, in each iteration, when the engine performs an adaptive operation on a configuration parameter item according to the compatibility rules and executes the operation, i.e. each time an adaptive operation is performed on any configuration parameter item (whether filtering, conversion or downgrading), the engine immediately triggers a log recording action. A detailed log record is generated and appended to the conversion execution log. This newly generated log record is a structured data entry, which contains multiple key fields to ensure the completeness and accuracy of the information. The log record at least contains: the identifier of the operated parameter, the type of the performed operation, the value before the operation, and the value after the operation. The identifier of the operated parameter is used to explicitly indicate which configuration item is modified; the type of the performed operation is used to indicate the nature of the operation; the value before the operation records the original state of the parameter item in the source configuration data packet, such as the value 80 or the string "Enabled"; and the value after the operation records the new state of the parameter item in the target configuration data packet after adaptive processing, such as the value 210 or the string "Disabled". For filtered operations, the value can be empty.

[0240] Therefore, through the above-mentioned real-time recording synchronized with the processing process, the engine ensures the absolute accuracy and completeness of the conversion execution log.

[0241] Further, in each step of the iteration loop, the core intelligence of the engine is reflected in how it executes a decision-making process to determine the adaptive operation according to the loaded compatibility rules. The decision-making process mainly includes:

[0242] First, the engine queries the loaded compatibility rules with the currently processing configuration parameter item. When the compatibility rules indicate that the target device does not support the currently processing configuration parameter item at all, it determines the adaptation operation as a filtering operation. Then, the engine performs this operation, i.e. discarding the currently processing configuration parameter item, which means that this parameter item will not be added into the target configuration data structure being built.

[0243] When the first condition is not met, the engine continues to judge the next condition. When the compatibility rules indicate that the target device supports the currently processing configuration parameter item, but the value range or unit is different from that in the source configuration data package, it determines the adaptation operation as a conversion operation. Then, the engine performs this operation, and adjusts the value of the currently processing configuration parameter item according to the specific mapping function (such as linear scaling) defined in the compatibility rules.

[0244] When the first two conditions are not met, the engine makes the last judgment. When the compatibility rules indicate that the target device does not support the advanced function in the source device corresponding to the currently processing configuration parameter item, but supports an alternative basic function, it determines the adaptation operation as a downgrading operation. For example, the function equivalence and downgrading rules in the rule library indicate that the "shear wave elastography" configuration used by the source device can be downgraded to "strain elastography" on the target device which does not support the former function. Then, the engine performs this operation, and replaces the currently processing configuration parameter item (which may be a complex object containing multiple sub-parameters) related to the advanced function with a new set of parameters for configuring the adapted basic function according to the replacement logic defined in the compatibility rules.

[0245] Further, in an embodiment of the present application, the step of adjusting the currently processing configuration parameter item according to the compatibility rules comprises:

[0246] performing numerical mapping adjustment when the configuration parameter item is a numerical parameter;

[0247] performing enumeration value mapping adjustment when the configuration parameter item is an enumeration parameter;

[0248] performing semantic identifier replacement when the configuration parameter item is an identifier parameter.

[0249] Specifically, the step of performing the numerical value mapping adjustment comprises: obtaining, from the compatibility rule library, a source numerical value range, a target numerical value range and a preset mapping function type for the current numerical type parameter; calling a corresponding numerical conversion algorithm according to the mapping function type, the numerical conversion algorithm being one of a linear scaling algorithm, a piecewise linear interpolation algorithm, a logarithmic mapping algorithm or a lookup table replacement algorithm; taking the parameter value of the configuration parameter item currently being processed as an input, calculating a new parameter value adapted to the target numerical value range by the numerical conversion algorithm, and updating the configuration parameter item currently being processed with the new parameter value.

[0250] The step of performing the enumeration value mapping adjustment comprises: obtaining, from the compatibility rule library, a mapping table of enumeration values from the source device to the target device for the current enumeration type parameter; finding, in the mapping table, a target enumeration value corresponding to the enumeration value of the configuration parameter item currently being processed; if the corresponding target enumeration value is found, updating the configuration parameter item currently being processed with the target enumeration value; and if the corresponding target enumeration value is not found, setting a new enumeration value of the configuration parameter item currently being processed according to a default value or a closest equivalent value defined in the compatibility rule library.

[0251] The step of performing the semantic identifier replacement comprises: identifying a semantic identifier corresponding to the parameter value of the configuration parameter item currently being processed, the semantic identifier being used to refer to a specific function or resource; querying, from the compatibility rule library, a global identifier mapping table defining cross-device semantic equivalent relationships; finding, in the global identifier mapping table, an equivalent identifier valid on the target device corresponding to the semantic identifier of the configuration parameter item currently being processed; and replacing the source identifier with the equivalent identifier to update the configuration parameter item currently being processed, so as to restore the correct linkage of the specific function or resource on the target device.

[0252] Further, in an embodiment of the present application, the step of replacing the configuration parameter item currently being processed with a parameter item adapted to the basic function according to the compatibility rule comprises:

[0253] when the configuration parameter item relates to an advanced imaging function, performing imaging function degradation replacement;

[0254] when the configuration parameter item relates to a proprietary data format, performing data format degradation conversion;

[0255] when the configuration parameter item relates to a composite workflow setting, performing workflow disassembly and remapping.

[0256] Specifically, the step of performing the imaging function downgrade replacement comprises: querying, from the compatibility rule library, a downgrade rule for the current advanced imaging function, the downgrade rule specifying one or more basic imaging functions supported on the target device as its equivalent replacement; removing all parameter items related to the advanced imaging function from the source configuration data packet; and generating a set of new parameter items for activating and configuring the basic imaging functions in the target configuration data packet according to default parameter values or mapping relationships defined in the downgrade rule.

[0257] The step of performing the data format downgrade conversion comprises: identifying a proprietary data structure contained or referenced by the current processing configuration parameter item; querying, from the compatibility rule library, a downgrade rule for the proprietary data format, the rule specifying a general and basic standard format as its replacement; invoking a predefined format conversion module to parse the proprietary data structure to extract core semantic information therein; and re-encapsulating the extracted core semantic information according to the specification of the standard format to generate a new data object conforming to the standard format, and replacing the original proprietary data structure.

[0258] The step of performing the workflow disassembly and remapping comprises: identifying a composite workflow setting of the current processing configuration parameter item, the composite workflow setting binding multiple independent operations to a single shortcut key or custom button; querying, from the compatibility rule library, support conditions of the target device for the multiple independent operations; discarding all independent operations not supported by the target device; and disassembling all supported independent operations from the original composite binding, and remapping one or more most important operations thereof to an independent shortcut key or custom button available on the target device according to a priority or default mapping rule defined in the rule library.

[0259] In this embodiment of the invention, by receiving and storing source configuration data packets containing device characteristic information and user-personalized configuration data, and establishing an association index between these packets and user accounts and device identifiers, a fundamental shift from isolated local storage to centralized, structured, and traceable cloud management is achieved. This not only provides users with reliable data backup but also lays a solid data foundation for subsequent intelligent processing by strongly binding configuration data with its generated "device context." Furthermore, by performing multi-level decision tree comparisons and preliminary compatibility judgments on each source configuration under the user account based on the target device's device characteristic information and a preset compatibility rule base when responding to configuration list requests, the feasibility of cross-model and cross-version configuration migration is realized. It can predict and categorize configurations; by activating the configuration conversion engine, when a compatibility status indicates a need for conversion, it iteratively processes each parameter item of the source configuration and executes a precise decision-making process based on the loaded compatibility rules, achieving intelligent and automated adaptation of configuration data; by synchronously generating detailed conversion execution logs during the adaptive processing, recording the operation type and numerical changes of each parameter item, and distributing these logs along with the final generated target configuration data package, it achieves complete transparency and traceability of the processing process; and by integrating a series of complex operations such as receiving, storing, judging, converting, and distributing into a unified cloud platform, it achieves intensive utilization of computing resources and centralized maintenance and dynamic updates of the compatibility rule base. This solves the shortcomings of existing ultrasound equipment in synchronizing personalized configurations across devices. Example 3

[0260] Please see Figure 3 The diagram shown is a structural schematic of an ultrasonic equipment configuration synchronization system provided in the third embodiment of the present invention. For ease of explanation, only the parts related to the embodiment of the present invention are shown. The ultrasonic equipment configuration synchronization system provided in this embodiment of the present invention is applied to an ultrasonic equipment, and the system includes:

[0261] The source configuration data packet upload module 11 is used to respond to the upload command when the ultrasound device performs a configuration upload operation as a source device, generate a source configuration data packet containing its own device feature information and user personalized configuration data, and send it to the cloud platform for storage and association with the user account.

[0262] The configuration list request sending module 12 is used to respond to the synchronization command and send a configuration list request containing its own device feature information to the cloud platform when the ultrasound device performs a configuration synchronization operation as the target device.

[0263] The configuration list receiving module 13 is configured to receive a configuration list returned by the cloud platform, the configuration list comprising compatibility statuses between each source configuration data packet under a user account and the target device;

[0264] The download request sending module 14 is configured to, in response to an operation of the user selecting a selected configuration item from the configuration list, send a download request for the selected configuration item to the cloud platform;

[0265] The target configuration data packet receiving module 15 is configured to receive and apply a target configuration data packet corresponding to the selected configuration item and issued by the cloud platform, to update the local configuration.

[0266] Further, in an embodiment of the present application, the target configuration data packet receiving module 15 comprises:

[0267] The first target configuration data packet receiving unit is configured to, when the compatibility status of the selected configuration item is compatible, receive a source configuration data packet corresponding to the selected configuration item and issued by the cloud platform as a target configuration data packet, and apply the target configuration data packet to update the local configuration;

[0268] The second target configuration data packet receiving unit is configured to, when the compatibility status of the selected configuration item is conversion required, receive a target configuration data packet generated by adaptively processing a source configuration data packet corresponding to the selected configuration item to adapt to the target device, and a conversion execution log recording the adaptive processing process;

[0269] The configuration updating unit is configured to, based on the conversion execution log, perform confirmation interaction with the user, and after obtaining a confirmation instruction of the user, apply the target configuration data packet to update the local configuration.

[0270] Further, in an embodiment of the present application, the configuration updating unit comprises:

[0271] The parsing subunit is configured to parse the conversion execution log to extract an operation type of each adaptive operation, a configuration parameter item acted on, and details of value or status changes before and after the operation;

[0272] The visualization subunit is configured to, based on the extracted details, generate a visualized change confirmation summary in the form of a highlighted or contrasted list on a user interaction interface;

[0273] The user instruction receiving subunit is configured to receive an explicit instruction of the user input through the change confirmation summary interface, the explicit instruction being one of confirmation, cancellation, or modification;

[0274] The configuration application subunit is configured to apply the target configuration package in response to receiving a confirmation instruction input by the user.

[0275] Further, in an embodiment of the present application, the configuration updating unit further comprises:

[0276] The modification instruction response subunit is configured to provide an interactive option for each modified configuration item in response to receiving a modification instruction input by the user, to allow the user to select from a set of preset solutions, including at least: maintaining the original state of the configuration item in the source configuration package, or applying the adapted state set for the configuration item in the target configuration package, or reverting to the default state of the factory default value of the device;

[0277] The parameter item updating subunit is configured to update the corresponding configuration parameter item in the target configuration package in response to the target solution selected by the user.

[0278] Further, in an embodiment of the present application, the system further comprises:

[0279] The local snapshot creation module is configured to create a local snapshot of all personalized configuration data of the target device and store it before applying the target configuration package to update the local configuration;

[0280] The first configuration recovery module is configured to automatically abort the application process and recover the configuration of the target device to the state before the application using the local snapshot if any error or configuration conflict occurs to interrupt the application when applying the target configuration package to update the local configuration;

[0281] The second configuration recovery module is configured to recover the configuration of the target device to the state before the application using the local snapshot if a rollback instruction triggered by the user is received within a preset time after applying the target configuration package.

[0282] Further, in an embodiment of the present application, the source configuration package uploading module 11 comprises:

[0283] The device feature information acquisition unit is configured to acquire the state information of multiple dimensions of the ultrasound device in real time to constitute the device feature information;

[0284] The data serialization unit is configured to serialize all personalized configuration data of the current activity of the user into a predefined structured data format;

[0285] The data encapsulation unit is configured to encapsulate the device feature information and the serialized personalized configuration data of the user into a structured source configuration package;

[0286] The source configuration data packet sending unit is configured to establish an encrypted secure communication link with the cloud platform and send the source configuration data packet to the cloud platform through the secure communication link.

[0287] The implementation principle and the technical effects of the ultrasound device configuration synchronization system provided by the embodiments of the present application are the same as those of the foregoing method embodiments. For brevity, the part not mentioned in the device embodiment part can be referred to the corresponding content in the foregoing method embodiments. Embodiment Four

[0288] Referring to Figure 4 , a structural schematic diagram of an ultrasound device configuration synchronization system provided by a fourth embodiment of the present application is shown. For brevity, only the part related to the embodiments of the present application is shown. The ultrasound device configuration synchronization system provided by the embodiments of the present application is applied to a cloud platform. The system comprises:

[0289] A source configuration data packet receiving module 21 is configured to receive and store a source configuration data packet containing device characteristic information and user personalized configuration data sent by an ultrasound device as a source device, and establish an association between the source configuration data packet and a corresponding user account;

[0290] A configuration list request receiving module 22 is configured to receive a configuration list request containing device characteristic information sent by an ultrasound device as a target device;

[0291] A configuration list sending module 23 is configured to perform preliminary compatibility judgment on each source configuration data packet associated with the user account according to the device characteristic information of the target device and a preset compatibility rule library, and generate a configuration list containing the compatibility status of each source configuration data packet and return the configuration list to the target device;

[0292] A download request receiving module 24 is configured to receive a download request for a selected configuration item in the configuration list sent by the target device;

[0293] A target configuration data packet sending module 25 is configured to respond to the download request, process the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet, and deliver the target configuration data packet to the target device.

[0294] Further, in an embodiment of the present application, the target configuration data packet sending module 25 comprises:

[0295] A first target configuration data packet sending unit is configured to, when the compatibility status of the selected configuration item is compatible, directly deliver the source configuration data packet corresponding to the selected configuration item to the target device as a target configuration data packet;

[0296] The second target configuration data packet sending unit is configured to, when the compatibility state of the selected configuration item is to be converted, start a configuration conversion engine to perform adaptive processing on the source configuration data packet corresponding to the selected configuration item, generate a target configuration data packet adapted to the target device, and synchronously generate a conversion execution log recording the adaptive processing process, and deliver the target configuration data packet and the conversion execution log to the target device.

[0297] Further, in an embodiment of the present application, the source configuration data packet receiving module 21 comprises:

[0298] The upload request receiving unit is configured to establish an encrypted secure communication link with the source device, and receive an upload request sent by the source device through the secure communication link, wherein the upload request comprises user authentication credentials and the source configuration data packet.

[0299] The verification unit is configured to verify the user authentication credentials to confirm the user identity and obtain a unique user identifier.

[0300] The data parsing unit is configured to, if the verification is passed, parse and extract device feature information and user personalized configuration data from the source configuration data packet.

[0301] The device identifier obtaining unit is configured to query or create a unique device record corresponding to the source device in a device information database according to the extracted device feature information, and obtain a corresponding device identifier.

[0302] The configuration data storing unit is configured to create a new configuration record in a configuration storage database, and store configuration data obtained by encrypting the user personalized configuration data in the configuration record.

[0303] The data association unit is configured to store the configuration record in association with the user identifier and the device identifier in a configuration index database.

[0304] Further, in an embodiment of the present application, the second target configuration data packet sending unit comprises:

[0305] The index record retrieving sub-unit is configured to retrieve, from the configuration index database, index records of all source configuration data packets associated with the user account according to the user account in the received configuration list request.

[0306] The device feature information extracting sub-unit is configured to, for each index record retrieved, extract the stored device feature information of the source device.

[0307] a compatibility determining sub-unit configured to compare the extracted device feature information of the source device with the device feature information of the target device carried in the configuration list request by using a multi-level decision tree to determine a compatibility state;

[0308] a configuration list constructing sub-unit configured to add the determined compatibility state and the corresponding source configuration data packet information into the currently constructed configuration list.

[0309] Further, in an embodiment of the present application, the compatibility determining sub-unit is configured to:

[0310] compare the device model and firmware version in the device feature information of the source device and the target device;

[0311] if the device model and firmware version in the source device and the target device are consistent, determine the compatibility state as compatible;

[0312] if the device model in the source device and the target device is consistent but the firmware version is different, query the configuration difference information between firmware versions in the compatibility rule library to determine the compatibility state as compatible or conversion required;

[0313] if the device model in the source device and the target device is different, query whether there is a cross-model parameter mapping rule in the compatibility rule library to determine the compatibility state as conversion required or incompatible.

[0314] Further, in an embodiment of the present application, the second target configuration data packet sending unit comprises:

[0315] a data structure initializing sub-unit configured to initialize an empty target configuration data structure and load the compatibility rules related to the source device and the target device;

[0316] a configuration data iterative parsing sub-unit configured to process each configuration parameter item parsed from the source configuration data packet in an iterative manner;

[0317] an adaptive operation determining sub-unit configured to determine an adaptive operation for each configuration parameter item according to the loaded compatibility rules by executing a decision flow, the adaptive operation being one of filtering operation, conversion operation or degradation operation;

[0318] a data adding sub-unit configured to add the result after executing the adaptive operation or the original parameter item when no operation is required into the target configuration data structure;

[0319] a data encapsulating sub-unit configured to encapsulate the target configuration data structure to form the target configuration data packet after all parameter items are processed.

[0320] Further, in an embodiment of the present application, the second target configuration data packet sending unit further comprises:

[0321] a log initialization sub-unit, configured to initialize an empty conversion execution log while processing each configuration parameter item parsed from the source configuration data packet in an iterative manner;

[0322] a log recording sub-unit, configured to generate a detailed log record and append it to the conversion execution log whenever an adaptive operation is performed on any configuration parameter item, the log record at least containing an identifier of the operated parameter, a type of the performed operation, a value before the operation and a value after the operation.

[0323] Further, in an embodiment of the present application, the adaptive operation determination sub-unit is configured to:

[0324] when the compatibility rule indicates that the target device does not support the current processing configuration parameter item at all, determine the adaptive operation as a filtering operation and discard the current processing configuration parameter item;

[0325] when the compatibility rule indicates that the target device supports the current processing configuration parameter item but the value range or unit is different from that in the source configuration data packet, determine the adaptive operation as a conversion operation and adjust the current processing configuration parameter item according to the compatibility rule;

[0326] when the compatibility rule indicates that the target device does not support an advanced function in the source device corresponding to the current processing configuration parameter item but supports a replaceable basic function, determine the adaptive operation as a downgrade operation and replace the current processing configuration parameter item with a parameter item adapted to the basic function according to the compatibility rule.

[0327] The ultrasonic device configuration synchronization system provided by the embodiment of the present application has the same implementation principle, technical effects and the above-mentioned method embodiment. For brevity of description, the part not mentioned in the device embodiment can be referred to the corresponding content in the above-mentioned method embodiment. Embodiment five

[0328] In another aspect, the present application further provides an ultrasonic device, comprising a memory, a processor and a program stored in the memory and executable on the processor, wherein the processor implements the ultrasonic device configuration synchronization method of the above-mentioned embodiment one when executing the program.

[0329] In some embodiments, the processor can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor or other data processing chip, configured to run program codes stored in the memory or process data, for example, to execute the access restriction program.

[0330] The memory includes at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a magnetic memory, a disk, an optical disk, etc. The memory can be an internal storage unit of the ultrasound device in some embodiments, such as a hard disk of the ultrasound device. The memory can also be an external storage device of the ultrasound device in other embodiments, such as a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the ultrasound device. Further, the memory can include both the internal storage unit and the external storage device of the ultrasound device. The memory can be used to store application software and various data installed on the ultrasound device, and to temporarily store data that has been output or is to be output. Embodiment six

[0331] Another aspect of the present application also provides a cloud platform, including a memory, a processor, and a program stored in the memory and executable on the processor, and the processor implements the ultrasound device configuration synchronization method of Embodiment Two when executing the program.

[0332] Specifically, the processor can be a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments, and is used to run program codes or process data stored in the memory, such as executing the access restriction program.

[0333] The memory includes at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a magnetic memory, a disk, an optical disk, etc. The memory can be an internal storage unit of the cloud platform in some embodiments, such as a hard disk of the cloud platform. The memory can also be an external storage device of the cloud platform in other embodiments, such as a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the cloud platform. Further, the memory can include both the internal storage unit and the external storage device of the cloud platform. The memory can be used to store application software and various data installed on the cloud platform, and to temporarily store data that has been output or is to be output. Embodiment seven

[0334] Another aspect of the present application also provides a synchronization system, comprising the ultrasonic device according to the above-mentioned embodiment five; and the cloud platform according to the above-mentioned embodiment six, which is in communication connection with the ultrasonic device.

[0335] The embodiment of the present application also provides a storage medium, which stores a program, and the program is executed by a processor to realize the ultrasonic device configuration synchronization method according to the above-mentioned embodiment one.

[0336] The embodiment of the present application also provides a storage medium, which stores a program, and the program is executed by a processor to realize the ultrasonic device configuration synchronization method according to the above-mentioned embodiment two.

[0337] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional units and modules is exemplified, and in actual application, the above functions can be completed by different functional units or modules according to needs, that is, the internal structure of the storage device is divided into different functional units or modules to complete all or part of the above-described functions. Each functional unit and module in the embodiment can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit, and the integrated unit can be realized in the form of hardware or software. In addition, the specific names of each functional unit and module are only for easy distinction, and do not limit the protection scope of the present application.

[0338] Those skilled in the art can understand that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequence list of executable instructions for implementing logical functions, which can be specifically implemented in any storage medium for use by or in conjunction with an instruction execution system, device or equipment, such as a computer-based system, a system including a processor or other system that can fetch and execute instructions from an instruction execution system, device or equipment. For the present specification, the "storage medium" can be any device that can contain, store, communicate, propagate or transmit programs for use by or in conjunction with an instruction execution system, device or equipment.

[0339] More specific examples (a non-exhaustive list) of the storage media include the following: an electrical connection having one or more wires (electrical wiring), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the storage media can even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for instance via an optical scanner, then compiled, interpreted, or otherwise processed, using an appropriate medium, into an electronically usable form capable of being stored in a memory and subsequently executed by a processing element.

[0340] It should be understood that aspects of the application can be implemented in hardware, software, firmware or combinations thereof. In the embodiments described above, various steps or methods can be implemented, for example, by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and in another embodiment, any of the following techniques, which are well known in the art, can be used to implement the application: a hybrid of the above techniques, discrete logic circuitry having logic gates for implementing logic functions upon data signals, programmable logic array (PLA), field programmable gate array (FPGA), etc.

[0341] In the description of the specification, the description of the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the application. In the specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any appropriate manner in one or more embodiments or examples.

[0342] The above-described embodiments are merely some embodiments of the present application, and the description is more specific and detailed, but should not be understood as limiting the scope of the present application. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are within the scope of the present application. Therefore, the scope of the present application should be determined by the appended claims.

Claims

1. A method for configuring synchronization in an ultrasonic device, characterized in that, Applied to ultrasonic equipment, the method includes: When the ultrasound device performs a configuration upload operation as a source device, it responds to the upload command, generates a source configuration data packet containing its own device feature information and user personalized configuration data, and sends it to the cloud platform for storage and association with the user account. When the ultrasound device performs a configuration synchronization operation as a target device, it responds to the synchronization command and sends a configuration list request containing its own device feature information to the cloud platform. Receive a configuration list returned by the cloud platform, which includes the compatibility status between the various source configuration data packets under the user account and the target device; In response to a user's selection of a configuration item from the configuration list, a download request for the selected configuration item is sent to the cloud platform. Receive and apply the target configuration data packet corresponding to the selected configuration item sent by the cloud platform to update the local configuration; The step of receiving and applying the target configuration data packet corresponding to the selected configuration item issued by the cloud platform includes: When the compatibility status of the selected configuration item is compatible, the source configuration data packet corresponding to the selected configuration item sent by the cloud platform is received as the target configuration data packet, and the target configuration data packet is applied to update the local configuration. When the compatibility status of the selected configuration item is "needs conversion", the system receives the target configuration data packet generated by adapting the source configuration data packet corresponding to the selected configuration item to the target device, which is sent by the cloud platform, and the conversion execution log that records the adaptation process. Based on the conversion execution log, a confirmation interaction is performed with the user, and after obtaining the user's confirmation instruction, the target configuration data packet is applied to update the local configuration; The step of confirming the user based on the conversion execution log, and applying the target configuration data packet to update the local configuration after obtaining the user's confirmation instruction, includes: The transformation execution log is parsed to extract the operation type, configuration parameter items of each adaptive operation, and details of the numerical or state changes before and after the operation. Based on the extracted details, a visual summary of the change confirmation is generated on the user interface in the form of a highlighted or contrasted list; Receive the exact instruction input by the user through the change confirmation summary interface, wherein the exact instruction is one of confirmation, cancellation or modification; In response to receiving a confirmation command from the user, the target configuration data packet is applied.

2. The ultrasonic equipment configuration synchronization method according to claim 1, characterized in that, After the step of receiving the exact instruction input by the user through the change confirmation summary interface, the method further includes: In response to receiving a modification instruction from the user, an interactive option is provided for each modified configuration item to allow the user to choose from a set of preset solutions, the preset solutions including at least: maintaining the original state of the configuration item in the source configuration data packet, or applying the adaptation state set for the configuration item in the target configuration data packet, or restoring to the default state of the device's factory default value. In response to the user's selected target solution, update the corresponding configuration parameter items in the target configuration data package.

3. The ultrasonic equipment configuration synchronization method according to claim 1, characterized in that, The method further includes: Before applying the target configuration data package to update the local configuration, a local snapshot of all personalized configuration data of the target device is created and stored. If any error or configuration conflict causes the application to be interrupted when the target configuration data package is applied to update the local configuration, the application process will be automatically terminated and the target device configuration will be restored to the state before the application using the local snapshot. After applying the target configuration data package, if a rollback command triggered by the user is received within a preset time, the target device configuration is restored to the state before the application using the local snapshot.

4. The ultrasonic equipment configuration synchronization method according to claim 1, characterized in that, The step of generating a source configuration data packet containing the device's own characteristic information and the user's personalized configuration data, and sending it to the cloud platform, includes: Real-time acquisition of multiple dimensions of status information of the ultrasound equipment to constitute the equipment feature information; Serialize all personalized configuration data of the user's current activity into a predefined structured data format; The device feature information and the serialized user personalized configuration data are encapsulated into a structured source configuration data packet; An encrypted secure communication link is established with the cloud platform, and the source configuration data packet is sent to the cloud platform through the secure communication link.

5. A method for synchronizing the configuration of an ultrasonic device, characterized in that, Applied to a cloud platform, the method includes: Receive and store source configuration data packets containing device feature information and user personalized configuration data sent from the ultrasound device as the source device, and establish an association between the source configuration data packets and the corresponding user account; Receive a configuration list request containing its own device characteristic information from the ultrasound device that is the target device; Based on the device feature information of the target device and the preset compatibility rule base, a preliminary compatibility judgment is made on each source configuration data packet associated with the user account, and a configuration list containing the compatibility status of each source configuration data packet is generated and returned to the target device. Receive a download request from the target device for a selected configuration item in the configuration list; In response to the download request, the source configuration data packet corresponding to the selected configuration item is processed to generate a target configuration data packet and sent to the target device; The step of processing the source configuration data packet corresponding to the selected configuration item to generate the target configuration data packet and sending it to the target device includes: When the compatibility status of the selected configuration item is compatible, the source configuration data packet corresponding to the selected configuration item is directly used as the target configuration data packet and sent to the target device. When the compatibility status of the selected configuration item is "needs conversion", the configuration conversion engine is started to perform adaptive processing on the source configuration data packet corresponding to the selected configuration item, generate a target configuration data packet adapted to the target device, and simultaneously generate a conversion execution log that records the adaptive processing process, and send the target configuration data packet and the conversion execution log to the target device together. The target device interacts with the user for confirmation based on the conversion execution log, and after receiving the user's confirmation instruction, applies the target configuration data packet to update the local configuration, including: The transformation execution log is parsed to extract the operation type, configuration parameter items of each adaptive operation, and details of the numerical or state changes before and after the operation. Based on the extracted details, a visual summary of the change confirmation is generated on the user interface in the form of a highlighted or contrasted list; Receive the exact instruction input by the user through the change confirmation summary interface, wherein the exact instruction is one of confirmation, cancellation or modification; In response to receiving a confirmation command from the user, the target configuration data packet is applied.

6. The ultrasonic equipment configuration synchronization method according to claim 5, characterized in that, The steps of receiving and storing a source configuration data packet containing the device's own characteristic information and the user's personalized configuration data sent from the ultrasound device (as the source device), and establishing an association between the source configuration data packet and the corresponding user account, include: An encrypted secure communication link is established with the source device, and an upload request sent by the source device is received through the secure communication link. The upload request includes user authentication credentials and the source configuration data packet. The user authentication credentials are verified to confirm the user's identity and obtain a unique user identifier; If the verification is successful, device feature information and user personalized configuration data are parsed and extracted from the source configuration data packet; Based on the extracted device feature information, query or create a unique device record corresponding to the source device in the device information database, and obtain the corresponding device identifier; Create a new configuration record in the configuration storage database, and store the encrypted configuration data of the user's personalized configuration data into the configuration record; The configuration record is associated with the user identifier and the device identifier and stored in the configuration index database.

7. The ultrasonic equipment configuration synchronization method according to claim 5, characterized in that, The step of performing a preliminary compatibility assessment on each source configuration data packet associated with the user account based on the device characteristic information of the target device and a preset compatibility rule base includes: Based on the user account in the received configuration list request, retrieve the index records of all source configuration data packets associated with the user account from the configuration index database; For each index record retrieved, extract the device characteristic information of the stored source device; The extracted device feature information of the source device is compared with the device feature information of the target device carried in the configuration list request using a multi-level decision tree method to determine the compatibility status. Add the determined compatibility status along with the corresponding source configuration data package information to the currently constructed configuration list.

8. The ultrasonic equipment configuration synchronization method according to claim 7, characterized in that, The step of performing a multi-level decision tree comparison between the extracted source device's device feature information and the target device's device feature information carried in the configuration list request to determine the compatibility status includes: Compare the device model and firmware version in the device feature information of the source device and the target device; If the target device and the source device have the same device model and firmware version, then the compatibility status is determined to be compatible. If the target device and the source device have the same device model but different firmware versions, query the compatibility rule base for configuration differences between firmware versions to determine whether the compatibility status is compatible or requires conversion. If the target device is different from the device model in the source device, the compatibility rule base is queried to determine whether there is a cross-model parameter mapping rule, so as to determine whether the compatibility status is that it needs to be converted or is incompatible.

9. The ultrasonic equipment configuration synchronization method according to claim 5, characterized in that, The step of the startup configuration conversion engine adaptively processing the source configuration data packet corresponding to the selected configuration item to generate a target configuration data packet adapted to the target device includes: Initialize an empty target configuration data structure and load compatibility rules related to the source device and the target device; Each configuration parameter item parsed from the source configuration data packet is processed iteratively. For each configuration parameter item, a decision process is executed based on the loaded compatibility rules to determine the adaptive operation, which is one of the following: filtering operation, transformation operation, or degradation operation. The results of the adaptive operation, or the original parameter items when no operation is required, are added to the target configuration data structure. After all parameter items have been processed, the target configuration data structure is encapsulated to form the target configuration data package.

10. The ultrasonic equipment configuration synchronization method according to claim 9, characterized in that, The step of synchronously generating a transformation execution log that records the adaptive processing includes: While iteratively processing each configuration parameter item parsed from the source configuration data packet, an empty transformation execution log is initialized; Whenever an adaptive operation is performed on any configuration parameter item, a detailed log record is generated and appended to the transformation execution log. The log record includes at least the identifier of the operated parameter, the type of operation performed, the value before the operation, and the value after the operation.

11. The ultrasonic equipment configuration synchronization method according to claim 9, characterized in that, The steps of executing a decision process based on the loaded compatibility rules to determine adaptive operations include: When the compatibility rule indicates that the target device does not support the currently processed configuration parameter item at all, the adaptive operation is determined to be a filtering operation, and the currently processed configuration parameter item is discarded; When the compatibility rule indicates that the target device supports the currently processed configuration parameter item, but the value range or unit is different from that in the source configuration data packet, the adaptive operation is determined to be a conversion operation, and the currently processed configuration parameter item is adjusted according to the compatibility rule; When the compatibility rule indicates that the target device does not support the advanced functions in the source device corresponding to the currently processed configuration parameter item, but supports an alternative basic function, the adaptive operation is determined to be a degradation operation, and the currently processed configuration parameter item is replaced with a parameter item that adapts to the basic function according to the compatibility rule.

12. A synchronization system for an ultrasonic device, characterized in that, The system, applied to ultrasonic equipment, includes: The source configuration data packet upload module is used to respond to the upload command when the ultrasound device performs a configuration upload operation as a source device, generate a source configuration data packet containing its own device feature information and user personalized configuration data, and send it to the cloud platform for storage and association with the user account. The configuration list request sending module is used to respond to the synchronization command and send a configuration list request containing its own device feature information to the cloud platform when the ultrasound device performs a configuration synchronization operation as the target device. The configuration list receiving module is used to receive a configuration list returned by the cloud platform, which includes the compatibility status between each source configuration data packet under the user account and the target device. The download request sending module is used to respond to the user's operation of selecting a selected configuration item from the configuration list and send a download request for the selected configuration item to the cloud platform; The target configuration data packet receiving module is used to receive and apply the target configuration data packet corresponding to the selected configuration item issued by the cloud platform to update the local configuration; The target configuration data packet receiving module includes: The first target configuration data packet receiving unit is used to receive the source configuration data packet corresponding to the selected configuration item sent by the cloud platform as the target configuration data packet when the compatibility status of the selected configuration item is compatible, and to apply the target configuration data packet to update the local configuration. The second target configuration data packet receiving unit is used to receive, when the compatibility status of the selected configuration item is to be converted, the target configuration data packet generated by the source configuration data packet corresponding to the selected configuration item after adaptive processing to adapt to the target device, which is sent by the cloud platform, and the conversion execution log that records the adaptive processing process; The configuration update unit is used to perform a confirmation interaction with the user based on the conversion execution log, and after obtaining the user's confirmation instruction, apply the target configuration data packet to update the local configuration; The configuration update unit includes: The parsing subunit is used to parse the transformation execution log to extract the operation type, configuration parameter items of the action, and details of the numerical or state changes before and after the operation for each adaptive operation. The visualization subunit is used to generate a visual summary of change confirmations on the user interface, in the form of a highlighted or contrasted list, based on the extracted details. The user instruction receiving subunit is used to receive the exact instruction input by the user through the change confirmation summary interface, wherein the exact instruction is one of confirmation, cancellation or modification; The configuration application subunit is used to perform application operations on the target configuration data packet in response to receiving a confirmation command input by the user.

13. A synchronization system for an ultrasonic device, characterized in that, The system, applied to a cloud platform, includes: The source configuration data packet receiving module is used to receive and store source configuration data packets sent from the ultrasound device as the source device, which contain its own device characteristic information and user personalized configuration data, and to establish the association between the source configuration data packet and the corresponding user account. The configuration list request receiving module is used to receive a configuration list request containing its own device characteristic information sent by the ultrasound device that is the target device. The configuration list sending module is used to perform a preliminary compatibility judgment on each source configuration data packet associated with the user account based on the device feature information of the target device and a preset compatibility rule library, and generate a configuration list containing the compatibility status of each source configuration data packet and return it to the target device. A download request receiving module is used to receive a download request from the target device for a selected configuration item in the configuration list; The target configuration data packet sending module is used to respond to the download request, process the source configuration data packet corresponding to the selected configuration item to generate the target configuration data packet and send it to the target device; The target configuration data packet sending module includes: The first target configuration data packet sending unit is used to directly send the source configuration data packet corresponding to the selected configuration item as the target configuration data packet to the target device when the compatibility status of the selected configuration item is compatible. The second target configuration data packet sending unit is used to start the configuration conversion engine to perform adaptive processing on the source configuration data packet corresponding to the selected configuration item when the compatibility status of the selected configuration item is that it needs to be converted, generate a target configuration data packet adapted to the target device, and simultaneously generate a conversion execution log that records the adaptive processing process, and send the target configuration data packet and the conversion execution log to the target device together. The target device interacts with the user for confirmation based on the conversion execution log, and after receiving the user's confirmation instruction, applies the target configuration data packet to update the local configuration, including: The transformation execution log is parsed to extract the operation type, configuration parameter items of each adaptive operation, and details of the numerical or state changes before and after the operation. Based on the extracted details, a visual summary of the change confirmation is generated on the user interface in the form of a highlighted or contrasted list; Receive the exact instruction input by the user through the change confirmation summary interface, wherein the exact instruction is one of confirmation, cancellation or modification; In response to receiving a confirmation command from the user, the target configuration data packet is applied.

14. An ultrasonic device, characterized in that, It includes a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the ultrasonic device configuration synchronization method as described in any one of claims 1-4.

15. A cloud platform, characterized in that, It includes a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the ultrasonic device configuration synchronization method as described in any one of claims 5-11.

Images