Application adaptation method and device of operating system and computer equipment

Abstract

The invention relates to an application adaptation method and device of an operating system and computer equipment. The method comprises the following steps: acquiring system function information and system architecture information of an operating system and application function information and function demand information of an application program, and identifying function condition information of each application function of the application program and function architecture information of each system function of the operating system; constructing function interaction logic between each application function and each system function based on the function condition information of each application function and the function architecture information of each system function; the method comprises the following steps: acquiring interaction information of each front-end application of an application program and a front-end function interaction mechanism between the application program and each application function of the application program, and constructing front-end interaction architecture information of the application program and an operating system based on the front-end function interaction mechanism and function interaction logic. By adopting the method, the running effect of the intelligent insurance service application in a new generation of operating system can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of system adaptation, and in particular to an operating system application adaptation method, device and computer equipment. Background Art

[0002] With the development of the new generation of operating systems, it has achieved complete Android-free, with self-developed kernels, runners, frameworks and application ecosystems. In order to adapt to the operation mode of the new generation of operating systems and to be able to run normally on the new replacement operating system, the smart insurance service application client needs to adapt to the above system and develop a set of dedicated applications. Therefore, how to improve the operation adaptation effect of the smart insurance service application on the new generation of operating systems is the current application focus.

[0003] The existing technology has not adapted the new smart insurance service application in the new generation operating system, making the smart insurance service application unable to support the use of mobile devices of the new generation system, resulting in poor operation of the smart insurance service application in the new generation operating system. Summary of the invention

[0004] Based on this, it is necessary to provide an operating system application adaptation method, apparatus, computer device, computer-readable storage medium and computer program product to address the above technical issues.

[0005] In a first aspect, the present application provides an application adaptation method for an operating system, comprising:

[0006] Acquiring system function information of an operating system, system architecture information of the operating system, application function information of an application program, and function requirement information of the application program, and identifying function condition information of each application function of the application program based on the application function information of the application program and the function requirement information of the application program;

[0007] Based on the system function information of the operating system and the system architecture information of the operating system, functional architecture information of each system function of the operating system is identified, and based on the functional condition information of each application function and the functional architecture information of each system function, functional interaction logic between each application function and each system function is constructed;

[0008] Collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and build the front-end interaction architecture information of the application and the operating system based on the front-end function interaction mechanism and the function interaction logic.

[0009] Optionally, the identifying the function condition information of each application function of the application based on the application function information of the application and the function requirement information of the application includes:

[0010] Based on the application function information of the application, identifying the function type of each application function of the application and the interaction logic of each application function, and based on the function requirement information of the application, identifying the function interaction requirement information of each application function;

[0011] Based on the interaction logic of each application function and the functional interaction requirement information of each application function, the interaction condition information of each application function is identified, and the function type of each application function and the interaction condition information of each application function are used as the functional condition information of each application function.

[0012] Optionally, the identifying the functional architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system includes:

[0013] Splitting the system architecture information of the operating system into sub-architecture information of each sub-system architecture, and identifying architecture specification information corresponding to each sub-architecture information;

[0014] Splitting the system function information into subsystem function information of each system function, and identifying architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information;

[0015] The architecture usage information of each system function for each of the subsystem architectures and the architecture specification information corresponding to each subsystem architecture are used as the functional architecture information of each system function.

[0016] Optionally, constructing the functional interaction logic between each application function and each system function based on the functional condition information of each application function and the functional architecture information of each system function includes:

[0017] Based on the function type of each application function, query the target system functions applied by each application function in the system application database;

[0018] For each application function, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture;

[0019] The architecture interaction condition information of the application function to each subsystem architecture and the interaction call information of the application function to each subsystem architecture are used as the function interaction logic between the application function and each target system function applied by the application function.

[0020] Optionally, the identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture includes:

[0021] Based on the architecture usage information of each target system function for each subsystem architecture, identifying the operation call logic of each target system function for each subsystem architecture, and the operation support condition information of each subsystem architecture for each target system function;

[0022] Based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, identifying the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function, and using the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture;

[0023] Based on the interaction logic of the application function and the operation calling logic of each target system function for each subsystem architecture, the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are identified, and the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are used as the interaction calling information of the application function for each subsystem architecture.

