A method for intelligent driver compatibility across operating systems

Abstract

The application relates to the field of driving compatibility processing, in particular to an intelligent driving compatibility method for cross operating systems, which comprises the following steps: determining whether to perform compatibility cache analysis and stage cache analysis on each driving operation device according to a bandwidth execution index and an associated reference bandwidth index; when performing the compatibility cache analysis, determining a compatibility execution risk coefficient of each compatible optimization driver of the driving operation device based on a stage exception index or a reference clustering fluctuation index, so as to determine whether to perform compatibility update cache on a compatible optimization resource set of the compatible optimization driver; when performing the stage cache analysis, determining whether to perform combined calling loading or direct calling loading based on an associated resource correlation index, so as to periodically perform cache loading on data corresponding to driving update and compatible performance repair. The application can guarantee the normal work efficiency of devices corresponding to each operating system, and improve the supervision quality of the driving compatibility performance of each device.

Description

Technical Field

[0001] This invention relates to the field of driver compatibility processing, and more particularly to a smart driver compatibility method for cross-operating systems. Background Technology

[0002] In large-scale industrial production processes, there are often situations where devices with mixed operating systems operate together. The actual compatibility requirements of the drivers for devices using different operating systems vary. The drivers used in practice need to meet the compatibility requirements of the corresponding devices. However, different drivers used in actual operation may also be updated. For large-scale industrial operation scenarios, monitoring and managing the compatibility of each device with the drivers they use generates a large data analysis burden and affects the bandwidth usage of the actual operation process. Therefore, how to ensure the quality of monitoring and management of the driver compatibility of each device while ensuring the normal operation of each device is a problem that urgently needs to be solved by those skilled in the art.

[0003] Chinese patent application publication number CN120578429A discloses a hardware driver method supporting multiple operating systems. The method divides the driver into a device layer and a connection layer. The device layer includes the corresponding logic for operating the hardware, and the connection layer includes adaptation code for the corresponding operating system. Specifically, the method includes: Step 1: Constructing the device layer, organizing the same functions for devices of the same type, abstracting them into a device type model, and designing a cross-platform unified interface specification based on the hardware functions. The unified interface specification includes multiple types of interfaces. Step 2: Implementing specific functions based on the cross-platform unified interface specification designed in Step 1. Step 3: Creating the connection layer. Step 4: Implementing the upper-layer operating system's operation on the device in the connection layer. This invention unifies the handling of asynchronous and synchronous modes for driver development, reducing development costs. However, the above solution has the following drawbacks: it fails to specifically monitor the compatibility of the drivers used based on the actual application status of each operating device, resulting in the inability to guarantee the quality of monitoring the actual compatibility performance of the drivers while ensuring the operating efficiency of the actual devices. Summary of the Invention

[0004] To address this issue, the present invention provides an intelligent driver compatibility method for cross-operating systems, which overcomes the problem that existing technologies fail to monitor the compatibility of drivers based on the actual application status of each operating device, resulting in the inability to guarantee the quality of monitoring the actual compatibility performance of drivers while ensuring the operating efficiency of the actual devices.

[0005] To achieve the above objectives, the present invention provides a smart driver compatibility method for cross-operating system use, comprising:

[0006] The operation status of each driver operating device is determined based on the bandwidth execution index and the associated reference bandwidth index, and the compatibility cache analysis and stage cache analysis are determined based on the operation status.

[0007] When performing compatibility cache analysis, the compatibility execution risk coefficient of each compatible optimization driver of the driving equipment in the second-class operation state is determined based on the stage anomaly index or the reference clustering fluctuation index. Based on the compatibility execution risk coefficient, it is determined whether to perform compatibility update cache for the compatibility optimization resource set of the compatible optimization driver based on the execution trigger parameters and execution coordination parameters.

[0008] When performing phased cache analysis, based on the relevant index of associated resources, it is determined whether to perform combined call loading or direct call loading for each driver running device in a certain job running state, so as to periodically cache and load the data corresponding to driver updates and compatibility performance repairs.

[0009] Furthermore, the operating status of the drive and operation equipment includes a first-class operating status and a second-class operating status;

[0010] The driving operation device in the aforementioned type of operation state is a driving operation device whose bandwidth execution index is less than or equal to the preset bandwidth execution index and whose associated reference bandwidth index is less than or equal to the preset associated reference bandwidth index.

