Distributed call processing method and device for front-end upper-layer application and computer equipment

Abstract

The invention relates to a distributed call processing method and device for front-end upper-layer applications and computer equipment. The method comprises the following steps: acquiring application function information of a front-end upper-layer application and equipment function information of middleware of each hardware equipment, and splitting sub-function information of each sub-application function; identifying hardware equipment middleware adapted to each sub-application function, identifying each target sub-application function called by the user based on the current application calling information of the user, and calling the target sub-application function through a front-end upper-layer application base and a calling dependency strategy of each hardware equipment middleware. Calling each target sub-application function to obtain a calling result of each target sub-application function; and analyzing and processing the calling result of each target sub-application function through the processing module of each target sub-application function to obtain a target calling result of the user. By adopting the method, the calling processing efficiency of the front-end upper-layer application can be improved.

Description

Technical Field

[0001] The present application relates to the field of micro-frontend technology for a front-end upper-layer application framework, and in particular to a distributed call processing method, apparatus, and computer device for a front-end upper-layer application. Background Art

[0002] When customers handle related business functions, they need to invoke the corresponding modules on the hardware devices, such as calling the camera, reading the ID card, etc. With the promotion of trusted version devices, front-end upper-layer applications face the challenge of adapting to the communication interactions of various types of devices. Due to the differences in the ways of establishing communication with front-end upper-layer applications provided by different equipment manufacturers, front-end upper-layer applications need to customize the adaptation for each device, including agreeing on unified interface call specifications, introducing the underlying dependencies of communication interactions, and verifying whether the equipment communication in the business function link is available. In the device scenario, how the front-end upper-layer application can be compatible with the communication scenarios of different types of devices at low cost is the current research focus.

[0003] Traditional front-end upper-layer applications require large-volume devices to carry them, and in actual applications, front-end upper-layer applications cannot adapt to different devices. When a type of device is connected, in addition to the compatible transformation of the device communication module in the application, the business function module in the application also needs to be fully regressed for the device call scenario and the application needs to be repackaged and launched. In the long run, it will be difficult to deliver applications reliably, and it will be impossible to conduct comprehensive and thorough testing. The risk of production launch is high, resulting in poor call processing efficiency of the front-end upper-layer application. Summary of the invention

[0004] Based on this, it is necessary to provide a distributed call processing method, device, computer equipment, computer-readable storage medium and computer program product for front-end upper-layer applications to address the above technical problems.

[0005] In a first aspect, the present application provides a distributed call processing method for a front-end upper layer application, comprising:

[0006] Acquire application function information of the front-end upper layer application and device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function;

[0007] Based on the sub-function information and the device function information, identify the hardware device middleware adapted by each sub-application function, and collect the user's current application call information;

[0008] Based on the current application call information of the user, identify each target sub-application function called by the user, and through the front-end upper-layer application base and the call dependency strategy of the hardware device middleware corresponding to each target sub-application function, call the hardware device middleware corresponding to each target sub-application function to obtain the call result of each target sub-application function;

[0009] The calling results of each target sub-application function are transmitted to the processing modules of each target sub-application function through the front-end upper-layer application base, and the calling results of each target sub-application function are analyzed and processed by the processing modules of each target sub-application function to obtain the target calling results of the user.

[0010] Optionally, splitting the application function information into sub-function information of each sub-application function includes:

[0011] Identify each functional content included in the application function information, and functional logic information corresponding to each functional content;

[0012] For each functional content, based on the functional logic information of the functional content, identifying the hardware requirement information corresponding to the functional content and the communication requirement information corresponding to the functional content, and identifying the function type corresponding to the functional content;

[0013] The function type corresponding to the function content is used as the sub-application function corresponding to the function content, and the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content are used as sub-function information of the sub-application function corresponding to the function content.

[0014] Optionally, the identifying the hardware device middleware adapted for each of the sub-application functions based on the sub-function information and the device function information includes:

[0015] Based on the device function information, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, select each initial hardware device middleware corresponding to each functional content in each hardware device middleware;

[0016] For each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, each initial hardware device middleware is sorted to obtain a device sequence, and the first initial hardware device middleware in the device sequence is selected as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

[0017] Optionally, the identifying each target sub-application function called by the user based on the current application calling information of the user includes:

[0018] Splitting the current application call information of the user into sub-call requirement information of each call type, and identifying the call function requirement corresponding to each sub-call requirement information;

[0019] Based on the call type corresponding to each sub-call requirement information, the call function requirement corresponding to each sub-call requirement information, and the function type corresponding to each sub-application function, the target sub-application function corresponding to each sub-call requirement information is identified.

