Touch data conversion module in multi-operating system touch display device and method thereof

Abstract

The invention discloses a touch data conversion module in a multi-operation system touch display device and a method thereof, relates to the technical field of multi-operation system data conversion, and solves the technical problem of poor user experience caused by difficulty in timely and accurate response to a touch event during conversion of the existing multi-operation system. Comprising the following steps of 1, generating a touch data label according to touch data; when the touch data tag is valid; entering the step 2; 2, when the number of conversion failures is larger than a set failure number threshold value; entering the step 3; 3, obtaining converted touch data according to the touch data conversion parameters; generating a conversion label according to the conversion touch data; when the label conversion is successful; entering step 4; otherwise, adding one to the conversion failure times, and entering the step 2; 4, the converted touch data are packaged and sent to a second operating system; and timely and accurate response enables the user experience to be greatly improved.

Description

Technical Field

[0001] The present application belongs to the technical field of multi-operating system data conversion, and relates to multi-operating system data conversion technology, and specifically to a touch data conversion module and method in a multi-operating system touch display device. Background Art

[0002] With the continuous development of technology, multi-operating system touch display devices have gradually occupied a place in the market. Such devices can usually switch between different operating systems (such as Android and Windows) to meet the diverse usage needs of users.

[0003] Due to the differences in the underlying architecture, drivers and event processing mechanisms of different operating systems, it is difficult for touch data to be directly communicated between different systems. In existing multi-operating systems, since each system may have different definitions of the format of touch events, the type of touch data and its range, it is difficult to respond to touch events in a timely and accurate manner during system conversion. This greatly limits the flexibility and user experience of multi-operating system devices in touch interaction. Therefore, a touch data conversion module and method in a multi-operating system touch display device are needed. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art; to this end, the present application proposes a touch data conversion module and method in a multi-operating system touch display device, which is used to solve the technical problem that the existing multi-operating systems are difficult to respond to touch events in a timely and accurate manner during conversion, resulting in a poor user experience.

[0005] To achieve the above-mentioned purpose, the first aspect of the present application provides a touch data conversion method in a multi-operating system touch display device, comprising the following steps:

[0006] Step 1: acquiring touch data corresponding to a touch event generated by the first operating system; generating a touch data tag according to the touch data; determining whether the touch data tag is valid; if yes, proceeding to step 2; if no, discarding the touch data;

[0007] Step 2: Obtain the number of conversion failures, and determine whether the number of conversion failures is greater than a set failure threshold; if yes, discard the touch data and generate a non-convertible signal; if no, proceed to step 3;

[0008] Step 3: obtaining touch data conversion parameters between the first operating system and the second operating system, converting the touch data according to the touch data conversion parameters to obtain converted touch data; generating a conversion label according to the converted touch data; determining whether the conversion label is successful; if yes, setting the number of conversion failures to zero and proceeding to step 4; if no, increasing the number of conversion failures by one and proceeding to step 2;

[0009] Step 4: Encapsulate the converted touch data into a touch event format 2 corresponding to the second operating system, and package and send it to the second operating system;

[0010] Step 5: When the second operating system cannot respond to the touch event, a response failure signal is generated; otherwise, the touch conversion is completed.

[0011] The present application obtains touch data corresponding to a touch event generated by a first operating system; generates a touch data tag according to the touch data; when the touch data tag is valid, obtains touch data conversion parameters between the first operating system and the second operating system, converts the touch data according to the touch data conversion parameters to obtain converted touch data; generates a conversion tag according to the converted touch data; when the conversion tag is successful, encapsulates the converted touch data into a touch event format 2 corresponding to the second operating system, and packages and sends it to the second operating system; when the operating system is converted in multiple operating systems, the touch event is converted accordingly, thereby achieving seamless response of touch operations in a multiple operating system environment; timely and accurate response greatly increases user experience.

[0012] Preferably, the touch data includes a touch type item and a plurality of touch data items.