[0011] The driving operation equipment in the second type of operation state is the driving operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index or whose associated reference bandwidth index is greater than the preset associated reference bandwidth index.

[0012] Furthermore, the associated reference bandwidth index of any of the driving operation devices is determined based on the bandwidth execution index of each driving operation device in the update association set corresponding to that driving operation device;

[0013] The update association set is determined based on the driver compatibility processing time of each driver-running device.

[0014] Furthermore, a compatibility cache analysis was performed on the drive-operated equipment in the second-class operation state, among which...

[0015] Periodically check the compatibility execution risk coefficient of each compatible and optimized driver used by the driving device to determine whether to update the cache for each compatible and optimized driver.

[0016] The method for setting the compatibility execution risk coefficient of any of the aforementioned compatibility optimization drivers is determined based on the bandwidth execution index of the device on which the driver runs.

[0017] Furthermore, based on the change phase analysis, a compatibility risk analysis is performed on the drive operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index, and the compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the phase abnormality index;

[0018] The stage anomaly index is determined based on the trend evaluation index of each compatibility optimization-driven change response stage.

[0019] Furthermore, based on association clustering analysis, a compatibility risk analysis is performed on the drive operation equipment whose bandwidth execution index is less than or equal to the preset bandwidth execution index, and the compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the reference clustering fluctuation index.

[0020] The reference clustering volatility index is determined based on the trend evaluation index of each compatibility optimization-driven change response phase.

[0021] Furthermore, for compatibility optimization drivers with a compatibility execution risk coefficient greater than the preset compatibility execution risk coefficient, a compatibility update cache is performed, and the compatibility optimization resource set of the compatibility optimization driver is pre-cached and loaded based on the execution trigger parameters and execution coordination parameters;

[0022] The execution trigger parameters and execution coordination parameters during the pre-caching loading process are determined based on the compatibility execution risk coefficient, and the execution trigger parameters and execution coordination parameters are positively correlated with the compatibility execution risk coefficient.

[0023] Furthermore, stage cache analysis is performed on the driving devices that are in a certain type of operation state, and the related resource indices of the driving devices are detected to determine whether to perform combined call loading for the driving devices.

[0024] The associated resource-related index is determined based on the update execution driver corresponding to each driving device.

[0025] Furthermore, for drive-running devices whose related resource correlation index is greater than the preset related resource correlation index, combined invocation and loading are performed;

[0026] The combined invocation gateway for each relevant execution driver is determined based on the reference invocation interval index. The combined invocation gateway for any relevant execution driver is the gateway with the smallest reference invocation interval index for that relevant execution driver.

[0027] Furthermore, for cases where the related resource index is less than or equal to the preset related resource index, or for cases where the combined loading is completed, the driver running device is directly loaded.

[0028] The target invocation gateway for each direct execution driver is determined based on the invocation interval index. The target invocation gateway for any direct execution driver is the gateway with the smallest invocation interval index for that direct execution driver.

[0029] Compared with the prior art, the beneficial effects of the present invention are that the technical solution of the present invention periodically evaluates the bandwidth conditions of each existing driver running device, determines the operation status of each driver running device based on the bandwidth execution index and the associated reference bandwidth index, and determines whether to perform compatibility cache analysis and stage cache analysis for each driver running device based on the operation status. This makes the monitoring method of driver compatibility of each driver running device more in line with the actual operation situation. The present invention improves the quality of monitoring the driver compatibility performance of each device without affecting the normal operation efficiency of the devices corresponding to each operating system.

[0030] Furthermore, in this invention, the operating status of each driving device is determined based on the bandwidth execution index and the associated reference bandwidth index. The bandwidth execution index and the associated reference bandwidth index characterize the available bandwidth of the driving device itself and the available bandwidth of each driving device in the updated associated set. This indicates whether each driving device has sufficient bandwidth resources for the transmission of monitoring and analysis data of driving compatibility during actual operation. This avoids the monitoring and analysis process of driving compatibility affecting the normal operation of the equipment. This invention reduces the impact of the driving compatibility monitoring process on the working efficiency of the equipment.

