WO2020168567A1

WO2020168567A1 - Data processing method and device, and mobile terminal

Info

Publication number: WO2020168567A1
Application number: PCT/CN2019/075943
Authority: WO
Inventors: 朱洪波
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2019-02-22
Filing date: 2019-02-22
Publication date: 2020-08-27
Also published as: CN113168332A; CN113168332B

Abstract

Disclosed in embodiments of the present application are a data processing method and apparatus, and a mobile terminal. The method comprises: receiving, by means of an expansion interface configured for a fast application engine, a data processing instruction sent by the fast application engine, wherein the data processing instruction is sent by the fast application engine in response to a trigger operation in an operation interface, the operation interface is generated by the fast application engine, and the data processing instruction carries identification information of a target SDK; obtaining a corresponding target SDK plug-in on the basis of the identification information; and calling the target SDK plug-in to execute the data processing instruction. According to the method, the fast application triggers a client to control the SDK plug-in on the basis of a cross-application mode, so that the fast application calls the SDK plug-in, and a function of the fast application is greatly expanded, so as to call other components in the mobile terminal by means of the fast application.

Description

Data processing method, device and mobile terminal

Technical field

This application relates to the field of Internet of Things, and more specifically, to a data processing method, device, and mobile terminal.

Background technique

Quick application is a new type of application that is deeply integrated with the operating system and provides a scene-based experience. Like small programs, it has the features of free installation and direct opening. With the popularization of fast apps, fast apps can be used to control smart home devices. However, fast apps have not yet been able to flexibly control devices from multiple manufacturers, and the user experience needs to be improved.

Summary of the invention

In view of the above problems, this application proposes a data processing method, device and mobile terminal to improve the above problems.

In the first aspect, this application provides a data processing method applied to a client. The method includes: receiving a data processing instruction sent by the fast application engine through an extension interface configured to the fast application engine, and the data processing The instruction is sent by the quick application engine in response to a trigger operation in the operation interface, the operation interface is generated by the quick application engine, the data processing instruction carries the identification information of the target SDK; based on the identification information, the corresponding The target SDK plug-in; call the target SDK plug-in to execute the data processing instruction.

In a second aspect, this application provides a data processing method applied to a fast application engine, the method comprising: generating a data processing instruction in response to a touch operation in an operation interface, the operation interface being generated by the fast application engine Call the extension interface configured by the client for the fast application engine, send the data processing instruction to the client through the extension interface; receive the execution of the data returned by the client based on the extension interface The result information of the processing instruction.

In a third aspect, the present application provides a data processing device that runs on a mobile terminal. The device includes: a data receiving unit configured to receive data processing sent by the quick application engine through an extension interface configured to the quick application engine Instruction, the data processing instruction is sent by the fast application engine in response to a trigger operation in an operation interface, the operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK; data detection The unit is used to obtain the corresponding target SDK plug-in based on the identification information; the SDK calling unit is used to call the target SDK plug-in to execute the data processing instruction.

In a fourth aspect, the present application provides a data processing device that runs on a mobile terminal. The device includes an operation detection unit for generating data processing instructions in response to a touch operation in an operation interface. Application engine generation; data sending unit, used to call the extended interface configured by the client to the fast application engine, and send the data processing instruction to the client through the extended interface; data receiving unit, used to receive The client is based on the result information of executing the data processing instruction returned by the extended interface.

In a fifth aspect, the present application provides a mobile terminal, including one or more processors and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be The one or more processors execute, and the one or more programs are configured to execute the above methods.

In a sixth aspect, the present application provides a computer-readable storage medium having program code stored in the computer-readable storage medium, wherein the above method is executed when the program code is running.

The data processing method, device, and mobile terminal provided by this application, by configuring the extension interface for the fast application engine in the client, enable the client to be configured to the fast application during the process of controlling the SDK plug-in through the fast application The extension interface of the engine, which receives the data processing instruction sent by the quick application engine in response to the touch operation in the quick application, obtains the corresponding target SDK plug-in based on the data processing instruction, and calls the target SDK plug-in to execute the data Processing instructions. As a result, the quick app triggers the client to control the SDK plug-in based on a cross-application method, and then realizes that the quick app can call the SDK plug-in, and greatly expands the function of the quick app to facilitate the realization of mobile Call other components in the terminal.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

FIG. 1 shows a schematic diagram of the architecture of the Internet of Things proposed in an embodiment of the present application;

FIG. 2 shows a schematic diagram of another architecture of the Internet of Things proposed in an embodiment of the present application;

FIG. 3 shows a schematic diagram of yet another architecture of the Internet of Things proposed by an embodiment of the present application;

FIG. 4 shows a schematic diagram of a fast application engine architecture proposed by an embodiment of the present application;

FIG. 5 shows a schematic diagram of a communication mode between a client and a server proposed by an embodiment of the present application;

FIG. 6 shows a schematic diagram of the operating environment of the data processing method proposed in an embodiment of the present application;

