WO2023093429A1 - Micro-application running method and apparatus, and device, storage medium and program product - Google Patents

Abstract

A micro-application running method and apparatus, and 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, wherein the target micro-application is a set composed of services, the target micro-application script is composed of a trigger, and the trigger is used for performing service invoking by means of executing control logic under a trigger event (301); when a target trigger event has been received, triggering a target trigger corresponding to the target trigger event in the target micro-application script (302); and executing target control logic corresponding to the target trigger, and invoking a target service, so as to realize a micro-application function of the target micro-application (303). Since the running of a micro-application is based on a micro-application script with a low code amount, a storage space needing to be occupied is relatively small; and services are assembled into a micro-application, and the componentization of the micro-application is realized by using an invoking relationship between micro-application script management services, which is conducive to reducing the difficulty of micro-application development.

Description

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

This application claims the priority of the Chinese patent application with the application number 202111434742.1 and the title of the invention "Operation method, device, equipment, storage medium and program product of micro-application" filed on November 29, 2021, the entire contents of which are incorporated by reference incorporated in this application.

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:

Acquire the target micro-application script of the target micro-application, the target micro-application is a collection of services, the target micro-application script is composed of triggers, and the triggers are used to perform service calls by executing control logic under trigger events ;

In the case of receiving a target trigger event, trigger a target trigger corresponding to the target trigger event in the target micro-application script;

Execute the target control logic corresponding to the target trigger, and call the target service, so as to realize the micro-application function of the target micro-application.

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

The script obtaining module is used to obtain the target micro-application script of the target micro-application, the target micro-application is a collection of services, the target micro-application script is composed of a trigger, and the trigger is used to pass Execute control logic to make service calls;

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

The service calling module is used to execute the target control logic corresponding to the target trigger, and call the target service to realize the micro-application function of the target micro-application.

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 program, and the at least one program 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 program is stored in the computer-readable storage medium, and the at least one program is loaded and executed by a processor to implement the above-mentioned The running method of the microapp.

On the other hand, an embodiment of the present application provides a computer program product, the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer-readable storage medium from the computer-readable storage medium. A computer instruction, 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 foregoing aspect.

Description of drawings

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

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

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

Fig. 4 is a schematic interface diagram of a micro-application subscription process shown in an exemplary embodiment of the present application;

Fig. 5 is an implementation schematic diagram of a micro-application subscription process shown in an exemplary embodiment of the present application;

Fig. 6 is an implementation schematic diagram of a micro-application unsubscribing process shown in an exemplary embodiment of the present application;

FIG. 7 is a flow chart of a target service determination process shown in an exemplary embodiment of the present application;

Fig. 8 is an implementation schematic diagram of a service invocation process shown in an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of an implementation process of a service agent invoking a service process shown in an exemplary embodiment of the present application;

Fig. 10 is a flowchart of a static service invocation process shown in an exemplary embodiment of the present application;

Fig. 11 is a flowchart of a dynamic service invocation process shown in an exemplary embodiment of the present application;

Fig. 12 is a schematic diagram of implementation of service differential deployment shown in an exemplary embodiment of the present application;

Fig. 13 is an implementation schematic diagram of an engine state synchronization process shown in an exemplary embodiment of the present application;

Fig. 14 is a flowchart of a micro-app script acquisition process shown in an exemplary embodiment of the present application;

Fig. 15 is a schematic diagram of a target micro-application determination process shown in an exemplary embodiment of the present application;

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

Fig. 17 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. 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.

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 may be xml or javascript.

As shown in FIG. 1 , 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.

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-application 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.

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. 2 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. 2 , the device 210 includes a smart phone, a tablet computer, and a vehicle 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 lifecycle 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. 2 , 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. 2 , 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. 2 , 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 micro-app scripts of micro-apps from the micro-app store server 222 . Schematically, as shown in Figure 2, 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. 3 , 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. 2 as an example for illustration. The method include:

Step 301 , acquire the target micro-application script of the target micro-application. The target micro-application is a collection of services, and the target micro-application script is composed of triggers, and the triggers are used to call services by executing control logic under trigger events.

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-application script is composed of several triggers, and each trigger is used to trigger under a specific trigger event, and after triggering, the service call is made through the corresponding control logic of the trigger.

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 302, in the case of receiving the target trigger event, trigger the target trigger corresponding to the target trigger event in the target micro-application script.

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 control logic corresponding to the trigger through the micro-application engine 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 303, execute the target control logic corresponding to the target trigger, and call the target service, so as to realize the micro-application function of the target micro-application.

In a possible implementation manner, the computer device executes the target control logic corresponding to the target trigger through the runtime module in the micro-application engine, and then the target control logic invokes the target service. Optionally, when the services called by the target control logic include at least two services, the at least two services will be called sequentially according to the business logic.

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 302 and 303, 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 the present application, when running a micro-application composed of several services, the computer device obtains the micro-application script of the micro-application, and triggers the corresponding trigger in the micro-application script based on the received trigger event, Then, by executing the control logic corresponding to the trigger, the corresponding service is called to realize the micro-application function of the micro-application. Since the operation of micro-applications is based on micro-application scripts with low code volume, it requires less storage space than traditional applications; moreover, assemble services into micro-applications, and use micro-application scripts to manage the calling relationship between services , realizing the componentization of micro-applications, improving the reusability of services between micro-applications, and helping to reduce the difficulty of developing micro-applications.

Optionally, before invoking the target service, the method includes:

Determining a candidate service list based on the service identifier of the service invoked by the target control logic, where at least one candidate service matching the service identifier is included in the candidate service list;

The target service is determined from the candidate services in the candidate service list.

Optionally, based on the service identifier of the service invoked by the target control logic, determine a list of candidate services, including:

Determine a candidate static service that matches the service identifier in the current device, where the static service is a service provided by a host application in the device;

Determining a candidate dynamic service matching the service identifier from the cloud service library, wherein the dynamic service is a service that supports dynamic deployment to the device;

A candidate service list is generated based on the candidate static services and the candidate dynamic services.

Optionally, the target service is determined from the candidate services in the candidate service list, including:

Display a list of candidate services;