[0013] Preferably, the touch data items include touch point coordinates, pressure values ​​and touch timestamps; the touch types include single-point touch or multi-point touch, etc.

[0014] Preferably, generating a touch data label according to the touch data includes:

[0015] Acquire touch data and determine whether there is a missing touch data item or a missing touch type item in the touch data; if yes, set the touch data label to invalid; if no, set the touch data label to valid;

[0016] The touch data whose touch data label is set as qualified is preprocessed.

[0017] Preferably, the preprocessing includes noise removal, touch point filtering, coordinate normalization, etc.

[0018] Preferably, the touch data conversion parameters are obtained by the following method, including:

[0019] Acquire touch event format 1 of the first operating system and touch event format 2 of the second operating system;

[0020] Extracting touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; generating a touch type item conversion relationship according to the touch type items and their corresponding available touch type 1 and available touch type 2;

[0021] Extracting the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; generating a touch data item conversion relationship according to each touch data item and its corresponding available range 1 and available range 2;

[0022] The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

[0023] Preferably, the touch event format is generated according to the touch type item and each touch data item, including:

[0024] Obtain available touch types corresponding to touch type items and available ranges corresponding to respective touch data items; integrate the available ranges and the corresponding touch type items or respective touch data items into a touch event format; the touch event format includes touch event format one and touch event format two.

[0025] Preferably, generating a touch type item conversion relationship according to the touch type item and the corresponding available touch type one and available touch type two includes:

[0026] Extract each available touch type one from available touch type one; extract each available touch type two from available touch type two; obtain the same touchable type one as the touchable type two, and establish a conversion relationship between the same touchable type two and the touchable type one; and integrate each conversion relationship into a touch type item conversion relationship.

[0027] Preferably, generating a touch data item conversion relationship according to each touch data item and the available range 1 and available range 2 corresponding thereto includes:

[0028] Obtaining the available range 1 and the available range 2 corresponding to each touch data item; establishing a conversion relationship between the available range 1 and the available range 2 of the same touch data item; and integrating each conversion relationship into a touch data item conversion relationship.

[0029] Preferably, the first operating system is an Android system, and the second operating system is a Windows system.

[0030] Preferably, converting the touch data according to the touch data conversion parameter to obtain the converted touch data includes:

[0031] Extracting the touch type item conversion relationship and the conversion relationship of each touch data item in the touch data conversion parameter; extracting the touch type item and each touch data item in the touch data; converting the touch type item into the conversion type item according to the touch type item conversion relationship; converting the corresponding touch data item into the conversion data item according to the conversion relationship of each touch data item; integrating the conversion type item and each conversion data item into the conversion touch data.

[0032] Preferably, generating a conversion label according to the conversion touch data includes:

[0033] Extracting a conversion type item and each conversion data item in the conversion touch data;

[0034] Determine whether there is a missing conversion type item or a missing conversion data item in the conversion touch data; if yes, set the conversion label to failure; if no, when the conversion type item is not within the available touch type two, or each conversion data item is not within its corresponding available range two; set the conversion label to failure; otherwise, set the conversion label to success.

[0035] A second aspect of the present application provides a touch data conversion module in a multi-operating system touch display device, comprising: a touch data acquisition unit, a conversion parameter generation unit and a touch data conversion unit;

[0036] The touch data acquisition unit is used to acquire touch data corresponding to the touch event generated by the first operating system; and generate a touch data label according to the touch data;

[0037] The conversion parameter generating unit: obtains the touch event format 1 of the first operating system and the touch event format 2 of the second operating system; generates touch data conversion parameters according to the touch event format 1 and the touch event format 2;

[0038] The touch data conversion unit: when the touch data tag is valid, obtains touch data and touch data conversion parameters between the first operating system and the second operating system; converts the touch data according to the touch data conversion parameters to obtain converted touch data; and generates a conversion tag according to the converted touch data.