FIG. 7 shows a flowchart of a data processing method proposed in an embodiment of the present application;

FIG. 8 shows a schematic diagram of an entry of an operation interface in a data processing method proposed in an embodiment of the present application;

FIG. 9 shows a schematic diagram of an entry of another operation interface in a data processing method proposed by an embodiment of the present application;

FIG. 10 shows a schematic diagram of an entry of yet another operation interface in a data processing method proposed in an embodiment of the present application;

FIG. 11 shows a flowchart of a data processing method proposed by another embodiment of the present application;

FIG. 12 shows a flowchart of a data processing method proposed in another embodiment of the present application;

FIG. 13 shows a flowchart of a data processing method proposed by another embodiment of the present application;

FIG. 14 shows a flowchart of a data processing method proposed by another embodiment of the present application;

FIG. 15 shows a structural block diagram of a data processing device proposed in an embodiment of the present application;

FIG. 16 shows a structural block diagram of a data processing device proposed by another embodiment of the present application;

FIG. 17 shows a structural block diagram of a data processing device proposed by another embodiment of the present application;

FIG. 18 shows a structural block diagram of a data processing device proposed by another embodiment of the present application;

FIG. 19 shows a structural block diagram of a data processing device proposed by another embodiment of the present application;

FIG. 20 shows a structural block diagram of a mobile terminal of the present application for executing the data processing method according to an embodiment of the present application;

Fig. 21 is a storage unit for storing or carrying program codes for implementing the device control method according to the embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of this application.

The Internet of Things is a network concept that extends and expands its user end to any item and item for information exchange and communication based on the "Internet concept". With the development of IoT technology, some scenarios can be configured in the IoT system. For the configuration scenario, multiple controlled devices may be involved, and multiple controlled devices have a certain linkage relationship and can work together.

Among them, the controlled devices can be projectors, projection screens, smart lights, smart sockets, human sensors, door and window sensors, wireless switches, air conditioners, smoke alarms, smart curtain motors, and mobile terminals such as air purifiers and smart speakers. In one manner, as shown in FIG. 1, the mobile terminal 100 that plays a control role can implement data interaction with the controlled device 99 by directly establishing a wireless connection with the router 90. Furthermore, the mobile terminal 100 can also realize data interaction with the controlled device 99 through the data link between the cloud 91 and the router 90 after establishing a connection with the cloud 91.

As another way, as shown in FIG. 2, the mobile terminal 100 directly establishes data interaction with the first cloud 91a, and then implements the mobile terminal 100 based on the data interaction between the first cloud 91a and the second cloud 91b. Data interaction with the second cloud 91b, and then the second cloud 91b can perform data interaction with the controlled device 99, the mobile terminal 100 further realizes the data interaction with the controlled device 99.

As another way, as shown in FIG. 3, the controlled device 99 may establish a wireless connection with the router 90 through the gateway 98. Among them, the data interaction may include the mobile terminal sending a control instruction to the controlled device, and may also include the controlled device returning status information to the mobile terminal or returning the instruction execution result. Among them, the data interaction between the mobile terminal and the controlled device can be triggered by a client installed in the mobile terminal.

With the popularization of fast apps, mobile terminal developers expect to implement the same functions as the aforementioned clients through fast apps, so as to improve the development efficiency of smart home functions and at the same time save the storage space of mobile terminals.

Among them, the fast application is a new application form based on the hardware platform of the terminal device. It does not need to be installed, it is click-to-use, and it has the original application experience (performance, system integration, interaction, etc.). As shown in Figure 4, the structure diagram of the fast application engine, the front-end design of fast application draws on and integrates the design ideas of mainstream front-end frameworks (Vue, React, etc.): build applications in a componentized way, with data binding as the core The MVVM design mode uses V-DOM to improve performance, while choosing a concise and clear Vue-like template.

In order to facilitate data interaction, each manufacturer will develop its own SDK plug-in for the client in the mobile terminal to call. After the client loads the manufacturer's SDK plug-in, it can call the loaded SDK plug-in, and then interact with the manufacturer's server through the SDK plug-in. For example, as shown in FIG. 5, the client 110 shown in FIG. 5 is loaded with the SDK plug-in 111 of manufacturer A and the SDK plug-in 112 of manufacturer B. The client 110 can communicate with manufacturer A by calling the SDK plug-in of manufacturer A. The server 210 of manufacturer B performs data interaction, and the client 110 can interact with the server 220 of manufacturer B by calling the SDK plug-in of manufacturer B. However, the inventor found that Quick App cannot directly call the manufacturer’s SDK plug-in, and there is no direct communication between Quick App and the client that can load the SDK plug-in. As a result, Quick App cannot call the SDK plug-in through the client, thus making Quick App. Can not achieve the same function as the client.

Therefore, the inventor proposes that in this application, Quick App can trigger the client to control the SDK plug-in based on a cross-application approach, thereby realizing that Quick App can call the SDK plug-in and greatly expanding the functions of Quick App. , So that the data processing method, device and mobile terminal for calling other components in the mobile terminal can be realized through the quick application.