[0024] Optionally, constructing the front-end interaction architecture information of the application program and the operating system based on the front-end function interaction mechanism and the function interaction logic includes:

[0025] Based on the front-end function interaction mechanism, identify the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component, and based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function, identify the target front-end interaction component corresponding to each application function;

[0026] Based on the target front-end interaction components corresponding to each application function and the functional interaction logic between the target system functions applied by each application function, a functional interaction architecture between each application function and each system function is constructed through a hybrid development program;

[0027] The functional interaction architecture between each of the application functions and each of the system functions is used as the front-end interaction architecture information between the application program and the operating system.

[0028] In a second aspect, the present application also provides an application adaptation device for an operating system, including:

[0029] an acquisition module, configured to acquire system function information of an operating system, system architecture information of the operating system, application function information of an application program, and function requirement information of the application program, and identify function condition information of each application function of the application program based on the application function information of the application program and the function requirement information of the application program;

[0030] an identification module, configured to identify functional architecture information of each system function of the operating system based on system function information of the operating system and system architecture information of the operating system, and to construct functional interaction logic between each application function and each system function based on functional condition information of each application function and functional architecture information of each system function;

[0031] A construction module is used to collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and based on the front-end function interaction mechanism and the function interaction logic, construct the front-end interaction architecture information of the application and the operating system.

[0032] Optionally, the acquisition module is specifically used to:

[0033] Based on the application function information of the application, identifying the function type of each application function of the application and the interaction logic of each application function, and based on the function requirement information of the application, identifying the function interaction requirement information of each application function;

[0034] Based on the interaction logic of each application function and the functional interaction requirement information of each application function, the interaction condition information of each application function is identified, and the function type of each application function and the interaction condition information of each application function are used as the functional condition information of each application function.

[0035] Optionally, the identification module is specifically used to:

[0036] Splitting the system architecture information of the operating system into sub-architecture information of each sub-system architecture, and identifying architecture specification information corresponding to each sub-architecture information;

[0037] Splitting the system function information into subsystem function information of each system function, and identifying architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information;

[0038] The architecture usage information of each system function for each of the subsystem architectures and the architecture specification information corresponding to each subsystem architecture are used as the functional architecture information of each system function.

[0039] Optionally, the identification module is specifically used to:

[0040] Based on the function type of each application function, query the target system functions applied by each application function in the system application database;

[0041] For each application function, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture;

[0042] The architecture interaction condition information of the application function to each subsystem architecture and the interaction call information of the application function to each subsystem architecture are used as the function interaction logic between the application function and each target system function applied by the application function.

[0043] Optionally, the building module is specifically used for:

[0044] Based on the architecture usage information of each target system function for each subsystem architecture, identifying the operation call logic of each target system function for each subsystem architecture, and the operation support condition information of each subsystem architecture for each target system function;

[0045] Based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, identifying the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function, and using the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture;

[0046] Based on the interaction logic of the application function and the operation calling logic of each target system function for each subsystem architecture, the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are identified, and the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are used as the interaction calling information of the application function for each subsystem architecture.

[0047] Optionally, the building module is specifically used for:

[0048] Based on the front-end function interaction mechanism, identify the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component, and based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function, identify the target front-end interaction component corresponding to each application function;

[0049] Based on the target front-end interaction components corresponding to each application function and the functional interaction logic between the target system functions applied by each application function, a functional interaction architecture between each application function and each system function is constructed through a hybrid development program;

[0050] The functional interaction architecture between each of the application functions and each of the system functions is used as the front-end interaction architecture information between the application program and the operating system.

[0051] In a third aspect, the present application provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of any one of the methods in the first aspect are implemented.

[0052] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of any one of the methods in the first aspect are implemented.

[0053] In a fifth aspect, the present application provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of any one of the methods in the first aspect are implemented.