[0020] Optionally, the calling process of the hardware device middleware corresponding to each target sub-application function is performed through the front-end upper layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function to obtain the calling result of each target sub-application function, including:

[0021] Based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, a device call strategy for the hardware device middleware corresponding to each target sub-application function is generated, and the device environment information to which the hardware device middleware corresponding to each target sub-application function belongs is identified through the front-end upper-layer application base;

[0022] Based on the device environment information of each hardware device middleware, query the device dependency program adapted by each hardware device middleware, and send the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware;

[0023] Through the device wake-up strategy of each hardware device middleware, each hardware device middleware is controlled to perform data collection and processing, and the data collection results of each hardware device middleware are obtained. Based on the device dependency program adapted by each hardware device middleware, the data collection results of each hardware device middleware are formatted and packaged through the front-end upper-layer application base to obtain the calling results of the target sub-application functions corresponding to each hardware device middleware.

[0024] Optionally, analyzing and processing the call results of each target sub-application function through the processing module of each target sub-application function to obtain the target call result of the user includes:

[0025] Based on the functional content corresponding to each target sub-application function, identify the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and query the current task information corresponding to the current application call information of the user and the task analysis strategy corresponding to the current task information;

[0026] Based on the data type of the calling result of each target sub-application function and the data application strategy of the calling result of each target sub-application function, the target calling result of the user is identified through the task analysis strategy corresponding to the current task information.

[0027] In a second aspect, the present application also provides a distributed call processing device for a front-end upper layer application, including:

[0028] An acquisition module is used to acquire application function information of the front-end upper layer application and device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function;

[0029] An identification module, used to identify the hardware device middleware adapted for each sub-application function based on each sub-function information and each device function information, and collect the user's current application call information;

[0030] A calling module, for identifying each target sub-application function called by the user based on the current application calling information of the user, and performing calling processing on the hardware device middleware corresponding to each target sub-application function through the front-end upper layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, to obtain the calling result of each target sub-application function;

[0031] The analysis module is used to transmit the call results of each target sub-application function to the processing module of each target sub-application function through the front-end upper-layer application base, and analyze and process the call results of each target sub-application function through the processing module of each target sub-application function to obtain the target call result of the user.

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

[0033] Identify each functional content included in the application function information, and functional logic information corresponding to each functional content;

[0034] For each functional content, based on the functional logic information of the functional content, identifying the hardware requirement information corresponding to the functional content and the communication requirement information corresponding to the functional content, and identifying the function type corresponding to the functional content;

[0035] The function type corresponding to the function content is used as the sub-application function corresponding to the function content, and the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content are used as sub-function information of the sub-application function corresponding to the function content.

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

[0037] Based on the device function information, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, select each initial hardware device middleware corresponding to each functional content in each hardware device middleware;

[0038] For each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, each initial hardware device middleware is sorted to obtain a device sequence, and the first initial hardware device middleware in the device sequence is selected as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

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

[0040] Splitting the current application call information of the user into sub-call requirement information of each call type, and identifying the call function requirement corresponding to each sub-call requirement information;

[0041] Based on the call type corresponding to each sub-call requirement information, the call function requirement corresponding to each sub-call requirement information, and the function type corresponding to each sub-application function, the target sub-application function corresponding to each sub-call requirement information is identified.

[0042] Optionally, the calling module is specifically used to:

[0043] Based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, a device call strategy for the hardware device middleware corresponding to each target sub-application function is generated, and the device environment information to which the hardware device middleware corresponding to each target sub-application function belongs is identified through the front-end upper-layer application base;

[0044] Based on the device environment information of each hardware device middleware, query the device dependency program adapted by each hardware device middleware, and send the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware;

[0045] Through the device wake-up strategy of each hardware device middleware, each hardware device middleware is controlled to perform data collection and processing, and the data collection results of each hardware device middleware are obtained. Based on the device dependency program adapted by each hardware device middleware, the data collection results of each hardware device middleware are formatted and packaged through the front-end upper-layer application base to obtain the calling results of the target sub-application functions corresponding to each hardware device middleware.

[0046] Optionally, the analysis module is specifically used to:

[0047] Based on the functional content corresponding to each target sub-application function, identify the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and query the current task information corresponding to the current application call information of the user and the task analysis strategy corresponding to the current task information;