The following first introduces the application environment of the embodiments of the present application in conjunction with the drawings.

As shown in FIG. 6, in the mobile terminal 100 shown in the figure, a fast application and a client 110 are running. The fast application runs on the fast application engine, and an extended interface 97 provided by the client is set in the fast application engine. The client 110 is provided with an extension interface 96 that communicates with the extension interface 97. The client 110 can call SDK plug-ins of various manufacturers through an extended interface. For example, the SDK plug-in 111 of manufacturer A, the SDK plug-in 112 of manufacturer B, and the SDK plug-in 113 of manufacturer C in the figure can be called. In this case, the data processing instructions triggered in the fast application can be transferred to the extended interface 96 in the client through the extension interface 97 set in the fast application engine, and then the data processing instructions are transmitted to the SDK plug-ins of various manufacturers .

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 7, a data processing method provided by an embodiment of the present application is applied to a client, and the method includes:

Step S110: Receive a data processing instruction sent by the quick application engine through the extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, the operation interface Generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

Among them, the operation interface that can be used for operation is rendered and generated by the quick application engine, and in the quick application-based operation mode, the mobile terminal may have multiple ways to trigger the display of the operation interface.

As a way, a quick application client can be configured in the mobile terminal, so that the operation interface corresponding to other applications can be entered through the interface of the quick application client. It can be understood that the fast application client here is different from the client run by the data processing method provided in this embodiment.

For example, the operation interface 95 shown in FIG. 8, in which the operation interface entry controls of application A, application B, and application C are displayed, it can be understood that application A, application The operation interface of B and application C refers to the operation interface generated by the fast application engine. In this case, when the fast application client detects that the user has touched the entry control of application A, the fast application client can load and display the operation interface of application A, and the fast application client detects that the user has touched After controlling the entry control of application B, the fast application client can load and display the operation interface of application B. After the fast application client detects that the user has touched the entry control of application C, the fast application client can load The operation interface of application C is displayed.

As another way, a quick application card 93 can be displayed in the negative one-screen interface 94 as shown in FIG. 9, and the entry controls of the operation interface generated by the quick application engine corresponding to each application program are displayed in the card. . For example, the operation interface entry controls of application A, application B, and application C can still be displayed in card 93. Correspondingly, after the mobile terminal detects that the entry control of application A in the card is touched, it triggers the quick application client to load and display the operation interface of application A, and the mobile terminal detects that the entry control of application B in the card After the entry control is touched, the quick application client will be triggered to load and display the operation interface of application B. Then when the mobile terminal detects that the entry control of application C in the card is touched, it will trigger the quick application client to Load and display the operation interface of application C.

As another way, the entry control can be set in other clients, for example, the client on which the data processing method provided in the embodiment of the present application runs. For example, as shown in FIG. 10, in the case where the client terminal on which the data processing method provided in the embodiment of the present application runs is a smart home client, the interface 92 of the smart home client may display manufacturer A, manufacturer B, and manufacturer C corresponds to the entry control of the operation interface. It is understandable that, just like the content shown in Figure 6 above, the operation interface is running on the fast application engine. Based on this situation, the client detects that it is acting on the entry control named "Vendor A". After the touch operation, you can send instructions to display the operation interface corresponding to manufacturer A to the fast application engine through the extended interface configured to the fast application engine (more details will be introduced later), thereby triggering the fast application engine to render the display corresponding to manufacturer A The operation interface.

Among them, it can be understood that if the fast application engine renders and displays the data (for example, interface UI data or device status data, etc.) required in the process of rendering and displaying the operation interface of manufacturer A, the fast application engine can be transferred to the intelligent The home client requests, and the smart home client calls the SDK plug-in corresponding to vendor A after receiving the request, and then returns it to the fast application engine through the extended interface. Among them, if the SDK plug-in determines that the required data can be obtained locally, it can be directly searched locally (for example, UI data may have been encapsulated in the SDK plug-in), and if it is determined that it needs to be obtained from the server (for example, device status data, etc.) ), then you can send a data acquisition request to the corresponding vendor server as shown in Figure 5.

It should be noted that in one way, the fast application engine and the client are two applications that run relatively independently. In this case, the extended interface between the fast application engine and the client is based on inter-process communication The expansion interface. Optionally, the extended interface based on inter-process communication includes an AIDL channel interface. Optionally, the extended interface based on inter-process communication includes a localSocket interface.

In the implementation of the AIDL channel interface, the fast application engine can call the client through the interface function in the jar package provided by the client, and write the data processing instructions to be executed into the interface function in the form of parameters. In turn, the client can obtain data processing instructions in the form of parameters. Furthermore, as a way to improve security, the fast application engine can judge the package name and application signature in the onTransact callback so that applications without authentication cannot access the AIDL channel interface.

