WO2023124657A1

WO2023124657A1 - Micro-application running method and apparatus, device, storage medium, and program product

Info

Publication number: WO2023124657A1
Application number: PCT/CN2022/133516
Authority: WO
Inventors: 杨俊拯
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-12-30
Filing date: 2022-11-22
Publication date: 2023-07-06
Also published as: CN114356520A

Abstract

A micro-application running method and apparatus, a device, a storage medium, and a program product, which belong to the technical field of applications. The method comprises: acquiring a target micro-application script of a target micro-application (401); in response to a target trigger event, triggering a target trigger corresponding to the target trigger event in the target micro-application script (402); reading from a first data storage area an event parameter corresponding to the target trigger event, wherein different triggers correspond to different first data storage areas (403); and on the basis of the event parameter, executing a target call action corresponding to the target trigger (404). The micro-application running method can avoid the conflict problem of data corresponding to different triggers during a micro-application running process.

Description

Operation method, device, device, storage medium and program product of micro-application

This application claims the priority of the Chinese patent application filed on December 30, 2021 with the application number 202111651803.X and the title of the invention is "Operation method, device, equipment, storage medium and program product of micro-application", the entire content of which Incorporated in this application by reference.

technical field

The embodiments of the present application relate to the field of application technology, and in particular to a micro-application running method, device, equipment, storage medium, and program product.

Background technique

With the continuous development of application technology, more and more multi-functional applications emerge as the times require, bringing convenience to people's daily life.

Before using the application, the user first needs to download the application installation package from the application store, and install the application on the terminal by parsing the application installation package, and then click the application icon to start the application. However, with the continuous improvement of application quality, the storage space required by the application is also increasing.

Contents of the invention

Embodiments of the present application provide a micro-application running method, device, device, storage medium, and program product. Described technical scheme is as follows:

On the one hand, the embodiment of the present application provides a method for running a micro-application, the method comprising:

acquiring a target micro-application script of the target micro-application, wherein the target micro-application script is composed of at least one trigger;

triggering a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event;

Reading event parameters corresponding to the target trigger event from the first data storage area, where different triggers correspond to different first data storage areas;

Based on the event parameters, execute the target invocation action corresponding to the target trigger.

On the other hand, the embodiment of the present application provides a micro-application running device, the device includes:

A script acquisition module, configured to acquire a target micro-application script of the target micro-application, wherein the target micro-application script is composed of at least one trigger;

A trigger module, configured to trigger a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event;

A data reading module, configured to read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas;

An action calling module, configured to execute a target calling action corresponding to the target trigger based on the event parameter.

On the other hand, an embodiment of the present application provides a computer device, the computer device includes a processor and a memory; the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the following: The running method of the micro-application described in the above aspect.

On the other hand, an embodiment of the present application provides a computer-readable storage medium, where at least one piece of program code is stored in the computer-readable storage medium, and the program code is loaded and executed by a processor to implement the above aspects. The running method of the microapp.

On the other hand, an embodiment of the present application provides a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the micro-application running method provided in various optional implementation manners of the above aspect.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

Fig. 1 is a schematic diagram of a micro-application software package shown in an exemplary embodiment of the present application;

Fig. 2 is a schematic diagram of a micro-application script shown in an exemplary embodiment of the present application;

FIG. 3 shows a system architecture diagram of a micro-application system provided by an exemplary embodiment of the present application;

FIG. 4 shows a flowchart of a micro-application running method provided by an exemplary embodiment of the present application;

Fig. 5 shows a schematic diagram of a trigger scope shown in an exemplary embodiment of the present application;

FIG. 6 shows a flow chart of a micro-application running method provided by another exemplary embodiment of the present application;

Fig. 7 shows a schematic diagram of simple action types and combined action types shown in an exemplary embodiment of the present application;

FIG. 8 shows a schematic diagram of a child node acting on an exemplary embodiment of the present application;

Fig. 9 shows a schematic diagram of the relationship among sub-node scopes, trigger scopes and global scopes shown in an exemplary embodiment of the present application;

FIG. 10 shows a flow chart of a micro-application running method provided by another exemplary embodiment of the present application;

Fig. 11 shows a schematic diagram of a condition controller shown in an exemplary embodiment of the present application;

Fig. 12 shows a schematic diagram of a cycle controller shown in an exemplary embodiment of the present application;

Fig. 13 shows a schematic diagram of a delay controller shown in an exemplary embodiment of the present application;

Fig. 14 shows a schematic diagram of a condition controller shown in an exemplary embodiment of the present application;

Fig. 15 shows a schematic diagram of a selection controller shown in an exemplary embodiment of the present application;

Fig. 16 shows a schematic diagram of a parallel controller shown in an exemplary embodiment of the present application;

FIG. 17 shows a structural block diagram of a micro-application running device provided by an embodiment of the present application;

Fig. 18 shows a structural block diagram of a computer device provided by an exemplary embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

For the convenience of understanding, the nouns involved in the embodiments of the present application are described below.

Micro-applications: Micro-applications can be regarded as a collection of services, which are used to implement specific business logic through calls between services, that is, micro-application functions of micro-applications. Unlike traditional applications that can only run on a specific operating system, the services of micro-apps can be services on different operating systems, that is, micro-apps support heterogeneous operating systems and can run across platforms.

Unlike traditional applications that need to be downloaded before use and bound to devices, micro-apps adopt a subscription mechanism and are bound to users. This microapp can be used.

As shown in Figure 1, the micro-application software package 100 of the micro-application consists of an application description file 110, a program file 120 (micro-application script) and an MD5 file 130, wherein the application description file 110 is used to perform some simple operations on the micro-application Description, including the author, version information, time, etc. of the micro-application; the program file 120 is used for the core file in the micro-application software package, which is the main generated part edited by the developer through the editor, and is also the scheduling object of the micro-application engine; The MD5 file 130 is used for integrity verification of the micro-application software package 100 .

Micro-application script: also known as micro-application definition, it is used to control the calling relationship between services in micro-applications, and uses scripting language to describe a general business logic. Wherein, the scripting language can be xml, javascript, JSON, YMAL, C++, Python, etc., or some grammatical format customized by the user.

As shown in FIG. 2 , micro-application script 11 is composed of several triggers 12 , and each trigger 12 is composed of trigger event 13 , control logic 14 and several services 15 controlled by control logic 14 . Wherein, the service in the micro-application script is not the service itself, but the service identifier of the service. Optionally, in this embodiment, the service 15 may also be called a simple action or an action.

Different from traditional applications that need to download and install the application installation package before running, for example, before running an Android application, you need to download the apk package. Before running a micro application, you only need to download the corresponding micro application script. The application engine executes the micro-application script to realize the function of the micro-application. Compared with traditional applications, micro-application scripts have a lower code volume, so they occupy less storage space and are conducive to dynamic deployment and updates.

Service: As the smallest unit in the running process of micro-applications, it is used to achieve specific tasks. For example, the screen capture service is used to realize the screen capture function of the device, and the screen projection service is used to realize the screen projection of the display screen between devices, and so on. Moreover, the service invoked during the running of the micro-app may be a service on the current device or a service on other devices. For example, during the running of the micro-app, you can obtain the device screenshots of other devices by calling the screenshot service on other devices, and display the device screenshots of other devices by calling the image display service.

Action (simple action): refers to the smallest granularity action entity that is directly invoked and executed during the running process of the micro-application. Simple actions include actions provided by the micro-application system itself and service actions registered by service developers. Actions provided by the system include: device selection action, multi-action, reset application action, traversal list action, custom parameter action, parameter setting action, etc.; service action is a service developer registers a service, and the corresponding micro-app will be automatically generated Service actions, such as: screenshot action, open camera action, open screen mirroring server action, open screen mirroring client action, etc. In this embodiment, during the running process of the micro-app, simple actions are executed through the control logic, so as to realize the invocation of the service corresponding to the simple action. Obtain the device screenshots of other devices, and display the device screenshots of other devices by executing the display action and calling the image display service; it should be noted that in the micro-app, executing the call action is essentially calling a service.