[0048] Based on the data type of the calling result of each target sub-application function and the data application strategy of the calling result of each target sub-application function, the target calling result of the user is identified through the task analysis strategy corresponding to the current task information.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] The above-mentioned distributed call processing method, device and computer equipment of the front-end upper-layer application obtain the application function information of the front-end upper-layer application and the device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function; based on each sub-function information and each device function information, identify the hardware device middleware adapted for each sub-application function, and collect the user's current application call information; based on the user's current application call information, identify each target sub-application function called by the user, and through the front-end upper-layer application base and the call dependency strategy of the hardware device middleware corresponding to each target sub-application function, call and process the hardware device middleware corresponding to each target sub-application function to obtain the call result of each target sub-application function; transmit the call result of each target sub-application function to the processing module of each target sub-application function through the front-end upper-layer application base, and analyze and process the call result of each target sub-application function through the processing module of each target sub-application function to obtain the target call result of the user. This solution splits the front-end upper-layer application into several smaller applications by splitting the application, obtaining the sub-function information of each sub-application function, and then adapting the hardware device middleware corresponding to each sub-application function, so as to reduce the application's requirements for device specifications and device requirements, and reduce the coupling between business applications. The calling process of the complex and single front-end upper-layer application can be completed through multiple hardware device middlewares, and this solution uses the device communication module as an application base alone, so that the application base uniformly handles the calling logic of different devices, reducing the coupling between business applications and device communication modules. When docking various devices, the compatible transformation is completed in the base application of device communication, and the device calling method exposed to the upper-layer business application is guaranteed to remain unchanged. In this way, the development and testing of customized docking devices will remain in the base application, and the upper-layer business application can be unaware of the changes in the underlying device without modification, avoiding full regression testing and production changes. Thereby comprehensively improving the calling processing efficiency of the front-end upper-layer application. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] 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.

[0054] Figure 1 An application environment diagram of a distributed call processing method for a front-end upper layer application in one embodiment;

[0055] Figure 2 It is a flowchart of a distributed call processing method of a front-end upper layer application in one embodiment;

[0056] Figure 3 A diagram showing the relationship between data flow and scheduling in one embodiment;

[0057] Figure 4 A schematic diagram of a process flow of a distributed call processing example of a front-end upper layer application in one embodiment;

[0058] Figure 5 It is a structural block diagram of a distributed call processing device of a front-end upper layer application in one embodiment;

[0059] Figure 6 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 distributed call processing method for the front-end upper layer application provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. In this application environment, the front-end upper-layer application is split into multiple sub-application functions (i.e., upper-layer applications 1, 2, 3, ..., N), and then, through the front-end application base, the data required to be called by each sub-application function is distributed to each hardware device middleware, and the structure is called through the js dependency structure corresponding to each hardware device middleware, so as to obtain the call result of each target sub-application function. In this case, the method can be applied to a terminal. In this case, the terminal can be, but is not limited to, various personal computers, laptops, medium-sized computers, etc. In this case, the terminal obtains the sub-function information of each sub-application function by splitting the front-end upper-layer application, and then adapts the hardware device corresponding to each sub-application function to the middleware, thereby splitting a complex and single application into several smaller applications, so as to reduce the conditions of the application on the device specifications and device requirements, and reduce the coupling between business applications. The calling process of a complex and single front-end upper-layer application can be completed through multiple hardware device middlewares, and this solution uses the device communication module as an application base alone, so that the application base uniformly handles the calling logic of different devices, reducing the coupling between business applications and device communication modules. When docking various devices, the compatible transformation is completed in the base application of device communication, and the device calling method exposed to the upper-level business application is guaranteed to remain unchanged. In this way, the development and testing of customized docking devices will remain in the base application, and the upper-level business application can be unaware of the changes in the underlying device and does not need to be modified, avoiding full regression testing and production changes. This comprehensively improves the call processing efficiency of the front-end upper-level application.

[0062] In an exemplary embodiment, Figure 2 As shown, a distributed call processing method for a front-end upper layer application is provided, and the method is applied to a terminal as an example for explanation, including the following steps S201 to S204. Among them:

[0063] Step S201, obtaining application function information of the front-end upper layer application and device function information of each hardware device middleware, and splitting the application function information into sub-function information of each sub-application function.

[0064] In this embodiment, the terminal responds to the staff's information upload operation and obtains the application function information of the front-end upper-layer application, wherein the application function information includes the functional logic information corresponding to each functional content of the front-end upper-layer application, wherein the functional content is a function that requires data collection through a device, for example, an image recognition function, a recording recognition function, a text recognition function, a device data receiving function, etc., wherein the image recognition function requires a device for collecting image data, the recording recognition function requires a device for collecting audio data, the text recognition function requires a device for collecting text data, and the device data receiving function requires a device for collecting data transmission interfaces of other devices. The functional logic information corresponding to each functional content is the hardware demand information of the work content, and the communication demand information, etc. Finally, the terminal splits the application function information into sub-function information of each sub-application function. Among them, each sub-application function corresponds to a functional content, and the specific splitting process will be described in detail later. Then, the terminal also needs to obtain the device function information of each hardware device middleware called by each sub-application function. The device function information not only represents the device communication function of the hardware device middleware, but also includes the device specification information of the hardware device middleware. Among them, the data content collected by hardware device middleware of different specifications has different integrity, clarity and accuracy. Therefore, the hardware device middleware adapted to each sub-application function needs to be adapted and identified. The specific identification process will be described in detail later.