[0054] The application adaptation method, device and computer equipment of the above operating system obtain the system function information of the operating system, the system architecture information of the operating system, the application function information of the application, and the function requirement information of the application, and identify the function condition information of each application function of the application based on the application function information of the application and the function requirement information of the application; identify the function architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system, and build the function interaction logic between each application function and each system function based on the function condition information of each application function and the function architecture information of each system function; collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and build the front-end interaction architecture information of the application and the operating system based on the front-end function interaction mechanism and the function interaction logic. This solution improves the accuracy of identifying the interaction and call between the application and the operating system by comprehensively analyzing the application function information and function requirement information of the application, the system function information of the operating system, and the system architecture information. Then, this solution, by splitting each application function and system function, accurately identifies the interaction, call, reference, and data transmission relationship between each application function and each system function, as well as the system architecture from the perspective of function adaptation. Finally, this solution constructs the front-end interaction architecture information of the application and the operating system by identifying each application function based on the above information, the functional interaction logic between each system function, and the front-end functional interaction mechanism between each application function of the application, so that during actual interactive communication, the influence of the specificity of the operating system on communication interaction and program adaptation is eliminated through the front-end scaffolding function, thereby comprehensively improving the operation effect of the smart insurance service application in the new generation of operating systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are 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.

[0056] Figure 1 A schematic diagram of a flow chart of an application adaptation method of an operating system in one embodiment;

[0057] Figure 2 A schematic diagram of a flow chart of an example of application adaptation of an operating system in one embodiment;

[0058] Figure 3 A structural block diagram of an application adapter device for an operating system in one embodiment;

[0059] Figure 4 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0061] The application adaptation method of the operating system provided in the embodiment of the present application can be applied to the application environment of the application adaptation of the operating system. Among them, the method can be applied to the terminal, can also be applied to the server, and can also be applied to the system including the terminal and the server, and is realized through the interaction between the terminal and the server. Among them, the terminal can be, but is not limited to, various personal computers, laptops, medium-sized computers, etc. Among them, the terminal comprehensively analyzes the application function information and function requirement information of the application, the system function information of the operating system, and the system architecture information, thereby improving the recognition accuracy of the interaction and call between the application and the operating system. Then, this scheme, by splitting each application function and the system function, accurately identifies the interaction, call, reference, and data transmission relationship between each application function and each system function and the system architecture from the perspective of each function adaptation. Finally, this scheme constructs the front-end interaction architecture information of the application and the operating system through the functional interaction logic between each application function identified based on the above information and each system function, and the front-end functional interaction mechanism between each application function of the application obtained, so that in actual interactive communication, through the front-end scaffolding function, the specificity of the operating system is eliminated. The influence of the communication interaction and program adaptation, thereby comprehensively improving the operation effect of the smart insurance service application in the new generation of operating systems.

[0062] In an exemplary embodiment, Figure 1 As shown, a method for application adaptation of an operating system is provided, and the method is applied to a terminal as an example for explanation, including the following steps S101 to S103. Among them:

[0063] Step S101, obtain system function information of the operating system, system architecture information of the operating system, application function information of the application, and function requirement information of the application, and identify function condition information of each application function of the application based on the application function information of the application and the function requirement information of the application.

[0064] In this embodiment, the terminal obtains the system function information of the operating system and the system architecture information of the operating system by collecting information from the operating system. The operating system is a new generation terminal operating system, such as the Hongmeng operating system, and the system function information of the operating system includes the subsystem function information of each system function, wherein each subsystem function information includes the function information contained in each subsystem function and the system architecture information that can be called by each subsystem function. Then, the terminal collects the application function information of the application and the function requirement information of the application on the application side. The application function information of the application includes the function type and interaction logic of each application function. The function type is used to characterize the function type corresponding to each application function, such as query function, consultation function, business function, and link function. The function requirement information includes the function interaction requirement information of each application function. Then, the terminal identifies the function condition information of each application function of the application based on the application function information of the application and the function requirement information of the application. The function condition information includes the function type of each application function and the interaction condition information of each application function. The specific identification process will be described in detail later.

[0065] Step S102, based on the system function information of the operating system and the system architecture information of the operating system, identify the functional architecture information of each system function of the operating system, and based on the functional condition information of each application function and the functional architecture information of each system function, construct the functional interaction logic between each application function and each system function.