determining the selected candidate service as the target service in response to a selection operation on the candidate service in the candidate service list; or,

Based on the service selection strategy, the target service is determined from the candidate services in the candidate service list.

Optionally, call the target service, including:

The target service is invoked through the target service gateway, where the target service gateway is the service gateway of the current device, and/or, the service gateway of an external device other than the current device, and the target micro-application script is set in the external device.

Optionally, call the target service through the target service gateway, including:

When the target service gateway is the service gateway of the current device, the service invocation request is obtained through the target service gateway; the target service proxy corresponding to the target service is determined through the target service gateway; based on the service invocation request, the target service is invoked through the target service proxy;

When the target service gateway is the service gateway of the external device, the service call request is sent to the external device, and the external device is used to determine the target service proxy corresponding to the target service through the target service gateway, and based on the service call request, through the target service proxy call target service;

Wherein, different service agents correspond to different programming development languages, or different service agents correspond to different deployment forms, or different service agents correspond to different operating environments.

Optionally, based on the service invocation request, the target service is invoked through the target service proxy, including:

Convert the original input parameters in the service call request through the target service agent to obtain the target input parameters, wherein the original input parameters adopt a unified parameter format, and the target input parameters conform to the parameter format of the target service;

Based on the target input parameters, the target service is invoked through the target service proxy to obtain the original output parameters of the target service;

The original output parameters are converted by the target service agent to obtain the target output parameters, and the target output parameters adopt a unified parameter format.

Optionally, based on the service invocation request, before invoking the target service through the target service proxy, the method further includes:

When the target service is a static service, obtain the service status of the target service through the static service manager;

When the service status is not started, start the target service.

Optionally, based on the service invocation request, before invoking the target service through the target service proxy, the method further includes:

When the target service is a dynamic service, obtain the service status of the host service corresponding to the target service through the dynamic service manager;

When the service status is not started, start the host service;

Query the deployment status of the target service through the host service;

If the target service is not deployed, download the target service from the cloud service library, and load the target service through the host service.

Optionally, after invoking the target service, the method further includes:

When the target service is a synchronous call service, obtain the service return value of the target service; call the next service based on the service return value;

In the case that the target service is an asynchronous call service, the service output event of the target service is obtained; the trigger in the target micro-application script is triggered by the service output event.

Optionally, before obtaining the target micro-application script of the target micro-application, the method includes:

downloading a target microapplication script for the target microapplication in response to a subscribe operation to the target microapplication; or,

When a subscription push message is received, the target microapp script of the target microapp is downloaded based on the application identifier in the subscription push message. The subscription push message is sent to the user account when the server detects that the microapp subscribed by the user account has changed. Each device under push.

Optionally, after downloading the target micro-application script of the target micro-application, the method further includes:

Based on the initialization trigger in the target micro-application script, the initialization service is deployed, and the initialization service is the service invoked by the initialization trigger.

Optionally, the method also includes:

deleting the target microapplication script of the target microapplication in response to an unsubscribe operation on the target microapplication;

A subscription cancellation instruction is sent to the server, and the server is configured to push a subscription cancellation message to each device under the user account based on the subscription cancellation instruction, so that each terminal deletes the target micro-app script.

Optionally, obtain the target microapp script of the target microapp, including:

When an initialization trigger event is received, at least one candidate micro-application corresponding to the initialization trigger event is determined, and the initialization trigger event is used to trigger an initialization trigger of at least one candidate micro-application;

determining a target microapplication from at least one candidate microapplication;

Get the target microapp script for the target microapp.

Optionally, determining a target micro-application from at least one candidate micro-application includes:

displaying a microapplication selection list based on at least one candidate microapplication; determining the selected candidate microapplication as a target microapplication in response to a selection operation on the microapplication selection list; or,

Based on the application selection strategy, a target micro-application is determined from at least one candidate micro-application.

Since the micro-app is not bound to the device but to the user, before using the target micro-app, it is first necessary to subscribe to the micro-app through the user account, so as to download the target micro-app script corresponding to the target micro-app to the individual devices.

For the subscription initiator device, in a possible implementation manner, in response to a subscription operation on the target micro-application, the subscription initiator device downloads the target micro-application script of the target micro-application.

Optionally, the subscription initiator device can obtain a micro-app list including all micro-apps by accessing the micro-app store server, and download the micro-app from the micro-app store server when receiving a subscription operation to the target micro-app in the micro-app list Target microapp script.

Optionally, the subscription initiator device can also use the micro-app search engine of the micro-app store server to search for micro-apps by inputting micro-app keywords, and then initiate a subscription operation to the target micro-app from the search results.

Wherein, the subscription operation may be a click operation on a subscription control corresponding to the target micro-application.

Schematically, as shown in FIG. 4 , the subscription initiator device accesses the micro-app store, and displays each micro-app in the micro-app list on the micro-app store interface 41 , including micro-apps subscribed and unsubscribed by the current user account. Alternatively, the user may enter a micro-application keyword in the search bar of the micro-application store interface 41, and click the search control 43 to trigger the micro-application store server to feed back micro-applications containing the micro-application keyword. When receiving a click operation on the subscription control 42 corresponding to the target micro-application, the subscription initiator device downloads the target micro-application script from the micro-application store server according to the application identifier of the target micro-application.

For other devices that log in to the same user account as the subscription initiator device, in a possible implementation manner, when receiving the subscription push message, the computer device downloads the target The micro-application script, wherein the subscription push message is pushed to each device under the user account when the server detects that the micro-application subscribed to by the user account changes.

Optionally, after the subscription initiator device finishes subscribing to the target micro-application, the user resource management server updates the subscription relationship between the user account and the micro-application based on the user account logged in by the subscription initiator device and the application identifier of the target micro-application, and Based on inquiring about the devices under the user account, a subscription push message is sent to each of the queried devices, and the subscription push message at least includes the application identifier of the target micro-application.

After the computer device receives the subscription push message, it knows that other devices that log in to the same user account as itself have subscribed to the target micro-app, and then downloads the target micro-app script of the target micro-app from the micro-app store server based on the application identifier in the subscription push message .