[0065] Step S202: Based on the information of each sub-function and the information of each device function, the hardware device middleware adapted to each sub-application function is identified, and the user's current application calling information is collected.

[0066] In this embodiment, the terminal identifies the hardware device middleware adapted to each sub-application function based on each sub-function information and each device function information, and collects the user's current application call information. Among them, the hardware device middleware adapted to each sub-application function is capable of completing the data collection requirements of the sub-application function, and is also the hardware device middleware with the fastest collection efficiency among the hardware device middleware adapted to the sub-application function. The specific identification process will be described in detail later. The current application call information is the information of each device function that the user needs to call.

[0067] Step S203, based on the user's current application call information, identify the target sub-application functions called by the user, and through the front-end upper-layer application base, and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, call and process the hardware device middleware corresponding to each target sub-application function to obtain the calling results of each target sub-application function.

[0068] In this embodiment, the terminal identifies each target sub-application function called by the user based on the user's current application call information, and through the front-end upper-layer application base and the call dependency strategy of the hardware device middleware corresponding to each target sub-application function, calls and processes the hardware device middleware corresponding to each target sub-application function to obtain the call result of each target sub-application function. The specific calling process will be described in detail later. Each current application call information includes the call requirement information for each sub-application function.

[0069] Step S204, transmits the call results of each target sub-application function to the processing module of each target sub-application function through the front-end upper-layer application base, and analyzes and processes the call results of each target sub-application function through the processing module of each target sub-application function to obtain the user's target call result.

[0070] In this embodiment, the terminal transmits the call result of each target sub-application function to the processing module of each target sub-application function through the front-end upper layer application base, and analyzes and processes the call result of each target sub-application function through the processing module of each target sub-application function to obtain the target call result of the user. The specific analysis process will be described in detail later.

[0071] Based on the above scheme, by splitting the front-end upper-layer application, the sub-function information of each sub-application function is obtained, and then the hardware device corresponding to each sub-application function is adapted to the middleware, thereby splitting a complex and single application into several smaller applications, so as to reduce the conditions of the application on the device specifications and device requirements, and reduce the coupling between business applications. The calling process of the complex and single front-end upper-layer application can be completed through multiple hardware device middlewares, and this scheme uses the device communication module as an application base alone, so that the application base uniformly handles the calling logic of different devices, reducing the coupling between business applications and device communication modules. When docking various devices, the compatible transformation is completed in the base application of the device communication, and the device calling method exposed to the upper-layer business application is guaranteed to remain unchanged. In this way, the development and testing of customized docking devices will remain in the base application, and the upper-layer business application can be unaware of the changes in the underlying device without modification, avoiding full regression testing and production changes. Thereby comprehensively improving the call processing efficiency of the front-end upper-layer application.

[0072] Optionally, the application function information is split into sub-function information of each sub-application function, including: identifying each function content included in the application function information, and function logic information corresponding to each function content; for each function content, based on the function logic information of the function content, identifying the hardware requirement information corresponding to the function content, and communication requirement information corresponding to the function content, and identifying the function type corresponding to the function content; using the function type corresponding to the function content as the sub-application function corresponding to the function content, and using the hardware requirement information corresponding to the function content, and communication requirement information corresponding to the function content, as sub-function information of the sub-application function corresponding to the function content.

[0073] In this embodiment, the terminal identifies each functional content contained in the application function information, and the functional logic information corresponding to each functional content. Then, for each functional content, based on the functional logic information of the functional content, the terminal identifies the hardware requirement information corresponding to the functional content, the communication requirement information corresponding to the functional content, and identifies the functional type corresponding to the functional content. The functional type includes, but is not limited to, image recognition function, text recognition function, audio recognition function, and other functional types.

[0074] Then, the terminal uses the function type corresponding to the function content as the sub-application function corresponding to the function content, and uses the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content as the sub-function information of the sub-application function corresponding to the function content. Among them, the hardware requirement information is the device format information of the hardware intermediate device that the sub-application function needs to collect data, and the communication requirement information is the data communication information such as the communication data transmission volume, transmission frequency, transmission format, and transmission mode that the sub-application function can accept.

[0075] Based on the above solution, by splitting the application function information into several smaller applications, the coupling between business applications is reduced, and the demand for hardware middleware for each application can be effectively increased.