[0066] In this embodiment, the terminal identifies the functional architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system, and constructs the functional interaction logic between each application function and each system function based on the functional condition information of each application function and the functional architecture information of each system function. Among them, the functional interaction logic is used to characterize the changes, data interactions, and application processes of the system functions, and the changes, data interactions, and application processes of the corresponding application programs. That is, the functional interaction logic is an interactive bridge between the system functions and the application functions. The way to build this interactive bridge is to combine native code with Web technology through a hybrid development framework to achieve cross-platform operation. Among them, the core of the hybrid development technology applied by the hybrid development framework is to realize the two-way communication layer between the native and Web ends, namely JSBridge. JSBridge is a bridge built with JavaScript, with one end being Web and the other end being Native. It allows Native to call the JavaScript code of Web, and Web can also call the native code of Native. The original Cordova technology framework has an iteration lag and cannot support Android, iOS, and Hongmeng operating systems. Therefore, through the self-developed hybrid development framework (WingsJs), a unified front-end scaffolding is provided for Android, iOS, and Hongmeng. The front-end interacts with Hongmeng natively without worrying about the implementation details, which smooths out the differences between the front-ends on the three operating systems, achieves experience consistency in the multi-platform architecture, and lays a good foundation for subsequent iterative upgrades.

[0067] Step S103, collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and build the front-end interaction architecture information of the application and the operating system based on the front-end function interaction mechanism and the function interaction logic.

[0068] In this embodiment, the terminal collects each front-end application interaction information of the application, the front-end function interaction mechanism between each application function of the application, and builds the front-end interaction architecture information of the application and the operating system based on the front-end function interaction mechanism and the function interaction logic. Among them, the front-end interaction architecture information is the front-end UI components and interaction components (for example, buttons, text boxes, lists, cards, etc.) in the client where the terminal's front-end application is located, and the interaction mechanism between the application functions of the application when performing data interaction, information communication, and function screening. The way to build the front-end interaction architecture information of the application and the operating system is to build the architecture information through a hybrid development framework. The specific construction process will be described in detail later.

[0069] Based on the above scheme, by splitting each application function and system function, the interaction, call, reference, and data transmission relationship between each application function and each system function and the system architecture can be accurately identified from the perspective of function adaptation. Finally, this scheme constructs the front-end interaction architecture information of the application and the operating system by identifying each application function based on the above information, the functional interaction logic between each system function, and the front-end functional interaction mechanism between each application function of the application, so that during actual interactive communication, the influence of the specificity of the operating system on communication interaction and program adaptation can be eliminated through the front-end scaffolding function, thereby comprehensively improving the operation effect of the smart insurance service application in the new generation of operating systems.

[0070] Optionally, based on the application function information of the application and the function requirement information of the application, function condition information of each application function of the application is identified, including: based on the application function information of the application, the function type of each application function of the application and the interaction logic of each application function are identified, and based on the function requirement information of the application, the function interaction requirement information of each application function is identified; based on the interaction logic of each application function and the function interaction requirement information of each application function, the interaction condition information of each application function is identified, and the function type of each application function and the interaction condition information of each application function are used as the function condition information of each application function.

[0071] In this embodiment, the terminal identifies the function type of each application function of the application and the interaction logic of each application function based on the application function information of the application, and identifies the function interaction requirement information of each application function based on the function requirement information of the application. The function interaction requirement information is used to characterize the requirement information of each application function on the system architecture and system function during data interaction and function application.

[0072] Then, the terminal identifies the interaction condition information of each application function based on the interaction logic of each application function and the functional interaction requirement information of each application function, wherein the interaction condition information is the system architecture and system function requirement information of the different interaction logics of the application function.

[0073] Finally, the terminal uses the function type of each application function and the interaction condition information of each application function as the function condition information of each application function.

[0074] Based on the above solution, by comprehensively analyzing the application function information and interaction logic, the interaction condition information of each application function is identified, thereby improving the comprehensiveness and accuracy of the identification of the functional condition information of the application function.

[0075] Optionally, based on the system function information of the operating system and the system architecture information of the operating system, functional architecture information of each system function of the operating system is identified, including: splitting the system architecture information of the operating system into sub-architecture information of each subsystem architecture, and identifying architecture specification information corresponding to each sub-architecture information; splitting the system function information into subsystem function information of each system function, and based on each subsystem function information and each sub-architecture information, identifying architecture usage information of each system function for each subsystem architecture; using the architecture usage information of each system function for each subsystem architecture and the architecture specification information corresponding to each subsystem architecture as the functional architecture information of each system function.