Schematically, as shown in FIG. 5 , after device A logging in to the user account "Zhang San" accesses the micro-app store server 52 and subscribes to the micro-app, the application management module 511 in the user resource management server 51 adds "Zhang San" The subscription relationship with the micro-app, and through the device management module 512, it is found that the user account "Zhang San" also includes device B and device C, so as to send subscription push messages to device B and device C. After device B and device C receive the subscription push message, they automatically download the micro application script from the micro application store server 52 through the micro application engine.

Since the services in the micro-app are connected in series by the business logic, and the device to which the service is deployed can only be determined at runtime, after the micro-app script of the micro-app is downloaded, the initialization trigger in the micro-app script needs to be executed immediately, and the The service called by the initial trigger is deployed on the current device, so as to ensure the normal operation of the micro application.

In a possible implementation manner, after the computer device downloads the target micro-application script of the target micro-application, an initialization service is deployed based on an initialization trigger in the target micro-application script, where the initialization service is a service called by the initialization trigger, and The quantity of the initialization service is at least one.

In an illustrative example, when the micro-application is used to realize cross-device screen capture by tapping with two fingers, the micro-application script of the micro-application includes an initialization trigger, a trigger for tapping with two fingers, and an end trigger. Since the two-finger tap service needs to be invoked in the initialization trigger, the double-finger tap service needs to be pre-deployed on the device to avoid failure to capture the double-finger tap event due to the non-pre-deployment of the two-finger tap service, which in turn cannot trigger the two-finger tap Hit the trigger, which eventually leads to the problem that the micro application cannot run.

In addition to being able to subscribe to the micro-application, the computer device can also unsubscribe from the micro-application. In a possible implementation manner, in response to the unsubscribing operation of the target micro-application, the computer device deletes the target micro-application script of the target micro-application, so as to prevent the unsubscribed target micro-application script from occupying device storage space.

At the same time, in order to ensure the consistency of micro-application scripts in each device under the same user account, the computer device also needs to send a subscription cancellation instruction to the server, so that the server can push a subscription cancellation message to each device under the user account based on the subscription cancellation instruction, so that Each terminal deletes the target microapp script. Wherein, the subscription cancellation instruction at least includes the application identification of the target micro-application.

Schematically, as shown in FIG. 6 , after logging in to the user account "Zhang San", the device A cancels the subscription to the micro-app, and then sends a subscription cancel instruction to the user resource management server 51, and the application management module 511 in the user resource management server 51 bases on the The subscription cancellation instruction deletes the subscription relationship between "Zhang San" and the micro-app, and through the device management module 512, it is found that the user account "Zhang San" also includes device B and device C, so that by sending subscriptions to device B and device C cancel message. After receiving the subscription cancellation message, device B and device C delete the micro-app script of the micro-app.

In this embodiment, through the subscription, push and unsubscribe mechanisms, the micro-app scripts in each device under the same user account are kept consistent, avoiding the problem of abnormal use of micro-apps due to inconsistent micro-app scripts on different device sides, and ensuring The availability of micro-apps and the consistency of user experience on different device sides. In addition, after the computer device downloads the micro-application script, based on the service called by the initialization trigger in the micro-application script, the initialization service is pre-deployed to ensure the normal operation of subsequent micro-applications.

In the embodiment of the present application, the called service is defined in the micro-application script, but in actual situations, there may be multiple specific service instances for realizing the same service function. For example, the payment function can be realized through the payment service A provided by the payment application, the payment service B provided by the instant messaging application, or the payment dynamic service C. Therefore, before invoking the target service, the computer device first needs to determine the target service from several candidate services. In a possible implementation manner, as shown in FIG. 7 , the process for the computer device to determine the target service includes the following steps.

Step 701: Determine a candidate service list based on the service ID of the service invoked by the target control logic, and the candidate service list includes at least one candidate service matching the service ID.

In a possible implementation, the target control logic in the target micro-application script includes the service identifier of the called service, and when the runtime module in the micro-application engine executes the target control logic, it obtains the service identifier, thereby passing the service The scheduling module determines at least one candidate service matching the service identifier. Wherein, the service identifier may be a service name or a service ID, which is not limited in this embodiment.

Since the service invoked by the control logic may be either a static service or a dynamic service, the computer device needs to query available candidate services locally and from the cloud. Optionally, this step may include the following sub-steps:

1. Determine the candidate static service matching the service identifier in the current device, wherein the static service is a service provided by the host application in the device.

The static service is a pre-installed service, and its invocation depends on the host application, that is, the static service can be invoked only when the host application is installed. In a possible implementation manner, the service management module is used to manage the static services provided by the host application in the local device. After obtaining the service identifier, the service scheduling module queries the local device for candidate services that match the service identifier through the service management module. static service.

In an illustrative example, based on the service name "payment", the service management module determines the payment service A provided by the payment application and the payment service B provided by the instant messaging application as candidate static services (the computer device is installed with payment application A and instant messaging Communication application B).

2. Determine the candidate dynamic service that matches the service identifier from the cloud service library, where the dynamic service is a service that supports dynamic deployment to the device.

As a service that supports dynamic deployment, dynamic services do not depend on pre-installed applications, and the dynamic services that can be called are uniformly stored in the cloud service library. In a possible implementation manner, based on the service identifier, the service scheduling module queries the cloud service library for candidate dynamic services matching the service identifier.

In an illustrative example, the service dispatching module queries the payment dynamic service C from the cloud service library based on the service name "payment", and determines the payment dynamic service C as a candidate dynamic service.

It should be noted that after the candidate dynamic service is determined, the computer device does not directly download the service, but performs service download when the target service is determined and belongs to the candidate dynamic service.

3. Generate a candidate service list based on the candidate static service and the candidate dynamic service.

Further, the computer device combines the queried candidate dynamic services and candidate static services to obtain a candidate service list.

Step 702, determine the target service from the candidate services in the candidate service list.

Optionally, when the candidate service list contains only one candidate service, the computer device directly determines the candidate service as the target service; when the candidate service list contains at least two candidate services, the computer device needs to determine the target service therefrom.