Different from the traditional application installation process, all the services used in the running process need to be pre-installed locally. Since the business logic of the micro-application is dynamically assembled during the running process, the services in the micro-application support dynamic deployment, that is, during the running process Based on the business logic executed by the current device, the service corresponding to the business logic is dynamically deployed to the current device. Correspondingly, when the micro-application function of the same micro-application is implemented through multiple devices, since the business logic of different devices may be different, the services deployed on different devices may also be different, that is, the services in the micro-application have the characteristics of differential deployment .

In the embodiment of the present application, the services constituting the micro-application may include static services and dynamic services, wherein the static services refer to the services provided by the host application and need to be pre-installed in the device, while the dynamic services refer to the services that support dynamic deployment. It can be dynamically deployed in the device during the running of the micro application.

Fig. 3 shows a system architecture diagram of a micro-application system provided by an exemplary embodiment of the present application. The system includes at least one computer device 210 and a server 220 .

The computer device 210 is an electronic device with a micro-application running function. The electronic device may be a smart phone, a tablet computer, a personal computer, a car machine, etc., which is not limited in this implementation. In FIG. 3 , the device 210 includes a smart phone, a tablet computer, and a car machine as an example for illustration, but this is not limited thereto.

In a possible implementation, the computer device 210 is provided with a micro-application engine 211. The micro-application engine 211 serves as the core for controlling the operation of the micro-application, including a script management module 2111, an event bus module 2112, an application scheduling module 2113, and a runtime Module 2114 and service scheduling module 2115.

The script management module 2111 is used to manage the micro-application scripts of each micro-application stored in the computer device 210, and is responsible for analyzing the micro-application scripts, so as to determine the triggers in the micro-application scripts and the services under the triggers. Optionally, the script management module 2111 is further configured to download the corresponding micro-application script when receiving a micro-application subscription operation, and delete the micro-application script corresponding to the micro-application when receiving a micro-application subscription cancellation operation.

The event bus module 2112 is used to cooperate with the application scheduling module 2113 to implement micro-application scheduling based on trigger events. In some embodiments, triggers corresponding to multiple micro-applications are mounted under the event bus module 2112. Since the same trigger event may trigger multiple subscribing micro-applications, after the event bus module 2112 receives the trigger event, the The application scheduling module 2113 determines the micro-applications that need to be run from several micro-applications. Wherein, the application scheduling module 2113 can automatically determine the micro-application based on the scheduling strategy, or allow the user to manually select the micro-application.

The runtime module 2114 is used to execute the control logic in the micro-application script, so as to interact with the service scheduling module 2115 based on the control logic, and the service scheduling module 2115 makes a service call.

In addition, in addition to the micro-application engine 211 , the computer device 210 is also provided with a service management module 212 , a data synchronization module 213 and a service gateway 214 .

Among them, the service management module 212 is used to manage the pre-installed static services in the device; the data synchronization module 213 is used to update the status to other computer devices when the state of the micro-application engine 211 changes (for example, an event generated by the service causes a state change). Synchronization ensures the state consistency of the micro-application engine 211 on different computer devices.

The service gateway 214 is configured to perform service invocation based on the service invocation request of the service scheduling module 2115 , and specifically includes an agent management module 2141 and a life cycle management module 2142 . The proxy management module 2141 is provided with different service proxies, and the service proxies are used to convert service invocation requests in a unified format to obtain requests that meet the requirements of the real service format. The lifecycle management module 2142 is used to manage the lifecycle of the service, and may include a static service lifecycle management module and a dynamic service lifecycle management module.

During the running process of the micro-application, the computer device 210 can not only make service calls through its own service gateway 214, but also make service calls through the service gateway 214 of other devices (determined by the business logic of the micro-application), that is, cross-device service call.

For services in different deployment modes, as shown in FIG. 3 , a static service module 216 and a dynamic service module 215 are also provided in the computer device 210 . The static service module 216 is used to manage pre-installed static services, and the dynamic service module 215 is used to manage dynamically deployed dynamic services.

In some embodiments, the services contained in the dynamic service module 215 may correspond to different operating environments, different deployment forms or different programming development languages. In FIG. 3 , the dynamic service module 215 includes the Android dynamic service 2151 , the Web dynamic service 2152 and the container dynamic service 2153 as an example for schematic illustration, but this is not limited thereto.

The server 220 is a server, a service cluster composed of several servers, or a cloud computing center. According to the functions realized by each server in the server cluster, as shown in FIG. 3 , the server cluster includes a user resource management server 221 , a micro application store server 222 , a service market server 223 and a cloud service library 224 .

The user resource management server 221 includes a user management module 2211 , an application management module 2212 , a service management module 2213 , a device management module 2214 and a security module 2215 . The user management module 2211 is used to manage the user accounts using micro-applications; the application management module 2212 is used to manage the micro-applications subscribed under different user accounts; the service management module 2213 is used to manage the invoked services; the device management module 2214 is used to manage the binding relationship between the user account and the device; the security module 2215 is used to perform security verification during the interaction process.

The micro application store server 222 is used to provide micro application subscription services. When a user needs to use a micro-app, he can search for the micro-app through the micro-app search engine 2221 provided by the micro-app store server 222, and then choose to subscribe to the micro-app from the search results.

In some embodiments, after the micro application store server 222 receives the subscription operation to the micro application, it sends the user account and the application identification of the subscribed micro application to the user resource management server 221, and the application management in the user resource management server 221 Module 2212 updates the subscription relationship between the user account and the micro-application. Further, the user management module 2211 and the device management module 2214 determine other devices under the user account, and push subscription notifications to other devices, so that other devices download the micro application script of the micro application from the micro application store server 222. Schematically, as shown in Figure 3, after the user "Zhang San" subscribes to the micro-app through the smart phone, the car and tablet computer that logs in to the user account of "Zhang San" receive the subscription notification pushed by the user resource management server 221, The micro-app script of the micro-app is thereby downloaded based on the app identification in the notification.

The service market server 223 is a server for developers to provide service inquiry services. Developers can search for services through the service search engine 2231 provided by the service market server 223, and apply the searched services to the developed micro-applications, and then upload the developed micro-applications to the micro-application store server 222 for other users Download and use.

In addition, developers can also develop dynamic services and upload the developed dynamic services to the cloud service library 224 . The subsequent computer device 210 can download and deploy the dynamic service from the cloud service library 224 .

It should be noted that the above embodiments only illustrate the basic structure of the micro-application system, and the micro-application system may also include other computer devices (such as developer devices) or servers that implement other functions, and this embodiment does not constitute limited.

Please refer to FIG. 4 , which shows a flow chart of a micro-application running method provided by an exemplary embodiment of the present application. The embodiment of the present application takes the application of the method to the computer device shown in FIG. 3 as an example for illustration. The method include:

Step 401, acquiring a target micro-application script of a target micro-application, where the target micro-application script consists of at least one trigger.

In a possible implementation manner, when receiving the startup instruction of the target micro-application, the computer device obtains the target micro-application script corresponding to the target micro-application from the locally stored micro-application script, wherein the local storage of the computer device is determined by the current The microapp script of the microapp subscribed by the logged in user account.

Optionally, the start instruction can be triggered by the user clicking the micro-application icon, or can be triggered by interaction (such as voice, shake, tap, scene perception, etc.). way is limited.

In the embodiment of the present application, a micro-application is a collection of services, and its business logic is realized by computer equipment executing micro-application scripts through a micro-application engine, wherein micro-application scripts of different micro-applications are all executed by the same micro-application engine.

As a low-code script file, the micro-app script is composed of several triggers, and each trigger is used to trigger under a specific trigger event, and after the trigger is triggered, the service call is performed by executing the call action corresponding to the trigger.

Optionally, the calling action can be a simple action or a combined action. If the calling action is a simple action, when the trigger is triggered, the simple action can be directly executed to call the service; if the calling action is a combined action In the case of , when the trigger is triggered, a simple action needs to be executed through the controller to make a service call. The controller is used to indicate the call logic of the simple action.

In some embodiments, the micro-application script includes at least an initialization trigger and an end trigger. The initialization trigger is used to trigger the micro-application to start running, and the end trigger is used to trigger the micro-application to stop running. In addition to the initialization trigger and the end trigger, the micro-application script also includes other triggers for implementing specific micro-application functions, which is not limited in this embodiment of the present application.