[0076] In this embodiment, the terminal divides the system architecture information of the operating system into sub-architecture information of each subsystem architecture, and identifies the architecture specification information corresponding to each sub-architecture information. The architecture specification information is used to characterize the function type of the application function to which the sub-architecture information can be applied, and the support information of the sub-architecture information for the application function.

[0077] Then, the terminal splits the system function information into subsystem function information of each system function, and identifies the architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information. Each system function can apply one or more subsystem architectures.

[0078] Finally, the terminal uses the architecture usage information of each system function for each subsystem architecture and the architecture specification information corresponding to each subsystem architecture as the functional architecture information of each system function.

[0079] Based on the above solution, after splitting each system function and splitting the system function information, the corresponding relationship between each system function and the system architecture is identified, thereby improving the comprehensiveness of the analysis of the operating system.

[0080] Optionally, based on the functional condition information of each application function and the functional architecture information of each system function, construct the functional interaction logic between each application function and each system function, including: based on the functional type of each application function, querying the target system functions applied by each application function in the system application database; for each application function, based on the interaction condition information of the application function and the architecture usage information of each subsystem architecture of each target system function, identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture; using the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture as the functional interaction logic between the application function and the target system functions applied by the application function.

[0081] In this embodiment, the terminal queries the target system functions applied by each application function in the system application database based on the function type of each application function. Then, for each application function, the terminal identifies the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture. Among them, the interaction call information is used to characterize the underlying call logic between the application function and the subsystem architecture. The architecture interaction condition information is the architecture operation information of each subsystem architecture when each application function is running.

[0082] Finally, the terminal uses the architecture interaction condition information of the application function to each subsystem architecture, and the interactive call information of the application function to each subsystem architecture as the functional interaction logic between the application function and each target system function applied by the application function.

[0083] Based on the above scheme, by identifying the interaction conditions and interaction call information between each application function and each subsystem architecture, the functional interaction logic between the application function and the target system functions to which the application function is applied is identified, thereby improving the accuracy and comprehensiveness of the identification of the interaction functions between the application program and the operating system.

[0084] Optionally, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture are identified, including: based on the architecture usage information of each target system function for each subsystem architecture, the operation call logic of each target system function for each subsystem architecture and the operation support condition information of each subsystem architecture for each target system function are identified; based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, the operation support condition of each subsystem architecture for the application function is identified, and The operation support scope of each subsystem architecture for the application function, and the operation support conditions of each subsystem architecture for the application function, as well as the operation support scope of each subsystem architecture for the application function, are used as the architecture interaction condition information of the application function for each subsystem architecture; based on the interaction logic of the application function and the operation call logic of each target system function for each subsystem architecture, the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are identified, and the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are used as the interaction call information of the application function for each subsystem architecture.

[0085] In this embodiment, the terminal identifies the operation call logic of each target system function for each subsystem architecture and the operation support condition information of each subsystem architecture for each target system function based on the architecture usage information of each target system function for each subsystem architecture. The operation call logic is the operation information of each subsystem architecture when the target system function is running, and the operation support condition information is the operation mode of each subsystem architecture and the operation degree that can support the operation of the target system function.

[0086] Then, based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, the terminal identifies the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function. The operation support condition is the operation mode of each subsystem architecture and the application function that can be supported by the operation degree. The operation support range is the operation degree of the application function that can be supported by the operation mode of each subsystem architecture and the operation degree.

[0087] Afterwards, the terminal uses the operation support conditions of each subsystem architecture for the application function and the operation support scope of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture. Finally, based on the interaction logic of the application function and the operation call logic of each target system function for each subsystem architecture, the terminal identifies the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture, and uses the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture as the interaction call information of the application function for each subsystem architecture.

[0088] Based on the above scheme, by respectively identifying the operation correlation information between the subsystem architecture and the target system function, as well as the operation correlation information between the subsystem architecture and the application function, and then analyzing the architecture interaction condition information of the application function on each subsystem architecture, as well as the interaction call information, the comprehensiveness and accuracy of the analysis are improved.