[0076] Optionally, based on each sub-function information and each device function information, identify the hardware device middleware adapted for each sub-application function, including: based on each device function information, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, filter out each initial hardware device middleware corresponding to each functional content in each hardware device middleware; for each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, perform device sorting processing on each initial hardware device middleware to obtain a device sequence, and filter out the first initial hardware device middleware in the device sequence as the hardware device middleware adapted for the sub-application function corresponding to the functional content.

[0077] In this embodiment, the terminal identifies the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware based on the device function information of each device, and screens each initial hardware device middleware corresponding to each functional content in each hardware device middleware based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content. The device specification information of each initial hardware device middleware is the device specification information that meets the device format information of the hardware middleware that the sub-application function needs to collect data.

[0078] For each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, each initial hardware device middleware is subjected to device sorting processing to obtain a device sequence. Specifically, the device sequence of each initial hardware device middleware is a sequence obtained by sorting the device communication functions of each initial hardware device middleware in descending order.

[0079] Finally, the terminal selects the first initial hardware device middleware in the device sequence as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

[0080] Based on the above solution, by first screening the hardware middleware that is adapted to each sub-application function, the hardware device middleware that is most suitable for the sub-application function is screened in order of communication function strength, thereby improving the accuracy of screening the hardware device middleware.

[0081] Optionally, based on the user's current application calling information, identify each target sub-application function called by the user, including: splitting the user's current application calling information into sub-call demand information of each calling type, and identifying the calling function requirement corresponding to each sub-call demand information; based on the call type corresponding to each sub-call demand information, the calling function requirement corresponding to each sub-call demand information, and the function type corresponding to each sub-application function, identify the target sub-application function corresponding to each sub-call demand information.

[0082] In this embodiment, the terminal splits the user's current application call information into sub-call demand information of each call type, and identifies the call function requirement corresponding to each sub-call demand information. Then, based on the call type corresponding to each sub-call demand information, the call function requirement corresponding to each sub-call demand information, and the function type corresponding to each sub-application function, the terminal identifies the target sub-application function corresponding to each sub-call demand information. Among them, the current application call information includes a call task for calling the current application, and the call task includes sub-call demand information of each call type. Then, based on the sub-call demand information of each call type, the terminal adapts the function type corresponding to each call type in the function type corresponding to each sub-application function, and uses the sub-application function of the function type corresponding to each call type as the target sub-application function corresponding to each sub-call demand information.

[0083] Based on the above solution, after splitting the call type, the target sub-application function corresponding to each sub-call demand information is identified, thereby improving the accuracy and comprehensiveness of the identification of the call demand information.

[0084] Optionally, through the front-end upper-layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, the hardware device middleware corresponding to each target sub-application function is called and processed to obtain the calling result of each target sub-application function, including: based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, a device wake-up strategy for the hardware device middleware corresponding to each target sub-application function is generated, and through the front-end upper-layer application base, the device environment information of the hardware device middleware corresponding to each target sub-application function is identified; based on the device environment information of each hardware device middleware, each target sub-application function is queried. A device dependency program adapted by each hardware device middleware is used, and the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function is sent to each hardware device middleware through the device dependency program adapted by each hardware device middleware; through the device wake-up strategy of each hardware device middleware, each hardware device middleware is controlled to perform data collection and processing to obtain the data collection result of each hardware device middleware, and based on the device dependency program adapted by each hardware device middleware, the data collection result of each hardware device middleware is formatted and packaged through the front-end upper-layer application base to obtain the call result of the target sub-application function corresponding to each hardware device middleware.

[0085] In this embodiment, the terminal generates a device wake-up strategy for the hardware device middleware corresponding to each target sub-application function based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, and identifies the device environment information to which the hardware device middleware corresponding to each target sub-application function belongs through the front-end upper-layer application base. Among them, for example, if the hardware device middleware to be called is a camera, then the device wake-up strategy is for the front-end upper-layer application to call the uniformly encapsulated camera wake-up method doCameraStart(). Among them, the front-end upper-layer application base is a unified interface API exposed to the upper layer that is compatible with various types of js dependencies (i.e., device dependency programs).

[0086] Then, based on the device environment information of each hardware device middleware, the terminal queries the device dependency program adapted by each hardware device middleware, and sends the device call strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware. Different device environment information corresponds to different device dependency programs, thereby ensuring that the comprehensiveness and accuracy of the call between the hardware device middleware and the sub-application function can be achieved under different device environment information.

[0087] Then, the terminal controls each hardware device middleware to perform data collection and processing through the device wake-up strategy of each hardware device middleware, obtains the data collection results of each hardware device middleware, and based on the device dependency program adapted by each hardware device middleware, formats and packages the data collection results of each hardware device middleware through the front-end upper-layer application base to obtain the call results of the target sub-application function corresponding to each hardware device middleware.