Step 402, triggering a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event.

When the micro-application is running, when the target trigger event is received, the computer device determines the target trigger triggered by the target trigger event from the target micro-application script, thereby setting the target trigger from the untriggered state to the triggered state. In the triggered state, the computer device executes the calling action corresponding to the trigger through the micro-application engine, and calls the corresponding service to realize the corresponding business logic.

Optionally, the target trigger event can be an event triggered by the user, such as a tap event, a shake event, etc., or an event output after calling the service, for example, the last trigger corresponding to the service returned after the call is completed event, which is not limited in this embodiment.

Step 403, read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas.

In addition to the execution of the call action, the running process of the micro-app also involves the data transmission process. For example, the "screen projection event" will carry the relevant parameter information of the source device and the destination device of the screen projection, and the parameter information will be stored in the "projection event" screen event" in the trigger scope of the corresponding trigger, so that the corresponding target call action under the trigger can access the relevant parameter information. Therefore, in a possible implementation manner, when a target trigger event is received, the event parameters corresponding to the target trigger event will also be stored in the first data storage area, so that the subsequent target call action corresponding to the target trigger can be executed During the process, the first data storage area can be accessed to obtain corresponding event parameters, and the subsequent service invocation process can be continued.

Since the micro-application contains several triggers, and different triggers are triggered by different trigger events, in order to avoid conflicts caused by too much data, or it takes a long time to find the required data during the calling process, in a possible implementation, for Different triggers set different first data storage areas (trigger scope or data scope), the event parameters related to the trigger are stored in the first data storage area corresponding to the trigger, and the event parameters corresponding to the target trigger event It can only be accessed by the target call action corresponding to the target trigger event. Optionally, when the target call action includes multiple controllers and multiple simple actions, it can only be accessed by the controller and simple action corresponding to the target trigger.

It should be noted that when a target trigger event is received, while the target trigger corresponding to the target trigger event in the target micro-app script is triggered, the event parameter corresponding to the target trigger event can be stored in the trigger scope corresponding to the target trigger (first data store).

In some illustrative examples, the event parameter may be the data carried by the target trigger event, for example, the relevant information of the source device and the destination device carried by the "screen casting event".

As shown in FIG. 5 , it shows a schematic diagram of a trigger scope shown in an exemplary embodiment of the present application. When the target event 503 is received, the trigger 501 corresponding to the target event 503 is triggered, and the event parameters corresponding to the target event 503 can be stored in the trigger scope 510, the controllers 1 to 4 associated with the trigger 501, and Actions 1 to 4 can call the event parameters; but controllers 5 to 7, and actions 5 to 9 cannot call the data stored in the trigger scope 510; when the target event 504 is received, the target The trigger 502 corresponding to the event 504, and the event parameters corresponding to the target event 504 can be stored in the trigger scope 520, and the controller 5-controller 7 and action 5-action 9 associated with the trigger 502 can call this event Parameters; while Controller 1-Controller 4, and Action 1-Action 4 cannot call the data existing in the trigger scope 520 .

The data transfer process is involved in the running process of the micro-app. For example, for the event parameter of the screen projection event, the event parameter is required when the call action of the screen projection service is executed, and the corresponding event parameter needs to be obtained during the execution of the call action. Event parameters, so that the subsequent service call process can be performed based on the event parameters. Therefore, in a possible implementation manner, before executing the target call action corresponding to the target trigger, access the first data storage area, and read the event parameter corresponding to the target trigger event therefrom.

Step 404, based on the event parameter, execute the target invocation action corresponding to the target trigger.

In a possible implementation, the computer device executes the target invocation action corresponding to the target trigger based on the event parameters through the runtime module in the micro-application engine, so as to realize the invocation of the target service, and then realize the specific micro-application of the micro-application. App function.

It should be noted that the calling action in the embodiment of the present application is essentially calling a certain service. By executing the target calling action, the target service is called to realize the micro application function of the micro application; schematically, the target calling action is a screenshot action , the process of executing the screen capture action is the process of calling the screen capture service, and the screen capture function of the micro-app is realized by calling the screen capture service.

In the embodiment of the present application, the target service invoked by the computer device may be a service of the current device or a service of an external device, that is, a cross-device service call may be realized, thereby realizing the micro-application function of the target micro-application through interaction with the external device.

In addition, in the embodiment of this application, since the service of the micro-application supports dynamic deployment during operation in addition to static deployment, before invoking the target service, the computer device needs to determine whether the target service has been deployed locally, and During deployment, the target service is dynamically deployed (for dynamic services).

It should be noted that, when the micro-application contains multiple triggers, the computer device repeatedly executes the above steps 402 to 404, and after the end trigger is triggered, executes the control logic of the end trigger to end the running of the micro-application.

To sum up, in the embodiment of this application, during the running process of the micro-application, by obtaining the micro-application script of the micro-application, and triggering the corresponding trigger in the micro-application script based on the trigger event, and then executing the call action corresponding to the trigger , to implement the micro-app function of the micro-app. Since the operation of micro-apps is based on micro-app scripts with low code volume, the storage space required is smaller than that of traditional applications; and the calling actions are assembled into micro-apps, and the micro-app scripts are used to manage the relationship between calling actions The call relationship realizes the componentization of micro-applications, improves the reusability of calling actions between micro-applications, and helps to reduce the development difficulty of micro-applications. The data storage area enables the call action associated with the trigger to access the data storage area. While achieving the purpose of data transfer in the micro-app, it can also avoid the conflict of data corresponding to different triggers.

Optionally, the action type of the target call action includes simple action type and combined action type. The target call action under the simple action type consists of a single target simple action, and the target call action under the combined action type consists of at least one target controller and at least one target Simple action composition, the target controller is used to instruct the target call logic of the simple action of the target;

Execute the target invocation action corresponding to the target trigger, including:

In the case that the target calling action includes at least one target controller, at least one target simple action is controlled to be executed by the at least one target controller.

Optionally, the target call action includes a target simple action located at the parent node and a target simple action located at the child node;

Perform at least one target simple action controlled by at least one target controller, including:

Control the execution of the target simple action at the parent node through the target controller, and obtain the target service data fed back after executing the target simple action at the parent node;

Reading the target service data from the second data storage area, the target simple action located in the parent node is different, and corresponds to a different second data storage area;

Based on the target service data, execute the target simple action located in the child node.

Optionally, the method also includes:

The operating environment parameters corresponding to the target micro-application are stored in the third data storage area, and the third data storage area allows access to the calling action triggered by each trigger.

Execute the target call action corresponding to the trigger, including:

Where the target invocation action includes at least one target controller, determining the target invocation logic indicated by the target controller;

Based on the target call logic, execute the target simple action.

Optionally, the target controller is a conditional controller, and the conditional controller is associated with at least two candidate simple actions;

Determine the target invocation logic indicated by the target controller, including:

determining the target scheduling conditions indicated by the target controller;

Based on the target invocation logic, execute the simple actions of the target, including:

Based on the target scheduling condition, the target simple action is determined from the candidate simple actions, and the target simple action is executed.

Optionally, the target controller is a loop controller;

determining target cycle conditions indicated by the target controller;

In the case that the execution state of the target simple action does not meet the target loop condition, continue to execute the target simple action cyclically.

Optionally, when the execution state of the target simple action does not meet the target cycle condition, continue to execute the target simple action, including any of the following:

When the number of executions of the target simple action does not reach the number threshold, continue to execute the target simple action in a loop;

If the target service corresponding to the target simple action is not called successfully, continue to execute the target simple action in a loop;

In the case that the target service corresponding to the target simple action does not fail to be called, continue to execute the target simple action in a loop.

Optionally, the target controller is a delay controller;

determining the target invocation latency indicated by the target controller;

In case the target call delay is reached, execute the target simple action.

Optionally, the target controller is a sequence controller, and the sequence controller is associated with at least two candidate simple actions;

Determine the target invocation sequence corresponding to each candidate simple action indicated by the target controller;

Based on the target calling sequence, the candidate simple actions are sequentially determined as the target simple actions, and each target simple action is sequentially executed.