[0089] Optionally, based on the front-end functional interaction mechanism and the functional interaction logic, construct the front-end interaction architecture information of the application and the operating system, including: based on the front-end functional interaction mechanism, identifying the front-end interaction functional information of each front-end interaction component and the data interaction functional information of each front-end interaction component, and identifying the target front-end interaction component corresponding to each application function based on the front-end interaction functional information of each front-end interaction component, the data interaction functional information of each front-end interaction component, and the interaction condition information of each application function; based on the target front-end interaction component corresponding to each application function and the functional interaction logic between each target system function applied by each application function, constructing the functional interaction architecture between each application function and each system function through a hybrid development program; using the functional interaction architecture between each application function and each system function as the front-end interaction architecture information of the application and the operating system.

[0090] In this embodiment, the terminal identifies the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component based on the front-end interaction function information of each front-end interaction component, and identifies the target front-end interaction component corresponding to each application function based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function. Then, based on the target front-end interaction component corresponding to each application function and the functional interaction logic between each target system function applied by each application function, the terminal constructs the functional interaction architecture between each application function and each system function through a mixed development program. Finally, the terminal uses the functional interaction architecture between each application function and each system function as the front-end interaction architecture information between the application program and the operating system.

[0091] Based on the above solution, after determining the functional interaction logic between application functions, system functions, and system architecture, the accuracy and calling effect of the interactive calls between the application and the operating system are improved by increasing the calling and interactive relationships between the front-end interactive components and the application functions, as well as the system functions, thereby improving the running effect of the application in the operating system.

[0092] This application also provides an example of application adaptation of an operating system, such as Figure 2 As shown, the specific processing process includes the following steps:

[0093] Step S201, obtaining system function information of the operating system, system architecture information of the operating system, application function information of the application program, and function requirement information of the application program.

[0094] Step S202, based on the application function information of the application, identifying the function type of each application function of the application and the interaction logic of each application function, and based on the function requirement information of the application, identifying the function interaction requirement information of each application function.

[0095] Step S203, based on the interaction logic of each application function and the functional interaction requirement information of each application function, identify the interaction condition information of each application function, and use the function type of each application function and the interaction condition information of each application function as the functional condition information of each application function.

[0096] Step S204 , splitting the system architecture information of the operating system into sub-architecture information of each sub-system architecture, and identifying architecture specification information corresponding to each sub-architecture information.

[0097] Step S205 , splitting the system function information into subsystem function information of each system function, and identifying architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information.

[0098] Step S206 , taking the architecture usage information of each system function for each subsystem architecture and the architecture specification information corresponding to each subsystem architecture as the functional architecture information of each system function.

[0099] Step S207 , based on the function type of each application function, query the system application database for each target system function applied by each application function.

[0100] Step S208, for each application function, based on the architecture usage information of each target system function for each subsystem architecture, identify the operation call logic of each target system function for each subsystem architecture, and the operation support condition information of each subsystem architecture for each target system function.

[0101] Step S209, based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, identify the operation support conditions of each subsystem architecture for the application function and the operation support scope of each subsystem architecture for the application function, and use the operation support conditions of each subsystem architecture for the application function and the operation support scope of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture.

[0102] Step S210, based on the interaction logic of the application function and the operation calling logic of each target system function to each subsystem architecture, identify the architecture interaction mode of the application function to each subsystem architecture and the architecture interaction logic of the application function to each subsystem architecture, and use the architecture interaction mode of the application function to each subsystem architecture and the architecture interaction logic of the application function to each subsystem architecture as the interaction calling information of the application function to each subsystem architecture.

[0103] Step S211, using the architecture interaction condition information of the application function to each subsystem architecture and the interaction call information of the application function to each subsystem architecture as the function interaction logic between the application function and each target system function applied by the application function.

[0104] Step S212, collecting each front-end application interaction information of the application program and the front-end function interaction mechanism between each application function of the application program.

[0105] Step S213, based on the front-end function interaction mechanism, identifies the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component, and identifies the target front-end interaction component corresponding to each application function based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function.

[0106] Step S214, based on the target front-end interaction components corresponding to each application function and the functional interaction logic between the target system functions applied by each application function, a functional interaction architecture between each application function and each system function is constructed through a hybrid development program.

[0107] Step S215, the functional interaction architecture between each application function and each system function is used as the front-end interaction architecture information between the application program and the operating system.