[0039] Preferably, the touch data conversion module further comprises a data encapsulation unit: when the conversion tag is successful, the converted touch data is acquired, the converted touch data is encapsulated into a touch event format 2 corresponding to the second operating system, and the data is packaged and sent to the second operating system.

[0040] Preferably, the step of generating touch data conversion parameters according to touch event format 1 and touch event format 2 includes:

[0041] Extracting touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; extracting each available touch type 1 in available touch type 1; extracting each available touch type 2 in available touch type 2; acquiring the same touchable type 1 as the touchable type 2, and establishing a conversion relationship between the same touchable type 2 and the touchable type 1; and integrating each conversion relationship into a touch type item conversion relationship;

[0042] Extract the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; obtain the available range 1 and available range 2 corresponding to each touch data item; establish a conversion relationship between the available range 1 and available range 2 of the same touch data item; and integrate each conversion relationship into a touch data item conversion relationship;

[0043] The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

[0044] Compared with the prior art, the beneficial effects of this application are:

[0045] 1. The present application obtains touch data corresponding to a touch event generated by a first operating system; generates a touch data tag according to the touch data; when the touch data tag is valid, obtains touch data conversion parameters between the first operating system and the second operating system, converts the touch data according to the touch data conversion parameters, and obtains converted touch data; generates a conversion tag according to the converted touch data; when the conversion tag is successful, encapsulates the converted touch data into a touch event format 2 corresponding to the second operating system, and packages and sends it to the second operating system; when the operating system is converted in multiple operating systems, the touch event is converted accordingly, thereby achieving seamless response of touch operations in a multiple operating system environment; timely and accurate response greatly increases user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0047] Figure 1 A schematic flow chart of a touch data conversion method in a multi-operating system touch display device of the present application;

[0048] Figure 2 This is a schematic diagram of the touch data conversion module of this application. DETAILED DESCRIPTION

[0049] The technical solution of the present application will be described clearly and completely below in conjunction with the embodiments. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0050] See also Figure 1 The first aspect of the present application provides a touch data conversion method in a multi-operating system touch display device, comprising the following steps:

[0051] Step 1: Acquire touch data corresponding to a touch event generated by a first operating system; a touch event is an event corresponding to a touch operation when a device user uses the device; generate a touch data label according to the touch data; the touch data label is valid or invalid; a valid value indicates that the corresponding touch data can correctly trigger a response to the touch event; an invalid value indicates that the touch data may not correctly trigger a response to the touch event due to missing data; determine whether the touch data label is valid; if yes, proceed to step 2; if no, discard the touch data; the touch data is touch event data captured by a touch screen driver of the first operating system; the touch data includes a touch type item and several touch data items, and the touch data items include touch point coordinates, pressure values, touch timestamps, etc.; the touch type includes single-point touch or multi-point touch, etc.; the specific touch type item and touch data item are set according to the corresponding operating system;

[0052] Step 2: Obtain the number of conversion failures, where the touch data conversion parameter is the conversion relationship between the touch type item and each touch data item when the touch data obtained by the first operating system requests the second operating system to convert the touch format; determine whether the number of conversion failures is greater than a set failure number threshold; if yes, discard the touch data and generate a non-convertible signal; if no, proceed to step 3;

[0053] In step 2, a conversion failure threshold is set. When the number of conversion failures is greater than the conversion failure threshold, it means that the conversion cannot be performed in time when the system is converted, and a non-convertible signal is generated to remind the relevant operator to perform the touch operation again;

[0054] Step 3: obtaining touch data conversion parameters between the first operating system and the second operating system, converting the touch data according to the touch data conversion parameters to obtain converted touch data; generating a conversion label according to the converted touch data; determining whether the conversion label is successful; if yes, setting the number of conversion failures to zero and proceeding to step 4; if no, increasing the number of conversion failures by one and proceeding to step 2;

[0055] Step 4: Encapsulate the converted touch data into a touch event format 2 corresponding to the second operating system, and package and send it to the second operating system;

[0056] Step 5: When the second operating system cannot respond to the touch event, a response failure signal is generated; otherwise, the touch conversion is completed; and the operator is reminded to perform the touch operation again.