Optionally, execute the simple actions of each target in sequence, including:

When the nth target simple action is successfully executed, continue to execute the n+1th target simple action;

Methods also include:

In the case that the execution of the nth target simple action fails, the execution of the n+1th target simple action is stopped.

Optionally, the target controller is a selection controller, and the selection controller is associated with at least two candidate simple actions;

determine the sequence of target invocations indicated by the target controller;

Based on the target invocation sequence, the candidate simple actions are executed sequentially; if there is a candidate simple action that is successfully executed, the candidate simple action is determined as the target simple action, and the execution of other candidate simple actions is stopped.

Optionally, the target controller is a parallel controller, and the parallel controller is associated with at least two candidate simple actions;

Each candidate simple action is determined as a target simple action, and each target simple action is executed in parallel.

In addition to the event parameter transfer process, the data transfer process involved in the running process of the micro-app also involves the transfer process of the service return value. For example, the "screen capture action" will return the captured image data, and the When the "action" is executed, the intercepted image data needs to be accessed; therefore, in a possible implementation, a corresponding data space scope is also set for the service return value.

Please refer to FIG. 6, which shows a flow chart of a micro-application running method provided by another exemplary embodiment of the present application. The embodiment of the present application takes the application of the method to the computer device shown in FIG. 3 as an example for illustration. Methods include:

Step 601 , acquiring a target micro-application script of a target micro-application, where the target micro-application script consists of at least one trigger.

Step 602, triggering a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event.

Step 603, read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas.

For implementation manners of steps 601 to 603, reference may be made to the foregoing embodiments, and details are not described herein in this embodiment.

Step 604, in the case that the target call action includes at least one target controller, based on the event parameters, at least one target simple action is controlled by the at least one target controller.

Among them, the action type of calling action includes simple action type and combined action type. The calling action under the simple action type is composed of a single simple action, and the calling action under the combined action type is composed of at least one controller and at least one simple action. The controller is used to indicate Call logic for simple actions.

As shown in FIG. 7 , it shows a schematic diagram of simple action types and combined action types shown in an exemplary embodiment of the present application. When the action type of the call action is a simple action type, when event 1 is received, the trigger 1 corresponding to event 1 is triggered, and the trigger 1 triggers the execution of simple action 701 to call the service; when the action type of the call action is combination For the action type, when event 2 is received, trigger 2 corresponding to event 2 is triggered, and trigger 2 triggers the execution of combined action 702. The combined action 702 is composed of controller 1-controller 5 and action 1-action 8, where , actions 1 to 8 are simple actions; during the execution of the call action, it is necessary to control the execution of action 1 by controller 1 and controller 2; the execution of action 2 is controlled by controller 1, controller 2, and controller 4; Actions 3 to 5 are controlled by controller 1, controller 2, and control 5; actions 6 to 8 need to be controlled by

controllers

1 and 3.

Since the call action of the simple action type only contains a single simple action and does not contain a controller, in a possible implementation, when the call action does not contain a controller, it can directly carry the event parameters of the target event and execute the target event. Simple actions to call the corresponding target service, and then realize the micro-application function of the micro-application.

The call action of the simple action type can only realize the call of a single service, but in the actual application scenario of the micro application, if a micro application function needs to be completed, it is often impossible to achieve it only by a single simple action, and it may require several simple actions to realize it together , therefore, in order to achieve more complex micro-application functions, the micro-application provides a call action mechanism for developing combined action types, and defines the call logic between simple actions through the controller to realize the combination of different simple actions, so as to achieve more Complex microapp functionality.

It should be noted that when the calling action is a combined action type, it consists of several controllers and several simple actions, as shown in Figure 7, it can be a "multi-fork tree structure; where the leaf nodes of the tree must be "simple action", the root node (the node connected to the trigger) is the controller, and the child nodes of the controller can be controllers or simple actions; the child nodes of simple actions can be simple actions or controllers. When When the micro-application engine triggers the call action through the trigger, it will traverse the entire tree from the controller of the root node in sequence, and finally traverse to different leaf nodes (simple actions) according to the control logic of the controller, and execute the simple action.

For the call action of the combined action type, during the running of the micro-application, when the computer device receives the target trigger event, it triggers the target trigger corresponding to the target event, and the trigger is controlled by at least one target controller to execute at least one target simple action, so as to Realize the call to the target service, and during the execution of the target call action, both the target controller and the target simple action can read the event parameters from the first data storage area, and realize the micro application of the micro application through data transfer and action call Function.

In addition to the event parameter transfer process, the data transfer process involved in the running process of the micro-app also involves the transfer process of the service return value. For example, the "screen capture action" will return the captured image data, and the When the "action" is executed, the intercepted image data needs to be accessed; therefore, in a possible implementation, a corresponding data space scope is also set for the service return value. In an exemplary example, step 604 may further include steps 604A to 604C.

Step 604A, control the execution of the target simple action at the parent node through the target controller, and obtain the target service data fed back after executing the target simple action at the parent node.

As shown in Figure 7, in combined action 702, action 7 and action 8 are the child nodes of action 6, that is, action 6 is the parent node. In the process of executing the combined action 702, according to the scheduling logic, the action needs to be executed first 6. Perform action 8 and/or action 7 again, and during the process of performing action 7 or action 8, the service data fed back after performing action 6 may be required; schematically, when the target call action includes actions such as action 6 and For the simple action of the relationship between actions 7, it is determined that the target call action includes the target simple action located in the parent node and the target simple action located in the child node; corresponding to the running process of the micro application, firstly, the target controller is used to control the execution of the target simple action located in the parent node If the target simple action of , if the target service data can be obtained after executing the target simple action, the target service data can be stored in a specific data storage area, so that the target service data can be referenced when the subsequent target simple action is executed.

The target service data fed back after executing the target simple action of the parent node will only be called by the child nodes associated with the parent node. For example, as shown in Figure 7, the target service data fed back by executing Action 6 will only be invoked by Action 7 and/or Action 8 associated with Action 6, while other Actions 1 to 5 in the combined Action 702 do not need to The target service data fed back by action 6, in order to distinguish and store the target service data fed back by different parent node actions, in a possible implementation, a second data storage area (also called a child node scope ) to store the return value data after calling the parent node action, corresponding to the child node action associated with the parent node can read the required data from the second data storage area during the calling process.

Step 604B, read the target service data from the second data storage area. The target simple action located in the parent node is different and corresponds to a different second data storage area.

In order to facilitate the target service data fed back by the target simple action located at the parent node, it can be transferred to the target simple action located at the child node. In a possible implementation, a second data storage area is set to store and execute the The target service data fed back after the target simple action of the node.

Optionally, in order to avoid data conflicts, different second data storage areas are set for different target simple actions located in the parent node, and the second data storage area only allows child nodes associated with target simple actions of the same parent node The target of the simple action call.

In a possible implementation, before executing the target simple action located in the child node, if the target simple action needs to refer to the target service data returned by the previous node during the execution process, it first needs to be retrieved from the second data storage area Read the target service data, and then execute the target simple action located in the child node based on the target service data.

Optionally, in the micro-application, a special symbol is set to refer to the target service data from the child node scope (second data storage area). Schematically, the special symbol can be $, such as "showPicture=$picture ", which means that the display image action refers to the image in the scope of the child node.

Step 604C, based on the target service data, execute the target simple action located in the child node.

In a possible implementation, after obtaining the target service data fed back by the previous node (parent node), the target simple action located at the child node can be executed by referencing the target service data to realize the target simple action Corresponds to the invocation of the target service.

As shown in FIG. 8 , it shows a schematic diagram of the sub-node scope shown in an exemplary embodiment of the present application. After receiving the event 801, the trigger 802 corresponding to the event 801 is triggered, and the controller 1 and the controller 2 control and call the screen capture action and the display picture action to realize the screen capture display function, wherein the display picture action is a child node of the screen capture action ; Correspondingly, in the realization process of the screenshot display function, at first, the controller 2 controls and executes the screenshot action, obtains the target picture intercepted after executing the screenshot action, stores the target picture in the child node scope 803, and when the execution display When performing an image action, it is necessary to display the target image fed back by the screen capture action, and it is necessary to call the target image from the child node scope 803 and pass the target image as an input parameter for displaying the image. Optionally, since action 2 is also a child node of the screenshot action, when executing action 2, if the target picture is also needed, the target picture may also be called from the child node scope 803 .