[0108] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0109] Based on the same inventive concept, the embodiment of the present application also provides an operating system application adaptation device for implementing the operating system application adaptation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the application adaptation device embodiments of one or more operating systems provided below can refer to the limitations of the operating system application adaptation method above, and will not be repeated here.

[0110] In an exemplary embodiment, Figure 3 As shown, an application adaptation device for an operating system is provided, comprising: an acquisition module 310, an identification module 320 and a construction module 330, wherein:

[0111] An acquisition module 310 is used to acquire system function information of an operating system, system architecture information of the operating system, application function information of an application program, and function requirement information of the application program, and identify function condition information of each application function of the application program based on the application function information of the application program and the function requirement information of the application program;

[0112] An identification module 320, configured to identify functional architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system, and to construct functional interaction logic between each application function and each system function based on functional condition information of each application function and the functional architecture information of each system function;

[0113] The construction module 330 is used to collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and based on the front-end function interaction mechanism and the function interaction logic, construct the front-end interaction architecture information of the application and the operating system.

[0114] Optionally, the acquisition module 310 is specifically configured to:

[0115] Based on the application function information of the application, identifying the function type of each application function of the application and the interaction logic of each application function, and based on the function requirement information of the application, identifying the function interaction requirement information of each application function;

[0116] Based on the interaction logic of each application function and the functional interaction requirement information of each application function, the interaction condition information of each application function is identified, and the function type of each application function and the interaction condition information of each application function are used as the functional condition information of each application function.

[0117] Optionally, the identification module 320 is specifically configured to:

[0118] Splitting the system architecture information of the operating system into sub-architecture information of each sub-system architecture, and identifying architecture specification information corresponding to each sub-architecture information;

[0119] Splitting the system function information into subsystem function information of each system function, and identifying architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information;

[0120] The architecture usage information of each system function for each of the subsystem architectures and the architecture specification information corresponding to each subsystem architecture are used as the functional architecture information of each system function.

[0121] Optionally, the identification module 320 is specifically configured to:

[0122] Based on the function type of each application function, query the target system functions applied by each application function in the system application database;

[0123] For each application function, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture;

[0124] The architecture interaction condition information of the application function to each subsystem architecture and the interaction call information of the application function to each subsystem architecture are used as the function interaction logic between the application function and each target system function applied by the application function.

[0125] Optionally, the construction module 330 is specifically used to:

[0126] Based on the architecture usage information of each target system function for each subsystem architecture, identifying the operation call logic of each target system function for each subsystem architecture, and the operation support condition information of each subsystem architecture for each target system function;

[0127] Based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, identifying the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function, and using the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture;

[0128] Based on the interaction logic of the application function and the operation calling logic of each target system function for each subsystem architecture, the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are identified, and the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are used as the interaction calling information of the application function for each subsystem architecture.

[0129] Optionally, the construction module 330 is specifically used to:

[0130] Based on the front-end function interaction mechanism, identify the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component, and based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function, identify the target front-end interaction component corresponding to each application function;

[0131] Based on the target front-end interaction components corresponding to each application function and the functional interaction logic between the target system functions applied by each application function, a functional interaction architecture between each application function and each system function is constructed through a hybrid development program;

[0132] The functional interaction architecture between each of the application functions and each of the system functions is used as the front-end interaction architecture information between the application program and the operating system.

[0133] Each module in the application adapter of the above operating system can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0134] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 4As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, an application adaptation method of an operating system is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0135] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0136] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the application adaptation method of the operating system when executing the computer program.

[0137] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the application adaptation method of the operating system are implemented.

[0138] In one embodiment, a computer program product is provided, including a computer program, which implements the steps of the application adaptation method of the operating system when the computer program is executed by a processor.

[0139] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0140] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0141] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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.

[0142] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. An application adaptation method for an operating system, characterized in that: The method comprises: Acquiring system function information of an operating system, system architecture information of the operating system, application function information of an application program, and function requirement information of the application program, and identifying function condition information of each application function of the application program based on the application function information of the application program and the function requirement information of the application program; Based on the system function information of the operating system and the system architecture information of the operating system, functional architecture information of each system function of the operating system is identified, and based on the functional condition information of each application function and the functional architecture information of each system function, functional interaction logic between each application function and each system function is constructed; Collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and build the front-end interaction architecture information of the application and the operating system based on the front-end function interaction mechanism and the function interaction logic.

