A terminal device compatibility adaptation method and system

Abstract

This invention discloses a terminal device compatibility adaptation method and system, belonging to the field of device compatibility technology. The method includes: a client obtaining a device support capability table, a compatibility detection strategy, and a compatibility adaptation strategy from a server; the client executing device functions according to the device support capability table and the compatibility adaptation strategy; when the device function execution fails, the client retrying according to the compatibility detection strategy; when the device function still fails after retrying, the client reporting error information to the server; the server making a decision based on the error information, determining whether the error information meets preset conditions; when the error information meets the preset conditions, the server updating the device support capability table. This invention eliminates the need for laboratory testing and user feedback, saving testing resources, and can cover various new models and systems, improving device coverage. It also eliminates the need for manual maintenance of compatibility issue record tables, saving maintenance costs.

Description

Technical Field

[0001] This invention belongs to the field of device compatibility technology, specifically relating to a terminal device compatibility adaptation method and system. Background Technology

[0002] The diversity of terminal devices and system versions, along with different combinations of systems and terminals, can lead to various compatibility issues.

[0003] Most existing compatibility solutions identify incompatible scenarios through user feedback or testing in a laboratory environment, and manually maintain a compatibility issue log in the background. The client then requests the backend interface to verify the functionality and select a suitable compatibility adaptation solution.

[0004] However, laboratory and testing environments cannot exhaustively cover all scenarios. Relying on user feedback increases latency and also fails to cover all scenarios. Furthermore, the release of new device models and operating systems leads to new compatibility issues. Additionally, the need for manual maintenance of compatibility issue logs increases the maintenance costs of software products. Summary of the Invention

[0005] To address the limitations of existing technologies, such as the inability to exhaustively cover all scenarios in laboratory and testing environments, the increased reliance on user feedback leading to delays and continued inability to encompass all scenarios, and the emergence of new compatibility issues with the release of new models and systems, as well as the increased maintenance costs associated with manually maintaining compatibility issue logs, this invention provides a terminal device compatibility adaptation method and system.

[0006] First aspect

[0007] This invention provides a terminal device compatibility adaptation method, comprising:

[0008] S101: The client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server;

[0009] S102: The client executes device functions according to the device support capability table and the compatibility adaptation strategy;

[0010] S103: When the device function fails to execute, the client retryes according to the compatibility detection strategy.

[0011] S104: When the device function still fails after retrying, the client reports an error message to the server;

[0012] S105: The server makes a decision based on the error information and determines whether the error information meets the preset conditions;

[0013] S106: When the error message meets the preset conditions, the server updates the device support capability table.

[0014] Second aspect

[0015] This invention provides a terminal device compatibility adaptation system, comprising:

[0016] The client-side compatibility detection module is used by the client to obtain the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server.

[0017] The client compatibility detection module is also used for the client to execute device functions according to the device support capability table and the compatibility adaptation strategy;

[0018] The client compatibility detection module is also used to allow the client to retry according to the compatibility detection strategy when the device function fails to execute.

[0019] The client data collection and reporting module is used to report error information to the server when the device function still fails after retrying.

[0020] The server-side compatibility decision module is used by the server to make decisions based on the error information and determine whether the error information meets preset conditions.

[0021] The server-side device support capability query and storage module is used to update the device support capability table when the error information meets the preset conditions.

[0022] Compared with the prior art, the present invention has at least the following beneficial technical effects:

[0023] In this invention, after the client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server, it autonomously executes the function. During the function execution process, it automatically detects compatibility issues and submits them to the server. The server makes a decision based on the error information. When the error information meets the preset conditions, the server updates the device support capability table. This method eliminates the need for laboratory testing and user feedback, saving testing resources. It can cover various new models and systems, improving device coverage. Furthermore, it eliminates the need for manual maintenance of the compatibility issue record table, saving maintenance costs. Attached Figure Description

[0024] The preferred embodiments will now be described in a clear and easy-to-understand manner, in conjunction with the accompanying drawings, to further explain the above-mentioned characteristics, technical features, advantages, and implementation methods of the present invention.

[0025] Figure 1 This is a flowchart illustrating a terminal device compatibility adaptation method provided by the present invention;

