A dental integrated treatment machine and its data synchronization method
By standardizing and mapping the data from dental comprehensive treatment machines across systems, and combining dynamic synchronization range and security strategies, the problems of data silos and synchronization delays in multi-system environments of dental comprehensive treatment machines are solved, achieving efficient and secure data synchronization.
Patent Information
- Application Number
- CN202611269520.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-20
- Publication Date
- 2026-11-17
AI Technical Summary
Existing data synchronization solutions for dental integrated treatment units suffer from problems such as data silos, formatting issues, synchronization delays, insufficient security, and a lack of dynamic sensing capabilities, making it difficult to meet the real-time data synchronization requirements in multi-system environments.
By standardizing the format and filtering redundant fields of the dental comprehensive treatment machine's diagnostic and treatment operation data, a standardized diagnostic and treatment data stream is generated. Fields are classified and attributes are labeled. Cross-system mapping is performed using data semantic alignment technology to generate a cross-system field mapping table. Hierarchical synchronization tasks are sorted, the synchronization range is dynamically adjusted, and a multi-channel parallel execution scheduling is adopted to achieve a secure and robust synchronization strategy.
It achieves efficient integration of data from multiple systems, reduces redundant data usage, improves the security and timeliness of data transmission, reduces synchronization delay and data leakage risks, and enhances the overall efficiency and stability of data synchronization.
Smart Images