2. The method according to claim 1, characterized in that The identifying the function condition information of each application function of the application based on the application function information of the application and the function requirement information of the application includes: Based on the application function information of the application, identifying the function type of each application function of the application and the interaction logic of each application function, and based on the function requirement information of the application, identifying the function interaction requirement information of each application function; Based on the interaction logic of each application function and the functional interaction requirement information of each application function, the interaction condition information of each application function is identified, and the function type of each application function and the interaction condition information of each application function are used as the functional condition information of each application function.

3. The method according to claim 1, characterized in that The identifying the functional architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system includes: Splitting the system architecture information of the operating system into sub-architecture information of each sub-system architecture, and identifying architecture specification information corresponding to each sub-architecture information; Splitting the system function information into subsystem function information of each system function, and identifying architecture usage information of each system function for each subsystem architecture based on each subsystem function information and each sub-architecture information; The architecture usage information of each system function for each of the subsystem architectures and the architecture specification information corresponding to each subsystem architecture are used as the functional architecture information of each system function.

4. The method according to claim 2, characterized in that: The function interaction logic between each application function and each system function is constructed based on the function condition information of each application function and the function architecture information of each system function, including: Based on the function type of each application function, query the target system functions applied by each application function in the system application database; For each application function, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, identifying the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture; The architecture interaction condition information of the application function to each subsystem architecture and the interaction call information of the application function to each subsystem architecture are used as the function interaction logic between the application function and each target system function applied by the application function.

5. The method according to claim 4, characterized in that The identifying, based on the interaction condition information of the application function and the architecture usage information of each target system function for each subsystem architecture, the architecture interaction condition information of the application function for each subsystem architecture and the interaction call information of the application function for each subsystem architecture includes: Based on the architecture usage information of each target system function for each subsystem architecture, identifying the operation call logic of each target system function for each subsystem architecture, and the operation support condition information of each subsystem architecture for each target system function; Based on the interaction condition information of the application function and the operation support condition information of each subsystem architecture for each target system function, identifying the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function, and using the operation support condition of each subsystem architecture for the application function and the operation support range of each subsystem architecture for the application function as the architecture interaction condition information of the application function for each subsystem architecture; Based on the interaction logic of the application function and the operation calling logic of each target system function for each subsystem architecture, the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are identified, and the architecture interaction mode of the application function for each subsystem architecture and the architecture interaction logic of the application function for each subsystem architecture are used as the interaction calling information of the application function for each subsystem architecture.

6. The method according to claim 5, characterized in that The constructing of the front-end interaction architecture information of the application program and the operating system based on the front-end function interaction mechanism and the function interaction logic includes: Based on the front-end function interaction mechanism, identify the front-end interaction function information of each front-end interaction component and the data interaction function information of each front-end interaction component, and based on the front-end interaction function information of each front-end interaction component, the data interaction function information of each front-end interaction component, and the interaction condition information of each application function, identify the target front-end interaction component corresponding to each application function; Based on the target front-end interaction components corresponding to each application function and the functional interaction logic between the target system functions applied by each application function, a functional interaction architecture between each application function and each system function is constructed through a hybrid development program; The functional interaction architecture between each of the application functions and each of the system functions is used as the front-end interaction architecture information between the application program and the operating system.

7. An application adaptation device for an operating system, characterized in that: The device comprises: an acquisition module, configured to acquire system function information of an operating system, system architecture information of the operating system, application function information of an application program, and function requirement information of the application program, and identify function condition information of each application function of the application program based on the application function information of the application program and the function requirement information of the application program; an identification module, configured to identify functional architecture information of each system function of the operating system based on the system function information of the operating system and the system architecture information of the operating system, and to construct functional interaction logic between each application function and each system function based on functional condition information of each application function and the functional architecture information of each system function; A construction module is used to collect each front-end application interaction information of the application and the front-end function interaction mechanism between each application function of the application, and based on the front-end function interaction mechanism and the function interaction logic, construct the front-end interaction architecture information of the application and the operating system.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images