In a possible implementation manner, the computer device displays a list of candidate services, and the user selects a target service to call from the list of candidate services. In response to a selection operation on a candidate service in the candidate service list, the computer device determines the selected candidate service as the target service.

In some embodiments, the computer device may display a list of candidate services in the form of a pop-up window, and determine a target service when receiving a click operation on a candidate service in the list of candidate services. The embodiment of the present application does not limit the display manner of the candidate service list.

In another possible implementation manner, the computer device may automatically determine the target service from the candidate services based on the service selection policy. Optionally, the computer device may determine the target service based on at least one of user information, device information, historical use records, and service information. This embodiment does not limit the specific service selection strategy.

For example, when the candidate service list includes the payment service A provided by the payment application, the payment service B provided by the instant messaging application, and the payment dynamic service C, based on the historical payment records of the current device, the computer device will determine the payment service A with the highest frequency of use. serve the purpose.

For another example, when the list of candidate services includes services provided by different types of devices, the computer device may, based on the location relationship between the current device and each device (which can be determined based on information such as location and network location), select the service provided by the nearest device. The service identified as the target service.

After the target service is determined, the computer device further invokes the target service. Wherein, when the target service is a static service, the computer device does not need to dynamically download the target service, and when the target service is a dynamic service, the computer device needs to determine whether to download and deploy in real time based on the deployment of the dynamic service.

In a schematic example, as shown in FIG. 8 , during execution of the control logic, the runtime module 801 requests the service scheduling module 802 to call the service based on the service identifier of the service called by the control logic. The service scheduling module 802 searches for available candidate services from the service management module 803 and the cloud service library 804 respectively based on the service identifier. The server scheduling module 802 can display a candidate service list 805 for the user to select a target application to be invoked, and can also determine a target service from several candidate services based on a service selection strategy. When the determined target service is service 1 of the C device, the service scheduling module 802 further calls service 1 in the C device through the service gateway 806 .

In this embodiment, based on the service identifier of the invoked service, the computer device queries the static service and dynamic service that match the service identifier, and further determines the target service from the queried static service and dynamic service, which enriches the service invocation. types, increasing the diversity of service implementations.

In the embodiment of the present application, the service invocation can be realized by the service gateway, and the computer device can not only invoke the local service through its own service gateway, but also invoke the service through the service gateway of other devices, so as to realize the cross-terminal service invocation. In a possible implementation manner, when the computer device invokes the target service, it determines the target device providing the target service, so as to invoke the target server through the target service gateway. Wherein, the target service gateway can be the service gateway of the current device, and/or the service gateway of an external device other than the current device (determined by the business logic of the micro-application), and the target micro-application script is set in the external device, that is, the external device Both the device and the current device are capable of running the target microapp.

In order to enable micro-applications to support heterogeneous operating systems and achieve cross-platform operation, service invocation requests in a uniform format must be used when invoking services. The service gateway needs to convert service invocation requests in the same format into real Service calls (because different operating systems have their own different process upper layer abstraction methods, and different call methods between processes), that is, service calls that conform to the current platform service specification.

When the target service gateway is the service gateway of the current device, in a possible implementation manner, the computer device obtains the service invocation request through the target service gateway, so as to determine the target service agent corresponding to the target service through the target service gateway. Further, based on the service invocation request, the target service is invoked through the target service proxy.

In the case where the target service gateway is the service gateway of the external device, the computer device sends a service invocation request to the external device, and the external device determines the target service agent corresponding to the target service through the target service gateway, and based on the service invocation request, through the target service The proxy invokes the target service.

Optionally, when the target service gateway is the service gateway of the external device, the computer device may obtain the gateway address of the service gateway of the external device through the user resource management server (device management module), so as to send the service call request based on the gateway address.

In some embodiments, based on the type of service that needs to be provided, the computer device can be deployed with different service agents as needed (for example, there is no need to deploy an Android service agent on a Windows system device), where different service agents correspond to different Programming development languages (such as java, js, php, C, C++, etc.), or, different service agents correspond to different deployment forms (such as applets, browser plug-ins, applications, etc.), or, different service agents Corresponding to different operating environments (such as virtual machines, browsers, operating systems, containers, etc.).

Schematically, as shown in Figure 9, the proxy management module 91 of the service gateway 90 is provided with an Android Service proxy 911, a cloud restful proxy 912, an Android dynamic service proxy 913 and a Web dynamic service proxy 914.

Optionally, after the target service gateway obtains the service invocation request, it determines whether a target service proxy corresponding to the target service is deployed based on the service information of the target service. If the target service proxy is deployed, the service call is made through the target service proxy; if the target service proxy is not deployed, the service call cannot be made.

Regarding the specific manner in which the target service proxy invokes the target service, in a possible implementation manner, the invocation process may include the following steps:

1. Convert the original input parameters in the service call request through the target service proxy to obtain the target input parameters, wherein the original input parameters adopt a unified parameter format, and the target input parameters conform to the parameter format of the target service.

Optionally, the service proxy defines how to call the service, including how to convert the original call parameters into the parameters required by the real service, how to access the service of the specified process in the operating system, and how to convert the parameters returned by the real service into a unified format parameters and so on. Since the original input parameters in the unified parameter format in the server invocation request do not conform to the parameter input format of the target service, the target service agent first needs to convert the original input parameters to obtain the target input parameters that conform to the parameter format specified by the target service.

Schematically, as shown in Figure 9, when service A in the Android dynamic service 93 needs to be called, the service gateway 90 converts the original input parameters through the Android dynamic service agent 913, and calls the Android dynamic service 93 based on the converted parameters Service A in; when service B in Web dynamic service 94 needs to be invoked, service gateway 90 converts the original input parameters through Web dynamic service proxy 914, and invokes service B in Web dynamic service 94 based on the converted parameters.

2. Based on the target input parameters, the target service is invoked through the target service agent to obtain the original output parameters of the target service.

Further, the target service proxy invokes the target service based on the target input parameter, thereby obtaining the original output parameter of the target server, wherein the original output parameter conforms to the parameter input format of the target service.

3. Convert the original output parameters through the target service agent to obtain the target output parameters, and the target output parameters adopt a unified parameter format.