After the operation interface is displayed, the user can realize the network distribution and control of the equipment by operating the operation interface. Among them, as a way, different fast applications correspond to different operation objects.

For example, if you enter the operation interface through the entry control of manufacturer A shown in Figure 10, then the executed operation is made on the equipment of manufacturer A, and if it is through manufacturer B shown in Figure 10 The operation interface entered by the entry control, then the operation performed is made on the equipment of manufacturer B. It is understandable that for the data processing instructions of devices of different manufacturers, the client will subsequently call the SDK plug-ins of different manufacturers to execute, so in order to facilitate the subsequent client to distinguish the manufacturer’s equipment to be operated by the data processing instructions, then generate in the fast application engine In the process of the data processing instruction, the identification information of the fast application that triggers the generation of the data processing instruction is added to the data processing instruction. The identification information may be a unique identifier allocated by the mobile terminal, or may be a package name of the quick application.

Step S120: Obtain a corresponding target SDK plug-in based on the identification information.

It is understandable that, in the embodiments of the present application, the fast application can implement calling applications of multiple types or controlling devices of multiple manufacturers. In the process of controlling the devices of multiple vendors, it is implemented by calling the SDK plug-ins of multiple vendors loaded in the client. Then, after the client receives the data processing instruction by providing it to the fast application engine, it will first extract the identification information of the SDK plug-in from the data processing instruction, and then find the matching SDK plug-in from the multiple SDK plug-ins recorded before as the target SDK plugin.

Among them, as a way, the client can record the downloaded SDK plug-in after loading the SDK plug-in of a certain manufacturer. You can also record after loading a downloaded SDK plug-in. Then take the package name as an example. For the recorded SDK plug-ins belonging to a certain vendor, QuickApp will store the package name of the vendor’s QuickApp, and then obtain the data processing instruction, and then according to the extracted from the data processing instruction Package name to identify the corresponding target SDK plug-in.

Step S130: Call the target SDK plug-in to execute the data processing instruction.

It is understandable that some software functions are encapsulated inside the SDK plug-in, and the corresponding functions can be realized through the operation of the software functions. In order to facilitate the external program to call the SDK plug-in, the SDK plug-in will expose its interface so that the SDK plug-in can be called through the interface. In the embodiments of the present application, in order to facilitate unified calls, the interfaces of SDK plug-ins of different vendors are all packaged according to unified setting rules. That is, the interface rules of SDK plug-ins of different manufacturers are the same. Then, in the process of calling the target SDK plug-in, the client invokes the target SDK plug-in based on the interface rules defined by the target SDK plug-in, so as to call the target SDK plug-in to execute the data processing instruction.

It should be noted that, in addition to the SDK plugins belonging to different manufacturers, the different SDK plugins called in the client can also be SDK plugins belonging to different devices, or SDK plugins belonging to different applications. For the difference between the different SDK plug-ins called in the client, besides the manufacturer, the device, and the application, there may also be other different ways, which are not specifically limited in the embodiment of the present application.

It should be noted that the fast application engine and the client that executes the data processing method in the embodiment of this application can be two independently running applications, or the fast application engine is embedded in the data processing method in the embodiment of this application. In the client, that is, the client includes the fast application engine.

This application provides a data processing method that configures an extended interface for the fast application engine in the client, so that in the process of controlling the SDK plug-in through the fast application, the client can use the extended interface configured to the fast application engine. Receive a data processing instruction sent by the quick application engine in response to a touch operation in the quick application, obtain a corresponding target SDK plug-in based on the data processing instruction, and call the target SDK plug-in to execute the data processing instruction. As a result, the quick app triggers the client to control the SDK plug-in based on a cross-application method, and then realizes that the quick app can call the SDK plug-in, and greatly expands the function of the quick app to facilitate the realization of mobile Call other components in the terminal.

Referring to FIG. 11, a data processing method provided by an embodiment of the present application is applied to a client, and the method includes:

Step S210: Receive a data processing instruction sent by the quick application engine through the extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, the operation interface Generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

Step S220: Obtain the corresponding target SDK plug-in based on the identification information.

Step S230: Read the version identifier of the fast application carried from the data processing instruction.

Step S240: Obtain the version identifier of the target SDK plug-in.

Step S250: Determine whether the version identifier of the quick application matches the version identifier of the target SDK plug-in.

With the update of fast apps, fast apps of different manufacturers or fast apps of different devices can be upgraded. And the fast application after the upgrade can have more functions. It is understandable that the fast application in the embodiment of this application executes data processing instructions by calling the SDK plug-in in the client. If the function displayed in the operation interface is actually not completed by the corresponding target SDK plug-in, then It may cause data errors and affect user experience. For example, if the function information of obtaining the device status is displayed on the operation interface, but if the SDK plug-in corresponding to the quick application does not have a handle to send the device status to the server, the SDK plug-in cannot execute the touch device state The data processing instructions generated after the acquisition. The inconsistency between the version of the SDK plug-in corresponding to the same manufacturer or the same device and the quick app version may be caused by the mobile terminal not downloading the latest version in time or an error occurred during the update process.