[0026] Figure 2 This is a schematic diagram of another terminal device compatibility adaptation method provided by the present invention;

[0027] Figure 3 This is a schematic diagram of the structure of a terminal device compatibility adaptation system provided by the present invention. Detailed Implementation

[0028] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings and other implementation methods can be obtained based on these drawings without any creative effort.

[0029] To keep the drawings concise, each figure only schematically shows the parts relevant to the invention, and these do not represent the actual structure of the product. Furthermore, to facilitate understanding, in some figures, only one of components with the same structure or function is schematically depicted, or only one is labeled. In this document, "one" not only means "only one," but can also mean "more than one."

[0030] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

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

[0032] Furthermore, in the description of this invention, the terms "first," "second," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0033] Example 1

[0034] In one embodiment, refer to the appendix to the specification. Figure 1 The diagram shows a flowchart of a terminal device compatibility adaptation method provided by the present invention.

[0035] Reference manual attached Figure 2The diagram illustrates a flowchart of another terminal device compatibility adaptation method provided by the present invention.

[0036] This invention provides a terminal device compatibility adaptation method, comprising:

[0037] S101: The client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server.

[0038] The device support capability table, compatibility detection strategy, and compatibility adaptation strategy are stored on the server.

[0039] The device support capability table is a data structure used to describe the capabilities and characteristics of terminal devices.

[0040] Furthermore, the device support capability table includes: device name, function name, operating system version, function adaptation index, and detection strategy index.

[0041] The compatibility adaptation strategies include: hard-coding strategy and soft-coding strategy, with hard-coding strategy being the default strategy.

[0042] Furthermore, hard-coded policies are typically default policies, based on fixed rules and settings that guide clients on how to adapt to device functionality. These policies are usually pre-set during the manufacturing or configuration of the terminal device and are not easily changed at runtime. Hard-coded policies may include a set of default parameters, rules, or operations to ensure the stability and performance of device functionality.

[0043] Furthermore, software coding strategies can typically be adjusted and configured as needed. Unlike hardware coding strategies, software coding strategies can be flexibly adjusted at runtime to meet specific compatibility requirements or solve specific problems. Software coding strategies may include algorithms, settings, parameters, or adaptation rules, allowing clients to have more granular control and adaptation over device functionality as needed.

[0044] S102: The client executes device functions based on the device support capability table and compatibility adaptation strategy.

[0045] Specifically, the client identifies the terminal device and functions based on the device support capability table. This includes reviewing information such as the device name, function name, and operating system version to determine the functions and devices the client will be performing. Based on the information in the device support capability table, the client selects an adaptation strategy, typically including a hardware encoding strategy and a software encoding strategy. The hardware encoding strategy is usually the default, but the client can choose a software encoding strategy as needed for more flexible device function adaptation. The client uses the selected adaptation strategy to perform the device functions, which may include calling specific APIs, sending requests to the device, or performing other necessary operations to achieve the required functionality.

[0046] S103: When a device function fails to execute, the client retryes according to the compatibility detection policy.

[0047] Specifically, when a device function fails, the client should capture the relevant error information or exception. This information may include error codes, error messages, stack traces, or other failure-related data. The client should determine whether a retry is necessary based on the captured error information and compatibility detection policies.

[0048] Optionally, a compatibility testing strategy may include the following considerations:

[0049] (1) Specific error codes: Some error codes may require retries, while others may indicate that the problem cannot be solved by retries.

[0050] (2) Frequency of error occurrence: If the same error occurs repeatedly, it may be necessary to retry, but if the error occurs infrequently, different measures may be required.

[0051] In one possible implementation, S103 specifically involves the client retrying according to the compatibility detection strategy, with the number of retries being 3.

[0052] Specifically, the client should monitor the result of the function execution after each retry. If the retry is successful, the task is completed. If the retry fails, the client should continue to retry until the maximum number of retries specified by the compatibility detection policy is reached (3 times in this embodiment).