[0088] The specific application process takes the hardware device middleware as an example: Figure 3 As shown:

[0089] 1. The front-end upper-layer application calls the uniformly encapsulated camera wake-up method doCameraStart() and passes the instruction to the front-end application base.

[0090] 2. The front-end application base receives the command from the upper-layer application, identifies the current device type, and calls the camera start method CameraStart() in the js dependency adapted by the current device.

[0091] 3. js relies on calling the camera wake-up method of the middleware.

[0092] 4. The middleware returns the camera opening result to the js dependency.

[0093] 5. js relies on returning the camera opening result CameraFinishCallback() to the front-end application base.

[0094] 6. The front-end application base processes the opening result, encapsulates it into a unified callback format, and returns the result doCameraFinishCallback() to the front-end upper-layer application.

[0095] Based on the above solution, the application base uniformly handles the calling logic of different devices, reduces the coupling between business applications and device communication modules, and ensures that the device calling method exposed to the upper-level business application remains unchanged.

[0096] Optionally, the call results of each target sub-application function are analyzed and processed through the processing module of each target sub-application function to obtain the user's target call result, including: based on the functional content corresponding to each target sub-application function, identifying the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and querying the current task information corresponding to the user's current application call information and the task analysis strategy corresponding to the current task information; based on the data type of the call result of each target sub-application function and the data application strategy of the call result of each target sub-application function, identifying the user's target call result through the task analysis strategy corresponding to the current task information.

[0097] In this embodiment, the terminal identifies the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function based on the functional content corresponding to each target sub-application function, and queries the current task information corresponding to the user's current application call information and the task analysis strategy corresponding to the current task information. Then, based on the data type of the call result of each target sub-application function and the data application strategy of the call result of each target sub-application function, the terminal identifies the user's target call result through the task analysis strategy corresponding to the current task information.

[0098] Based on the above solution, after completing data collection, the data analysis strategy corresponding to each sub-application function is used to perform task analysis on the collected data to obtain task analysis results, thereby improving the accuracy and efficiency of identifying the user's target call results.

[0099] This application also provides an example of distributed call processing of a front-end upper layer application, such as Figure 4 As shown, the specific processing process includes the following steps:

[0100] Step S401, obtaining application function information of the front-end upper layer application and device function information of each hardware device middleware.

[0101] Step S402: identifying each functional content included in the application functional information and the functional logic information corresponding to each functional content.

[0102] Step S403, for each functional content, based on the functional logic information of the functional content, identifying the hardware requirement information corresponding to the functional content and the communication requirement information corresponding to the functional content, and identifying the function type corresponding to the functional content.

[0103] Step S404, taking the function type corresponding to the function content as the sub-application function corresponding to the function content, and taking the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content as the sub-function information of the sub-application function corresponding to the function content.

[0104] Step S405, based on the function information of each device, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, screen the initial hardware device middleware corresponding to each functional content in each hardware device middleware.

[0105] Step S406, for each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, perform device sorting processing on each initial hardware device middleware to obtain a device sequence, and select the first initial hardware device middleware in the device sequence as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

[0106] Step S407: collecting the user's current application calling information.

[0107] Step S408: split the user's current application call information into sub-call requirement information of each call type, and identify the call function requirement corresponding to each sub-call requirement information.

[0108] Step S409, based on the call type corresponding to each sub-call requirement information, the call function requirement corresponding to each sub-call requirement information, and the function type corresponding to each sub-application function, identify the target sub-application function corresponding to each sub-call requirement information.

[0109] Step S410, based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, generates a device wake-up strategy for the hardware device middleware corresponding to each target sub-application function, and identifies the device environment information of the hardware device middleware corresponding to each target sub-application function through the front-end upper-layer application base.

[0110] Step S411, based on the device environment information of each hardware device middleware, query the device dependency program adapted by each hardware device middleware, and send the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware.

[0111] Step S412, through the device wake-up strategy of each hardware device middleware, control each hardware device middleware to perform data collection and processing, obtain the data collection results of each hardware device middleware, and based on the device dependency program adapted by each hardware device middleware, format the data collection results of each hardware device middleware through the front-end upper-layer application base, and obtain the call result of the target sub-application function corresponding to each hardware device middleware.

[0112] Step S413, based on the functional content corresponding to each target sub-application function, identify the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and query the current task information corresponding to the user's current application call information and the task analysis strategy corresponding to the current task information.

[0113] Step S414, based on the data type of the call result of each target sub-application function and the data application strategy of the call result of each target sub-application function, the user's target call result is identified through the task analysis strategy corresponding to the current task information.

[0114] 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.