Since the data finally fed back to the micro-application engine needs to conform to the same parameter format, the target service agent needs to convert the original output parameters to obtain the target output parameters, and then feed the target output parameters back to the micro-application engine.

Schematically, as shown in Figure 9, the service gateway 90 converts the parameters output by service A in the Android dynamic service 93 through the Android dynamic service agent 913, and feeds back to the micro-application engine; the service gateway 90 passes the Web dynamic service agent 914 to the The parameters output by service B in the Web dynamic service 94 are converted and fed back to the micro application engine.

In this embodiment, the service gateway calls the service through the service agent, and the service agent performs parameter conversion on the calling parameters, so that the converted parameters meet the parameter requirements of the real service, ensuring that the service can be called correctly; The parameters are converted so that the converted parameters conform to the unified parameter format, which ensures the normal interaction between devices under different operating systems, platforms and operating environments, and realizes the cross-platform deployment of micro-applications.

For services with different deployment methods (static deployment and dynamic deployment), there are differences in their invocation methods. The invocation methods of static services and dynamic services are described below.

In a possible implementation, when the target service is a static service, the computer device uses a static service manager (as shown in FIG. 9, a static service manager 951 is provided in the life cycle management module 95 of the service gateway 90) Obtain the service status of the target service, and start the target service when the service status is not started. Wherein, the computer device may determine the deployment mode of the target service based on the description information of the target service.

Optionally, the static service manager is used to manage the life cycle of the static service. For example, when the static service is not invoked within the target duration, the static service manager ends the life cycle of the static service.

Optionally, if the target service is successfully started, the computer device determines the target service agent corresponding to the target service according to the description information of the target service, and performs parameter conversion through the target service agent, so that based on the host application and access information corresponding to the target service Path to invoke the target service.

Optionally, if the target service fails to start, or the target service does not meet the pre-installation conditions (for example, the host application is abnormal and the target service is unavailable), the computer device will give a failure prompt.

In a schematic example, the invocation process of the static service is shown in FIG. 10 .

Step 1001, the micro application engine initiates a service call request to the service gateway.

Step 1002, the service gateway verifies whether the request is legal; if it is legal, execute step 1003; if not, execute step 1010.

Step 1003, check whether the target service is started; if it is started, execute step 1005; if not, start the target service, and execute step 1004.

Step 1004, check whether the target service is started successfully; if the start is successful, execute step 1005; if fail to start, execute step 1010.

Step 1005, check whether there is a target service proxy corresponding to the target service; if yes, execute step 1006; if not, execute step 1010.

Step 1006, convert the input parameters through the target service proxy.

Step 1007, calling the target service based on the converted input parameters.

Step 1008, convert the output parameters through the target service proxy.

Step 1009, return the service call result to the micro application engine.

Step 1010, return call failure.

In a possible implementation, when the target service is a dynamic service, the computer device uses a dynamic service manager (as shown in FIG. 9, a dynamic service manager 952 is provided in the life cycle management module 95 of the service gateway 90) Get the service status of the host service corresponding to the target service.

Wherein, the operation of the dynamic service depends on its corresponding host service. For example, when a dynamic service creates a service for a container, the computer device obtains the service status of the container service. The embodiment of the present application does not limit the specific type of hosting service.

Therefore, when the service status of the host service is not started, the computer device starts the host service. Further, the computer device queries the deployment status of the target service through the host service.

When the target service is not deployed, the computer device downloads the target service from the cloud service library, and loads the target service through the host service. In the case that the target service has been deployed (it may be cached locally when the target service is called historically), the computer device directly loads the target service through the host service.

Optionally, the computer device needs to determine the target service proxy corresponding to the target service according to the description information of the target service, and perform parameter conversion through the target service proxy, so as to transfer the converted parameters to the host service, so that the host service can call target service.

In a schematic example, the calling process of the dynamic service is shown in FIG. 11 .

Step 1101, the micro application engine initiates a service call request to the service gateway.

Step 1102, the service gateway verifies whether the request is legal; if it is legal, execute step 1103; if not, execute step 1112.

Step 1103 , check whether the host service of the target service is started; if it is started, execute step 1105 ; if not, start the host service, and execute step 1104 .

Step 1104 , check whether the host service is started successfully; if the start is successful, perform step 1105 ; if fail to start, perform step 1112 .

Step 1105, check whether there is a target service agent corresponding to the target service; if yes, execute step 1106; if not, execute step 1112.

Step 1106, convert the input parameters through the target service agent.

Step 1107, check whether the target service is deployed through the host service; if deployed, execute step 1108; if not deployed, execute step 1109.

Step 1108, call the target service based on the converted input parameters.

Step 1109, download the target service from the cloud service library.

Step 1110, convert the output parameters through the target service proxy.

Step 1111, return the service call result to the micro application engine.

Step 1112, return call failure.

When micro-applications interact with different devices to realize micro-application functions, since the business logic on different device sides may be different, the services deployed on different device sides may also be different to achieve different functions, that is, during the running of the same micro-application , Differential deployment of services in different devices. Schematically, as shown in FIG. 12 , for the cross-device screen capture micro-application, the services invoked to realize the cross-device screen capture include two-finger tap service, picture display service and screen capture service. When a user account subscribes to the cross-device screenshot micro-app, the mobile phone, tablet, car, and TV under the user account will download the corresponding micro-app script, and after downloading the micro-app script, they will deploy dual Refers to tap service.

When the user taps the screen of the mobile phone with two fingers, the mobile phone determines that the executed business logic should be image display based on the micro-app script, downloads and dynamically deploys the image display service, and requests to call the screenshot service on the other device side. After the tablet, car machine and TV receive the service call request, based on the micro-app script, it is determined that the executed business logic should be to capture and send the screen, so as to download and dynamically deploy the screen capture service, and call the screen capture service to capture the screen of the current device and give feedback to the phone. After the mobile phone receives the screenshot image fed back by other devices, it calls the image display service to realize the screenshot display.