[0057] This embodiment obtains touch data corresponding to a touch event generated by a first operating system; generates a touch data tag according to the touch data; when the touch data tag is valid, obtains touch data conversion parameters between the first operating system and the second operating system, converts the touch data according to the touch data conversion parameters to obtain converted touch data; generates a conversion tag according to the converted touch data; when the conversion tag is successful, encapsulates the converted touch data into touch event format 2 corresponding to the second operating system, and packages and sends it to the second operating system; when the operating system is converted in multiple operating systems, the touch event is converted accordingly, thereby achieving seamless response of touch operations in a multiple operating system environment; timely and accurate response greatly increases user experience.

[0058] Generate touch data labels based on touch data, including:

[0059] Acquire touch data and determine whether there is a missing touch data item or a missing touch type item in the touch data; if yes, set the touch data label to invalid; if no, set the touch data label to valid;

[0060] The touch data label is valid or invalid; valid means that the corresponding touch data can correctly trigger the response of the touch event; invalid means that the touch data may not correctly trigger the response of the touch event due to missing data.

[0061] The touch data whose touch data labels are set as qualified are preprocessed; the preprocessing includes noise removal, touch point filtering, coordinate normalization, etc.

[0062] The touch data conversion parameters are obtained in the following manner, including: obtaining touch event format 1 of the first operating system and touch event format 2 of the second operating system;

[0063] Extracting touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; generating a touch type item conversion relationship according to the touch type items and their corresponding available touch type 1 and available touch type 2;

[0064] Extracting the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; generating a touch data item conversion relationship according to each touch data item and its corresponding available range 1 and available range 2;

[0065] The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

[0066] The touch event format is generated based on the touch type item and each touch data item, including: obtaining the available touch type corresponding to the touch type item, and the available range corresponding to each touch data item; integrating the available range, and the corresponding touch type item or each touch data item into a touch event format; the touch event format includes touch event format one and touch event format two; it can be understood that the touch event format is a touch data format that can be recognized by the corresponding operating system.

[0067] It can be understood that the available touch types in touch event format one are recorded as available touch type one; the available touch types in touch event format two are recorded as available touch type two; each available range in touch event format one is recorded as available range one; each available range in touch event format two is recorded as available range two;

[0068] A touch type item conversion relationship is generated according to the touch type item and the corresponding available touch type one and available touch type two, including:

[0069] Extract each available touch type one from available touch type one; extract each available touch type two from available touch type two; obtain the same touchable type one as the touchable type two, and establish a conversion relationship between the same touchable type two and the touchable type one; and integrate each conversion relationship into a touch type item conversion relationship.

[0070] Specifically, the available touch type one corresponding to the touch type item in the first operating system includes single-click, double-click, long press, single finger and multi-finger; the available touch type two corresponding to the touch type item in the second operating system includes single-click, double-click and long press; at this time, a conversion relationship is established between a single-click in the first operating system and a single-click in the second operating system; a conversion relationship between a double-click in the first operating system and a double-click in the second operating system; a conversion relationship between a long press in the first operating system and a long press in the second operating system; and each conversion relationship is integrated into a touch type item conversion relationship.

[0071] A touch data item conversion relationship is generated according to each touch data item and the corresponding available range 1 and available range 2, including:

[0072] Obtaining the available range 1 and the available range 2 corresponding to each touch data item; establishing a conversion relationship between the available range 1 and the available range 2 of the same touch data item; and integrating each conversion relationship into a touch data item conversion relationship. It is understandable that the number and type of touch data items of the first operating system and the second operating system are the same;