[0031] Furthermore, this invention performs compatibility caching analysis on drive-running devices in the second-class operation state. Since the available bandwidth of such drive-running devices is large, or the available bandwidth of each drive-running device in the update association set is large, targeted risk analysis can be performed on the compatibility optimization driver with actual version update requirements to determine whether it is necessary to pre-cache the corrective resources for compatibility issues caused by driver updates. The caching arrangement of the pre-cache loading process is dynamically adjusted based on the risk level, further reducing the occupation of bandwidth resources. This invention ensures the reliability of the risk level of the update process of the compatibility optimization driver, thereby ensuring the effectiveness of the subsequent dynamic adjustment of the pre-cache loading scheme.

[0032] Furthermore, this invention performs staged cache analysis on drive-running devices in a certain type of operation state. Since the available bandwidth of such drive-running devices is small and the available bandwidth of each drive-running device in its update association set is also small, it is impossible to predict and identify drive operation faults with high accuracy during the actual operation of such drive-running devices, and it is impossible to meet the update requirements of compatible and optimized drivers in a timely manner. Therefore, it is necessary to uniformly load the relevant resources required by the drivers that may be updated for the drive-running devices in stages, and reduce the bandwidth occupation caused by the resource loading process through targeted loading. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the intelligent driver compatibility method for cross-operating systems according to the present invention;

[0034] Figure 2 This is a flowchart illustrating the present invention's method for determining whether to perform compatibility cache analysis and stage cache analysis for each driving device based on the job operation status;

[0035] Figure 3 This is a flowchart illustrating the method for setting the compatibility execution risk coefficient based on the bandwidth execution index of the driving operating device according to the present invention;

[0036] Figure 4 This is a flowchart illustrating the process of determining whether to perform a compatibility update cache for the compatibility optimization resource set driven by the compatibility optimization based on the compatibility execution risk coefficient. Detailed Implementation

[0037] To make the objectives and advantages of the present invention clearer, the present invention will be further described below with reference to embodiments; it should be understood that the specific embodiments described herein are merely for explaining the present invention and are not intended to limit the present invention.

[0038] Preferred embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0039] It should be noted that in the description of this invention, the terms "upper", "lower", "left", "right", "inner", "outer", etc., which indicate directions or positional relationships, are based on the directions or positional relationships shown in the accompanying drawings. This is only for the convenience of description and is not intended to indicate or imply that the device or element must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation of this invention.

[0040] Furthermore, it should be noted that, in the description of this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0041] Please see Figures 1 to 4 As shown, this invention provides a smart driver compatibility method for cross-operating system use, comprising:

[0042] The operation status of each driver operating device is determined based on the bandwidth execution index and the associated reference bandwidth index, and the compatibility cache analysis and stage cache analysis are determined based on the operation status.

[0043] When performing compatibility cache analysis, the compatibility execution risk coefficient of each compatible optimization driver of the driving equipment in the second-class operation state is determined based on the stage anomaly index or the reference clustering fluctuation index. Based on the compatibility execution risk coefficient, it is determined whether to perform compatibility update cache for the compatibility optimization resource set of the compatible optimization driver based on the execution trigger parameters and execution coordination parameters.

[0044] When performing phased cache analysis, based on the relevant index of associated resources, it is determined whether to perform combined call loading or direct call loading for each driver running device in a certain job running state, so as to periodically cache and load the data corresponding to driver updates and compatibility performance repairs.

[0045] This invention is used to perform driver compatibility management for work scenarios that include several devices with mixed operating systems. The work scenario for which driver compatibility management is performed is denoted as the compatibility management target. The devices with deployed operating systems within the compatibility management target are denoted as driver running devices. The drivers used in the compatibility management target are denoted as compatibility optimized drivers. In this invention, the driver running devices correspond to multiple operating systems. Therefore, it is necessary to perform cross-operating system compatibility management for the existing compatibility optimized drivers to ensure driver compatibility and adaptation during actual operation, thereby avoiding low quality of compatibility supervision caused by compatibility failure. In this invention, there are several gateways between each driver running device for transmitting data resources to realize data transmission between each driver running device.

[0046] This invention utilizes several compatibility management records. Each compatibility management record contains at least one instance of bandwidth execution index, associated reference bandwidth index, update correlation coefficient, compatibility execution risk coefficient, and associated resource related index during the compatibility management process for each compatibility optimization driver targeting the compatibility management objective. Each compatibility management record also has a corresponding qualification mark, which indicates whether the compatibility supervision quality of the driver operation process of each driver running device within the compatibility management objective meets the user's requirements.

[0047] Specifically, the operating states of the driving and operating equipment include a first-class operating state and a second-class operating state;