For different service invocation types, there are also differences in subsequent steps after the computer device completes the service invocation. In a possible implementation manner, when the target service is a synchronous call service, the computer device obtains the service return value of the target service, so as to call the next service based on the service return value (until the call of all services under the trigger is completed ); when the target service is an asynchronous call service, the computer device obtains the service output event of the target service, so as to trigger the trigger in the target micro-application script through the service output event.

Among them, the service return value can be data, files, instructions, etc. For example, the return value of the screenshot service can be the captured picture; the trigger triggered by the service output event can be a trigger other than the target trigger, or it can be the target Trigger, which is not limited in this embodiment.

Moreover, since the micro-application engines on different devices are peer-to-peer, all the state information required during the running of the micro-applications needs to be maintained, so when the state of the micro-application engine on a certain device changes (may be output by the service result in state changes), the micro-application engine needs to synchronize the state changes to other devices through the data synchronization module.

Schematically, as shown in Figure 13, when different devices under the same user account are running the same micro-app, device A deploys service 1 and service 2, device B deploys service 1 and service 3, and device C deploys service 4 and serve 5. After service 1 is invoked in device B, the service output event output by service 1 changes the engine state of the micro-application engine 1301, and the micro-application engine 1301 on the device B side synchronizes the engine state to device A and device A through the data synchronization module 1302 C, so that device A and device C update the engine state of their own micro-application engine 1301 . When service 5 in device C is invoked, the service output event output by service 5 changes the engine state of the micro-application engine 1301, and the micro-application engine 1301 on the side of device C synchronizes the engine state to device A and device A through the data synchronization module 1302 B, so that device A and device B update the engine state of their own micro-application engine 1301 .

Through the above synchronization mechanism, each device under the user account is equal, and the disconnection of a single device will not affect the operation of the micro application. For example, when two-finger tapping captures the screen of other devices and sends it to the current device, the user can tap any device to complete this operation, and if any device is offline, it will not affect the normal screenshot of other devices.

In addition to being launched by clicking on icons like traditional applications, micro-apps can also be launched by other interactive methods. When the user performs a specific interactive action, and multiple micro-applications in the computer device can be started by the specific interactive action, the computer device needs to determine the target micro-application that actually needs to be started based on the multiple micro-applications, and then obtain the target micro-application The target microapp script for .

In a possible implementation manner, as shown in FIG. 14 , the process for the computer device to obtain the target micro-application script may include the following steps.

Step 1401, if an initialization trigger event is received, at least one candidate micro-application corresponding to the initialization trigger event is determined, and the initialization trigger event is used to trigger a trigger of at least one candidate micro-application.

In a possible implementation manner, when an initialization trigger event is received, the computer device determines, from at least one subscribed micro-application, a candidate micro-application containing a trigger corresponding to the initialization trigger event, that is, a candidate micro-application that can be triggered by the initialization trigger event The micro-application that is triggered to run is determined as a candidate micro-application. Wherein, the initialization triggering event may be an event triggered by voice output, an event triggered by a gesture operation (such as shaking, touching) or an event triggered by situational awareness (such as detecting returning home, arriving at an office location, etc.), This embodiment does not limit it.

Step 1402, determining a target micro-application from at least one candidate micro-application.

Optionally, the target micro-application may be specified by the user, or automatically determined by the computer device based on an application selection policy.

In a possible implementation manner, the computer device displays a micro-application selection list based on at least one candidate micro-application; when a selection operation on the micro-application selection list is received, the selected candidate micro-application is determined as a target micro-application.

For example, when the user triggers micro-application A and micro-application B to run by shaking the terminal, when the user shakes the terminal, the terminal displays the application icons of micro-application A and micro-application B through a pop-up window for the user to choose and use.

In another possible implementation manner, the computer device determines a target micro-application from at least one candidate micro-application based on an application selection policy.

Optionally, the computer device may determine the target micro-application based on at least one item of user information, device information, geographic location information, and time information. For example, when the user shakes the terminal, if the terminal is at home, micro-application A is determined as the target micro-application based on the application selection strategy; if the terminal is located at the office, micro-application B is determined as the target micro-application based on the application selection policy .

For another example, when the user shakes the terminal, if it is currently in the morning time period, micro-application C is determined as the target micro-application based on the application selection strategy; if it is currently in the afternoon time period, then micro-application D is determined as the target micro-application based on the application selection strategy micro app. The embodiment of the present application does not limit the specific application selection strategy.

Schematically, as shown in Figure 15, the event bus module 1502 of the micro application engine 1501 is loaded with triggers corresponding to multiple micro applications. When an initialization trigger event is received, and the initialization trigger event causes the event bus module 1502 to When the trigger of is triggered, the event bus module 1502 determines the candidate micro-applications from the micro-applications A, B, and C based on the triggered trigger, and instructs the application scheduling module 1503 to perform application scheduling. The application scheduling module 1503 can display a micro-application selection list for the user to select, and can also determine micro-application C as the target micro-application based on the application selection policy.

Step 1403, acquiring the target micro-application script of the target micro-application.

Further, the computer device acquires the target micro-application script locally based on the application identification of the target micro-application.

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. 16 , which shows a structural block diagram of a micro-application running device provided by an embodiment of the present application. The device can include:

The script acquisition module 1601 is used to acquire the target micro-application script of the target micro-application, the target micro-application is a collection of services, the target micro-application script is composed of triggers, and the triggers are used to Service invocation by executing control logic;

A trigger module 1602, configured to trigger a target trigger corresponding to the target trigger event in the target micro-application script when the target trigger event is received;

The service calling module 1603 is configured to execute the target control logic corresponding to the target trigger, and call the target service to realize the micro-application function of the target micro-application.

Optionally, the device also includes:

A candidate service determining module, configured to determine a candidate service list based on the service identifier of the service invoked by the target control logic, the candidate service list including at least one candidate service matching the service identifier;

A target service determining module, configured to determine the target service from the candidate services in the candidate service list.

Optionally, the candidate service determination module is configured to:

Determine a candidate static service that matches the service identifier in the current device, where the static service is a service provided by a host application in the device;

Determining a candidate dynamic service matching the service identifier from the cloud service library, wherein the dynamic service is a service that supports dynamic deployment to the device;