[0073] Specifically, if the touch data item is the touch point coordinate, in the first operating system, the available range 1 corresponding to the x coordinate is 0-1079, and the available range 1 corresponding to the y coordinate is 0-1919; in the second operating system, the available range 2 of the x coordinate is 0-1023, and the available range 2 corresponding to the y coordinate is 0-767; a conversion relationship between the corresponding touch items between the first operating system and the second operating system is established, and the corresponding conversion relationship is obtained by mapping the x coordinate 0-1079 to 0-1023, and the corresponding conversion relationship is obtained by mapping the y coordinate 0-1919 to 0-767; the conversion relationships corresponding to the x and y coordinates are integrated into the conversion relationship of the touch point coordinates; if the touch data item is touch pressure, the available range corresponding to the touch pressure of the first operating system is 80-150g; the available range corresponding to the touch pressure of the second operating system is 10-300g; the conversion relationship mapping the touch pressure range 80-150g to 10-300g is obtained as the conversion relationship of the touch pressure; the available range can be understood as the identifiable range corresponding to each touch data item of the corresponding operating system.

[0074] In this embodiment, the first operating system is an Android system, and the second operating system is a Windows system. It can be understood that the first operating system and the second operating system may also be other systems, and different operating systems correspond to different touch event formats.

[0075] The touch data is converted according to the touch data conversion parameters to obtain converted touch data, including: extracting the touch type item conversion relationship and the touch data item conversion relationship in the touch data conversion parameters; extracting the touch type item and the touch data item in the touch data; converting the touch type item into a conversion type item according to the touch type item conversion relationship; converting the touch data item corresponding to each touch data item into a conversion data item according to its conversion relationship; and integrating the conversion type item and the conversion data items into the converted touch data.

[0076] Generating a conversion label according to the conversion touch data includes: extracting a conversion type item and each conversion data item in the conversion touch data;

[0077] Determine whether there is a missing conversion type item or a missing conversion data item in the conversion touch data; if yes, set the conversion label to failure; if no, when the conversion type item is not within the available touch type two, or each conversion data item is not within its corresponding available range two; set the conversion label to failure; otherwise, set the conversion label to success.

[0078] The conversion tag is used to determine whether the converted touch data is successfully converted. When the converted touch data meets the touch data requirements that the corresponding system can recognize, it means that the touch data conversion is successful. Otherwise, it means that the touch data conversion fails. At this time, it is necessary to determine whether to perform another conversion. When the number of conversion failures is too large, no further conversion is performed; otherwise, another conversion is required. This embodiment avoids the conversion process from falling into an infinite loop by setting a threshold for the number of conversion failures.

[0079] See also Figure 2 , a second aspect of the present application provides a touch data conversion module in a multi-operating system touch display device, comprising: a touch data acquisition unit, a conversion parameter generation unit and a touch data conversion unit;

[0080] A touch data acquisition unit: used to acquire touch data corresponding to a touch event generated by the first operating system; and to generate a touch data label according to the touch data;

[0081] A conversion parameter generating unit: acquiring a touch event format 1 of the first operating system and a touch event format 2 of the second operating system; generating touch data conversion parameters according to the touch event format 1 and the touch event format 2;

[0082] Touch data conversion unit: when the touch data tag is valid, acquires touch data and touch data conversion parameters between the first operating system and the second operating system; converts the touch data according to the touch data conversion parameters to obtain converted touch data; generates a conversion tag according to the converted touch data.

[0083] The touch data conversion module also includes a data encapsulation unit: when the conversion tag is successful, it obtains the converted touch data, encapsulates the converted touch data into a touch event format 2 corresponding to the second operating system, and packages and sends it to the second operating system.

[0084] Generate touch data conversion parameters according to touch event format 1 and touch event format 2, including:

[0085] Extracting touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; extracting each available touch type 1 in available touch type 1; extracting each available touch type 2 in available touch type 2; acquiring the same touchable type 1 as the touchable type 2, and establishing a conversion relationship between the same touchable type 2 and the touchable type 1; and integrating each conversion relationship into a touch type item conversion relationship;

[0086] Extract the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; obtain the available range 1 and available range 2 corresponding to each touch data item; establish a conversion relationship between the available range 1 and available range 2 of the same touch data item; and integrate each conversion relationship into a touch data item conversion relationship;