[0115] Based on the same inventive concept, the embodiment of the present application also provides a distributed call processing device for front-end upper layer applications for implementing the distributed call processing method for front-end upper layer applications 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 embodiments of the distributed call processing device for one or more front-end upper layer applications provided below can refer to the limitations of the distributed call processing method for front-end upper layer applications above, and will not be repeated here.

[0116] In an exemplary embodiment, Figure 5 As shown, a distributed call processing device for a front-end upper layer application is provided, including: an acquisition module 510, an identification module 520, a call module 530 and an analysis module 540, wherein:

[0117] The acquisition module 510 is used to acquire application function information of the front-end upper layer application and device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function;

[0118] The identification module 520 is used to identify the hardware device middleware adapted by each sub-application function based on each sub-function information and each device function information, and collect the user's current application call information;

[0119] The calling module 530 is used to identify each target sub-application function called by the user based on the current application calling information of the user, and to call and process the hardware device middleware corresponding to each target sub-application function through the front-end upper layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, so as to obtain the calling result of each target sub-application function;

[0120] The analysis module 540 is used to transmit the calling results of each target sub-application function to the processing modules of each target sub-application function through the front-end upper-layer application base, and analyze and process the calling results of each target sub-application function through the processing modules of each target sub-application function to obtain the target calling results of the user.

[0121] Optionally, the acquisition module 510 is specifically configured to:

[0122] Identify each functional content included in the application function information, and functional logic information corresponding to each functional content;

[0123] For each functional content, based on the functional logic information of the functional content, identifying the hardware requirement information corresponding to the functional content and the communication requirement information corresponding to the functional content, and identifying the function type corresponding to the functional content;

[0124] The function type corresponding to the function content is used as the sub-application function corresponding to the function content, and the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content are used as sub-function information of the sub-application function corresponding to the function content.

[0125] Optionally, the identification module 520 is specifically configured to:

[0126] Based on the device function information, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, select each initial hardware device middleware corresponding to each functional content in each hardware device middleware;

[0127] For each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, each initial hardware device middleware is sorted to obtain a device sequence, and the first initial hardware device middleware in the device sequence is selected as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

[0128] Optionally, the calling module 530 is specifically used to:

[0129] Splitting the current application call information of the user into sub-call requirement information of each call type, and identifying the call function requirement corresponding to each sub-call requirement information;

[0130] Based on the call type corresponding to each sub-call requirement information, the call function requirement corresponding to each sub-call requirement information, and the function type corresponding to each sub-application function, the target sub-application function corresponding to each sub-call requirement information is identified.

[0131] Optionally, the calling module 530 is specifically used to:

[0132] Based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, a device call strategy for the hardware device middleware corresponding to each target sub-application function is generated, and the device environment information to which the hardware device middleware corresponding to each target sub-application function belongs is identified through the front-end upper-layer application base;

[0133] Based on the device environment information of each hardware device middleware, query the device dependency program adapted by each hardware device middleware, and send the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware;

[0134] Through the device wake-up strategy of each hardware device middleware, each hardware device middleware is controlled to perform data collection and processing, and the data collection results of each hardware device middleware are obtained. Based on the device dependency program adapted by each hardware device middleware, the data collection results of each hardware device middleware are formatted and packaged through the front-end upper-layer application base to obtain the call results of the target sub-application function corresponding to each hardware device middleware.

[0135] Optionally, the analysis module 540 is specifically used to:

[0136] Based on the functional content corresponding to each target sub-application function, identify the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and query the current task information corresponding to the current application call information of the user and the task analysis strategy corresponding to the current task information;

[0137] Based on the data type of the calling result of each target sub-application function and the data application strategy of the calling result of each target sub-application function, the target calling result of the user is identified through the task analysis strategy corresponding to the current task information.

[0138] Each module in the above-mentioned distributed call processing device of the front-end upper layer application can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules 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 corresponding operations of each of the above modules.

[0139] 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 6 As 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, a distributed call processing method for a front-end upper layer application is realized. 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.

[0140] Those skilled in the art will understand that Figure 6 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.

[0141] 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 when the processor executes the computer program, steps corresponding to the distributed call processing method of the front-end upper layer application are implemented.

[0142] 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 corresponding to the distributed call processing method of the front-end upper layer application are implemented.

[0143] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements steps corresponding to a distributed call processing method for a front-end upper layer application.

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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. A distributed call processing method for a front-end upper layer application, characterized in that: The method comprises: Acquire application function information of the front-end upper layer application and device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function; Based on the sub-function information and the device function information, identify the hardware device middleware adapted by each sub-application function, and collect the user's current application call information; Based on the current application call information of the user, identify each target sub-application function called by the user, and through the front-end upper-layer application base and the call dependency strategy of the hardware device middleware corresponding to each target sub-application function, call the hardware device middleware corresponding to each target sub-application function to obtain the call result of each target sub-application function; The calling results of each target sub-application function are transmitted to the processing modules of each target sub-application function through the front-end upper-layer application base, and the calling results of each target sub-application function are analyzed and processed by the processing modules of each target sub-application function to obtain the target calling results of the user.