The list of candidate services is generated based on the candidate static services and the candidate dynamic services.

Optionally, the target service determination module is configured to:

displaying the candidate service list; in response to a selection operation on candidate services in the candidate service list, determining the selected candidate service as the target service; or,

The target service is determined from the candidate services in the candidate service list based on a service selection policy.

Optionally, the service calling module 1603 is configured to:

The target service is invoked through the target service gateway, where the target service gateway is the service gateway of the current device, and/or, the service gateway of an external device other than the current device, and the target micro-application script is set in the external device.

Optionally, the service calling module 1603 includes:

The first invocation unit is configured to obtain a service invocation request through the target service gateway when the target service gateway is the service gateway of the current device; determine the target service agent corresponding to the target service through the target service gateway ; Based on the service invocation request, invoking the target service through the target service agent;

The second invoking unit is configured to send a service invocation request to the external device when the target service gateway is a service gateway of an external device, and the external device is configured to determine the target service through the target service gateway A corresponding target service proxy, and based on the service invocation request, invoke the target service through the target service proxy;

Wherein, different service agents correspond to different programming development languages, or different service agents correspond to different deployment forms, or different service agents correspond to different operating environments.

Optionally, the first calling unit or the second calling unit is used for:

The original input parameters in the service call request are converted by the target service proxy to obtain target input parameters, wherein the original input parameters adopt a unified parameter format, and the target input parameters conform to the parameter format of the target service ;

Invoking the target service through the target service proxy based on the target input parameters to obtain original output parameters of the target service;

The original output parameter is converted by the target service agent to obtain a target output parameter, and the target output parameter adopts the unified parameter format.

Optionally, the device also includes:

The first service starting module is used to obtain the service status of the target service through the static service manager when the target service is a static service; and start the service status when the service status is not started. target service.

Optionally, the device also includes:

The second service starting module is used to obtain the service status of the host service corresponding to the target service through the dynamic service manager when the target service is a dynamic service; when the service status is not started, Start the host service; query the deployment status of the target service through the host service; if the target service is not deployed, download the target service from the cloud service library, and load the target service through the host service target service.

Optionally, the service calling module 1603 is further configured to obtain a service return value of the target service when the target service is a synchronous call service; call the next service based on the service return value;

The triggering module 1602 is further configured to obtain a service output event of the target service when the target service is an asynchronous call service; trigger a trigger in the target micro-application script through the service output event.

Optionally, the device also includes:

A first download module, configured to download the target micro-application script of the target micro-application in response to a subscription operation to the target micro-application; or,

The second download module is configured to download the target micro-application script of the target micro-application based on the application identifier in the subscription push message when a subscription push message is received, and the subscription push message is sent by the server at When it is detected that the micro-application subscribed by the user account changes, push it to each device under the user account.

Optionally, the device also includes:

The initialization deployment module is configured to deploy an initialization service based on the initialization trigger in the target micro-application script, and the initialization service is a service invoked by the initialization trigger.

Optionally, the device also includes:

A deletion module, configured to delete the target micro-application script of the target micro-application in response to an unsubscribe operation on the target micro-application;

An instruction sending module, configured to send a subscription cancellation instruction to the server, and the server is configured to push a subscription cancellation message to each device under the user account based on the subscription cancellation instruction, so that each terminal deletes the target micro-application script.

Optionally, the script acquisition module 1601 includes:

A candidate application determining unit, configured to determine at least one candidate micro-application corresponding to the initialization trigger event in the case of receiving an initialization trigger event, and the initialization trigger event is used to trigger an initialization trigger of at least one candidate micro-application ;

a target application determining unit, configured to determine the target micro-application from at least one of the candidate micro-applications;

An acquiring unit, configured to acquire the target micro-application script of the target micro-application.

Optionally, the target application determining unit is configured to:

displaying a micro-application selection list based on at least one of the candidate micro-applications; in response to a selection operation on the micro-application selection list, determining the selected candidate micro-application as the target micro-application; or,

The target micro-application is determined from at least one of the candidate micro-applications based on an application selection strategy.

To sum up, in the embodiment of this application, when running a micro-application composed of several services, 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 trigger The corresponding control logic of the controller is used to call the corresponding service to realize the micro-application function of the micro-application. Since the operation of micro-applications is based on micro-application scripts with low code volume, it requires less storage space than traditional applications; moreover, assemble services into micro-applications, and use micro-application scripts to manage the calling relationship between services , realizing the componentization of micro-applications, improving the reusability of services between micro-applications, and helping to reduce the difficulty of developing micro-applications.

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

Processor 1710 may include one or more processing cores. The processor 1710 uses various interfaces and lines to connect various parts of the entire computer device 1700, and executes by running or executing instructions, programs, code sets or instruction sets stored in the memory 1720, and calling data stored in the memory 1720. Various functions of the computer device 1700 and processing data. Optionally, the processor 1710 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 1710 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 foregoing modem may also not be integrated into the processor 1710, but implemented by a single chip.

The memory 1720 may include random access memory (Random Access Memory, RAM), and may also include read-only memory (Read-Only Memory, ROM). Optionally, the memory 1720 includes a non-transitory computer-readable storage medium (non-transitory computer-readable storage medium). The memory 1720 may be used to store instructions, programs, codes, sets of codes or sets of instructions. The memory 1720 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 1700 (such as audio data, phonebook) and the like.

In addition, those skilled in the art can understand that the structure of the computer device 1700 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 1700 also includes a display screen, a camera assembly, 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 wireless fidelity (Wireless Fidelity, WiFi ) module, power supply, bluetooth module and other 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, and the at least one program is loaded and executed by a processor to realize the micro-application described in each embodiment above. run method.

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

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 (20)