[0048] The driving operation device in the aforementioned type of operation state is a driving operation device whose bandwidth execution index is less than or equal to the preset bandwidth execution index and whose associated reference bandwidth index is less than or equal to the preset associated reference bandwidth index.

[0049] The driving operation equipment in the second type of operation state is the driving operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index or whose associated reference bandwidth index is greater than the preset associated reference bandwidth index.

[0050] In this invention, a cyclic execution evaluation cycle is applied, the duration of which can be determined by the user. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the shorter the execution evaluation cycle. One example of an execution evaluation cycle is 60 hours. At the end of each execution evaluation cycle, the bandwidth execution index and associated reference bandwidth index of each driving device are detected. This invention also applies a cyclic bandwidth monitoring cycle, the duration of which can be determined by the user. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the shorter the bandwidth monitoring cycle. One example of a bandwidth monitoring cycle is 1 minute. At the end of each bandwidth monitoring cycle, the bandwidth parameters of each driving device are detected.

[0051] If the current time is the end time of an execution evaluation cycle, the next execution evaluation cycle is recorded as the critical execution cycle. The bandwidth execution index and associated reference bandwidth index of each driving device are detected. For a single driving device, the bandwidth execution index... , This refers to the bandwidth utilization parameters of the device being driven. To ensure compatibility with management objectives, the average bandwidth utilization parameters of each driving and operating device are used. , To determine the maximum value of the bandwidth parameters acquired for the drive-operated device during the evaluation phase, The average value of the bandwidth parameters obtained for each drive operation device during the evaluation phase is used. The end time of the evaluation phase is the start time of the critical execution cycle. The duration of the evaluation phase can be determined by the user according to the actual working scenario. The higher the user's requirements for the compatibility supervision quality of the drive operation process of each drive operation device within the compatibility management target, the longer the duration of the evaluation phase. One value for the duration of the evaluation phase is provided, which is 15 days. The bandwidth parameter is the maximum bandwidth that the drive operation device can use at the corresponding acquisition time, that is, the maximum allowed data throughput.

[0052] The values ​​of the preset bandwidth execution index and the preset associated reference bandwidth index can be determined by the user according to the actual working scenario. For example, the user can set them according to the compatibility management record. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the larger the value of the preset bandwidth execution index and the larger the value of the preset associated reference bandwidth index. A method for determining the value of the preset bandwidth execution index is provided, in which the maximum value of the bandwidth execution index of the driving device in the compatibility management record that meets the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target and is in a Class I operation state is recorded as the preset bandwidth execution index. A method for determining the value of the preset associated reference bandwidth index is provided, in which the maximum value of the associated reference bandwidth index of the driving device in the compatibility management record that meets the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target and is in a Class I operation state is recorded as the preset associated reference bandwidth index.

[0053] Specifically, the associated reference bandwidth index of any driving operation device is determined based on the bandwidth execution index of each driving operation device in the update association set corresponding to that driving operation device.

[0054] The update association set is determined based on the driver compatibility processing time of each driver-running device.

[0055] Specifically, for a single driver running device, the associated reference bandwidth index is the average of the bandwidth execution indices of each driver running device in the update association set corresponding to that driver running device. The update association set is a collection of several driver running devices. The update association coefficients of each driver running device in the update association set corresponding to that driver running device are all greater than the preset update association coefficient. For any two driver running devices, the update association coefficient is the reciprocal of the average of the association indices of each determined processing time of the two driver running devices. For any driver compatibility processing time of any driver running device among the two driver running devices, the minimum value of the interval between each driver compatibility processing time of the other driver running device that has the same category as the compatibility optimization driver corresponding to the driver compatibility processing time and the driver compatibility processing time is recorded as the processing time association index. The unit of measurement of the processing time association index is min. For a single driver running device, the driver compatibility processing time is the time when the compatibility update is completed during the process of using the compatibility optimization driver of the driver running device. Each driver compatibility processing time records the category of the corresponding compatibility optimization driver.

[0056] The value of the preset update correlation coefficient can be determined by the user based on the actual working scenario. For example, the user can set it based on the compatibility management record. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the larger the value of the preset update correlation coefficient. A method for determining the value of the preset update correlation coefficient is provided, which takes the minimum value of the update correlation coefficient of each driving device to the corresponding driving device in the update correlation set of the compatibility management record that meets the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target as the preset update correlation coefficient.