Step S260: If it is determined that the version identifier of the quick application matches the version identifier of the target SDK plug-in, call the target SDK plug-in to execute the data processing instruction.

Step S261: If it is determined that the version identifier of the quick application does not match the version identifier of the target SDK plug-in, obtain the functions supported by the target SDK plug-in.

It is understandable that, as a way, each SDK plug-in is downloaded from the corresponding server. For example, as shown in Figure 5, the SDK plug-in of manufacturer A is downloaded from the server of manufacturer A, and the SDK plug-in of manufacturer B is downloaded from the server of manufacturer B. When the mobile terminal downloads the SDK plug-in, it can also download a corresponding function description file, and the function description file can correspond to the functions supported by the currently downloaded version of the SDK.

Step S270: Determine whether the target SDK plug-in can complete the data processing instruction based on the acquired functions supported by the target SDK plug-in.

It is understandable that based on the aforementioned acquisition of the functions supported by the target SDK plug-in, if it is determined that the functions supported by the target SDK plug-in include the functions to be executed by the data processing instructions sent by the fast application engine received by the client, then It is determined that the target SDK plug-in can complete the data processing instruction. Otherwise, it is determined that the data processing instruction cannot be completed.

If it is determined that the data processing instruction can be completed, step S260 is executed.

Step S280: If it is determined that the data processing instruction cannot be completed, a prompt message of an operation error is returned to the quick application based on the extended interface.

This application provides a data processing method that configures an extended interface for the fast application engine in the client, so that in the process of controlling the SDK plug-in through the fast application, the client can use the extended interface configured to the fast application engine. Receive the data processing instruction sent by the quick app engine in response to the touch operation in the quick app, obtain the corresponding target SDK plug-in based on the data processing instruction, and when it is determined that the obtained target SDK plug-in is the same version as the quick app, Then call the target SDK plug-in to execute the data processing instruction. As a result, the quick app triggers the client to control the SDK plug-in based on a cross-application method, and then realizes that the quick app can call the SDK plug-in, and greatly expands the function of the quick app to facilitate the realization of mobile Call other components in the terminal. At the same time, it also avoids data errors caused by inconsistencies between the version of the target SDK plug-in and the version of the quick app, or the execution failure of data processing instructions.

Referring to FIG. 12, a data processing method provided by an embodiment of the present application is applied to a client, and the method includes:

Step S310: Receive the data processing instruction sent by the quick application engine through the extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, the operation interface Generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

Step S320: Obtain the corresponding target SDK plug-in based on the identification information.

Step S330: Read the version identifier of the fast application carried from the data processing instruction.

Step S340: Obtain the version identifier of the target SDK plug-in.

Step S350: Determine whether the version identifier of the quick application matches the version identifier of the target SDK plug-in.

Step S360: If it is determined that the version identifier of the quick application does not match the version identifier of the target SDK plug-in, and the version of the quick application is higher than the version of the target SDK plug-in, update the version of the target SDK plug-in To match the version of the quick application.

Step S361: Use the updated target SDK plug-in as a new target SDK plug-in.

Step S362: Invoke the new target SDK plug-in to execute the data processing instruction.

Step S370: If it is determined that the version identifier of the quick application does not match the version identifier of the target SDK plug-in, and the version of the quick application is lower than the version of the target SDK plug-in, call the target SDK plug-in to execute the Data processing instructions.

Step S380: If it is determined that the version identifier of the fast application matches the version identifier of the target SDK plug-in, call the target SDK plug-in to execute the data processing instruction.

The data processing method provided in this application enables Quick App to trigger the client to control the SDK plug-in based on a cross-application approach, thereby realizing that Quick App can call the SDK plug-in and greatly expanding the functions of Quick App. , In order to realize the call to other components in the mobile terminal through the fast application. At the same time, after detecting that the version of Quick App is higher than the version of the target SDK plug-in, the version of the target SDK plug-in will be updated in time, avoiding data errors or data errors caused by inconsistencies between the version of the target SDK plug-in and the Quick App version The processing instruction failed to execute.

Please refer to FIG. 13, a data processing method provided by an embodiment of the present application is applied to a client, and the method includes:

Step S410: Receive a data processing instruction sent by the quick application engine through an extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in an operation interface, the operation interface Generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

Step S420: Obtain the corresponding target SDK plug-in based on the identification information.

Step S430: Determine whether the target SDK plug-in is loaded.

Step S440: If it is determined that it is not loaded, dynamically load the target SDK plug-in.

Step S441: After the dynamic loading of the target SDK plug-in is completed, call the target SDK plug-in to execute the data processing instruction.

Step S450: If it is determined that it has been loaded, call the target SDK plug-in to execute the data processing instruction.