Optionally, in addition to the above-mentioned first data storage area (trigger scope) and second data storage area (child node scope), the data space scope of the micro application also includes a third data storage area (global Scope), the third data storage area stores the operating environment parameters corresponding to the target micro-application, as well as user-defined parameters, such as the device information of the current computer device, etc., which are stored in the third data storage area to allow each trigger The call action triggered by the controller is accessed, that is, the data of the global scope can be accessed by all controllers and simple actions of the micro application.

As shown in FIG. 9 , it shows a schematic diagram of the relationship among the child node scope, the trigger scope and the global scope shown in an exemplary embodiment of the present application. The micro-application 900 includes a micro-application global scope 910, a trigger scope 920, and a child node scope 930; wherein, the operating environment parameters and custom parameters of the micro-application are stored in the micro-application global scope 910, and the trigger 901 and The controllers and actions associated with the trigger 902 can call data from the micro-app global scope 910; when the target event is received, the trigger 901 corresponding to the target event is triggered, and the event parameters corresponding to the target event can be stored in the trigger In the scope 920, the controller 1~controller 4, and action 1~action 4 associated with the trigger 901 can call the event parameter; while the controller 5~controller 7, and action 5~action 9 cannot call the trigger The data in the scope 920 of the controller; after the execution of action 6, the service data fed back is stored in the scope 930 of the child node, allowing actions 7 to 9 to call the data in the scope 930 of the child node during execution; while action 5 cannot The data in the child node scope 930 is called, and the controllers 1 to 4 and actions 1 to 4 corresponding to the trigger 901 cannot call the data in the child node scope 930 . Optionally, the trigger 902 also has its own trigger scope (not shown in the figure), and only the controllers 5 to 7 and actions 5 to 9 associated with the trigger 902 are allowed to call the Event parameters in the scope of the controller.

In this embodiment, by dividing the global scope, trigger scope, and child node scope, and defining data reference relationships or restrictions between different scopes, excessive data can be avoided while achieving the purpose of internal data transfer in the micro-application the resulting conflict.

In order to realize more complex micro-application functions, the concept of combined action type is introduced, and the call action is composed of several controllers and several simple actions. In the actual application process, there are various scheduling logics, such as cycle scheduling, sequence Scheduling, conditional scheduling, etc., in order to realize the scheduling logic, multiple controllers indicating different scheduling logics are defined in this embodiment, and the micro-application functions of the micro-application can be further enriched through the combination of different types of controllers.

Please refer to FIG. 10 , which shows a flow chart of a micro-application running method provided by another exemplary embodiment of the present application. This embodiment of the present application is described by taking the method applied to the computer device shown in FIG. 3 as an example. Methods include:

Step 1001, acquire a target micro-application script of a target micro-application, where the target micro-application script consists of at least one trigger.

Step 1002, triggering a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event.

Step 1003, read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas.

For implementation manners of step 1001 and step 1003, reference may be made to the foregoing embodiments, and details are not described in this embodiment here.

Step 1004, if the target invocation action includes at least one target controller, determine the target invocation logic indicated by the target controller.

When the target call action includes at least one target controller, the target controller is used to indicate the target call logic of at least one target simple action, for example, if the target controller is a loop controller, the target controller defines the target simple action The loop condition is the call logic of the target simple action, which needs to be followed to call the target simple action, which is the action connected to the loop controller.

Optionally, the child nodes of a controller can be simple actions or other controllers.

Step 1005, execute target simple actions based on event parameters and target invocation logic.

In a possible implementation, the computer device executes the target simple action based on the target invocation logic corresponding to the target controller, so as to realize the invocation of the target service, and then realize the specific application function of the micro-application; and when executing the target simple action In the process, you can refer to the event parameters of the target event.

Wherein, the target controller may be a conditional controller, a loop controller, a delay controller, a sequential controller, a selection controller, a parallel controller, etc. The embodiment of the present application does not limit the controller type of the target controller. Business personnel can implement controllers with different functions according to different needs, so as to combine controllers with different functions to realize different micro-application functions.

Taking the target controller as the conditional controller as an example, in an exemplary example, step 1004 and step 1005 may be replaced by step 1004A and step 1005A.

Step 1004A, if the target calling action includes at least one target controller, determine the target scheduling condition indicated by the target controller.

Wherein, the condition controller is set with a judgment condition, and needs to determine whether to execute the target simple action corresponding to the branch or to execute the target simple action corresponding to the no branch according to the judgment result of the condition.

In a possible implementation, when a conditional controller is included in the target call action, when the conditional controller is executed, it is necessary to determine the target scheduling condition indicated by the conditional controller, and then judge based on the target scheduling condition The target simple action to perform.

Step 1005A, based on the target scheduling condition, determine the target simple action from candidate simple actions, and execute the target simple action.

In a possible implementation manner, based on the target scheduling condition, the target simple action to be executed is determined from at least two candidate simple actions associated with the condition controller, and then the target simple action is executed to invoke the target service.

Furthermore, when determining the target simple action to be executed based on the target scheduling condition, it is necessary to judge whether the event parameter satisfies the target scheduling condition. When the target scheduling condition is met, the target simple action corresponding to the branch is executed; otherwise, when When the target scheduling condition is met, execute the target simple action corresponding to the No branch.

As shown in FIG. 11 , it shows a schematic diagram of a condition controller shown in an exemplary embodiment of the present application. The target calling action includes a condition controller 1101, a first controller 1102, a second action 1104 and a first action 1103; when the target calling action is executed, the condition judgment result is first determined based on the condition 1105 of the condition controller 1101, when the condition If the judgment result indicates that the condition 1105 is satisfied, then the first controller 1102 corresponding to the Yes branch will continue to control and execute the second action 1104; if the condition judgment result indicates that the condition 1105 is not met, then the first action 1103 corresponding to the No branch will be executed.

Taking the target controller as a loop controller as an example, in an exemplary example, step 1004 and step 1005 may also be replaced by step 1004B and step 1005B.

Step 1004B, if the target calling action includes at least one target controller, determine the target loop condition indicated by the target controller.

Wherein, the loop controller is provided with a loop condition, and the loop scheduling mode of the simple action is limited by the loop condition. Only when the loop condition is satisfied, the execution of the target simple action can be stopped.

It should be noted that since the loop controller can only define loop conditions, it cannot define how to call two or more simple actions, so the loop controller only has a single child node, which will be cyclically scheduled.

In a possible implementation, when the target call action includes a loop controller, when the loop controller is executed, it is necessary to determine the target loop condition indicated by the loop controller, and then judge based on the target loop condition The stop execution timing of the target simple action.

Step 1005B, if the execution state of the target simple action does not meet the target loop condition, continue to execute the target simple action cyclically.

In a possible implementation, when the target controller is a loop controller, it means that the target simple action associated with the target controller needs to be executed cyclically, and only when the execution state of the target simple action satisfies the target loop condition, the It will stop executing the target simple action. That is to say, when the loop controller is executed, it is necessary to judge whether the execution state of the target simple action meets the target loop condition. If the target loop condition is not met, continue to execute the target simple action. Otherwise, when When the target loop condition is met, stop executing the target simple action.

Optionally, the loop controller can be divided into a count loop controller, a loop until success controller, and a loop until failure controller based on different target loop conditions.

In the case that the loop controller is a count loop controller, the count loop controller defines the threshold of the loop execution times of simple actions. When the loop controller should be executed to the count loop controller, it is necessary to obtain the execution times of the target simple action and determine the Whether the number of executions reaches the number threshold indicated by the target loop condition, when the number of executions reaches the number threshold, stop executing the target simple action; otherwise, when the number of executions does not reach the number threshold, continue to execute the target simple action until the execution of the target simple action The number of times reaches the number threshold. Exemplarily, if the number of times threshold is 10 times, when assigned to the loop controller, the target simple action associated with the loop controller is cyclically executed, and each time the target simple action is executed, the execution times of the target simple action + 1. Stop executing the target simple action until the number of executions reaches 10.