2. The method according to claim 1, characterized in that The application function information is split into sub-function information of each sub-application function, including: Identify each functional content included in the application function information, and functional logic information corresponding to each functional content; For each functional content, based on the functional logic information of the functional content, identifying the hardware requirement information corresponding to the functional content and the communication requirement information corresponding to the functional content, and identifying the function type corresponding to the functional content; The function type corresponding to the function content is used as the sub-application function corresponding to the function content, and the hardware requirement information corresponding to the function content and the communication requirement information corresponding to the function content are used as sub-function information of the sub-application function corresponding to the function content.

3. The method according to claim 2, characterized in that The identifying the hardware device middleware adapted for each sub-application function based on each sub-function information and each device function information includes: Based on the device function information, identify the device specification information of each hardware device middleware and the device communication function information of each hardware device middleware, and based on the device specification information of each hardware device middleware and the hardware requirement information corresponding to each functional content, select each initial hardware device middleware corresponding to each functional content in each hardware device middleware; For each functional content, based on the device communication function information of each initial hardware device middleware corresponding to the functional content and the communication requirement information corresponding to the functional content, each initial hardware device middleware is sorted to obtain a device sequence, and the first initial hardware device middleware in the device sequence is selected as the hardware device middleware adapted to the sub-application function corresponding to the functional content.

4. The method according to claim 2, characterized in that: The identifying each target sub-application function called by the user based on the current application calling information of the user includes: Splitting the current application call information of the user into sub-call requirement information of each call type, and identifying the call function requirement corresponding to each sub-call requirement information; Based on the call type corresponding to each sub-call requirement information, the call function requirement corresponding to each sub-call requirement information, and the function type corresponding to each sub-application function, the target sub-application function corresponding to each sub-call requirement information is identified.

5. The method according to claim 4, characterized in that The calling result of each target sub-application function is obtained by calling the hardware device middleware corresponding to each target sub-application function through the front-end upper layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, including: Based on the calling function requirements corresponding to each target sub-application function and the hardware device middleware corresponding to each target sub-application, a device call strategy for the hardware device middleware corresponding to each target sub-application function is generated, and the device environment information to which the hardware device middleware corresponding to each target sub-application function belongs is identified through the front-end upper-layer application base; Based on the device environment information of each hardware device middleware, query the device dependency program adapted by each hardware device middleware, and send the device wake-up strategy of the hardware device middleware corresponding to each target sub-application function to each hardware device middleware through the device dependency program adapted by each hardware device middleware; Through the device wake-up strategy of each hardware device middleware, each hardware device middleware is controlled to perform data collection and processing, and the data collection results of each hardware device middleware are obtained. Based on the device dependency program adapted by each hardware device middleware, the data collection results of each hardware device middleware are formatted and packaged through the front-end upper-layer application base to obtain the call results of the target sub-application function corresponding to each hardware device middleware.

6. The method according to claim 1, characterized in that The processing module of each target sub-application function analyzes and processes the call result of each target sub-application function to obtain the target call result of the user, including: Based on the functional content corresponding to each target sub-application function, identify the data type of the call result of each target sub-application function and the data content corresponding to the call result of each target sub-application function, and query the current task information corresponding to the current application call information of the user and the task analysis strategy corresponding to the current task information; Based on the data type of the calling result of each target sub-application function and the data application strategy of the calling result of each target sub-application function, the target calling result of the user is identified through the task analysis strategy corresponding to the current task information.

7. A distributed call processing device for front-end upper layer applications, characterized in that: The device comprises: An acquisition module is used to acquire application function information of the front-end upper layer application and device function information of each hardware device middleware, and split the application function information into sub-function information of each sub-application function; An identification module, used to identify the hardware device middleware adapted for each sub-application function based on each sub-function information and each device function information, and collect the user's current application call information; A calling module, used to identify each target sub-application function called by the user based on the current application calling information of the user, and to call and process the hardware device middleware corresponding to each target sub-application function through the front-end upper-layer application base and the calling dependency strategy of the hardware device middleware corresponding to each target sub-application function, so as to obtain the calling result of each target sub-application function; The analysis module is used to transmit the call results of each target sub-application function to the processing module of each target sub-application function through the front-end upper-layer application base, and analyze and process the call results of each target sub-application function through the processing module of each target sub-application function to obtain the target call result of the user.

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