The data processing method provided in this application enables Quick App to trigger the client to control the SDK plug-in based on a cross-application approach, thereby realizing that Quick App can call the SDK plug-in and greatly expanding the functions of Quick App. , In order to realize the call to other components in the mobile terminal through the fast application. At the same time, after the target SDK plug-in is obtained, even when it is detected that the target SDK plug-in is not loaded, the target SDK plug-in can be dynamically loaded. After the target SDK plug-in is dynamically loaded, the target can be called The SDK plug-in executes the data processing instructions, which not only eliminates the need to embed the target SDK plug-in in the client at the very beginning, so as to reduce the control occupation of the client, and facilitate the client to be lighter, and it also improves the loading of the SDK plug-in flexibility.

Referring to FIG. 14, a data processing method provided by an embodiment of the present application is applied to a client, and the method includes:

Step S510: Generate a data processing instruction in response to a touch operation in an operation interface, the operation interface being generated by the fast application engine.

Step S520: Call the extended interface configured by the client for the fast application engine, and send the data processing instruction to the client through the extended interface.

Step S530: Receive result information of executing the data processing instruction returned by the client based on the extended interface.

The data processing method provided in this application enables Quick App to trigger the client to control the SDK plug-in based on a cross-application approach, thereby realizing that Quick App can call the SDK plug-in and greatly expanding the functions of Quick App. , In order to realize the call to other components in the mobile terminal through the fast application.

Referring to FIG. 15, a data processing device 600 provided by an embodiment of the present application runs on a mobile terminal, and the device 600 includes:

The data receiving unit 610 is configured to receive a data processing instruction sent by the quick application engine through an extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, The operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

As a way, the data receiving unit 610 is specifically configured to receive the data processing instruction sent by the fast application engine through an extended interface based on inter-process communication configured to the fast application engine.

Optionally, the extended interface based on inter-process communication includes an AIDL channel interface.

Optionally, the extended interface based on inter-process communication includes a localSocket interface.

The data detection unit 620 is configured to obtain the corresponding target SDK plug-in based on the identification information.

The data detection unit 620 is specifically configured to obtain the target SDK plug-in from multiple SDK plug-ins based on the data processing instruction, and the interface rules defined by each of the multiple SDK plug-ins are the same.

The SDK calling unit 630 is configured to call the target SDK plug-in to execute the data processing instruction.

The SDK calling unit 630 is specifically configured to call the target SDK plug-in based on the interface rules defined by the target SDK plug-in, so as to call the target SDK plug-in to execute the data processing instruction.

Referring to FIG. 16, a data processing device 700 provided by an embodiment of the present application runs on a mobile terminal, and the device 700 includes:

The data receiving unit 710 is configured to receive a data processing instruction sent by the quick application engine through an extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, The operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

The data detection unit 720 is configured to obtain the corresponding target SDK plug-in based on the identification information.

The version obtaining unit 730 is configured to read the version identifier of the fast application carried in the data processing instruction.

The version obtaining unit 730 is further configured to obtain the version identifier of the target SDK plug-in.

The version determination unit 731 is configured to determine whether the version identifier of the quick application matches the version identifier of the target SDK plug-in.

The SDK calling unit 740 is configured to, if it is determined that the version identifier of the fast application matches the version identifier of the target SDK plug-in, call the target SDK plug-in to execute the data processing instruction.

The function acquiring unit 750 is configured to, if it is determined that the version identifier of the quick application does not match the version identifier of the target SDK plug-in, acquire the functions supported by the target SDK plug-in.

The function judgment unit 760 is configured to judge whether the target SDK plug-in can complete the data processing instruction based on the acquired functions supported by the target SDK plug-in;

The SDK calling unit 740 is further configured to call the target SDK plug-in to execute the data processing instruction if it is determined that the data processing instruction can be completed.

The information sending unit 770 is configured to, if it is determined that the data processing instruction cannot be completed, return prompt information of an operation error to the quick application based on the extended interface.

Referring to FIG. 17, a data processing device 800 provided by an embodiment of the present application runs on a mobile terminal, and the device 800 includes:

The data receiving unit 810 is configured to receive a data processing instruction sent by the quick application engine through an extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, The operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

The data detection unit 820 is configured to obtain the corresponding target SDK plug-in based on the identification information.

The version obtaining unit 830 is configured to read the version identifier of the fast application carried in the data processing instruction.

The version obtaining unit 830 is further configured to obtain the version identifier of the target SDK plug-in.

The version determination unit 831 is configured to determine whether the version identifier of the quick application matches the version identifier of the target SDK plug-in.

The SDK update unit 840 is configured to: if it is determined that the version identifier of the quick app does not match the version identifier of the target SDK plug-in, and the version of the quick app is higher than the version of the target SDK plug-in, the target SDK The version of the plug-in is updated to match the version of the quick application.

The data detection unit 820 is also used to use the updated target SDK plug-in as a new target SDK plug-in.

The SDK calling unit 850 is configured to call the new target SDK plug-in to execute the data processing instruction.