[0057] Specifically, compatibility cache analysis is performed on drive-operated devices operating in the second-class operation state, whereby...

[0058] Periodically check the compatibility execution risk coefficient of each compatible and optimized driver used by the driving device to determine whether to update the cache for each compatible and optimized driver.

[0059] The method for setting the compatibility execution risk coefficient of any of the aforementioned compatibility optimization drivers is determined based on the bandwidth execution index of the device on which the driver runs.

[0060] Specifically, for a single driver operating device, if the driver operating device is in a Class II operating state, it indicates that the bandwidth execution index of the driver operating device is large or the associated reference bandwidth index is large, which in turn indicates that the available bandwidth of the driver operating device is large or the available bandwidth of each driver operating device in its update association set is large. For such driver operating devices, if their own available bandwidth conditions are relatively good, they can simultaneously ensure the transmission of the data used to predict driver operation failures and the data required for compatibility updates of the compatibility optimization driver. If their own available bandwidth conditions are poor, the compatibility update data required by such driver operating devices can be pre-cached by considering the usage of the compatibility optimization driver of each driver operating device in its update association set. Therefore, compatibility caching analysis is performed for such driver operating devices.

[0061] During the critical execution cycle, compatibility cache analysis is performed on drive operation equipment in the second-class operation state. This invention applies a one-cycle risk assessment cycle, the duration of which can be determined by the user. The higher the user's requirements for the compatibility supervision quality of the drive operation process of each drive operation equipment within the compatibility management target, the shorter the duration of the risk assessment cycle. One risk assessment cycle duration is provided as 30 minutes. At the end of each risk assessment cycle, the compatibility execution risk coefficient of each compatible optimized drive used for the drive operation equipment in the second-class operation state is detected.

[0062] Specifically, based on the change phase analysis, a compatibility risk analysis is performed on the drive operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index, and the compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the phase abnormality index.

[0063] The stage anomaly index is determined based on the trend evaluation index of each compatibility optimization-driven change response stage.

[0064] Specifically, for a single drive operation device in a Class II operating state, if the bandwidth execution index of the drive operation device is greater than the preset bandwidth execution index, it indicates that the available bandwidth conditions of the drive operation device are relatively good. Therefore, the actual operation process of the drive operation device can be directly analyzed to determine the usage of each compatible optimized drive. For any compatible optimized drive corresponding to a single drive operation device whose bandwidth execution index is greater than the preset bandwidth execution index, the normalized stage anomaly index is recorded as the compatibility execution risk coefficient of the compatible optimized drive. The stage anomaly index is the average of the trend evaluation index of each change response stage corresponding to the compatible optimized drive. For any change response stage of the compatible optimized drive, the trend evaluation index... , This serves as an evaluation parameter for the execution trend of the compatibility optimization driver during the change response phase. The trend difference evaluation parameters for this response change phase driven by the compatibility optimization are the execution trend evaluation parameters. , In response to the average value of each anomaly monitoring parameter determined during the change phase, The trend difference assessment parameter is used to evaluate the standard deviation between the anomaly monitoring parameters determined during each change phase. , In response to the average value of the abnormal monitoring difference parameters determined during each change phase, To determine the standard deviation between the anomaly monitoring difference parameters determined in each response change phase, the midpoint of the time range corresponding to the response change phase is the moment when the compatibility optimization driver is updated. The duration of the response change phase can be determined by the user according to the actual scenario. The higher the user's requirements for the compatibility supervision quality of the driver operation process of each driver running device within the compatibility management target, the larger the duration of the response change phase. One possible duration of the response change phase is 10 minutes.

[0065] This invention employs a cyclical monitoring execution cycle. The duration of this cycle can be determined by the user. The higher the user's requirements for the compatibility monitoring quality of the driving operation process of each driving device within the compatibility management target, the shorter the monitoring execution cycle. One monitoring execution cycle duration is provided: 1 minute. At the end of each monitoring execution cycle, abnormal monitoring parameters for each driving device are detected. If the current time is the end of a monitoring execution cycle, abnormal monitoring parameters for each driving device are detected. For a single driving device, the abnormal monitoring parameter is the number of error codes occurring for that driving device within the monitoring execution cycle. The abnormal monitoring difference parameter... , The abnormal monitoring parameters determined for the driven operating equipment during this monitoring execution cycle. The abnormal monitoring parameters determined for the driven operating equipment in the previous monitoring execution cycle of this monitoring execution cycle.