In the case that the loop controller is a loop until success controller, the loop until success controller defines the loop execution purpose of the simple action. Only when the simple action is executed successfully, will it stop looping and execute the target simple action; correspondingly, it should be executed until the loop until When the controller is successful, it needs to execute the target simple action in a loop, and judge whether the target service corresponding to the target simple action is called successfully. When the target service is successfully called, stop executing the target simple action; otherwise, when the target service is not successfully called, continue to execute The target simple action will not stop executing the target simple action until the target service call is successful and the target loop condition of the loop controller is met.

In the case that the loop controller is a loop until failure controller, the loop until failure controller defines the loop execution purpose of the simple action. Only when the simple action fails to execute, will the loop execute the target simple action stop; correspondingly, it should be executed until the loop until When the controller fails, it needs to execute the target simple action in a loop, and judge whether the target service corresponding to the target simple action is called successfully. When the target service is successfully called, continue to execute the target simple action until the target service fails to be called; After the call fails, the execution of the target simple action will stop only if the target loop condition of the loop controller is met.

As shown in FIG. 12 , it shows a schematic diagram of a cycle controller shown in an exemplary embodiment of the present application. When the target call action includes the number of cycle controller 1201, the first controller 1202, and the first action 1203, in the process of executing the target call action, the first controller 1202 needs to control the loop execution of the first action 1203 until the second After the number of executions of an action 1203 reaches the number threshold, stop executing the first action 1203; when the target call action includes the loop until success controller 1204, the second controller 1205, and the second action 1206, the process of executing the target call action In the process, the second controller 1205 needs to control the loop execution of the second action 1206 until the execution of the second action 1206 is successful, then stop the execution of the second action 1206; And for the third action 1209, in the process of executing the target call action, the third controller 1208 needs to control the cyclic execution of the third action 1209, until the execution of the third action 1209 fails, the execution of the third action 1209 is stopped.

Taking the target controller as a delay controller as an example, in an exemplary example, step 1004 and step 1005 may also be replaced with step 1004C and step 1005C.

Step 1004C, if the target calling action includes at least one target controller, determine the target calling delay indicated by the target controller.

Among them, the delay controller defines a call delay, and only when the call delay is reached, the target simple action can be executed.

It should be noted that since the delay controller can only define the call delay, but cannot define how to call two or more simple actions, the delay controller only has a single child node, and the child node will be delayed for a certain period of time.

In a possible implementation, when the delay controller is included in the target call action, when the delay controller is executed, it is necessary to determine the target call delay indicated by the delay controller, and then extend After the target call is delayed, execute its associated target simple action.

Exemplarily, if the target call delay is 20ms, when the delay controller is executed, the controller and/or the target simple action associated with the delay controller will be executed after an extension of 20ms.

Step 1005C, execute the target simple action when the target call delay is reached.

In a possible implementation, when the target controller is a delay controller, it means that it needs to be delayed for a certain period of time to execute its associated subnodes, that is, when the delay controller is executed, temporarily stop To execute the target simple action associated with it, it is necessary to judge whether the target call delay is reached. If the target call delay is reached, the target simple action is executed. Otherwise, if the target call delay is not reached, it needs to wait until the target call delay is reached. Able to perform targeted simple actions.

As shown in FIG. 13 , it shows a schematic diagram of a delay controller shown in an exemplary embodiment of the present application. The child nodes of the delay controller can be other controllers or actions; when the target call action includes the first delay loop controller 1301 and the first action 1302, in the process of executing the target call action, it is necessary to reach the target call After the delay, execute the first action 1302; when the target call action includes the second delay controller 1303, the first controller 1304 and the second action 1305, in the process of executing the target call action, it is necessary to reach the target call delay After a period of time, the second action 1305 is executed under the control of the first controller 1304 .

Taking the target controller as the sequence controller as an example, in an exemplary example, step 1004 and step 1005 may be replaced by step 1004D and step 1005D.

Step 1004D, if the target invocation action includes at least one target controller, determine the target invocation sequence corresponding to each candidate simple action indicated by the target controller.

Among them, the sequence controller is used to define the execution sequence of several simple actions. For example, if the sequence controller corresponds to simple action A and simple action B, the sequence controller defines the calling sequence of simple action A and simple action B. Call The sequence may be to execute call action B first, and then call action A. Correspondingly, a general sequence controller includes at least two child nodes, that is, the sequence controller is associated with at least two candidate simple actions, so as to define the target invocation sequence of at least two child nodes or at least two candidate simple actions.

In a possible implementation, when the sequence controller is included in the target call action, when the sequence controller is executed, it is necessary to determine the target call sequence of each candidate simple action indicated by the sequence controller, and then based on The target invocation sequence executes the target simple actions in turn.

Step 1005D: Determine the candidate simple actions as the target simple actions in sequence based on the calling sequence of the targets, and execute each target simple action in sequence.

In a possible implementation manner, based on the execution order of each candidate simple action indicated by the target call sequence, each candidate simple action is sequentially determined as the target simple action, and each target simple action is sequentially executed, that is, sequence control Each candidate simple action associated with the controller needs to be executed in a fixed execution sequence, and the same micro-application function can only be realized after all the candidate simple actions are executed.

Further, in the process of executing the target simple action based on the target call sequence, when the nth target simple action is successfully executed, the n+1th target simple action can be continued until all candidate simple actions are successfully executed; otherwise, when After the execution of the nth target simple action fails, the follow-up target simple action cannot be executed, and correspondingly stop the execution of the n+1th target simple action. That is to say, each child node of the sequence controller will be scheduled sequentially, and as long as there is a child node that fails to execute, the execution will stop.

As shown in FIG. 14 , it shows a schematic diagram of a condition controller shown in an exemplary embodiment of the present application. The target call action includes a sequence controller 1401, a first controller 1402, a first action 1403, a second action 1404, a second controller 1405, and a third action 1406. The sequence controller 1401 defines the call sequence between the various actions It is the first action 1403-the second action 1404-the third action 1406; when executing the target call action, firstly based on the call sequence indicated by the sequence controller 1401, the first controller 1402 controls the execution of the first action 1403 first, When the first action 1403 is executed successfully, continue to execute the second action 1404; when the second action 1404 is executed successfully, the second controller 1405 controls to execute the third action 1406. The sequence controller 1401 will not complete the execution until the third action 1406 is executed. Optionally, if the execution of the first action fails, the second action 1404 and the third action 1406 cannot be executed; if the execution of the second action 1404 fails, the execution of the third action 1406 cannot continue; if the execution of the third action 1406 fails, even The first action 1403 and the second action 1404 are executed successfully, but the micro-application function corresponding to the sequence controller 1401 cannot be realized.

Taking the target controller as the selection controller as an example, in an exemplary example, step 1004 and step 1005 may be replaced by step 1004E and step 1005E.

Step 1004E, if the target calling action includes at least one target controller, determine the target calling sequence indicated by the target controller.

Among them, the selection controller can also define the execution sequence of several simple actions. Correspondingly, the general selection controller also contains at least two child nodes, that is, the selection controller is associated with at least two candidate simple actions; different from the sequence controller, The sub-nodes of the selection controller are scheduled sequentially, and return when there are sub-nodes executed successfully; that is to say, each sub-node corresponding to the selection controller can implement the same micro-application function, as long as a single sub-node call is successful, it can be realized The microapp functions without requiring all child nodes to be called successfully.

In a possible implementation, when a selection controller is included in the target call action, when the selection controller is executed, it is necessary to determine the target call sequence of each candidate simple action indicated by the selection controller, and then based on The target invocation sequence executes the target simple actions in sequence until the target simple actions are successfully executed.

Step 1005E: Execute the candidate simple actions sequentially based on the target calling sequence; if there is a candidate simple action that is successfully executed, determine the candidate simple action as the target simple action, and stop executing other candidate simple actions.

In a possible implementation manner, each candidate simple action is executed sequentially based on the execution order of each candidate simple action indicated by the target call sequence, and when there is a candidate simple action that is successfully executed, the candidate simple action is determined as the target simple action , and stop executing other candidate simple actions; on the contrary, if the candidate simple actions fail to execute, continue to execute other candidate simple actions according to the target call sequence.