[0053] In this invention, a retry mechanism can increase the reliability of a system or application. Sometimes, device functionality failure may be due to transient or network problems; retries can correct these problems and allow the function to execute successfully. By allowing multiple retries, even if a device function fails on the initial attempt, it has a chance to succeed in subsequent attempts. This improves the system's fault tolerance, making it more capable of handling temporary or transient problems.

[0054] S104: When the device function still fails after retrying, the client reports an error message to the server.

[0055] In one possible implementation, S104 specifically includes sub-steps S1041 and S1042:

[0056] S1041: When the device function fails after a retry, the client collects error information.

[0057] S1042: The client reports an error message to the server.

[0058] In this invention, the aggregation and analysis of error information can provide data support for server-side decision-making. By collecting and reporting error information, the server can more easily locate and diagnose the causes of device malfunctions. This helps to quickly identify and resolve problems, improving system maintainability.

[0059] S105: The server makes a decision based on the error message and determines whether the error message meets the preset conditions.

[0060] Optionally, the preset conditions may be: the number of errors exceeds a preset number, an error code exists, or the error message contains preset keywords, etc.

[0061] S106: When the error message meets the preset conditions, the server updates the device support capability table.

[0062] In this invention, by monitoring and analyzing error information, the server can detect potential problems more promptly and then take necessary actions to resolve them. By updating the device support capability table, the server can ensure that terminal devices can adapt to new environments, new functions, or new problems. This helps improve device compatibility, enabling it to cope with ever-changing needs.

[0063] In one possible implementation, S106 specifically involves: the server changing the compatibility adaptation strategy of the terminal device from a hardware encoding strategy to a software encoding strategy, and updating the device support capability table.

[0064] Furthermore, when an application with the same device and system is launched again, the software encoding strategy will be selected directly based on the device's support capabilities table, avoiding attempts to use the hardware encoding strategy.

[0065] In this invention, if a hardware coding strategy cannot solve certain problems or adapt to certain functions, a software coding strategy may provide more control and options to solve these problems, helping to address complex compatibility challenges. Switching from a hardware coding strategy to a software coding strategy allows for more flexible adaptation to device functions. Software coding strategies typically allow for more parameter adjustments and customization settings to better meet the requirements of various types of hardware adaptation.

[0066] Compared with the prior art, the present invention has at least the following beneficial technical effects:

[0067] In this invention, after the client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server, it autonomously executes the function. During the function execution process, it automatically detects compatibility issues and submits them to the server. The server makes decisions based on the error information, and when the error information meets preset conditions, the server updates the device support capability table. This method eliminates the need for laboratory testing and user feedback, saving testing resources. It can cover various new models and systems, improving device coverage. Furthermore, it eliminates the need for manual maintenance of the compatibility issue record table, saving maintenance costs.

[0068] Example 2

[0069] Reference manual attached Figure 3 The diagram shows a structural schematic of a terminal device compatibility adaptation system provided by the present invention.

[0070] In one embodiment, the terminal device compatibility adaptation system 20 provided by the present invention includes:

[0071] The client compatibility detection module 201 is used by the client to obtain the device support capability table, compatibility detection strategy and compatibility adaptation strategy from the server.

[0072] The client compatibility detection module 201 is also used for the client to execute device functions according to the device support capability table and the compatibility adaptation strategy;

[0073] The client compatibility detection module 201 is also used to retry the device function according to the compatibility detection strategy when the device function fails to execute.

[0074] The client data collection and reporting module 202 is used to report error information to the server when the device function still fails after retrying.

[0075] The server-side compatibility decision module 203 is used for the server to make a decision based on the error information and determine whether the error information meets preset conditions.

[0076] The server-side device support capability query and storage module 204 is used to update the device support capability table when the error information meets the preset conditions.

[0077] In one possible implementation, the device support capability table includes: device name, function name, operating system version, function adaptation index, and detection strategy index;

[0078] The compatibility adaptation strategy includes a hard-coded strategy and a soft-coded strategy, wherein the hard-coded strategy is the default strategy.

[0079] In one possible implementation, the client compatibility detection module 201 is specifically used for: the client to retry according to the compatibility detection strategy, and the number of retries is 3.

[0080] In one possible implementation, the client data collection and reporting module 202 is specifically used for:

[0081] When the device function fails to retry after a retrieval, the client collects error information.

[0082] The client reports error information to the server.

[0083] In one possible implementation, the server-side device support capability query and storage module 204 is specifically used to: change the compatibility adaptation strategy of the terminal device from a hard encoding strategy to a soft encoding strategy, and update the device support capability table.

[0084] In one possible implementation, the terminal device compatibility adaptation system 20 further includes a compatibility detection strategy query and storage module 205, used for querying and storing compatibility detection strategies.

[0085] The compatibility adaptation strategy query and storage module 206 is used to query and store compatibility adaptation strategies.

[0086] The terminal device compatibility adaptation system 20 provided by the present invention can realize the steps and effects of the terminal device compatibility adaptation method in the above embodiment 1. To avoid repetition, the present invention will not repeat them.

[0087] Compared with the prior art, the present invention has at least the following beneficial technical effects:

[0088] In this invention, after the client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server, it autonomously executes the function. During the function execution process, it automatically detects compatibility issues and submits them to the server. The server makes a decision based on the error information. When the error information meets the preset conditions, the server updates the device support capability table. This method eliminates the need for laboratory testing and user feedback, saving testing resources. It can cover various new models and systems, improving device coverage. Furthermore, it eliminates the need for manual maintenance of the compatibility issue record table, saving maintenance costs.

[0089] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0090] The above embodiments merely illustrate several implementation methods of the present invention, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this invention patent should be determined by the appended claims.

Claims

1. A terminal device compatibility adaptation method, characterized by, include: S101: The client obtains the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server; S102: The client executes device functions according to the device support capability table and the compatibility adaptation strategy; S103: When the device function fails to execute, the client retryes according to the compatibility detection strategy. S104: When the device function still fails after retrying, the client reports an error message to the server; S105: The server makes a decision based on the error information and determines whether the error information meets the preset conditions; S106: When the error message meets the preset conditions, the server updates the device support capability table; The device support capability table includes: device name, function name, operating system version, function adaptation index, and detection strategy index; The compatibility adaptation strategy includes: a hard-coded strategy and a soft-coded strategy, wherein the hard-coded strategy is the default strategy; Specifically, S106 is as follows: The server changes the compatibility adaptation strategy for the terminal device from a hardware encoding strategy to a software encoding strategy and updates the device support capability table.

2. The method of claim 1, wherein, Specifically, S103 is: The client will retry according to the compatibility detection strategy, with a maximum of 3 retries.

3. The terminal device compatibility adaptation method according to claim 1, characterized in that, S104 specifically includes: S1041: When the device function fails to retry after a retrieval, the client collects error information; S1042: The client reports an error message to the server.

4. A terminal device compatibility adaptation system, characterized in that, include: The client-side compatibility detection module is used by the client to obtain the device support capability table, compatibility detection strategy, and compatibility adaptation strategy from the server. The client compatibility detection module is also used for the client to execute device functions according to the device support capability table and the compatibility adaptation strategy; The client compatibility detection module is also used to allow the client to retry according to the compatibility detection strategy when the device function fails to execute. The client data collection and reporting module is used to report error information to the server when the device function still fails after retrying. The server-side compatibility decision module is used by the server to make decisions based on the error information and determine whether the error information meets preset conditions. The server-side device support capability query and storage module is used to update the device support capability table when the error information meets the preset conditions. The device support capability table includes: device name, function name, operating system version, function adaptation index, and detection strategy index; The compatibility adaptation strategy includes: a hard-coded strategy and a soft-coded strategy, wherein the hard-coded strategy is the default strategy; Specifically, the server-side device's capability query and storage module is used for: The server changes the compatibility adaptation strategy for the terminal device from a hardware encoding strategy to a software encoding strategy and updates the device support capability table.

5. A terminal device compatibility adaptation system according to claim 4, characterized in that, The client compatibility detection module is specifically used for: The client will retry according to the compatibility detection strategy, with a maximum of 3 retries.

6. A terminal device compatibility adaptation system according to claim 4, characterized in that, The client data collection and reporting module is specifically used for: When the device function fails to retry after a retrieval, the client collects error information. The client reports error information to the server.

Images