[0066] Specifically, based on association clustering analysis, a compatibility risk analysis is performed on drive operation equipment whose bandwidth execution index is less than or equal to the preset bandwidth execution index, and the compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the reference clustering fluctuation index.

[0067] The reference clustering volatility index is determined based on the trend evaluation index of each compatibility optimization-driven change response phase.

[0068] Specifically, for a single drive-operating device in a Class II operating state, if the bandwidth execution index of the drive-operating device is less than or equal to the preset bandwidth execution index, it indicates that the available bandwidth conditions of the drive-operating device are poor. However, the bandwidth conditions of the drive-operating devices in the updated association set are better. Therefore, by analyzing the usage of each compatible optimized drive by the drive-operating devices in the updated association set, an estimate can be made of the usage of the corresponding compatible optimized drive by the drive-operating device. For any compatible optimized drive corresponding to a single drive-operating device whose bandwidth execution index is less than or equal to the preset bandwidth execution index, the reference clustering fluctuation index after normalization is recorded as the compatibility execution risk coefficient of the compatible optimized drive. The reference clustering fluctuation index is the average value of the trend evaluation index of each drive-operating device in the updated association set of the compatible optimized drive.

[0069] Specifically, for compatibility optimization drivers with a compatibility execution risk coefficient greater than the preset compatibility execution risk coefficient, a compatibility update cache is performed, and the compatibility optimization resource set of the compatibility optimization driver is pre-cached and loaded based on the execution trigger parameters and execution coordination parameters;

[0070] The execution trigger parameters and execution coordination parameters during the pre-caching loading process are determined based on the compatibility execution risk coefficient, and the execution trigger parameters and execution coordination parameters are positively correlated with the compatibility execution risk coefficient.

[0071] Specifically, for any compatible and optimized driver corresponding to a single driver running device, if the compatibility execution risk coefficient is greater than the preset compatibility execution risk coefficient, it indicates that the driver running device is more prone to operational abnormalities when the version of the compatible and optimized driver is updated. In such cases, in order to ensure the operational stability of the actual operation process, it is necessary to cache the compatibility update for the driver running device in advance. The resource set used to handle the compatibility performance fluctuations caused by driver updates, i.e., the compatibility optimization resource set, is cached in advance. The compatibility optimization resource set includes the complete rollback package of the old version driver and other resources that may be used for compatibility performance repair. How to determine the compatibility optimization resource set is a matter that is known to those skilled in the art and will not be elaborated here.

[0072] For any compatible and optimized driver corresponding to a single driver-running device, a pre-cached loading of the compatible and optimized resource set for that driver is performed based on determined execution trigger parameters and execution coordination parameters. The execution trigger parameters are the interval between the time when the pre-cached loading of the corresponding compatible and optimized resource set is performed and the time when the version update for that compatible and optimized driver begins. , The execution coordination parameters represent the compatibility risk coefficient of the optimized driver for the device on which the driver operates. , The number of collaborative execution gateways during the pre-caching loading process for the corresponding compatibility-optimized resource set. The number of associated execution gateways for the driver running device is defined as follows: the associated execution gateway is a gateway connected to the driver running device; the collaborative execution gateway is a gateway used to receive the set of compatibility optimization resources corresponding to the compatibility optimization driver; the compatibility execution risk coefficient of the compatibility optimization driver for the driver running device is recorded as the execution collaboration parameter; during the pre-caching loading process, the larger the compatibility execution risk coefficient, the higher the completeness of the repair resources contained in the pre-cached compatibility optimization resource set and the higher the redundancy of the transmission process. Therefore, in order to ensure the quality of monitoring the driver compatibility performance of the driver running device while reducing the significant impact on bandwidth during the operation, the compatibility optimization resource set is sent to the collaborative execution gateway during the pre-caching loading process, and is retrieved from the collaborative execution gateway when the bandwidth parameter of the driver running device is less than or equal to the preset bandwidth parameter.

[0073] The value of the preset compatibility execution risk coefficient can be determined by the user based on the actual working scenario. For example, the user can set it based on the compatibility management record. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the more appropriate the preset compatibility execution risk coefficient is. The minimum value of the compatibility execution risk coefficient of the compatibility optimization driver in the compatibility management record that meets the user's compatibility supervision quality requirements for the driving operation process of each driving device within the compatibility management target is recorded as the preset compatibility execution risk coefficient.