[0087] The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

[0088] Part of the data in the above formula is calculated by removing the dimension and taking its numerical value. The formula is a formula closest to the actual situation obtained by software simulation of a large amount of collected data; the preset parameters and preset thresholds in the formula are set by technical personnel in this field according to actual conditions or obtained through simulation of a large amount of data.

[0089] How this application works:

[0090] The present application obtains touch data corresponding to a touch event generated by a first operating system; generates a touch data tag according to the touch data; when the touch data tag is valid, obtains touch data conversion parameters between the first operating system and the second operating system, converts the touch data according to the touch data conversion parameters to obtain converted touch data; generates a conversion tag according to the converted touch data; when the conversion tag is successful, encapsulates the converted touch data into a touch event format 2 corresponding to the second operating system, and packages and sends it to the second operating system; when the operating system is converted in multiple operating systems, the touch event is converted accordingly, thereby achieving seamless response of touch operations in a multiple operating system environment; timely and accurate response greatly increases user experience.

[0091] The above embodiments are only used to illustrate the technical method of the present application and are not intended to limit it. Although the present application has been described in detail with reference to the preferred embodiments, a person of ordinary skill in the art should understand that the technical method of the present application may be modified or replaced by equivalents without departing from the spirit and scope of the technical method of the present application.

Claims

1. A touch data conversion method in a multi-operating system touch display device, characterized in that: The following steps are involved: Step 1: Acquire touch data corresponding to a touch event generated by the first operating system; Generate a touch data tag according to the touch data; determine whether the touch data tag is valid; if yes, proceed to step 2; if no, discard the touch data; Step 2: Obtain the number of conversion failures, and determine whether the number of conversion failures is greater than a set failure threshold; if yes, discard the touch data and generate a non-convertible signal; If not, proceed to step 3; Step three: acquiring touch data conversion parameters between the first operating system and the second operating system, and converting the touch data according to the touch data conversion parameters to obtain converted touch data; Generate a conversion tag according to the conversion touch data; determine whether the conversion tag is successful; if yes, set the number of conversion failures to zero and proceed to step 4; No, the number of conversion failures increases by one and the process goes to step 2; Step 4: Encapsulate the converted touch data into a touch event format 2 corresponding to the second operating system, and package and send it to the second operating system; Step 5: When the second operating system cannot respond to the touch event, a response failure signal is generated; otherwise, the touch conversion is completed.

2. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: The touch data includes a touch type item and a plurality of touch data items.

3. The touch data conversion method in a multi-operating system touch display device according to claim 2, characterized in that: The touch data items include touch point coordinates, pressure values ​​and touch timestamps; the touch types include single-point touch or multi-point touch.

4. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: Generating a touch data label according to the touch data includes: Acquire touch data and determine whether there is a missing touch data item or a missing touch type item in the touch data; if yes, set the touch data label to invalid; if no, set the touch data label to valid; The touch data whose touch data label is set as qualified is pre-processed.

5. The touch data conversion method in a multi-operating system touch display device according to claim 4, characterized in that: The preprocessing includes noise removal, touch point filtering and coordinate normalization.

6. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: The touch data conversion parameters are obtained by: Acquire touch event format 1 of the first operating system and touch event format 2 of the second operating system; Extracting touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; generating a touch type item conversion relationship according to the touch type items and their corresponding available touch type 1 and available touch type 2; Extracting the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; generating a touch data item conversion relationship according to each touch data item and its corresponding available range 1 and available range 2; The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

7. The touch data conversion method in a multi-operating system touch display device according to claim 6, characterized in that: The touch event format is generated according to the touch type item and each touch data item, including: Obtain available touch types corresponding to touch type items and available ranges corresponding to respective touch data items; integrate the available ranges and the corresponding touch type items or respective touch data items into a touch event format; the touch event format includes touch event format one and touch event format two.