The SDK calling unit 850 is configured to call the target SDK if it is determined that the version identifier of the quick application does not match the version identifier of the target SDK plug-in, and the version of the quick application is lower than the version of the target SDK plug-in The plug-in executes the data processing instruction.

Referring to FIG. 18, a data processing device 900 provided by an embodiment of the present application runs on a mobile terminal, and the device 900 includes:

The data receiving unit 910 is configured to receive a data processing instruction sent by the quick application engine through an extended interface configured to the quick application engine, the data processing instruction being sent by the quick application engine in response to a trigger operation in the operation interface, The operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK.

The data detection unit 920 is configured to obtain the corresponding target SDK plug-in based on the identification information.

The loading judgment unit 930 is used to judge whether the target SDK plug-in is loaded.

The SDK loading unit 940 is configured to dynamically load the target SDK plug-in if it is determined that it is not loaded.

The SDK calling unit 950 is configured to call the target SDK plug-in to execute the data processing instruction after the target SDK plug-in is dynamically loaded.

The SDK calling unit 950 is further configured to call the target SDK plug-in to execute the data processing instruction if it is determined that it has been loaded.

Referring to FIG. 19, a data processing device 1000 provided by an embodiment of the present application runs on a mobile terminal. The device 1000 includes:

The operation detection unit 1010 is configured to generate a data processing instruction in response to a touch operation in the operation interface.

The data sending unit 1020 is configured to call an extended interface configured by the client for the fast application engine, and send the data processing instruction to the client through the extended interface.

The data receiving unit 1030 is configured to receive the result information of executing the data processing instruction returned by the client based on the extended interface.

It should be noted that the device embodiment in this application and the foregoing method embodiment correspond to each other, and the specific principles in the device embodiment can be referred to the content in the foregoing method embodiment, which is not repeated here.

In summary, the data processing method, device, and mobile terminal provided by this application allow the client to configure the extension interface for the fast application engine, so that the client can control the SDK plug-in through the fast application. Through the extended interface configured to the fast app engine, the fast app engine receives the data processing instruction sent by the fast app engine in response to the touch operation in the fast app, obtains the corresponding target SDK plug-in based on the data processing instruction, and calls the target SDK The plug-in executes the data processing instruction. As a result, the quick app triggers the client to control the SDK plug-in based on a cross-application method, and then realizes that the quick app can call the SDK plug-in, and greatly expands the function of the quick app to facilitate the realization of mobile Call other components in the terminal.

Hereinafter, a mobile terminal provided by the present application will be described with reference to FIG. 20.

Referring to FIG. 20, based on the above-mentioned data processing method and device, an embodiment of the present application also provides another mobile terminal 100 that can execute the aforementioned data processing method. The mobile terminal 100 includes one or more (only one is shown in the figure) a processor 102, a memory 104, and a wireless module 106 coupled to each other. Wherein, the memory 104 stores a program that can execute the content in the foregoing embodiment, and the processor 102 can execute the program stored in the memory 104.

The processor 102 may include one or more processing cores. The processor 102 uses various interfaces and lines to connect various parts of the entire mobile terminal 100, and executes by running or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and calling data stored in the memory 104. Various functions and processing data of the mobile terminal 100. Optionally, the processor 102 may use at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). A kind of hardware form to realize. The processor 102 may integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is used for rendering and drawing of display content; the modem is used for processing wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 102, but may be implemented by a communication chip alone.

The memory 104 may include random access memory (RAM) or read-only memory (Read-Only Memory). The memory 104 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 104 may include a storage program area and a storage data area, where the storage program area may store instructions for implementing the operating system and instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.) , Instructions for implementing the following method embodiments, etc. The data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.

The wireless module 106 is used to receive and send electromagnetic waves, and realize the mutual conversion between electromagnetic waves and electrical signals, so as to communicate with a communication network or other equipment, such as communicating with an audio playback device. The wireless module 106 may include various existing circuit elements for performing these functions, for example, an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a subscriber identity module (SIM) card, a memory, etc. . The wireless module 106 can communicate with various networks such as the Internet, an intranet, and a wireless network, or communicate with other devices through a wireless network. The aforementioned wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. For example, the wireless module 106 can exchange information with the base station.

Please refer to FIG. 21, which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. The computer-readable medium 1100 stores program code, and the program code can be invoked by a processor to execute the method described in the foregoing method embodiment.

The computer-readable storage medium 1100 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 1100 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 1100 has a storage space for executing the program code 810 of any method step in the foregoing method. These program codes can be read out from or written into one or more computer program products. The program code 1110 may be compressed in a suitable form, for example.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not drive the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A data processing method, characterized in that it is applied to a client, the method includes:

The data processing instruction sent by the fast application engine is received through the extended interface configured to the fast application engine, and the data processing instruction is sent by the fast application engine in response to a trigger operation in the operation interface, and the operation interface is sent by the Generated by the fast application engine, and the data processing instruction carries the identification information of the target SDK;