[0074] Specifically, stage cache analysis is performed on the driver running device that is in a certain type of operation running state, and the related resource index of the driver running device is detected to determine whether to perform combined call loading for the driver running device.

[0075] The associated resource-related index is determined based on the update execution driver corresponding to each driving device.

[0076] Specifically, for a single driver running device, if the driver running device is in a Class I running state, it indicates that the bandwidth execution index and the associated reference bandwidth index of the driver running device are both small. This indicates that the available bandwidth of the driver running device is small, and the available bandwidth of each driver running device in its update association set is also small. Relatively speaking, it is impossible to predict and identify driver running faults with high accuracy during the actual operation of such driver running devices, and it is impossible to meet the update requirements of compatible and optimized drivers in a timely manner. Therefore, a stage caching analysis is performed on driver running devices in Class I running state. At this time, when updating the version of the compatible and optimized driver used by such driver running devices, it is necessary to pre-cache the update resource set that needs to be updated in the critical execution cycle, and at the same time pre-cache the compatible and optimized resource set corresponding to the update resource set that needs to be updated. This ensures that the version update can be completed smoothly in the critical execution cycle, while ensuring that driver compatibility anomalies can be handled in a timely manner. The correlation resource related index is used to characterize the correlation between the update resource set that needs to be cached and the corresponding compatible and optimized resource set of the driver running device in the update association set and the driver running devices using the same gateway.

[0077] For a single drive-operated device in a certain type of operating state, the associated resource correlation index

[0078] , The number of update execution drivers existing on the device that is being driven by this driver. The number of related execution drivers existing for the driver running device, wherein the update execution driver is a compatibility optimization driver that needs to be updated within the critical execution cycle, the related execution driver is the update execution driver that exists together with the driver running device and its associated execution devices, and the associated execution devices are the driver running devices that share a common gateway with the driver running device in the update association set of the driver running device.

[0079] Specifically, for drive-running devices whose related resource correlation index is greater than the preset related resource correlation index, combined calls are made to load them;

[0080] The combined invocation gateway for each relevant execution driver is determined based on the reference invocation interval index. The combined invocation gateway for any relevant execution driver is the gateway with the smallest reference invocation interval index for that relevant execution driver.

[0081] Specifically, for a single driver running device in a certain type of operation state, if the associated resource correlation index is greater than the preset associated resource correlation index, it indicates that the correlation between the update resource set that needs to be cached and the corresponding compatibility optimization resource set of the driver running device and the driver running device that shares a common gateway within the update association set of the driver running device is strong. Therefore, combined call loading can be performed to reduce the bandwidth load. The combined call gateway is allocated for each related execution driver of the driver running device. For a single related execution driver, the reference call interval index of any gateway for the related execution driver is the average of the call interval indices of each related execution device corresponding to the related execution driver. For a single related execution device, the call interval index is the number of gateways that the related execution device needs to pass through to call the resources cached in the gateway. The related execution devices are the driver running device and its associated execution devices that share the related execution driver.

[0082] The value of the preset associated resource related index can be determined by the user based on the actual working scenario. For example, the user can set it based on the compatibility management record. The higher the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target, the larger the value of the preset associated resource related index. A method for determining the value of the preset associated resource related index is provided, which records the compatibility management record for combined loading of driving devices as a combined reference record, and records the minimum value of the associated resource related index in the combined reference record that meets the user's requirements for the compatibility supervision quality of the driving operation process of each driving device within the compatibility management target as the preset associated resource related index.

[0083] Specifically, for cases where the related resource index is less than or equal to the preset related resource index, or for cases where the driver running device has completed the combined call loading, direct call loading is performed.

[0084] The target invocation gateway for each direct execution driver is determined based on the invocation interval index. The target invocation gateway for any direct execution driver is the gateway with the smallest invocation interval index for that direct execution driver.

[0085] For a single driver running device in a certain type of running job state, if the correlation index of associated resources is greater than the preset correlation index of associated resources, it indicates that the correlation between the update resource set that needs to be cached and the corresponding compatibility optimization resource set of the driver running device that shares a common gateway with it is weak. Therefore, the update execution driver of this type of driver running device and the update execution driver of the driver running device that has completed the combined call loading (excluding the associated execution driver) are directly called and allocated. The update execution driver of this driver running device and the update execution driver of the driver running device that has completed the combined call loading (excluding the associated execution driver) are recorded as the direct execution driver.