8. The touch data conversion method in a multi-operating system touch display device according to claim 6, characterized in that: The step of generating a touch type item conversion relationship according to the touch type item and the corresponding available touch type one and available touch type two includes: Extract each available touch type one from available touch type one; extract each available touch type two from available touch type two; obtain the same touchable type one as the touchable type two, and establish a conversion relationship between the same touchable type two and the touchable type one; and integrate each conversion relationship into a touch type item conversion relationship.

9. The touch data conversion method in a multi-operating system touch display device according to claim 6, characterized in that: The step of generating a touch data item conversion relationship according to each touch data item and the corresponding available range 1 and available range 2 includes: Obtaining the available range 1 and the available range 2 corresponding to each touch data item; establishing a conversion relationship between the available range 1 and the available range 2 of the same touch data item; and integrating each conversion relationship into a touch data item conversion relationship.

10. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: The first operating system is an Android system, and the second operating system is a Windows system.

11. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: The touch data is converted according to the touch data conversion parameter to obtain the converted touch data, including: Extracting the touch type item conversion relationship and the conversion relationship of each touch data item in the touch data conversion parameter; extracting the touch type item and each touch data item in the touch data; converting the touch type item into the conversion type item according to the touch type item conversion relationship; converting the corresponding touch data item into the conversion data item according to the conversion relationship of each touch data item; integrating the conversion type item and each conversion data item into the conversion touch data.

12. The touch data conversion method in a multi-operating system touch display device according to claim 1, characterized in that: The step of generating a conversion label according to the conversion touch data includes: Extracting a conversion type item and each conversion data item in the conversion touch data; Determine whether there is a missing conversion type item or a missing conversion data item in the conversion touch data; if yes, set the conversion label to failure; if no, when the conversion type item is not within the available touch type two, or each conversion data item is not within its corresponding available range two; set the conversion label to failure; otherwise, set the conversion label to success.

13. A touch data conversion module in a multi-operating system touch display device, based on the touch data conversion method in an operating system touch display device according to any one of claims 1 to 12, characterized in that: include: A touch data acquisition unit, a conversion parameter generation unit and a touch data conversion unit; The touch data acquisition unit is used to acquire touch data corresponding to the touch event generated by the first operating system; Generate a touch data label according to the touch data; The conversion parameter generating unit: obtains the touch event format 1 of the first operating system and the touch event format 2 of the second operating system; generates touch data conversion parameters according to the touch event format 1 and the touch event format 2; The touch data conversion unit: when the touch data tag is valid, acquires the touch data and the touch data conversion parameters between the first operating system and the second operating system; converts the touch data according to the touch data conversion parameters to obtain converted touch data; Generates a conversion label based on the conversion touch data.

14. The touch data conversion module in the multi-operating system touch display device according to claim 13, characterized in that: The touch data conversion module further includes a data encapsulation unit: when the conversion tag is successful, it obtains the converted touch data, encapsulates the converted touch data into a touch event format 2 corresponding to the second operating system, and packages and sends the data to the second operating system.

15. The touch data conversion module in the multi-operating system touch display device according to claim 13, characterized in that: The step of generating touch data conversion parameters according to touch event format 1 and touch event format 2 includes: Extracting the touch type items in touch event format 1 and touch event format 2 and their corresponding available touch type 1 and available touch type 2; extracting each available touch type 1 in available touch type 1; extracting each available touch type 2 in available touch type 2; obtaining the same touchable type 1 as the touchable type 2, and establishing a conversion relationship between the same touchable type 2 and the touchable type 1; and Integrate each conversion relationship into a touch type item conversion relationship; Extracting the same touch data items in touch event format 1 and touch event format 2 and their corresponding available range 1 and available range 2; obtaining the available range 1 and available range 2 corresponding to each touch data item; establishing a conversion relationship between the available range 1 and available range 2 of the same touch data item; and Integrate each conversion relationship into a touch data item conversion relationship; The touch type item conversion relationship and a plurality of touch data item conversion relationships are integrated into a touch data conversion parameter.

Images