A method for running a micro-application, the method comprising: Acquire the target micro-application script of the target micro-application, the target micro-application is a collection of services, the target micro-application script is composed of triggers, and the triggers are used to perform service calls by executing control logic under trigger events ; In the case of receiving a target trigger event, trigger a target trigger corresponding to the target trigger event in the target micro-application script; Execute the target control logic corresponding to the target trigger, and call the target service, so as to realize the micro-application function of the target micro-application. The method according to claim 1, wherein, before invoking the target service, the method comprises: determining a candidate service list based on the service identifier of the service invoked by the target control logic, the candidate service list including at least one candidate service matching the service identifier; The target service is determined from the candidate services in the candidate service list. The method according to claim 2, wherein said determining the candidate service list based on the service identifier of the service invoked by the target control logic comprises: Determine a candidate static service that matches the service identifier in the current device, where the static service is a service provided by a host application in the device; Determining a candidate dynamic service matching the service identifier from the cloud service library, wherein the dynamic service is a service that supports dynamic deployment to the device; The list of candidate services is generated based on the candidate static services and the candidate dynamic services. The method according to claim 2, wherein said determining the target service from the candidate services in the candidate service list comprises: displaying the list of candidate services; In response to a selection operation on a candidate service in the candidate service list, determine the selected candidate service as the target service; or, The target service is determined from the candidate services in the candidate service list based on a service selection policy. The method according to any one of claims 1 to 4, wherein the invoking the target service includes: The target service is invoked through the target service gateway, where the target service gateway is the service gateway of the current device, and/or, the service gateway of an external device other than the current device, and the target micro-application script is set in the external device. The method according to claim 5, wherein invoking the target service through the target service gateway comprises: If the target service gateway is the service gateway of the current device, obtain a service invocation request through the target service gateway; determine the target service agent corresponding to the target service through the target service gateway; based on the service invocation request , invoking the target service through the target service proxy; When the target service gateway is a service gateway of an external device, sending a service invocation request to the external device, the external device is used to determine a target service proxy corresponding to the target service through the target service gateway, and Invoking the target service through the target service proxy based on the service invocation request; Wherein, different service agents correspond to different programming development languages, or different service agents correspond to different deployment forms, or different service agents correspond to different operating environments. The method according to claim 6, wherein the invoking the target service through the target service proxy based on the service invocation request comprises: The original input parameters in the service call request are converted by the target service proxy to obtain target input parameters, wherein the original input parameters adopt a unified parameter format, and the target input parameters conform to the parameter format of the target service ; Invoking the target service through the target service proxy based on the target input parameters to obtain original output parameters of the target service; The original output parameter is converted by the target service agent to obtain a target output parameter, and the target output parameter adopts the unified parameter format. The method according to claim 6, wherein, before invoking the target service through the target service proxy based on the service invocation request, the method further comprises: In the case that the target service is a static service, acquiring the service status of the target service through a static service manager; If the service state is not started, start the target service. The method according to claim 6, wherein, before invoking the target service through the target service proxy based on the service invocation request, the method further comprises: In the case where the target service is a dynamic service, obtain the service status of the host service corresponding to the target service through a dynamic service manager; If the service state is not started, start the hosting service; Querying the deployment status of the target service through the host service; If the target service is not deployed, the target service is downloaded from the cloud service library, and the target service is loaded through the host service. The method according to any one of claims 1 to 4, wherein, after invoking the target service, the method further comprises: If the target service is a synchronous invocation service, acquiring a service return value of the target service; invoking the next service based on the service return value; In the case that the target service is an asynchronous call service, a service output event of the target service is obtained; a trigger in the target micro-application script is triggered by the service output event. The method according to any one of claims 1 to 4, wherein, before acquiring the target micro-application script of the target micro-application, the method comprises: downloading the target microapplication script of the target microapplication in response to a subscribe operation to the target microapplication; or, When a subscription push message is received, the target micro-app script of the target micro-app is downloaded based on the application identifier in the subscription push message, and the subscription push message is sent by the server after detecting that the user account subscribes to the micro-app script. When the application changes, it is pushed to each device under the user account. The method according to claim 11, wherein, after downloading the target micro-application script of the target micro-application, the method further comprises: Deploy an initialization service based on the initialization trigger in the target micro-application script, where the initialization service is a service invoked by the initialization trigger. The method according to claim 11, wherein the method further comprises: deleting the target microapp script of the target microapp in response to an unsubscribe operation on the target microapp; sending a subscription cancellation instruction to the server, and the server is configured to push a subscription cancellation message to each device under the user account based on the subscription cancellation instruction, so that each terminal deletes the target micro-application script. The method according to any one of claims 1 to 4, wherein said obtaining the target micro-application script of the target micro-application comprises: When an initialization trigger event is received, at least one candidate micro-application corresponding to the initialization trigger event is determined, and the initialization trigger event is used to trigger an initialization trigger of at least one candidate micro-application; determining said target microapplication from at least one of said candidate microapplications; Obtain the target micro-application script of the target micro-application. The method according to claim 14, wherein said determining the target micro-application from at least one of the candidate micro-applications comprises: displaying a micro-application selection list based on at least one of the candidate micro-applications; in response to a selection operation on the micro-application selection list, determining the selected candidate micro-application as the target micro-application; or, The target micro-application is determined from at least one of the candidate micro-applications based on an application selection strategy. A micro-application running device, the device comprising: The script obtaining module is used to obtain the target micro-application script of the target micro-application, the target micro-application is a collection of services, the target micro-application script is composed of a trigger, and the trigger is used to pass Execute control logic to make service calls; A trigger module, configured to trigger a target trigger corresponding to the target trigger event in the target micro-application script when the target trigger event is received; The service calling module is used to execute the target control logic corresponding to the target trigger, and call the target service to realize the micro-application function of the target micro-application. The apparatus of claim 16, wherein the apparatus further comprises: A candidate service determining module, configured to determine a candidate service list based on the service identifier of the service invoked by the target control logic, the candidate service list including at least one candidate service matching the service identifier; A target service determining module, configured to determine the target service from the candidate services in the candidate service list. A computer device, the computer device comprising a processor and a memory; the memory stores at least one section of program, and the at least one section of program is used to be executed by the processor to realize any one of claims 1 to 15 How the microapp runs. A computer-readable storage medium, at least one section of program is stored in the computer-readable storage medium, and the at least one section of program is loaded and executed by a processor to realize the operation of the micro-application according to any one of claims 1 to 15 method. A computer program product comprising computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, the 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 15.

Images