Obtain the corresponding target SDK plug-in based on the identification information;

Invoke the target SDK plug-in to execute the data processing instruction.
The method according to claim 1, wherein the identification information of the target SDK includes a package name; the step of obtaining the corresponding target SDK plug-in based on the data processing instruction comprises:

Read the carried package name from the data processing instruction;

Use the SDK plug-in corresponding to the package name as the target SDK plug-in.
The method according to claim 1 or 2, wherein the step of receiving the data processing instruction sent by the fast application engine through the extended interface configured to the fast application engine comprises:

The data processing instruction sent by the fast application engine is received through an extended interface based on inter-process communication configured to the fast application engine.
The method according to claim 3, wherein the extended interface based on inter-process communication comprises an AIDL channel interface.
The method according to claim 3, wherein the extended interface based on inter-process communication comprises a localSocket interface.
The method according to any one of claims 1 to 5, wherein the data processing instruction carries the version identifier of the fast application, and before the step of calling the target SDK plug-in to execute the data processing instruction Also includes:

Read the version identifier of the fast application carried from the data processing instruction;

Acquiring the version identifier of the target SDK plug-in;

Determining whether the version identifier of the quick application matches the version identifier of the target SDK plug-in;

If it is determined that the version identifier of the quick application matches the version identifier of the target SDK plug-in, executing the invoking the target SDK plug-in to execute the data processing instruction.
The method according to claim 6, wherein the method further comprises:

If it is determined that the version identifier of the quick app does not match the version identifier of the target SDK plug-in, and the version of the quick app is higher than the version of the target SDK plug-in, update the version of the target SDK plug-in to Match the version of the fast application;

Use the updated target SDK plugin as the new target SDK plugin;

The step of calling the target SDK plug-in to execute the data processing instruction includes:

Call the new target SDK plug-in to execute the data processing instruction.
The method according to any one of claims 1-7, wherein before the step of invoking the target SDK plug-in to execute the data processing instruction, the method further comprises:

Determine whether the target SDK plug-in is loaded;

If it is determined that it is not loaded, dynamically load the target SDK plug-in;

After the target SDK plug-in is dynamically loaded, the target SDK plug-in is called to execute the data processing instruction.
The method according to any one of claims 1-8, wherein the data processing instruction represents controlling a target device; the step of invoking the target SDK plug-in to execute the data processing instruction comprises:

Make the target SDK plug-in send an instruction to control the target device to the corresponding server, so that the server controls the target device.
The method according to any one of claims 1-9, wherein the data processing instruction represents a local data acquisition request; the step of invoking the target SDK plug-in to execute the data processing instruction comprises:

Enabling the target SDK plug-in to read the requested data locally;

The read data is returned to the fast application engine through the extended interface.
The method according to any one of claims 1-10, wherein the extension interface configured to the fast application engine receives a data processing instruction sent by the fast application engine in response to a touch operation in the fast application Before the steps include:

In response to the quick application start instruction, the operation interface is displayed.
The method according to any one of claims 1-11, wherein the quick application engine is set in the client.
A data processing method, characterized in that it is applied to a fast application engine, and the method includes:

Generating a data processing instruction in response to a touch operation in an operation interface, the operation interface being generated by the fast application engine;

Call the extended interface configured by the client for the fast application engine, and send the data processing instruction to the client through the extended interface;

Receiving result information of executing the data processing instruction returned by the client based on the extended interface.
A data processing device, characterized in that it runs on a mobile terminal, and includes:

The data receiving unit is configured to receive the data processing instruction sent by the quick application engine through the extended interface configured to the quick application engine, and the data processing instruction is sent by the quick application engine in response to a trigger operation in the operation interface, so The operation interface is generated by the fast application engine, and the data processing instruction carries identification information of the target SDK;

The data detection unit is configured to obtain the corresponding target SDK plug-in based on the identification information;

The SDK calling unit is used to call the target SDK plug-in to execute the data processing instruction.
The device according to claim 14, wherein the SDK calling unit is specifically configured to call the target SDK plug-in based on the interface rules defined by the target SDK plug-in, so as to call the target SDK plug-in to execute the data Processing instructions.
A data processing device, characterized in that it runs on a mobile terminal, and includes:

The operation detection unit is configured to generate data processing instructions in response to the touch operation in the operation interface, the operation interface being generated by the fast application engine;

A data sending unit, configured to call an extension interface configured by the client for the fast application engine, and send the data processing instruction to the client through the extension interface;

The data receiving unit is configured to receive the result information of executing the data processing instruction returned by the client based on the extended interface.
A mobile terminal, characterized in that it comprises one or more processors and a memory;

One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute claim 1 -12 Any of the methods described in or execute the method described in claim 13.
A computer-readable storage medium, characterized in that a program code is stored in the computer-readable storage medium, wherein the method according to any one of claims 1-12 is executed when the program code is running or the claims are executed 13. The method described.