[0086] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A method for intelligent driver compatibility across operating systems, characterized in that, include: The operation status of each driver operating device is determined based on the bandwidth execution index and the associated reference bandwidth index, and the compatibility cache analysis and stage cache analysis are determined based on the operation status. When performing compatibility cache analysis, the compatibility execution risk coefficient of each compatible optimization driver of the driving equipment in the second-class operation state is determined based on the stage anomaly index or the reference clustering fluctuation index. Based on the compatibility execution risk coefficient, it is determined whether to perform compatibility update cache for the compatibility optimization resource set of the compatible optimization driver based on the execution trigger parameters and execution coordination parameters. When performing phased cache analysis, based on the relevant index of associated resources, it is determined whether to perform combined call loading or direct call loading for each driver running device in a certain job running state, so as to periodically cache and load the data corresponding to driver updates and compatibility performance repairs. The operational status of the drive and operation equipment includes a first-class operational status and a second-class operational status. The driving operation device in the aforementioned type of operation state is a driving operation device whose bandwidth execution index is less than or equal to the preset bandwidth execution index and whose associated reference bandwidth index is less than or equal to the preset associated reference bandwidth index. The driving operation equipment in the second type of operation state is the driving operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index or whose associated reference bandwidth index is greater than the preset associated reference bandwidth index; The associated reference bandwidth index of any of the driving operation devices is determined based on the bandwidth execution index of each driving operation device in the corresponding update association set. The updated association set is determined based on the driver compatibility processing time of each driver-running device; Compatibility cache analysis was performed on drive-operated devices operating in Category II operation mode, among which... Periodically check the compatibility execution risk coefficient of each compatible and optimized driver used by the driving device to determine whether to update the cache for each compatible and optimized driver. The method for setting the compatibility execution risk coefficient of any of the aforementioned compatibility optimization drivers is determined based on the bandwidth execution index of the device on which the driver runs; A stage cache analysis is performed on the driver running device that is in a certain job running state, and the related resource index of the driver running device is detected to determine whether to perform combined call loading for the driver running device. The associated resource-related index is determined based on the update execution driver corresponding to each driving device.

2. The intelligent driver compatibility method for cross-operating systems according to claim 1, characterized in that, Based on the change phase analysis, a compatibility risk analysis is performed on the drive operation equipment whose bandwidth execution index is greater than the preset bandwidth execution index. The compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the phase abnormality index. The stage anomaly index is determined based on the trend evaluation index of each compatibility optimization-driven change response stage.

3. The intelligent driver compatibility method for cross-operating systems according to claim 2, characterized in that, Based on association clustering analysis, a compatibility risk analysis is performed on the drive operation equipment whose bandwidth execution index is less than or equal to the preset bandwidth execution index. The compatibility execution risk coefficient of each compatible optimized drive of the drive operation equipment is determined according to the reference clustering fluctuation index. The reference clustering volatility index is determined based on the trend evaluation index of each compatibility optimization-driven change response phase.

4. The intelligent driver compatibility method for cross-operating systems according to claim 1, characterized in that, For compatibility optimization drivers with a compatibility execution risk coefficient greater than the preset compatibility execution risk coefficient, a compatibility update cache is performed, and the compatibility optimization resource set of the compatibility optimization driver is pre-cache loaded based on the execution trigger parameters and execution coordination parameters; The execution trigger parameters and execution coordination parameters during the pre-caching loading process are determined based on the compatibility execution risk coefficient, and the execution trigger parameters and execution coordination parameters are positively correlated with the compatibility execution risk coefficient.

5. The intelligent driver compatibility method for cross-operating systems according to claim 1, characterized in that, Combined loading is performed on drive-running devices whose associated resource correlation index is greater than the preset associated resource correlation index; The combined invocation gateway for each relevant execution driver is determined based on the reference invocation interval index. The combined invocation gateway for any relevant execution driver is the gateway with the smallest reference invocation interval index for that relevant execution driver.

6. The intelligent driver compatibility method for cross-operating systems according to claim 5, characterized in that, For cases where the related resource index is less than or equal to the preset related resource index, or for cases where the combined loading is completed, the driver running device is directly loaded. The target invocation gateway for each direct execution driver is determined based on the invocation interval index. The target invocation gateway for any direct execution driver is the gateway with the smallest invocation interval index for that direct execution driver.

Images