As shown in FIG. 15 , it shows a schematic diagram of a selection controller shown in an exemplary embodiment of the present application. The target call action includes a selection controller 1501, a first controller 1502, a first action 1503, a second action 1504, a second controller 1505, and a third action 1506, and the selection controller 1501 defines the calling order of each action It is the first action 1503-the second action 1504-the third action 1506; when executing the target invocation action, firstly based on the invocation order indicated by the selection controller 1501, the execution of the first action 1503 is preferentially controlled by the first controller 1502, When the first action 1503 is executed successfully, there is no need to execute the second action 1504 and the third action 1506; when the first action 1503 fails, continue to execute the second action 1504; Action 1506; if the execution of the second action 1504 fails, the second controller 1505 needs to control the execution of the third action 1506 . If the third action 1506 is executed successfully, it means that the corresponding micro-application function can be realized; if the third action 1506 fails to be executed, it means that the micro-application function cannot be realized.

Taking the target controller as a parallel controller as an example, in an exemplary example, step 1005 may be replaced with step 1005F.

In step 1005F, each candidate simple action is determined as a target simple action, and each target simple action is executed in parallel.

Among them, the parallel controller indicates that several simple actions need to be executed in parallel. Correspondingly, a general parallel controller also includes at least two child nodes, that is, the parallel controller is associated with at least two candidate simple actions, so as to execute each candidate simple action at the same time.

In a possible implementation manner, when the target call action includes a parallel controller, when the parallel controller is executed, each candidate simple action associated with the parallel controller is determined as the target simple action, and then Execute individual target simple actions in parallel.

As shown in FIG. 16 , it shows a schematic diagram of a parallel controller shown in an exemplary embodiment of the present application. The target calling action includes a parallel controller 1601, a first controller 1602, a first action 1603, a second action 1604, a second controller 1605, and a third action 1606; when the target calling action is executed, the first action 1603 is executed in parallel , the second action 1604 and the third action 1606 , that is, triggering the first controller 1602 to control the execution of the first action 1603 , triggering the execution of the second action 1604 , and triggering the second controller 1605 to execute the third action 1606 .

Optionally, the target invocation action may contain a combination of several controllers, and may contain different types of controllers, so as to realize more complicated invocation actions. Schematically, the target call action including various controllers can be defined in the micro-app script as:

It can be seen from this definition that the micro-application is implemented by xml syntax, and the micro-application contains two triggers: the trigger corresponding to the event "xxx" and the trigger corresponding to the event "yyy", wherein the trigger event "xxx" corresponds to the trigger The call action associated with the trigger is composed of a parallel controller, a selection controller, and actions A to E; the call action associated with the trigger event "yyy" is composed of a condition controller, action B and action C.

In this embodiment, the control logic of various controllers included in the call action is defined, so that the combination of several simple actions can be realized by combining various controllers to support more complex call action logic, so as to satisfy The application development requirements of developers in different complex scenarios.

The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 17 , which shows a structural block diagram of a micro-application running device provided by an embodiment of the present application. The device can include:

A script acquisition module 1701, configured to acquire a target micro-application script of the target micro-application, where the target micro-application script consists of at least one trigger;

A trigger module 1702, configured to trigger a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event;

A data reading module 1703, configured to read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas;

The action calling module 1704 is configured to execute the target calling action corresponding to the target trigger based on the event parameter.

Optionally, the action type of the target call action includes a simple action type and a combined action type, the target call action under the simple action type is composed of a single target simple action, and the target call action under the combined action type Consisting of at least one object controller and at least one of said object simple actions, said object controller being used to instruct an object invocation logic of said object simple action;

The action calling module 1704 is also used for:

In the case that the target calling action includes at least one target controller, at least one target simple action is controlled by at least one target controller.

Optionally, the target invocation action includes a target simple action located at a parent node and a target simple action located at a child node;

The action calling module 1704 is also used for:

controlling and executing the target simple action located at the parent node through the target controller, and acquiring target service data fed back after executing the target simple action located at the parent node;

Reading the target service data from the second data storage area, the target simple actions located in the parent node are different, and correspond to different second data storage areas;

Based on the target service data, the target simple action at the child node is executed.

Optionally, the device also includes:

A data storage module, configured to store the operating environment parameters corresponding to the target micro-application in a third data storage area, and the third data storage area allows access to the calling action triggered by each of the triggers.

The action calling module 1704 is also used for:

Where the target invocation action includes at least one of the target controllers, determining the target invocation logic indicated by the target controller;

Based on the target invocation logic, the target simple action is executed.

The action calling module 1704 is also used for:

determining a target scheduling condition indicated by the target controller;

The action calling module 1704 is also used for:

Optionally, the target controller is a loop controller;

The action calling module 1704 is also used for:

determining a target cycle condition indicated by the target controller;

The action calling module 1704 is also used for:

If the execution state of the target simple action does not meet the target cycle condition, continue to execute the target simple action cyclically.

Optionally, the action calling module 1704 is also used to:

In the case that the number of executions of the target simple action does not reach the number threshold, continue to execute the target simple action in a loop;

If the target service corresponding to the target simple action is not invoked successfully, continue to execute the target simple action in a loop;

If the target service corresponding to the target simple action does not fail to be invoked, the target simple action continues to be cyclically executed.

Optionally, the target controller is a delay controller;

The action calling module 1704 is also used for:

determining a target invocation latency indicated by the target controller;

The action calling module 1704 is also used for:

In case the target call delay is reached, the target simple action is executed.

The action calling module 1704 is also used for:

determining the target invocation sequence corresponding to each of the candidate simple actions indicated by the target controller;

The action calling module 1704 is also used for:

Based on the target calling sequence, the candidate simple actions are sequentially determined as the target simple actions, and each of the target simple actions is sequentially executed.

Optionally, the action calling module 1704 is also used to:

If the nth target simple action is successfully executed, continue to execute the n+1th target simple action;

The device also includes:

A stop execution module, configured to stop execution of the n+1th target simple action when the nth target simple action fails to be executed.

The action calling module 1704 is also used for:

determining the target invocation sequence indicated by the target controller;

The action calling module 1704 is also used for:

executing the candidate simple actions sequentially based on the target invocation sequence;

If there is a candidate simple action that is successfully executed, determine the candidate simple action as the target simple action, and stop executing other candidate simple actions.

The action calling module 1704 is also used for:

Each of the candidate simple actions is determined as the target simple action, and each of the target simple actions is executed in parallel.

Please refer to FIG. 18 , which shows a structural block diagram of a computer device provided by an exemplary embodiment of the present application. The computer device 1800 may be implemented as a source device or a destination device in each of the foregoing embodiments. Computer device 1800 may include one or more of the following components: processor 1810 and memory 1820 .

Processor 1810 may include one or more processing cores. The processor 1810 uses various interfaces and lines to connect various parts of the entire computer device 1800, and executes by running or executing instructions, programs, code sets or instruction sets stored in the memory 1820, and calling data stored in the memory 1820. Various functions of the computer device 1800 and processing data. Optionally, the processor 1810 may adopt at least one of Digital Signal Processing (Digital Signal Processing, DSP), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), and Programmable Logic Array (Programmable Logic Array, PLA). implemented in the form of hardware. The processor 1810 can integrate one or more of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), a neural network processor (Neural-network Processing Unit, NPU) and a modem, etc. The combination. Among them, the CPU mainly handles the operating system, user interface and application programs, etc.; the GPU is used to render and draw the content that needs to be displayed on the touch screen; the NPU is used to realize the artificial intelligence (Artificial Intelligence, AI) function; the modem is used to process Wireless communication. It can be understood that, the above-mentioned modem may not be integrated into the processor 1810, but may be realized by a single chip.

The memory 1820 may include random access memory (Random Access Memory, RAM), and may also include read-only memory (Read-Only Memory, ROM). Optionally, the memory 1820 includes a non-transitory computer-readable storage medium. The memory 1820 may be used to store instructions, programs, codes, sets of codes or sets of instructions. The memory 1820 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), Instructions and the like for implementing the various method embodiments described below; the storage data area can store data created according to the use of the computer device 1800 (such as audio data, phonebook) and the like.