Figure CN123120170A_ABST
Abstract
Description
Technical Field
[0001] This invention proposes a dental comprehensive treatment machine and its data synchronization method, belonging to the field of dental medical equipment data interaction technology. Background Technology
[0002] Dental treatment units are core equipment in clinical oral diagnosis and treatment, undertaking multiple functions such as oral examination, dental treatment, periodontal treatment, and oral surgery, and occupying an irreplaceable position in the modern oral healthcare system. As oral treatment technology continues to evolve towards refinement and intelligence, these units need to achieve deep data linkage with various hospital information systems, including hospital management systems, electronic medical record systems, image archiving and communication systems, and laboratory information systems. This requires real-time synchronization of multi-dimensional data such as patient basic information, treatment plans, oral imaging data, test results, and equipment operating parameters, thereby providing comprehensive data support for clinical diagnosis and treatment.
[0003] However, existing data synchronization solutions have significant shortcomings. Most treatment devices adopt a point-to-point, single-interaction mode, enabling only simple data interaction with a single system. This makes them ill-suited for the complex information environment of hospitals with multiple systems coexisting, easily leading to data silos. Furthermore, existing solutions lack intelligent adaptation capabilities, failing to automatically adjust synchronization strategies based on differences in data formats, transmission protocols, and update frequencies among different systems. This results in frequent issues such as data synchronization delays, format corruption, and missing content. In addition, existing synchronization mechanisms are weak in data verification, encrypted transmission, and fault tolerance, posing a high risk of data leakage, tampering, or synchronization interruption, failing to meet the stringent requirements of clinical diagnosis and treatment for data integrity and security. More critically, existing technologies lack dynamic perception capabilities for the treatment scenario, unable to adjust the scope of synchronized data in real time based on the patient's treatment stage and the doctor's operational needs. This creates a contradiction where redundant data occupies communication resources while critical data synchronization is untimely, hindering the effective implementation of intelligent diagnostic and treatment decisions. Summary of the Invention
[0004] This invention provides a dental comprehensive treatment machine and its data synchronization method to solve the problems mentioned in the background art above: This invention proposes a data synchronization method for a dental comprehensive treatment machine, the method comprising: S1. Collect and process the diagnostic and treatment operation data and equipment status data generated during the operation of the dental comprehensive treatment machine, standardize the format of the collected data and filter redundant fields to generate a standardized diagnostic and treatment data stream; perform field classification and attribute labeling processing on the standardized diagnostic and treatment data stream to generate a multi-attribute field feature set; S2. Perform cross-system mapping relationship analysis on the feature set of multi-attribute fields, and use data semantic alignment technology to associate and match the local data of the treatment machine with the data fields of the hospital management system and electronic medical record system to generate a cross-system field mapping table; evaluate the priority of synchronization needs on the cross-system field mapping table, and sort the synchronization tasks according to the urgency of diagnosis and treatment and the data update frequency to generate a hierarchical synchronization task sequence. S3. Perform transmission protocol adaptation processing on the hierarchical synchronization task sequence to generate protocol-adapted synchronization instructions; perform transmission channel optimization analysis on the protocol-adapted synchronization instructions to generate channel-matching transmission schemes. S4. Perform dynamic range definition processing on the channel matching transmission scheme, and adaptively adjust the data synchronization boundary of each target system in combination with the current diagnosis and treatment stage and the doctor's operation status to generate dynamic synchronization range data; perform security policy superposition processing on the dynamic synchronization range data to generate a security-enhanced synchronization strategy. S5. Perform resource scheduling preprocessing on the security hardening synchronization strategy, allocate independent transmission bandwidth and computing units to each synchronization task, and generate a resource allocation scheduling table; perform parallel execution scheduling on the resource allocation scheduling table to generate multi-channel synchronous parallel execution signals.
[0005] The comprehensive dental treatment machine proposed in this invention includes: One or more processors; Memory, used to store one or more programs; Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are made to implement the method described in any one of the above.
[0006] The beneficial effects of this invention are as follows: By classifying and semantically mapping clinical data at the field level, the treatment device can establish a unified data interaction channel with various hospital information systems such as hospital management systems and electronic medical record systems. This effectively breaks down the data silos between systems in the traditional point-to-point docking model, significantly improving the efficiency of multi-system data fusion. Simultaneously, the combination of adaptive transmission protocol adaptation and dynamic definition of synchronization range can automatically adjust the synchronization strategy according to the data format and update frequency of different systems. This avoids data format errors and content loss due to protocol incompatibility, and automatically shrinks or expands the synchronization boundary when the clinical scenario changes, reducing the ineffective occupation of communication resources by redundant data and lowering the probability of synchronization delays. At the security level, the superposition of hierarchical encryption and verification rules enhances the anti-tampering and anti-leakage capabilities of clinical data during transmission, avoiding clinical risks caused by synchronization interruptions or data tampering. Multi-channel parallel execution scheduling further improves the processing throughput in scenarios with large amounts of data synchronization, significantly improving the timeliness and completeness of data acquisition for doctors during the clinical process. Attached Figure Description
[0007] Figure 1 This is a diagram illustrating the steps of the method described in this invention; Figure 2 This is a detailed flowchart of step S2 in this invention. Detailed Implementation
[0008] The preferred embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.
[0009] One embodiment of the present invention, such as Figure 1 As shown, a data synchronization method for a dental comprehensive treatment machine includes: S1. Collect and process the diagnostic and treatment operation data and equipment status data generated during the operation of the dental comprehensive treatment machine, standardize the format of the collected data and filter redundant fields to generate a standardized diagnostic and treatment data stream; perform field classification and attribute labeling processing on the standardized diagnostic and treatment data stream, extract the patient identity field, treatment item field and equipment parameter field from the data, and generate a multi-attribute field feature set; S2. Perform cross-system mapping relationship analysis on the feature set of multi-attribute fields, and use data semantic alignment technology to associate and match the local data of the treatment machine with the data fields of the hospital management system and electronic medical record system to generate a cross-system field mapping table; evaluate the priority of synchronization needs on the cross-system field mapping table, and sort the synchronization tasks according to the urgency of diagnosis and treatment and the data update frequency to generate a hierarchical synchronization task sequence. S3. Perform transmission protocol adaptation processing on the hierarchical synchronization task sequence, transform the data interaction requirements between different systems into a unified synchronization command format, and generate protocol-adapted synchronization commands; perform transmission channel optimization analysis on the protocol-adapted synchronization commands, select transmission paths that match the current network environment from the preset wired and wireless transmission channels, and generate channel-matched transmission schemes. S4. Perform dynamic range definition processing on the channel matching transmission scheme, and adaptively adjust the data synchronization boundary of each target system in combination with the current diagnosis and treatment stage and the doctor's operation status to generate dynamic synchronization range data; perform security policy superposition processing on the dynamic synchronization range data, configure the corresponding encryption level and verification rules for diagnosis and treatment data of different security levels, and generate a security-strengthened synchronization strategy. S5. Perform resource scheduling preprocessing on the security hardening synchronization strategy, allocate independent transmission bandwidth and computing units to each synchronization task, and generate a resource allocation scheduling table; perform parallel execution scheduling on the resource allocation scheduling table to generate multi-channel synchronous parallel execution signals.
[0010] The working principle and effects of the above technical solution are as follows: By standardizing and precisely extracting fields from dental comprehensive treatment machine data, the regularity of data collection and organization is improved, reducing interference from invalid and redundant data in the synchronization process. Cross-system field semantic alignment and task hierarchical sorting optimize the adaptation effect of multi-system data synchronization, improving the orderliness and adaptability of cross-system data transmission. By unifying the transmission command format and dynamically optimizing the transmission channel, the data interaction needs under different network environments are adapted, reducing the probability of data transmission lag and failure. By adaptively adjusting the synchronization range and superimposing hierarchical security strategies, the security of data transmission is enhanced, reducing the risk of privacy data leakage. Through refined resource allocation and multi-channel parallel scheduling, the overall efficiency of multi-task data synchronization is improved, meeting the real-time synchronization needs of urgent medical data while ensuring the stable and orderly synchronization of routine archived data, avoiding resource contention, data corruption, and synchronization delays caused by concurrent multi-task operation.
[0011] In one embodiment of the present invention, S1 includes: S11. Deploy multi-channel distributed acquisition terminals to various functional module locations of the dental comprehensive treatment machine. The multi-channel distributed acquisition terminals continuously capture the equipment's dental drill operating parameters, air and water pressure parameters, and seat adjustment parameters to form the original equipment status message. Simultaneously, they collect patient registration information, dental treatment operation records, and consumable usage records to form the original treatment operation message. After summarizing the multiple original messages, they are sent to the protocol parsing and processing unit. The processing unit adapts the treatment machine's private communication protocol and the general serial port protocol to complete the message decomposition, stripping the protocol packet header check code and invalid padding code to generate the original parsed dataset. S12. The raw parsed dataset flows into the standardization conversion operation unit. The operation unit calls the preset data format conversion rules to unify the numerical measurement unit, date encoding format and character encoding type. The redundancy screening operation process is started simultaneously. The process traverses all field contents, filters out duplicate null value fields, redundant log fields generated in a loop, and temporary invalid fields generated by device self-test. After the redundant fields are removed, a standardized diagnosis and treatment data stream is generated. S13. The standardized diagnosis and treatment data flow enters the field splitting operation module. The module completes the splitting and classification of the full data according to the business dimension to which the data belongs. The splitting operation distinguishes three major data categories: patient basic information, clinical diagnosis and treatment execution, and hardware operation parameters. The storage attributes and business attributes of each category of data are marked line by line. After the full marking operation is completed, the initial version of the field summary data is generated. S14. The initial field summary data is sent to the feature extraction operation node. The node is configured with multi-dimensional feature capture logic to separate patient ID, name and age from the summary data to form a patient identity field cluster. It also separates items such as filling, root canal treatment and orthodontic treatment to form a treatment item field cluster. Finally, it separates motor power, water supply pressure and light power to form an equipment parameter field cluster. After the three types of field clusters are collected and organized, an intermediate field set is generated. S15. The intermediate field set undergoes field deduplication and feature completion operations, merging scattered fields from the same source, filling in missing field attribute information, removing abnormal fragments with disordered field formats, and generating a multi-attribute field feature set after the full operation is completed.
[0012] The working principle and effects of the above technical solution are as follows: By collecting raw messages from the operation and treatment processes of the equipment through multi-point distributed terminals, it can comprehensively capture the full-dimensional operation and treatment data of the dental comprehensive treatment machine, avoiding data omissions and partial collection problems caused by single-point collection. By unifying the data format and encoding and eliminating various redundant and invalid fields, the regularity and overall quality of the raw data are greatly improved, reducing the interference of invalid data on subsequent data processing. Through multi-dimensional data classification and attribute labeling, the treatment data and equipment data are finely divided, improving the regularity of data classification and organization. By selectively extracting different types of field clusters and completing field correction and completion, the integrity and standardization of the final output data can be guaranteed. This ensures the accurate collection of patient information and treatment project data, as well as the effective retention of equipment operating parameters, avoiding data disorder, missing data, and abnormal format problems from the source, and providing a high-quality data foundation for subsequent cross-system data synchronization.
[0013] One embodiment of the present invention, such as Figure 2 As shown, S2 includes: S21. Retrieve the underlying field library of the hospital management system and the underlying field library of the electronic medical record system. Simultaneously load the two types of system field libraries and multi-attribute field feature sets into the semantic computing engine. The engine traverses all field contents to extract the implicit business semantics, data value range and business usage scenario information of the fields. The full content is extracted and summarized to generate the third-party field semantic raw library. S22. The original semantic library of the third-party field starts cross-library association operation. The operation relies on the semantic similarity calculation logic to compare the semantic overlap between the local treatment machine field and the hospital's two types of system fields. Fields with semantic overlap meet the standard and automatically establish corresponding binding relationships. The binding information is entered into the blank mapping ledger one by one. After the ledger is continuously updated, the initial version of the cross-system field mapping table is generated. S23. The initial version of the cross-system field mapping table is sent to the mapping relationship verification unit. The unit verifies the data length, data type and business usage scenario matching degree of the bound fields group by group, disconnects the incorrect binding entries with mismatched scenarios and types, supplements the missing binding content of the same source fields, and generates the revised version of the cross-system field mapping table after the verification and rectification are completed. S24. The revised cross-system field mapping table is integrated into the synchronization priority calculation module. The module captures the diagnosis and treatment type and data change frequency parameters corresponding to each mapping field. Fields corresponding to emergency diagnosis and treatment are assigned high priority weights, fields for regular follow-up visits and archives are assigned medium priority weights, and fields for equipment idle self-checks are assigned low priority weights. After all weights are assigned, a priority weight dataset is generated. S25. The priority weight dataset enters the task sorting and processing unit. The unit rearranges all the tasks to be synchronized from high to low according to the weight values. Tasks with the same weight are then finely adjusted in order by changing the amount of data in bytes once. After sorting is completed, a hierarchical synchronization task sequence is generated.
[0014] The working principle and effects of the above technical solution are as follows: By comprehensively collecting and integrating semantic information of fields from multiple systems, the business adaptability characteristics of various types of data can be deeply explored, making the field association matching of different platforms more in line with actual diagnosis and treatment business. Cross-system field binding is completed through semantic similarity calculation, effectively improving the compatibility between dental treatment machine data and hospital management systems and electronic medical record systems, reducing data synchronization anomalies caused by field matching deviations. By verifying and correcting the generated mapping relationships item by item, erroneous binding content is eliminated and missing associations are filled, significantly improving the accuracy of cross-system field mapping and avoiding data connection errors. By assigning weights and multi-level sorting to synchronization tasks, differentiated task arrangements for different types of diagnosis and treatment data are achieved, ensuring priority synchronization of emergency diagnosis and treatment data while also balancing the orderly synchronization of routine archives and equipment data, significantly improving the overall rationality of data synchronization and business adaptability efficiency.
[0015] In one embodiment of the present invention, S25 includes: S251. The entire priority weight dataset is imported into the task sorting and processing unit. The processing unit reads the weight assignment parameters corresponding to each synchronous task in the dataset, performs hierarchical classification of all tasks to be synchronized, and divides the task items with different weight parameters into the corresponding priority task groups to generate multi-group task aggregation data. S252. The first round of sorting operation is started for the multi-group task collection data. The operation unit completes the forward sorting and arrangement according to the weight value. The high-weight emergency diagnosis and treatment synchronous task is arranged at the front of the task queue, the medium-weight follow-up archiving synchronous task is arranged in the middle of the queue, and the low-weight equipment self-test synchronous task is arranged at the end of the queue, generating the first round of hierarchical sorting task data. S253. The first round of hierarchical sorting task data filters out similar task items with the same weight value. The computing unit retrieves the single data change byte size parameter corresponding to the similar task and performs a second fine sorting on tasks with the same weight. Synchronous tasks with larger byte size are prioritized and arranged at the front, while synchronous tasks with smaller byte size are arranged at the back appropriately, generating secondary fine-tuning sorting task data. S254. The second fine-tuning sorting task data enters the queue compliance verification stage. The computing unit traverses the entire task arrangement order, checks for abnormal arrangement problems such as disordered arrangement of tasks with the same priority and the postponement of special diagnosis and treatment synchronous tasks, corrects the overall order of tasks that do not conform to the synchronous business logic, and generates compliant sorting task queue data. S255. The compliant sorting task queue data completes the overall standardization and sequence solidification of task items, unifies the queue number and execution order of all synchronous tasks, completes the sorting and finishing work of all tasks, and finally generates an ordered hierarchical synchronous task sequence.
[0016] The working principle and effects of the above technical solution are as follows: By classifying synchronization tasks hierarchically according to weight parameters, preliminary hierarchical management of various synchronization tasks can be achieved, improving the scheduling disorder caused by the mixed arrangement of messy tasks. The first round of hierarchical sorting is completed through weight values, allowing core emergency-related diagnostic and treatment data to participate in the synchronization process first, improving the timeliness of key diagnostic and treatment data synchronization. A second, fine-grained sorting of tasks with the same weight is completed by changing the byte size of the data, refining the task execution order and improving the overall precision and rationality of task arrangement. Compliance verification and deviation correction of the arrangement queue eliminate various abnormal arrangement problems and avoid delayed synchronization of special diagnostic and treatment tasks. By standardizing and solidifying the final task sequence and unifying task execution standards, it can ensure both efficient and priority synchronization of emergency diagnostic and treatment data and smooth, orderly synchronization of routine archived data and equipment data, reducing synchronization scheduling chaos and improving the overall stability and regularity of data synchronization scheduling.
[0017] In one embodiment of the present invention, S251 includes: Import the priority weight dataset into the built-in task sorting unit in batches. The unit reads all task weight parameters, task type identifiers and data update frequency information stored in the dataset to complete the batch parsing and reading of the full data and generate task weight parsing data. The parameter classification operation is performed on the task weight parsing data. The operation unit compares the weight value range of each synchronous task, distinguishes task individuals with different weight gradients of high, medium and low, and generates weight gradient classification data. The weighted gradient classification data is processed by item aggregation, which classifies and merges various synchronous diagnosis and treatment tasks and equipment parameter synchronization tasks with the same weight gradient to form multiple independent task sets and generate gradient aggregation raw data. The original gradient aggregation data is screened and cleaned for invalid entries, and erroneous data entries with missing weight parameters or abnormal task attributes are removed. The internal entry structure of each group of tasks is standardized to generate standardized grouped task data. The standardized grouped task data is labeled, integrated and encapsulated with group information, and the task content and attribute characteristics corresponding to each priority group are solidified, ultimately generating multi-group task aggregation data.
[0018] The working principle and effects of the above technical solution are as follows: By batch parsing various parameter information of synchronization tasks, the basic attributes and priority characteristics of all tasks to be synchronized can be fully grasped, providing a reliable data foundation for subsequent task grouping and processing. By dividing tasks into gradients based on weight value ranges, accurate differentiation of synchronization tasks of different importance can be achieved, making hierarchical task management more aligned with the needs of diagnosis and treatment. By grouping and merging tasks of the same gradient, scattered and disordered synchronization tasks can be formed into a regular task cluster, improving the overall efficiency of subsequent sorting and scheduling. By screening and cleaning up invalid task entries with missing parameters and abnormal attributes, the interference of abnormal data on task grouping results is reduced, avoiding the problem of grouping disorder. By solidifying the attribute characteristics of each group of tasks to complete data encapsulation, the uniformity and standardization of task grouping results can be guaranteed, and accurate and stable pre-data support can be provided for subsequent task ordering.
[0019] In one embodiment of the present invention, S3 includes: S31. The hierarchical synchronization task sequence is broken down into individual independent synchronization requirement segments. All requirement segments are sent to the protocol parsing and adaptation unit. The unit reads the communication protocol specification parameters of the target interface system one by one, captures the header format, data segmentation rules, and response receipt specification information of each protocol message, and summarizes all parameters to generate a multi-system protocol parameter resource pool. S32. The multi-system protocol parameter resource pool and a single independent synchronization requirement segment are adapted and converted. The calculation process converts the data encapsulation format of the differentiated protocol into a fixed segmented synchronization instruction format, fills in fixed fields such as target address, data length, and service identifier in the instruction one by one, and generates the initial version of the protocol adaptation synchronization instruction after batch encapsulation. S33. The initial version of the protocol adaptation and synchronization instructions enter the instruction compliance verification stage. The verification program checks the maximum number of bytes in a single instruction, the completeness of field filling, and the compliance of instruction identification. It truncates excessively long and invalid instructions, fills in missing field content, removes abnormal instructions with severely disordered formats that cannot be repaired, and generates compliant protocol adaptation and synchronization instructions after verification and adjustment. S34. Real-time collection of local area network latency parameters, wireless WiFi signal fluctuation parameters, and mobile private network packet loss rate parameters in the diagnosis and treatment department. The network parameters of multiple channels are summarized to generate a current environment network status dataset. The network status dataset is loaded into the channel filtering and calculation module. The module retrieves inherent parameters of the channel, such as the upper limit of wired link bandwidth and the maximum carrying rate of wireless link, for cross-comparison. S35. After the cross-comparison operation is completed, inferior transmission links that exceed the latency or packet loss rate limit are eliminated. The remaining available links are allocated to primary and secondary transmission links based on the data volume corresponding to the synchronization command. Large-volume synchronization tasks are paired with a wired primary link plus a wireless backup link, while small-volume real-time synchronization tasks use a single wireless link. The link pairing results are integrated to generate a channel matching transmission scheme.
[0020] The working principle and effects of the above technical solution are as follows: By decomposing hierarchical synchronization tasks and summarizing communication protocol parameters from multiple systems, it can fully adapt to the interaction standards of different hospital systems, eliminating data interaction barriers caused by differences in multi-system protocols. By unifying the instruction encapsulation format of various synchronization tasks, it improves the universality of cross-system data interaction and reduces data transmission failures caused by protocol incompatibility. By conducting compliance verification and adjustment on the initially generated synchronization instructions and cleaning up abnormal and invalid instructions, it improves the overall compliance and execution reliability of synchronization instructions and reduces the probability of instruction execution errors. By collecting multiple network status parameters in real time and comparing transmission channel performance, it can accurately select transmission paths suitable for the current scenario. By matching primary and secondary transmission links with data volume, it can ensure the stable transmission of large-capacity medical data while also accommodating the rapid synchronization of lightweight real-time data, effectively improving overall data synchronization efficiency and reducing synchronization lag and interruption problems caused by network fluctuations.
[0021] In one embodiment of the present invention, step S4 includes: S41. Real-time capture of the current operating status data of the dental comprehensive treatment machine, the treatment stage marker data, and the timing data of the doctor's operation console button operation. The three types of real-time data are summarized and stored in the synchronization boundary calculation database. The database synchronously retrieves the basic synchronization field list preset by each docking system. The list and the real-time operating status data are synchronously sent to the boundary calculation unit. S42. The boundary calculation unit dynamically expands and contracts the range of synchronized fields based on the changes in the diagnosis and treatment stages. During the admission and record-keeping stage, only the patient's basic identity fields are synchronized. During the intraoperative treatment stage, all diagnosis and treatment items and real-time equipment parameters are synchronized. During the follow-up visit and archiving stage, dynamic equipment instantaneous parameters are removed and only the treatment result data is retained. After the range is initially defined, a temporary synchronized boundary dataset is generated. S43. The temporary synchronization boundary dataset undergoes cross-system field permission verification and calculation. Combined with the system access permissions of medical staff in each department, the over-permission synchronization fields are trimmed. After trimming, the dynamic synchronization range data is obtained. S44. Retrieve the hospital's classification and confidentiality specification document for medical data, and extract the classification standards for three categories of confidentiality: general medical data, privacy-sensitive data, and high-risk medical confidential data from the specification document. Load the classification standards into the security configuration calculation unit, and match the asymmetric encryption algorithm, hash verification algorithm and cyclic redundancy check rule corresponding to different confidentiality levels to generate a security configuration resource library for confidentiality levels. S45. The security configuration resource library and the dynamic synchronization range data are bound one by one. Each type of field within the synchronization range is matched with the corresponding encryption algorithm and verification rules. The security configuration information attached to the synchronization field is integrated and summarized. The full binding operation is completed to generate a security hardening synchronization strategy.
[0022] The working principle and effects of the above technical solution are as follows: By collecting data related to equipment operating conditions, treatment stages, and operational sequences, and defining the synchronization scope based on a preset field list, the synchronized data content aligns with the on-site treatment rhythm, reducing the transmission of useless data. By dynamically adjusting the synchronization fields according to the treatment process, only the content required for the corresponding business flows at different stages, reducing the overall data transmission volume and alleviating the operational pressure on the transmission channel. By tailoring field content based on personnel access permissions, out-of-bounds data flow is blocked, avoiding unauthorized access to information. By classifying data security levels according to hospital standards and matching them with corresponding encryption and verification methods, the protection capabilities of treatment data during transmission are strengthened. By binding security rules and synchronization fields one by one, each type of data has an appropriate protection mechanism, ensuring both efficient flow of routine treatment data and robust protection for privacy and confidential data, reducing the risk of data leakage and content tampering, and making the data synchronization process both practical and secure.
[0023] In one embodiment of the present invention, S42 includes: The boundary computing unit receives real-time operating condition data and a list of basic synchronized fields synchronously sent in. It performs batch parsing and field classification and identification on the two types of input data, distinguishes synchronized fields such as patient identity, diagnosis and treatment operation, and equipment operation parameters, and generates a full dataset of fields to be screened. It then performs field attribute annotation processing on the full dataset of fields to be screened, marking the data update frequency and business synchronization attributes of each field, and generates an attribute-annotated field dataset. Match the attribute-annotated field dataset with the current business operation status of the patient registration stage, filter patient identity fields that are suitable for basic information registration business, block treatment operation fields and equipment dynamic parameter fields, complete the initial interception and filtering of low matching degree fields, and generate field data suitable for the registration stage. Match the attribute-annotated field dataset to the current operational status of the intraoperative treatment stage, grant synchronization permissions to all treatment execution fields and real-time equipment operating parameter fields, retain real-time business data such as surgical operation records and equipment operating parameters, and generate intraoperative stage-adaptive field data; Match the attribute-annotated field dataset with the current business operation status of the follow-up examination archiving stage, filter out dynamic invalid fields such as instantaneous fluctuation parameters of equipment and temporary working condition data, retain the fixed diagnosis and treatment result fields and patient follow-up examination record fields, and generate field data adapted for the archiving stage; The data of the corresponding adaptive fields for different stages of diagnosis and treatment are summarized, integrated and boundary-gathered to unify the coverage of the synchronous fields in each stage, and to complete the dynamic expansion and contraction adjustment of the synchronous field range in the whole scenario. After the range delineation is completed, a temporary synchronous boundary dataset is generated.
[0024] The working principle and effects of the above technical solution are as follows: By analyzing and identifying various synchronization fields and labeling their corresponding attributes, the application scenarios and update characteristics of different data can be clearly defined, laying a solid foundation for phased data filtering. By combining the business status of patient registration and file creation to filter corresponding fields, only basic patient information is transmitted, reducing the consumption of transmission resources by irrelevant data. By matching the intraoperative treatment status to open all diagnosis and treatment and equipment parameters, the complete synchronization of on-site operation-related data is ensured, meeting the real-time usage needs of the diagnosis and treatment process. By removing temporary dynamic data for follow-up visits and archiving, only valid result information is retained, making the archived content more concise and standardized. Integrating fields from each stage to form a unified boundary allows the data synchronization scope to change flexibly with the diagnosis and treatment process, ensuring accurate transmission of data required at different stages while simplifying transmission content, reducing network load, and avoiding channel congestion and decreased synchronization efficiency caused by the continuous flow of redundant data.
[0025] In one embodiment of the present invention, step S5 includes: S51. Read the data transmission volume, single synchronization time estimation parameters, and target docking system concurrent capacity limit parameters of all synchronization tasks within the security hardening synchronization strategy. Collect multiple parameters to generate a detailed dataset of synchronization task resource requirements. Send the detailed dataset to the hardware resource statistics module. S52, the hardware resource statistics module takes real-time inventory of the number of idle computing cores on the server, the size of idle transmission bandwidth in partitions, and the remaining temporary cache storage space. The hardware idle resource data obtained from the inventory is matched with the resource requirement dataset of the synchronization task to perform supply and demand matching calculations, and prioritizes reserving sufficient bandwidth and computing cores for high-priority synchronization tasks. S53. After the supply and demand matching operation is completed, a single task-specific resource allocation entry is generated. All entries are summarized and arranged in order according to the task number. Abnormal content such as over-allocation of resources and resource reservation gaps in the entries is checked and corrected. After the correction process is completed, the initial version of the resource allocation scheduling table is generated. S54. The initial version of the resource allocation and scheduling table is connected to the parallel scheduling and computing core. The computing core splits the full synchronous tasks into multiple groups of parallel tasks that do not compete for resources. Tasks within the same group are executed in time based on the allocated resources. Tasks across groups start a multi-way parallel running mode. The group arrangement is completed and task parallel arrangement data is generated. S55. The parallel task data is converted into control signals in level-coded format. Different transmission channels correspond to independently coded execution signals. After all channels are collected, multi-channel synchronous parallel execution signals are generated.
[0026] The working principle and effects of the above technical solution are as follows: By summarizing the various operating parameters of the synchronization tasks, the actual consumption of hardware resources by each task can be fully grasped, providing a real reference for resource allocation. By real-time statistics of hardware idle status and completion of supply and demand matching, priority is given to ensuring resource supply for important tasks, improving the processing speed of core diagnostic data. By checking resource allocation content item by item and correcting various anomalies, resource waste and uneven distribution are reduced, allowing hardware capabilities to be fully utilized. By dividing the tasks into independent groups and combining time-sharing and parallel operation modes, the resource contention problem caused by multiple tasks running simultaneously is resolved. By converting and generating dedicated control signals to drive the operation of each channel, the overall execution process is made smoother and more stable, capable of handling a large number of simultaneous synchronization tasks while maintaining stable operation of the equipment for a long time, avoiding system lag and task interruption caused by multi-task concurrency, and improving the overall efficiency and stability of data synchronization.
[0027] In one embodiment of the present invention, S52 includes: The hardware resource statistics module initiates a full-domain hardware status scan, sequentially collecting the number of idle computing cores in each computing unit of the server, the remaining transmission bandwidth of the network partition, and the available storage space in the local temporary cache area. The collected hardware status information is integrated and summarized to generate raw data on idle hardware resources. The raw data on idle hardware resources is then numerically calibrated and marked with status, and abnormal sampled values caused by instantaneous fluctuations are removed to generate standardized data on idle hardware resources. The standardized hardware idle resource data and the synchronous task resource requirement details dataset are synchronously imported into the resource matching calculation unit. The calculation unit extracts the resource usage indicators corresponding to each synchronous task, completes the item-by-item comparison between task requirement parameters and hardware margin parameters, and generates preliminary resource comparison result data. The initial resource comparison results are used to classify task priority levels, and high-priority synchronization tasks are selected from the top of the ranking. Dedicated resource occupation intervals are defined for these tasks, and high-priority task resource reservation planning data is generated after the division is completed. According to the high-priority task resource reservation planning data, the corresponding computing kernel and transmission bandwidth resources are locked, the hardware resource reservation operation is completed, and the remaining hardware capacity is allocated to medium and low priority synchronization tasks to complete the initial resource matching of all tasks and generate intermediate resource matching data. Perform global resource usage verification on intermediate data for resource matching, balance the resource allocation ratio between different tasks, avoid excessive concentration of a single type of resource, complete the overall supply and demand matching process, and form a complete task hardware matching result.
[0028] The working principle and effects of the above technical solution are as follows: By scanning and collecting the remaining resources of various hardware resources on the server and calibrating and filtering them, erroneous data caused by sampling fluctuations can be removed, ensuring the accuracy and reliability of hardware resource statistics and providing a precise basis for resource allocation. By comparing the resource requirements of each task with the hardware reserves, resource allocation is made to fit the actual operational needs of each synchronization task. By separately allocating dedicated resource ranges for high-priority tasks and locking resources in advance, resource shortages are prevented during the synchronization of emergency medical data. By rationally allocating remaining resources to medium and low-priority tasks, full coverage utilization of hardware resources is achieved. By globally verifying and balancing the resource ratio of various tasks, the stuttering and delay problems of other tasks caused by excessive resource consumption by a single task are avoided. This approach can not only ensure the efficient and stable operation of core synchronization tasks, but also fully utilize idle system resources, reduce resource waste, and effectively improve the overall operational stability in multi-task synchronization scenarios.
[0029] In one embodiment of the present invention, S54 includes: The initial version of the resource allocation scheduling table is fully integrated into the parallel scheduling operation core. The operation core reads the resource usage parameters, task execution duration parameters, and channel usage parameters of all synchronous tasks inside the scheduling table, completes the batch parsing and collection of all task resource configuration information, and generates task resource configuration parsing data. It performs resource usage conflict pre-detection on the task resource configuration parsing data, screens out resource overlap issues between tasks, and generates conflict-free task raw data. The original data of conflict-free tasks is split into clusters and divided into independent task units according to the transmission channel and computing resource type of the task. The overall synchronous task is decomposed into multiple resource-isolated task clusters, and each task cluster has its own corresponding hardware resources to generate parallel task grouping original data. Configure execution rules within the group for the original data of parallel tasks, and give multiple synchronous tasks in the same group a time-sharing execution mechanism to control the tasks in the group to occupy the corresponding resources in turn to complete the data synchronization operation, avoid the problem of resource contention among tasks in the group, and generate time-sharing execution configuration data within the group. Configure a cross-group parallel operation mechanism for multiple parallel task clusters, grant synchronous execution permissions to different task groups, and allow multiple task clusters to synchronously carry out data transmission operations in an independent resource environment, generating cross-group parallel scheduling configuration data. Integrate the time-sharing execution configuration data within the group with the parallel scheduling configuration data across groups, solidify the execution arrangement rules and operating modes of all synchronous tasks, complete the parallel arrangement optimization processing of all synchronous tasks, and generate the final task parallel arrangement data.
[0030] The working principle and effects of the above technical solution are as follows: By batch parsing the resource configuration information of synchronization tasks and checking for resource conflicts in advance, potential risks of parallel task execution can be eliminated in advance, reducing the probability of anomalies during multi-task synchronous execution. By splitting tasks into isolated task clusters according to resource type, each group of tasks has independent operating conditions, eliminating resource interference between different clusters. By setting up a time-sharing execution mechanism within a group, the execution rhythm of multiple tasks in the same group is smoothly guided, reducing synchronization stuttering and execution failures caused by task contention. By enabling cross-group parallel operation mode, the overall throughput speed of multi-task synchronous processing is significantly improved. This operational arrangement can ensure that tasks within a single group complete data synchronization in an orderly manner, while also supporting multiple groups of tasks to carry out transmission operations simultaneously, fully releasing the operating performance of the system hardware, avoiding the accumulation and blockage of a large number of synchronization tasks, and effectively improving the overall execution efficiency and operational stability of multi-channel synchronization of dental treatment data.
[0031] According to one embodiment of the present invention, a dental comprehensive treatment machine includes: One or more processors; Memory, used to store one or more programs; Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are made to implement the method described in any one of the above.
[0032] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.
Claims
1. A data synchronization method for a dental comprehensive treatment machine, characterized in that, The method includes: S1. Collect and process the diagnostic and treatment operation data and equipment status data generated during the operation of the dental comprehensive treatment machine, standardize the format of the collected data and filter redundant fields to generate a standardized diagnostic and treatment data stream; perform field classification and attribute labeling processing on the standardized diagnostic and treatment data stream to generate a multi-attribute field feature set; S2. Perform cross-system mapping relationship analysis on the feature set of multi-attribute fields, and use data semantic alignment technology to associate and match the local data of the treatment machine with the data fields of the hospital management system and electronic medical record system to generate a cross-system field mapping table; evaluate the synchronization requirement priority of the cross-system field mapping table, and sort the synchronization tasks according to the urgency of diagnosis and treatment and the data update frequency to generate a hierarchical synchronization task sequence. S3. Perform transmission protocol adaptation processing on the hierarchical synchronization task sequence to generate protocol-adapted synchronization instructions; perform transmission channel optimization analysis on the protocol-adapted synchronization instructions to generate channel-matching transmission schemes. S4. Perform dynamic range definition processing on the channel matching transmission scheme, and adaptively adjust the data synchronization boundary of each target system in combination with the current diagnosis and treatment stage and the doctor's operation status to generate dynamic synchronization range data; perform security policy superposition processing on the dynamic synchronization range data to generate a security-enhanced synchronization strategy. S5. Perform resource scheduling preprocessing on the security hardening synchronization strategy, allocate independent transmission bandwidth and computing units to each synchronization task, and generate a resource allocation scheduling table; perform parallel execution scheduling on the resource allocation scheduling table to generate multi-channel synchronous parallel execution signals.
2. The data synchronization method for a dental comprehensive treatment machine according to claim 1, characterized in that, S1 includes: S11. The multi-channel distributed acquisition terminal continuously captures the equipment's dental drill operating parameters, air and water pressure parameters, and seat adjustment parameters to form the original equipment status message. It also simultaneously collects patient registration information, dental treatment operation records, and consumable usage records to form the original treatment operation message. After the multiple original messages are aggregated, they are sent to the protocol parsing and processing unit. The processing unit adapts the treatment machine's private communication protocol and the general serial port protocol to complete the message decomposition, strips off the protocol packet header check code and invalid padding code, and generates the original parsed dataset. S12. The raw parsed dataset flows into the standardization conversion operation unit. The operation unit calls the preset data format conversion rules to unify the numerical measurement unit, date encoding format and character encoding type, and simultaneously starts the redundant screening operation process. The process traverses the content of all fields to generate a standardized diagnosis and treatment data stream. S13. The standardized diagnosis and treatment data flow enters the field splitting operation module, which completes the splitting and classification of all data according to the business dimension to which the data belongs. The splitting operation distinguishes three major data categories: patient basic information, clinical diagnosis and treatment execution, and hardware operation parameters. The storage attributes and business attributes of each category of data are marked line by line. After the full annotation operation is completed, the initial version of the field summary data is generated. S14. The initial field summary data is sent to the feature extraction operation node. The node is configured with multi-dimensional feature capture logic to separate the patient ID, name and age from the summary data to form a patient identity field cluster, separate the items to form a treatment item field cluster, and separate the motor power, water supply pressure and light power to form an equipment parameter field cluster. After the three types of field clusters are collected and organized, an intermediate field set is generated. S15. The intermediate field set undergoes field deduplication and feature completion operations, merging scattered fields from the same source and filling in missing field attribute information. After the full operation is completed, a multi-attribute field feature set is generated.
3. The data synchronization method for a dental comprehensive treatment machine according to claim 1, characterized in that, S2 includes: S21. Retrieve the underlying field library of the hospital management system and the underlying field library of the electronic medical record system. Simultaneously load the two types of system field libraries and multi-attribute field feature sets into the semantic computing engine. The engine traverses all field contents to extract the implicit business semantics, data value range and business usage scenario information of the fields. The full content is extracted and summarized to generate the third-party field semantic raw library. S22. The original semantic library of the third-party field starts cross-library association operation. The operation relies on the semantic similarity calculation logic to compare the semantic overlap between the local treatment machine field and the hospital's two types of system fields. Fields with semantic overlap meet the standard and automatically establish corresponding binding relationships. The binding information is entered into the blank mapping ledger one by one. After the ledger is continuously updated, the initial version of the cross-system field mapping table is generated. S23. The initial version of the cross-system field mapping table is sent to the mapping relationship verification unit. The unit verifies the data length, data type and business usage scenario matching degree of the bound fields group by group, disconnects the incorrect binding entries with mismatched scenarios and types, supplements the missing binding content of the same source fields, and generates the revised version of the cross-system field mapping table after the verification and rectification are completed. S24. The revised cross-system field mapping table is integrated into the synchronization priority calculation module. The module captures the diagnosis and treatment type and data change frequency parameters corresponding to each mapping field. Fields corresponding to emergency diagnosis and treatment are assigned high priority weights, fields for regular follow-up visits and archives are assigned medium priority weights, and fields for equipment idle self-checks are assigned low priority weights. After all weights are assigned, a priority weight dataset is generated. S25. The priority weight dataset enters the task sorting and processing unit. The unit rearranges all the tasks to be synchronized from high to low according to the weight values. Tasks with the same weight are then finely adjusted in order by changing the amount of data in bytes once. After sorting is completed, a hierarchical synchronization task sequence is generated.
4. The data synchronization method for a dental comprehensive treatment machine according to claim 3, characterized in that, The S25 includes: S251. The entire priority weight dataset is imported into the task sorting and processing unit. The processing unit reads the weight assignment parameters corresponding to each synchronous task in the dataset, performs hierarchical classification of all tasks to be synchronized, and divides the task items with different weight parameters into the corresponding priority task groups to generate multi-group task aggregation data. S252. The first round of sorting operation is started for the multi-group task collection data. The operation unit completes the forward sorting and arrangement according to the weight value. The high-weight emergency diagnosis and treatment synchronous task is arranged at the front of the task queue, the medium-weight follow-up archiving synchronous task is arranged in the middle of the queue, and the low-weight equipment self-test synchronous task is arranged at the end of the queue, generating the first round of hierarchical sorting task data. S253. The first round of hierarchical sorting task data filters out similar task items with the same weight value. The computing unit retrieves the single data change byte size parameter corresponding to the similar task and performs a second fine sorting on tasks with the same weight. Synchronous tasks with larger byte size are prioritized and arranged at the front, while synchronous tasks with smaller byte size are arranged at the back appropriately, generating secondary fine-tuning sorting task data. S254. The second fine-tuning sorting task data enters the queue compliance verification stage. The computing unit traverses the entire task arrangement order, checks for abnormal arrangement problems such as disordered arrangement of tasks with the same priority and the postponement of special diagnosis and treatment synchronous tasks, corrects the overall order of tasks that do not conform to the synchronous business logic, and generates compliant sorting task queue data. S255. The compliant sorting task queue data completes the overall standardization and sequence solidification of task items, unifies the queue number and execution order of all synchronous tasks, completes the sorting and finishing work of all tasks, and finally generates an ordered hierarchical synchronous task sequence.
5. The data synchronization method for a dental comprehensive treatment machine according to claim 4, characterized in that, S251 includes: Import the priority weight dataset into the built-in task sorting unit in batches. The unit reads all task weight parameters, task type identifiers and data update frequency information stored in the dataset to complete the batch parsing and reading of the full data and generate task weight parsing data. The parameter classification operation is performed on the task weight parsing data. The operation unit compares the weight value range of each synchronous task, distinguishes task individuals with different weight gradients of high, medium and low, and generates weight gradient classification data. The weighted gradient classification data is processed by item aggregation, which classifies and merges various synchronous diagnosis and treatment tasks and equipment parameter synchronization tasks with the same weight gradient to form multiple independent task sets and generate gradient aggregation raw data. The original gradient aggregation data is screened and cleaned for invalid entries, and erroneous data entries with missing weight parameters or abnormal task attributes are removed. The internal entry structure of each group of tasks is standardized to generate standardized grouped task data. The standardized grouped task data is labeled, integrated, and encapsulated with group information, and the task content and attribute characteristics corresponding to each priority group are solidified, ultimately generating multi-group task aggregation data.
6. The data synchronization method for a dental comprehensive treatment machine according to claim 1, characterized in that, The S3 includes: S31. The hierarchical synchronization task sequence is broken down into individual independent synchronization requirement segments. All requirement segments are sent to the protocol parsing and adaptation unit. The unit reads the communication protocol specification parameters of the target interface system one by one, captures the header format, data segmentation rules, and response receipt specification information of each protocol message, and summarizes all parameters to generate a multi-system protocol parameter resource pool. S32. The multi-system protocol parameter resource pool and a single independent synchronization requirement segment are adapted and converted. The calculation process converts the data encapsulation format of the differentiated protocol into a fixed segmented synchronization instruction format, fills in the fixed fields in the instruction one by one, and batch encapsulates to generate the initial version of the protocol adaptation synchronization instruction. S33. The initial version of the protocol adaptation and synchronization instruction enters the instruction compliance verification stage. After verification and adjustment, a compliant protocol adaptation and synchronization instruction is generated. S34. Real-time collection of local area network latency parameters, wireless WiFi signal fluctuation parameters, and mobile private network packet loss rate parameters in the diagnosis and treatment department. The network parameters of multiple channels are summarized to generate a current environment network status dataset. The network status dataset is loaded into the channel filtering and calculation module, and the module retrieves the inherent parameters of the channel for cross-comparison. S35. After the cross-comparison operation is completed, inferior transmission links that exceed the latency or packet loss rate limit are eliminated. The remaining available links are allocated to primary and secondary transmission links based on the data volume corresponding to the synchronization command. Large-volume synchronization tasks are paired with a wired primary link plus a wireless backup link, while small-volume real-time synchronization tasks use a single wireless link. The link pairing results are integrated to generate a channel matching transmission scheme.
7. The data synchronization method for a dental comprehensive treatment machine according to claim 1, characterized in that, The S4 includes: S41. Real-time capture of the current operating status data of the dental comprehensive treatment machine, the treatment stage marker data, and the timing data of the doctor's operation console button operation. The three types of real-time data are summarized and stored in the synchronization boundary calculation database. The database synchronously retrieves the basic synchronization field list preset by each docking system. The list and the real-time operating status data are synchronously sent to the boundary calculation unit. S42. The boundary calculation unit dynamically expands and contracts the range of synchronized fields based on the changes in the diagnosis and treatment stages. During the admission and record-keeping stage, only the patient's basic identity fields are synchronized. During the intraoperative treatment stage, all diagnosis and treatment items and real-time equipment parameters are synchronized. During the follow-up visit and archiving stage, dynamic equipment instantaneous parameters are removed and only the treatment result data is retained. After the range is initially defined, a temporary synchronized boundary dataset is generated. S43. The temporary synchronization boundary dataset undergoes cross-system field permission verification and calculation. Combined with the system access permissions of medical staff in each department, the over-permission synchronization fields are trimmed. After trimming, the dynamic synchronization range data is obtained. S44. Retrieve the hospital's classification and confidentiality specification document for medical data, and extract the classification standards for three categories of confidentiality: general medical data, privacy-sensitive data, and high-risk medical confidential data from the specification document. Load the classification standards into the security configuration calculation unit, and match the asymmetric encryption algorithm, hash verification algorithm and cyclic redundancy check rule corresponding to different confidentiality levels to generate a security configuration resource library for confidentiality levels. S45. The security configuration resource library and the dynamic synchronization range data are bound one by one. Each type of field within the synchronization range is matched with the corresponding encryption algorithm and verification rules. The security configuration information attached to the synchronization field is integrated and summarized. The full binding operation is completed to generate a security hardening synchronization strategy.
8. The data synchronization method for a dental comprehensive treatment machine according to claim 1, characterized in that, The S5 includes: S51. Read the data transmission volume, single synchronization time estimation parameters, and target docking system concurrent capacity limit parameters of all synchronization tasks within the security hardening synchronization strategy. Collect multiple parameters to generate a detailed dataset of synchronization task resource requirements. Send the detailed dataset to the hardware resource statistics module. S52, the hardware resource statistics module takes real-time inventory of the number of idle computing cores on the server, the size of idle transmission bandwidth in partitions, and the remaining temporary cache storage space. The hardware idle resource data obtained from the inventory is matched with the resource requirement dataset of the synchronization task to perform supply and demand matching calculations, and prioritizes reserving sufficient bandwidth and computing cores for high-priority synchronization tasks. S53. After the supply and demand matching operation is completed, a single task-specific resource allocation entry is generated. All entries are summarized and arranged in order according to the task number. Abnormal content such as over-allocation of resources and resource reservation gaps in the entries is checked and corrected. After the correction process is completed, the initial version of the resource allocation scheduling table is generated. S54. The initial version of the resource allocation and scheduling table is connected to the parallel scheduling and computing core. The computing core splits the full synchronous tasks into multiple groups of parallel tasks that do not compete for resources. Tasks within the same group are executed in time based on the allocated resources. Tasks across groups start a multi-way parallel running mode. The group arrangement is completed and task parallel arrangement data is generated. S55. The parallel task data is converted into control signals in level-coded format. Different transmission channels correspond to independently coded execution signals. After all channels are collected, multi-channel synchronous parallel execution signals are generated.
9. The data synchronization method for a dental comprehensive treatment machine according to claim 8, characterized in that, S52 includes: The hardware resource statistics module initiates a full-domain hardware status scan, sequentially collecting the number of idle computing cores in each computing unit of the server, the remaining transmission bandwidth of the network partition, and the available storage space in the local temporary cache area. The collected hardware status information is integrated and summarized to generate raw data on idle hardware resources. The raw data on idle hardware resources is then numerically calibrated and marked with status, and abnormal sampled values caused by instantaneous fluctuations are removed to generate standardized data on idle hardware resources. The standardized hardware idle resource data and the synchronous task resource requirement details dataset are synchronously imported into the resource matching calculation unit. The calculation unit extracts the resource usage indicators corresponding to each synchronous task, completes the item-by-item comparison between task requirement parameters and hardware margin parameters, and generates preliminary resource comparison result data. The initial resource comparison results are used to classify task priority levels, and high-priority synchronization tasks are selected from the top of the ranking. Dedicated resource occupation intervals are defined for these tasks, and high-priority task resource reservation planning data is generated after the division is completed. According to the high-priority task resource reservation planning data, the corresponding computing kernel and transmission bandwidth resources are locked, the hardware resource reservation operation is completed, and the remaining hardware capacity is allocated to medium and low priority synchronization tasks to complete the initial resource matching of all tasks and generate intermediate resource matching data. Perform global resource usage verification on intermediate data for resource matching, balance the resource allocation ratio between different tasks, avoid excessive concentration of a single type of resource, complete the overall supply and demand matching process, and form a complete task hardware matching result.
10. A dental comprehensive treatment machine, characterized in that, The dental comprehensive treatment machine includes: One or more processors; Memory, used to store one or more programs; Wherein, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1 to 9.