In addition, those skilled in the art can understand that the structure of the computer device 1800 shown in the above drawings does not constitute a limitation to the computer device, and the computer device may include more or less components than those shown in the illustration, or combine certain components, or a different arrangement of components. For example, the computer device 1800 also includes a display screen, a camera component, a microphone, a speaker, a radio frequency circuit, an input unit, a sensor (such as an acceleration sensor, an angular velocity sensor, a light sensor, etc.), an audio circuit, a WiFi module, a power supply, a Bluetooth module, etc. components, which will not be repeated here.

The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores at least one program code, and the program code is loaded and executed by a processor to realize the micro-application described in each of the above embodiments. run method.

An embodiment of the present application provides a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the micro-application running method provided in various optional implementation manners of the above aspect.

It should be understood that the "plurality" mentioned herein refers to two or more than two. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship. In addition, the numbering of the steps described herein only exemplarily shows a possible sequence of execution among the steps. In some other embodiments, the above-mentioned steps may not be executed according to the order of the numbers, such as two different numbers The steps are executed at the same time, or two steps with different numbers are executed in the reverse order as shown in the illustration, which is not limited in this embodiment of the present application.

The above are only optional embodiments of the application, and are not intended to limit the application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the application shall be included in the protection of the application. within range.

Claims

A method for running a micro-application, the method comprising:

acquiring a target micro-application script of the target micro-application, wherein the target micro-application script is composed of at least one trigger;

triggering a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event;

Reading event parameters corresponding to the target trigger event from the first data storage area, where different triggers correspond to different first data storage areas;

Based on the event parameters, execute the target invocation action corresponding to the target trigger.
The method according to claim 1, wherein the action types of the target call actions include simple action types and combined action types, the target call action under the simple action type is composed of a single target simple action, and the combined action The target invocation action under type is composed of at least one target controller and at least one target simple action, and the target controller is used to indicate the target invocation logic of the target simple action;

The execution of the target invocation action corresponding to the target trigger includes:

In the case that the target calling action includes at least one target controller, at least one target simple action is controlled by at least one target controller.
The method according to claim 2, wherein the target invocation action includes a target simple action located at a parent node and a target simple action located at a child node;

The performing at least one target simple action controlled by at least one target controller includes:

controlling and executing the target simple action located at the parent node through the target controller, and acquiring target service data fed back after executing the target simple action located at the parent node;

Reading the target service data from the second data storage area, the target simple actions located in the parent node are different, and correspond to different second data storage areas;

Based on the target service data, the target simple action at the child node is executed.
The method according to claim 1, wherein the method further comprises:

The operating environment parameters corresponding to the target micro-application are stored in a third data storage area, and the third data storage area allows access to the calling action triggered by each of the triggers.
The method according to any one of claims 1 to 4, wherein the action type of the target invocation action includes a simple action type and a combined action type, and the target invocation action under the simple action type is composed of a single target simple action, The target invocation action under the combined action type is composed of at least one target controller and at least one target simple action, and the target controller is used to indicate the target invocation logic of the target simple action;

The execution of the target invocation action corresponding to the target trigger includes:

Where the target invocation action includes at least one of the target controllers, determining the target invocation logic indicated by the target controller;

Based on the target invocation logic, the target simple action is executed.
The method according to claim 5, wherein the target controller is a conditional controller, and the conditional controller is associated with at least two candidate simple actions;

The determining the target calling logic indicated by the target controller includes:

determining a target scheduling condition indicated by the target controller;

The step of invoking logic based on the target and executing the simple action of the target includes:

Based on the target scheduling condition, the target simple action is determined from the candidate simple actions, and the target simple action is executed.
The method according to claim 5, wherein the target controller is a loop controller;

The determining the target calling logic indicated by the target controller includes:

determining a target cycle condition indicated by the target controller;

The step of invoking logic based on the target and executing the simple action of the target includes:

If the execution state of the target simple action does not meet the target cycle condition, continue to execute the target simple action cyclically.
The method according to claim 7, wherein when the execution state of the target simple action does not meet the target cycle condition, continuing to execute the target simple action comprises any of the following:

In the case that the number of executions of the target simple action does not reach the number threshold, continue to execute the target simple action in a loop;

If the target service corresponding to the target simple action is not invoked successfully, continue to execute the target simple action in a loop;

If the target service corresponding to the target simple action does not fail to be invoked, the target simple action continues to be cyclically executed.
The method according to claim 5, wherein the target controller is a delay controller;

The determining the target calling logic indicated by the target controller includes:

determining a target invocation latency indicated by the target controller;

The step of invoking logic based on the target and executing the simple action of the target includes:

In case the target call delay is reached, the target simple action is executed.
The method according to claim 5, wherein the target controller is a sequence controller, and the sequence controller is associated with at least two candidate simple actions;

The determining the target calling logic indicated by the target controller includes:

determining the target invocation sequence corresponding to each of the candidate simple actions indicated by the target controller;

The step of invoking logic based on the target and executing the simple action of the target includes:

Based on the target calling sequence, the candidate simple actions are sequentially determined as the target simple actions, and each of the target simple actions is sequentially executed.
The method according to claim 10, wherein said sequentially performing each of said target simple actions comprises:

If the nth target simple action is successfully executed, continue to execute the n+1th target simple action;

The method also includes:

If the execution of the nth target simple action fails, the execution of the n+1th target simple action is stopped.
The method according to claim 5, wherein the target controller is a selection controller, and the selection controller is associated with at least two candidate simple actions;

The determining the target calling logic indicated by the target controller includes:

determining the target invocation sequence indicated by the target controller;

The step of invoking logic based on the target and executing the simple action of the target includes:

Based on the target invocation sequence, execute the candidate simple actions in sequence; if there is a candidate simple action that is successfully executed, determine the candidate simple action as the target simple action, and stop executing other candidate simple actions action.
The method according to claim 5, wherein the target controller is a parallel controller, and the parallel controller is associated with at least two of the candidate simple actions;

The step of invoking logic based on the target and executing the simple action of the target includes:

Each of the candidate simple actions is determined as the target simple action, and each of the target simple actions is executed in parallel.
A micro-application running device, the device comprising:

A script acquisition module, configured to acquire a target micro-application script of the target micro-application, wherein the target micro-application script is composed of at least one trigger;

A trigger module, configured to trigger a target trigger corresponding to the target trigger event in the target micro-application script in response to the target trigger event;

A data reading module, configured to read event parameters corresponding to the target trigger event from the first data storage area, and different triggers correspond to different first data storage areas;

An action calling module, configured to execute a target calling action corresponding to the target trigger based on the event parameter.
The device according to claim 14, wherein the action type of the target-invoking action includes a simple action type and a combined action type, the target-invoking action under the simple action type is composed of a single target simple action, and the combined action The target invocation action under type is composed of at least one target controller and at least one target simple action, and the target controller is used to indicate the target invocation logic of the target simple action;

The action call module is also used for:

In the case where the target call action includes at least one target controller, at least one target simple action is controlled by at least one target controller.
The apparatus according to claim 15, wherein the target invocation action comprises a target simple action located at a parent node and a target simple action located at a child node;

The action call module is also used for:

controlling and executing the target simple action located at the parent node through the target controller, and acquiring target service data fed back after executing the target simple action located at the parent node;

Reading the target service data from the second data storage area, the target simple actions located in the parent node are different, and correspond to different second data storage areas;

Based on the target service data, the target simple action at the child node is executed.
The apparatus according to claim 14, wherein said apparatus further comprises:

A data storage module, configured to store the operating environment parameters corresponding to the target micro-application in a third data storage area, and the third data storage area allows access to the calling action triggered by each of the triggers.
A computer device, characterized in that the computer device includes a processor and a memory; the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement any of claims 1 to 13. A running method of the micro-application.
A computer-readable storage medium, characterized in that at least one piece of program code is stored in the computer-readable storage medium, and the program code is loaded and executed by a processor to implement the method described in any one of claims 1 to 13. How the microapp runs.
A computer program product, characterized in that the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer-readable Instructions, the processor executes the computer instructions, so that the computer device executes the micro-application running method according to any one of claims 1 to 13.