CN113168332B - Data processing method and device and mobile terminal - Google Patents
Data processing method and device and mobile terminal Download PDFInfo
- Publication number
- CN113168332B CN113168332B CN201980077010.6A CN201980077010A CN113168332B CN 113168332 B CN113168332 B CN 113168332B CN 201980077010 A CN201980077010 A CN 201980077010A CN 113168332 B CN113168332 B CN 113168332B
- Authority
- CN
- China
- Prior art keywords
- data processing
- processing instruction
- client
- target sdk
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 39
- 238000012545 processing Methods 0.000 claims abstract description 178
- 238000000034 method Methods 0.000 claims abstract description 55
- 230000006870 function Effects 0.000 claims abstract description 45
- 230000004044 response Effects 0.000 claims abstract description 17
- 238000004891 communication Methods 0.000 claims description 15
- 238000001514 detection method Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 description 18
- 230000003993 interaction Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 10
- 230000001960 triggered effect Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000004378 air conditioning Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Abstract
The embodiment of the application discloses a data processing method, a data processing device and a mobile terminal. The method comprises the following steps: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to the fast application engine, wherein the data processing instruction is sent by the fast application engine in response to a triggering 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; acquiring a corresponding target SDK plug-in based on the identification information; and calling the target SDK plug-in to execute the data processing instruction. The method enables the quick application to trigger the client to control the SDK plug-in based on a cross-application mode, further enables the quick application to call the SDK plug-in, and greatly expands functions of the quick application so as to call other components in the mobile terminal through the quick application.
Description
Technical Field
The present application relates to the field of internet of things, and in particular, to a data processing method, a data processing device, and a mobile terminal.
Background
Fast applications are new types of applications that are deeply integrated with an operating system to provide a scenerized experience. The device has the characteristics of no installation and direct opening like a small program. With the popularization of the fast application, the fast application can be applied to controlling the intelligent home equipment, however, the fast application cannot flexibly control equipment of a plurality of factories, and user experience is still to be improved.
Disclosure of Invention
In view of the above problems, the present application provides a data processing method, apparatus and mobile terminal, so as to improve the above problems.
In a first aspect, the present application provides a data processing method, applied to a client, the method including: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to the fast application engine, wherein the data processing instruction is sent by the fast application engine in response to a triggering 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; acquiring a corresponding target SDK plug-in based on the identification information; and calling the target SDK plug-in to execute the data processing instruction.
In a second aspect, the present application provides a data processing method applied to a fast application engine, the method comprising: generating a data processing instruction in response to touch operation in an operation interface, wherein the operation interface is generated by the fast application engine; calling an expansion interface configured by a client to the fast application engine, and sending the data processing instruction to the client through the expansion interface; and receiving result information of executing the data processing instruction returned by the client based on the expansion interface.
In a third aspect, the present application provides a data processing apparatus, for operation in a mobile terminal, the apparatus comprising: the data receiving unit is used for receiving a data processing instruction sent by the fast application engine through an expansion interface configured to the fast application engine, wherein the data processing instruction is sent by the fast application engine in response to a triggering 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; the data detection unit is used for acquiring a corresponding target SDK plug-in based on the identification information;
and the SDK calling unit is used for calling the target SDK plug-in to execute the data processing instruction.
In a fourth aspect, the present application provides a data processing apparatus, for operation in a mobile terminal, the apparatus comprising: the operation detection unit is used for responding to touch operation in an operation interface to generate a data processing instruction, wherein the operation interface is generated by a fast application engine; the data sending unit is used for calling an expansion interface configured by the client side and used for sending the data processing instruction to the client side through the expansion interface; and the data receiving unit is used for receiving result information of executing the data processing instruction, which is returned by the client based on the expansion interface.
In a fifth aspect, the present application provides a mobile terminal comprising one or more processors and 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, the one or more programs configured to perform the methods described above.
In a sixth aspect, the present application provides a computer readable storage medium having program code stored therein, wherein the method described above is performed when the program code is run.
According to the data processing method, the device and the mobile terminal, in the process of controlling the SDK plugin through the fast application by configuring the expansion interface for the fast application engine in the client, the client can receive the data processing instruction sent by the fast application engine after responding to the touch operation in the fast application through the expansion interface configured for the fast application engine, acquire the corresponding target SDK plugin based on the data processing instruction, and call the target SDK plugin to execute the data processing instruction. Therefore, the fast application triggers the client to control the SDK plug-in based on a cross-application mode, the fast application is further enabled to call the SDK plug-in, functions of the fast application are greatly expanded, and other components in the mobile terminal are conveniently called through the fast application.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 shows a schematic architecture diagram of an internet of things according to an embodiment of the present application;
fig. 2 shows a schematic architecture diagram of another internet of things according to an embodiment of the present application;
fig. 3 shows a schematic architecture diagram of still another internet of things according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a fast application engine architecture according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating a communication manner between a client and a server according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an operating environment of a data processing method according to an embodiment of the present application;
FIG. 7 is a flow chart of a data processing method according to an embodiment of the present application;
FIG. 8 is a schematic diagram showing an entry of an operation interface in a data processing method according to an embodiment of the present application;
FIG. 9 is a schematic diagram showing an entry of another operation interface in a data processing method according to an embodiment of the present application;
FIG. 10 is a schematic diagram showing an entry of a further operation interface in a data processing method according to an embodiment of the present application;
FIG. 11 is a flow chart of a data processing method according to another embodiment of the present application;
FIG. 12 is a flow chart of a data processing method according to still another embodiment of the present application;
FIG. 13 is a flow chart showing a data processing method according to still another embodiment of the present application;
FIG. 14 is a flow chart showing a data processing method according to still another embodiment of the present application;
FIG. 15 is a block diagram showing a data processing apparatus according to an embodiment of the present application;
FIG. 16 is a block diagram showing a data processing apparatus according to still another embodiment of the present application;
FIG. 17 is a block diagram showing a data processing apparatus according to still another embodiment of the present application;
FIG. 18 is a block diagram showing a data processing apparatus according to still another embodiment of the present application;
FIG. 19 is a block diagram showing a data processing apparatus according to still another embodiment of the present application;
fig. 20 is a block diagram showing a structure of a mobile terminal for performing a data processing method according to an embodiment of the present application;
Fig. 21 is a storage unit for storing or carrying program code for implementing a device control method according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The internet of things is a network concept which extends and expands a user end of the internet of things to any article and between articles on the basis of the internet concept to exchange information and communicate. With the development of the internet of things technology, some scenes can be configured in the internet of things system. For the configuration scene, a plurality of controlled devices can be involved, and a certain linkage relation exists among the plurality of controlled devices, so that the plurality of controlled devices can work cooperatively.
The controlled equipment can be a projector, a projection screen, an intelligent lamp, an intelligent socket, a human body sensor, a door and window sensor, a wireless switch, an air conditioning partner, a smoke alarm, an intelligent curtain motor, an air purifier, an intelligent sound box and other mobile terminals. In one manner, as shown in fig. 1, the controlling mobile terminal 100 may implement data interaction with the controlled device 99 by directly establishing a wireless connection with the router 90. Furthermore, the mobile terminal 100 may also implement data interaction with the controlled device 99 through a data link between the cloud 91 and the router 90 after establishing a connection with the cloud 91.
Alternatively, as shown in fig. 2, the mobile terminal 100 directly establishes data interaction with the first cloud 91a, and then based on the data interaction between the first cloud 91a and the second cloud 91b, realizes the data interaction between the mobile terminal 100 and the second cloud 91b, and then, in the case that 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 yet another approach, as shown in fig. 3, the controlled device 99 may establish a wireless connection with the router 90 through the gateway 98. 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 or returning an instruction execution result to the mobile terminal. Wherein the data interaction between the mobile terminal and the controlled device may be triggered by a client installed in the mobile terminal.
With the popularization of the quick application, the mobile terminal developer is more expected to realize the same functions as the client through the quick application, so as to improve the development efficiency of the intelligent home function and save the storage space of the mobile terminal.
The fast application is a novel application form based on a terminal equipment hardware platform, is used without installation, and has both original application experience (performance, system integration, interaction and the like). As shown in the structural schematic diagram of the fast application engine in fig. 4, the front end design of the fast application references and integrates the design thought of the main stream front end framework (Vue, practice, etc.): the application is constructed in a componentization mode, the MVVM design mode with the data binding as the core is adopted, the performance is improved in a V-DOM mode, and meanwhile, a concise and clear template of the class Vue is selected.
To facilitate data interaction, each vendor may develop its own SDK plug-in for client calls in the mobile terminal. After the client loads the SDK plugin of the manufacturer, the loaded SDK plugin can be called, and data interaction is further carried out between the SDK plugin and the server of the manufacturer. For example, as shown in fig. 5, the SDK plug-in 111 of vendor a and the SDK plug-in 112 of vendor B are loaded in the client 110 shown in fig. 5, wherein the client 110 may interact data with the server 210 of vendor a by calling the SDK plug-in of vendor a, and the client 110 may interact data with the server 220 of vendor B by calling the SDK plug-in of vendor B. However, the inventor finds that the quick application cannot directly call the SDK plug-in of the manufacturer, and cannot directly communicate with the client capable of loading the SDK plug-in, so that the quick application cannot call the SDK plug-in through the client, and therefore the quick application cannot achieve the same function as the client.
Therefore, the inventor proposes the data processing method, the device and the mobile terminal which can enable the quick application to trigger the client to control the SDK plug-in based on a cross-application mode, further achieve that the quick application calls the SDK plug-in, greatly expand functions of the quick application, and facilitate the quick application to call other components in the mobile terminal.
The application environment of the embodiments of the present application will be described with reference to the accompanying drawings.
As shown in fig. 6, in the mobile terminal 100 shown in the drawing, a quick application and a client 110 are running. Wherein the fast application is running on a fast application engine and wherein a client-provided expansion interface 97 is provided. And an expansion interface 96 communicating with the expansion interface 97 is provided in the client 110. And the client 110 may call the SDK plug-ins of the respective vendors through the extension interface. For example, the vendor A SDK plug-in 111, vendor B SDK plug-in 112, and vendor C SDK plug-in 113 in the diagram may be invoked. In this case, the data processing instruction triggered in the quick application may be transferred to the expansion interface 96 in the client through the expansion interface 97 provided in the quick application engine, and then the data processing instruction may be transferred to the SDK plug-in of each vendor.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring 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: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to 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.
The operation interface for operation is rendered and generated by the fast application engine, and under the operation mode based on the fast application, the mobile terminal can have various modes for triggering and displaying the operation interface.
As a way, a fast application client may be configured in the mobile terminal, so that an operation interface corresponding to another application program may be entered in the interface of the fast application client. It will be appreciated that the fast application client is different from the client on which the data processing method provided in this embodiment operates.
For example, in the operation interface 95 shown in fig. 8, operation interface entry controls of the application a, the application B, and the application C are displayed in the operation interface 95, and it is understood that the operation interfaces of the application a, the application B, and the application C herein refer to operation interfaces generated by the quick application engine. In this case, when the fast application client detects that the user touches the entry control of the application program a, the fast application client may load and display the operation interface of the application program a, and when the fast application client detects that the user touches the entry control of the application program B, the fast application client may load and display the operation interface of the application program B, and when the fast application client detects that the user touches the entry control of the application program C, the fast application client may load and display the operation interface of the application program C.
Alternatively, a card 93 of the quick application may be displayed in the interface 94 of the minus one screen as shown in fig. 9, in which entry controls of the operation interface generated by the quick application engine corresponding to the respective application programs are displayed. For example, the operation interface entry controls for application a, application B, and application C may still be displayed in the card 93. Correspondingly, after the mobile terminal detects that the entry control of the application program A in the card is touched, the fast application client is triggered to load and display the operation interface of the application program A, and after the mobile terminal detects that the entry control of the application program B in the card is touched, the fast application client is triggered to load and display the operation interface of the application program B, and when the mobile terminal detects that the entry control of the application program C in the card is touched, the fast application client is triggered to load and display the operation interface of the application program C.
As yet another manner, the entry control may be set in another client, for example, a client operated by the data processing method provided in the embodiment of the present application. For example, as shown in fig. 10, in the case where the client operated by the data processing method provided by the embodiment of the present application is an intelligent home client, an entry control of an operation interface corresponding to vendor a, vendor B, and vendor C may be displayed in an interface 92 of the intelligent home client. It will be understood that, as shown in fig. 6, the operation interface is running on the quick application engine, and based on this situation, after detecting the touch operation on the portal control named "vendor a", the client may send, through an extension interface (which will be described in detail later) configured to the quick application engine, an instruction for displaying the operation interface corresponding to vendor a to the quick application engine, so as to trigger the quick application engine to render the operation interface corresponding to vendor a.
It can be understood that, if the quick application engine renders the data (such as the interface UI data or the device status data) required by the operation interface of the vendor a, the quick application engine may request the smart home client through the foregoing expansion interface, and the smart home client may retrieve the request from the SDK plug-in corresponding to the loaded vendor a after receiving the request, and then return the request to the quick application engine through the expansion interface. Wherein the SDK plug-in may look up directly locally (e.g., UI data may already be encapsulated within the SDK plug-in) if it determines that the required data is available locally, and may send a data acquisition request to the corresponding vendor server as shown in fig. 5 if it determines that it needs to be acquired from the server (e.g., device status data, etc.).
It should be noted that, in one manner, the fast application engine and the client are two applications running relatively independently, and then in this case, the expansion interface between the fast application engine and the client is an expansion interface based on inter-process communication. Optionally, the inter-process communication based extension interface includes an AIDL channel interface. Optionally, the expansion interface based on inter-process communication includes a localSocket interface.
In the implementation mode of AIDL channel interface, the quick application engine can call the client through the interface function in the jar package provided by the client, and write the data processing instruction to be executed into the interface function in the form of parameters, so that the client can acquire the data processing instruction in the form of parameters. Furthermore, as a way of improving security, the fast application engine may determine, through the signature of the packet name and the application in the ontransactcallback, that an application without authentication cannot access the AIDL channel interface.
After the operation interface is displayed, the user can realize the network distribution, control and the like of the equipment by operating the operation interface. Wherein, as a way, the operation objects corresponding to different quick applications are different.
For example, if the operation interface is entered through the vendor A's portal control shown in FIG. 10, then the performed operation is made to vendor A's device, whereas if the operation interface is entered through the vendor B's portal control shown in FIG. 10, then the performed operation is made to vendor B's device. It can be understood that, for the data processing instruction of the device of the different manufacturer, the client will call the SDK plug-in of the different manufacturer to execute, so that in order to facilitate the distinguishing of the manufacturer device to which the data processing instruction is to operate by the subsequent client, in the process of generating the data processing instruction by the fast application engine, the identification information of the fast application triggering the generation of the data processing instruction is added into the data processing instruction. The identification information may be a unique identifier allocated to the mobile terminal, or may be a packet name of the fast application.
Step S120: and acquiring a corresponding target SDK plug-in based on the identification information.
It can be appreciated that in the embodiment of the present application, the quick application may implement the invocation of various types of application programs or the control of devices of multiple vendors. In the process of controlling equipment of multiple manufacturers, the method is realized by calling SDK plug-ins of the multiple manufacturers loaded in the client. After receiving the data processing instruction through providing the fast application engine, the client side firstly extracts the identification information of the SDK plugin from the data processing instruction, and then searches the matched SDK plugin from the plurality of SDK plugins recorded before as a target SDK plugin.
In one manner, the client may record the downloaded SDK plug-in after loading the SDK plug-in of a certain vendor. It is also possible to record after loading a certain downloaded SDK plug-in. Taking the package name as an example, the quick application can correspondingly store the package name of the quick application of a certain manufacturer for the recorded SDK plug-in of the manufacturer, acquire the data processing instruction, and then identify the corresponding target SDK plug-in according to the package name extracted from the data processing instruction.
Step S130: and calling the target SDK plug-in to execute the data processing instruction.
It will be appreciated that the SDK plug-in has some software functions encapsulated inside, and that corresponding functions can be implemented by the execution of the software functions. In order to facilitate the external program to call the SDK plug-in, the SDK plug-in exposes its interface through which the SDK plug-in is called. In the embodiment of the application, in order to facilitate uniform calling, interfaces of SDK plugins of different manufacturers are packaged according to uniform setting rules. I.e., the interface rules of the SDK plug-ins of different vendors are the same. And the client calls the target SDK plug-in based on interface rules defined by the target SDK plug-in the process of calling 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 plug-ins belonging to different vendors, the SDK plug-ins belonging to different devices may be called in the client, or the SDK plug-ins belonging to different applications may be called. The differences between the different SDK plug-ins invoked in the client may also be other different manners besides vendor, device and application program, and the embodiments of the present application are not limited in detail.
It should be noted that, the fast application engine and the client for executing the data processing method in the embodiment of the present application may be two independently running application programs, or the fast application engine may be embedded in the client of the data processing method in the embodiment of the present application, that is, the client includes the fast application engine.
According to the data processing method, in the mode that the expansion interface is configured for the fast application engine in the client, in the process of controlling the SDK plug-in through the fast application, the client can receive the data processing instruction sent by the fast application engine after responding to the touch operation in the fast application through the expansion interface configured for the fast application engine, acquire the corresponding target SDK plug-in based on the data processing instruction, and call the target SDK plug-in to execute the data processing instruction. Therefore, the fast application triggers the client to control the SDK plug-in based on a cross-application mode, the fast application is further enabled to call the SDK plug-in, functions of the fast application are greatly expanded, and other components in the mobile terminal are conveniently called through the fast application.
Referring to fig. 11, a data processing method provided in an embodiment of the present application is applied to a client, and the method includes:
Step S210: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to 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.
Step S220: and acquiring a corresponding target SDK plug-in based on the identification information.
Step S230: and reading the carried version identification of the fast application from the data processing instruction.
Step S240: and acquiring the version identification of the target SDK plug-in.
Step S250: and judging whether the version identifier of the quick application is matched with the version identifier of the target SDK plug-in.
With the update of the quick application, the quick application of different vendors or the quick application of different devices may be updated with the update. While fast applications after upgrades may have more functionality. It can be understood that, in the embodiment of the present application, the fast application executes the data processing instruction by calling the SDK plug-in the client, and if the function displayed in the operation interface is actually not completed by the corresponding target SDK plug-in, the data error may be caused, thereby affecting the user experience. For example, the function information of device status acquisition is displayed on the operation interface, but if the SDK plug-in corresponding to the quick application does not have a handle for sending the device status acquisition to the server, the SDK plug-in cannot execute the data processing instruction generated after the touch device status acquisition. The fact that the version of the SDK plug-in corresponding to the same vendor or the same device is inconsistent with the version of the fast application may be because the mobile terminal does not download the latest version in time or an error occurs in the updating process.
Step S260: and if the version identification of the quick application is judged to be matched with the version identification of the target SDK plug-in, calling the target SDK plug-in to execute the data processing instruction.
Step S261: and if the version identification of the quick application is not matched with the version identification of the target SDK plug-in, acquiring the function supported by the target SDK plug-in.
It will be appreciated that as one way, each SDK plug-in is downloaded from a corresponding server. For example, as shown in FIG. 5, vendor A's SDK plug-in is downloaded from vendor A's server, while vendor B's SDK plug-in is downloaded from vendor B's server. When the mobile terminal downloads the SDK plug-in, a function description file can be correspondingly downloaded, and the function supported by the currently downloaded version of the SDK can be correspondingly recorded in the function description file.
Step S270: and judging whether the target SDK plug-in can complete the data processing instruction or not based on the acquired functions supported by the target SDK plug-in.
It can be understood that, in the case of acquiring the function supported by the target SDK plug-in based on the foregoing, if it is determined that the function supported by the target SDK plug-in includes a function to be executed by a data processing instruction sent by the fast application engine received by the client, then it is determined that the target SDK plug-in may 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 performed.
Step S280: and if the data processing instruction cannot be completed, returning a prompt message of an operation error to the quick application based on the expansion interface.
According to the data processing method, in the method of configuring the expansion interface for the quick application engine in the client, in the process of controlling the SDK plug-in through the quick application, the client can receive the data processing instruction sent by the quick application engine after responding to the touch operation in the quick application through the expansion interface configured for the quick application engine, acquire the corresponding target SDK plug-in based on the data processing instruction, and call the target SDK plug-in to execute the data processing instruction when the acquired target SDK plug-in is judged to be identical with the version of the quick application. Therefore, the fast application triggers the client to control the SDK plug-in based on a cross-application mode, the fast application is further enabled to call the SDK plug-in, functions of the fast application are greatly expanded, and other components in the mobile terminal are conveniently called through the fast application. Meanwhile, data errors caused by inconsistent versions of the target SDK plug-in and the fast application or execution failure of the data processing instruction are avoided.
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: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to 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.
Step S320: and acquiring a corresponding target SDK plug-in based on the identification information.
Step S330: and reading the carried version identification of the fast application from the data processing instruction.
Step S340: and acquiring the version identification of the target SDK plug-in.
Step S350: and judging whether the version identifier of the quick application is matched with the version identifier of the target SDK plug-in.
Step S360: and if the version identification of the fast application is not matched with the version identification of the target SDK plugin and the version of the fast application is higher than the version of the target SDK plugin, updating the version of the target SDK plugin to be matched with the version of the fast application.
Step S361: and taking the updated target SDK plug-in as a new target SDK plug-in.
Step S362: and calling the new target SDK plug-in to execute the data processing instruction.
Step S370: and if the version identification of the fast application is not matched with the version identification of the target SDK plugin, and the version of the fast application is lower than the version of the target SDK plugin, calling the target SDK plugin to execute the data processing instruction.
Step S380: and if the version identification of the quick application is judged to be matched with the version identification of the target SDK plug-in, calling the target SDK plug-in to execute the data processing instruction.
According to the data processing method provided by the application, the quick application triggers the client to control the SDK plug-in based on the cross-application mode, so that the quick application can call the SDK plug-in, the functions of the quick application can be greatly expanded, and the quick application can call other components in the mobile terminal conveniently. Meanwhile, after the fact that the version of the fast application is higher than the version of the target SDK plug-in is detected, the version of the target SDK plug-in can be updated in time, and data errors or execution failure of data processing instructions caused by inconsistent versions of the target SDK plug-in and the fast application are avoided.
Referring to fig. 13, a data processing method provided in an embodiment of the present application is applied to a client, and the method includes:
step S410: receiving a data processing instruction sent by a fast application engine through an expansion interface configured to 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.
Step S420: and acquiring a corresponding target SDK plug-in based on the identification information.
Step S430: and judging whether the target SDK plug-in is loaded or not.
Step S440: and if the target SDK plug-in is judged to be unloaded, dynamically loading the target SDK plug-in.
Step S441: and after the dynamic loading of the target SDK plug-in is completed, calling the target SDK plug-in to execute the data processing instruction.
Step S450: and if the loading is judged, calling the target SDK plug-in to execute the data processing instruction.
According to the data processing method provided by the application, the quick application triggers the client to control the SDK plug-in based on the cross-application mode, so that the quick application can call the SDK plug-in, the functions of the quick application can be greatly expanded, and the quick application can call other components in the mobile terminal conveniently. Meanwhile, after the target SDK plug-in is obtained, even if the target SDK plug-in is detected to be unloaded, the target SDK plug-in is called to execute the data processing instruction by means of dynamically loading the target SDK plug-in after the target SDK plug-in is dynamically loaded, so that the target SDK plug-in does not need to be embedded into the client at first, the control occupation of the client is reduced, the client can be lightened conveniently, and the loading flexibility of the SDK plug-in is improved.
Referring to fig. 14, a data processing method provided in an embodiment of the present application is applied to a client, and the method includes:
step S510: and responding to touch operation in an operation interface to generate a data processing instruction, wherein the operation interface is generated by the fast application engine.
Step S520: and calling an expansion interface configured by the client side and used for the fast application engine, and sending the data processing instruction to the client side through the expansion interface.
Step S530: and receiving result information of executing the data processing instruction returned by the client based on the expansion interface.
According to the data processing method provided by the application, the quick application triggers the client to control the SDK plug-in based on the cross-application mode, so that the quick application can call the SDK plug-in, the functions of the quick application can be greatly expanded, and the quick application can call other components in the mobile terminal conveniently.
Referring to fig. 15, a data processing apparatus 600 according to an embodiment of the present application is operated in a mobile terminal, where the apparatus 600 includes:
the data receiving unit 610 is configured to receive, through an extension interface configured to a fast application engine, a data processing instruction sent by the fast application engine, where 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.
As one manner, the data receiving unit 610 is specifically configured to receive, through an expansion interface configured to a fast application engine and based on inter-process communication, a data processing instruction sent by the fast application engine.
Optionally, the inter-process communication based extension interface includes an AIDL channel interface.
Optionally, the expansion interface based on inter-process communication includes a localSocket interface.
And a data detection unit 620, configured to obtain a corresponding target SDK plug-in based on the identification information.
The data detection unit 620 is specifically configured to obtain a target SDK plug-in from a plurality of SDK plug-ins based on the data processing instruction, where the interface rules defined by the plurality of SDK plug-ins are the same.
And 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 rule 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 apparatus 700 according to an embodiment of the present application is operated in a mobile terminal, where the apparatus 700 includes:
the data receiving unit 710 is configured to receive, through an extension interface configured to a fast application engine, a data processing instruction sent by the fast application engine, where 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.
And a data detection unit 720, configured to obtain a corresponding target SDK plug-in based on the identification information.
And the version obtaining unit 730 is configured to read the carried version identifier of the fast application from the data processing instruction.
The version obtaining unit 730 is further configured to obtain a version identifier of the target SDK plug-in.
And the version judging unit 731 is configured to judge whether the version identifier of the fast application is matched with the version identifier of the target SDK plug-in.
And the SDK calling unit 740 is configured to call the target SDK plug-in to execute the data processing instruction if it is determined that the version identifier of the fast application matches the version identifier of the target SDK plug-in.
And the function obtaining unit 750 is configured to obtain a function supported by the target SDK plug-in if it is determined that the version identifier of the fast application does not match the version identifier of the target SDK plug-in.
A function judging unit 760 for judging whether the target SDK plug-in can complete the data processing instruction based on the acquired function 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.
And the information sending unit 770 is configured to return, if it is determined that the data processing instruction cannot be completed, a notification of an operation error to the fast application based on the expansion interface.
Referring to fig. 17, a data processing apparatus 800 according to an embodiment of the present application is operated in a mobile terminal, where the apparatus 800 includes:
the data receiving unit 810 is configured to receive, through an extension interface configured to a fast application engine, a data processing instruction sent by the fast application engine, where 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.
And the data detection unit 820 is configured to obtain a corresponding target SDK plug-in based on the identification information.
And the version obtaining unit 830 is configured to read, from the data processing instruction, a version identifier of the fast application carried by the data processing instruction.
The version obtaining unit 830 is further configured to obtain a version identifier of the target SDK plug-in.
And the version judging unit 831 is used for judging whether the version identifier of the quick application is matched with the version identifier of the target SDK plug-in.
And the SDK updating unit 840 is configured to update the version of the target SDK plug-in to match the version of the fast application if it is determined that the version identifier of the fast application does not match the version identifier of the target SDK plug-in, and the version of the fast application is higher than the version of the target SDK plug-in.
The data detection unit 820 is further configured to take the updated target SDK plug-in as a new target SDK plug-in.
And the SDK calling unit 850 is configured to call the new target SDK plug-in to execute the data processing instruction.
And the SDK calling unit 850 is configured to call the target SDK plug-in to execute the data processing instruction if it is determined that the version identifier of the fast application does not match the version identifier of the target SDK plug-in, and the version of the fast application is lower than the version of the target SDK plug-in.
Referring to fig. 18, a data processing apparatus 900 according to an embodiment of the present application is configured to operate in a mobile terminal, where the apparatus 900 includes:
the data receiving unit 910 is configured to receive, through an extension interface configured to a fast application engine, a data processing instruction sent by the fast application engine, where 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.
And the data detection unit 920 is configured to obtain a corresponding target SDK plug-in based on the identification information.
And a loading judgment unit 930, configured to judge whether the target SDK plug-in is loaded.
And an SDK loading unit 940, configured to dynamically load the target SDK plug-in if it is determined that the target SDK plug-in is not loaded.
And the SDK calling unit 950 is configured to call the target SDK plug-in to execute the data processing instruction after the dynamic loading of the target SDK plug-in is completed.
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 the data processing instruction is loaded.
Referring to fig. 19, a data processing apparatus 1000 according to an embodiment of the present application is operated in a mobile terminal, where the apparatus 1000 includes:
an operation detection unit 1010 for generating a data processing instruction in response to a touch operation in the operation interface.
And the data sending unit 1020 is configured to call an expansion interface configured by the client to the fast application engine, and send the data processing instruction to the client through the expansion interface.
And the data receiving unit 1030 is configured to receive result information of the execution of the data processing instruction returned by the client based on the extension interface.
It should be noted that, in the present application, the device embodiment and the foregoing method embodiment correspond to each other, and specific principles in the device embodiment may refer to the content in the foregoing method embodiment, which is not described herein again.
In summary, in the data processing method, the device and the mobile terminal provided by the application, by configuring the expansion interface for the fast application engine in the client, the client can receive the data processing instruction sent by the fast application engine after responding to the touch operation in the fast application through the expansion interface configured for the fast application engine in the process of controlling the SDK plug-in by the fast application, acquire the corresponding target SDK plug-in based on the data processing instruction, and call the target SDK plug-in to execute the data processing instruction. Therefore, the fast application triggers the client to control the SDK plug-in based on a cross-application mode, the fast application is further enabled to call the SDK plug-in, functions of the fast application are greatly expanded, and other components in the mobile terminal are conveniently called through the fast application.
A mobile terminal according to the present application will be described with reference to fig. 20.
Referring to fig. 20, based on the above-mentioned data processing method and apparatus, another mobile terminal 100 capable of executing the above-mentioned data processing method is provided in the embodiment of the present application. The mobile terminal 100 includes one or more (only one shown) processors 102, memory 104, and a wireless module 106 coupled to one another. The memory 104 stores therein a program capable of executing the contents of the foregoing embodiments, and the processor 102 can execute the program stored in the memory 104.
Wherein the processor 102 may include one or more processing cores. The processor 102 utilizes various interfaces and lines to connect various portions of the overall mobile terminal 100, perform various functions of the mobile terminal 100, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and invoking data stored in the memory 104. Alternatively, the processor 102 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 102 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 102 and may be implemented solely by a single communication chip.
The Memory 104 may include random access Memory (Random Access Memory, RAM) or Read-Only Memory (RAM). Memory 104 may be used to store instructions, programs, code sets, or instruction sets. The memory 104 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described below, etc. The storage data area may also store data created by the terminal 100 in use (such as phonebook, audio-video data, chat-record data), etc.
The wireless module 106 is configured to receive and transmit electromagnetic waves, and to implement mutual conversion between the electromagnetic waves and the electrical signals, so as to communicate with a communication network or other devices, such as an audio playback device. The wireless module 106 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and the like. The wireless module 106 may communicate with various networks such as the internet, intranets, wireless networks, or other devices via wireless networks. The wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. For example, the wireless module 106 may interact with a base station.
Referring to fig. 21, a block diagram of a computer readable storage medium according to an embodiment of the present application is shown. The computer readable medium 1100 has stored therein program code that can be invoked by a processor to perform the methods described in the method embodiments above.
The computer readable storage medium 1100 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Optionally, computer readable storage medium 1100 includes non-volatile computer readable medium (non-transitory computer-readable storage medium). The computer readable storage medium 1100 has storage space for program code 810 that performs any of the method steps described above. The program code can be read from or written to one or more computer program products. Program code 1110 may be compressed, for example, in a suitable form.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be appreciated by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not drive the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (14)
1. A data processing method, applied to a client, the method comprising:
receiving a data processing instruction sent by a fast application engine through an expansion interface based on process-to-process communication and configured to the fast application engine, wherein the data processing instruction is sent by the fast application engine in response to a triggering operation in an operation interface, the operation interface is generated by the fast application engine according to a selected manufacturer, the data processing instruction carries identification information of a target SDK, the expansion interface comprises an AIDL channel interface, the fast application engine calls the client through an interface function in a jar packet provided by the client, and the data processing instruction to be executed is written into the interface function in a parameter form so that the client acquires the data processing instruction in a parameter form;
based on the identification information, acquiring corresponding target SDK plugins from the SDK plugins of a plurality of manufacturers included in the client;
and calling the target SDK plug-in to execute the data processing instruction so as to control the equipment of the selected manufacturer.
2. The method of claim 1, wherein the identification information of the target SDK includes a packet name; the step of obtaining the corresponding target SDK plug-in comprises the following steps:
Reading the carried packet name from the data processing instruction;
and taking the SDK plugin corresponding to the package name as a target SDK plugin.
3. The method according to any one of claims 1-2, wherein the data processing instruction carries a version identifier of the fast application, and before the step of calling the target SDK plug-in to execute the data processing instruction, further comprises:
reading the carried version identification of the quick application from the data processing instruction;
acquiring a version identifier of the target SDK plug-in;
judging whether the version identifier of the quick application is matched with the version identifier of the target SDK plug-in;
and if the version identification of the quick application is judged to be matched with the version identification of the target SDK plug-in, executing the call of the target SDK plug-in to execute the data processing instruction.
4. A method according to claim 3, characterized in that the method further comprises:
if the version identification of the fast application is not matched with the version identification of the target SDK plugin, and the version of the fast application is higher than the version of the target SDK plugin, updating the version of the target SDK plugin to a version matched with the version of the fast application;
Taking the updated target SDK plug-in as a new target SDK plug-in;
the step of calling the target SDK plug-in to execute the data processing instruction comprises the following steps:
and calling the new target SDK plug-in to execute the data processing instruction.
5. The method of any of claims 1-2, wherein the step of invoking the target SDK plug-in to execute the data processing instruction further comprises:
judging whether the target SDK plug-in is loaded or not;
if the target SDK plug-in is judged to be unloaded, dynamically loading the target SDK plug-in;
and after the dynamic loading of the target SDK plug-in is completed, calling the target SDK plug-in to execute the data processing instruction.
6. The method of any of claims 1-2, wherein the data processing instructions characterize controlling the target device; the step of calling the target SDK plug-in to execute the data processing instruction comprises the following steps:
and the target SDK plug-in sends an instruction for controlling the target device to a corresponding server so that the server controls the target device.
7. The method of any of claims 1-2, wherein the data processing instructions characterize a local data acquisition request; the step of calling the target SDK plug-in to execute the data processing instruction comprises the following steps:
Causing the target SDK plug-in to locally read the requested data;
and returning the read data to the fast application engine through the expansion interface.
8. The method according to any one of claims 1-2, wherein the step of receiving, by the flash application engine, a data processing instruction sent by the flash application engine in response to a touch operation in the flash application via an inter-process communication based extension interface configured to the flash application engine further comprises:
and responding to a quick application starting instruction, and displaying the operation interface.
9. A data processing method for use with a fast application engine, the method comprising:
generating a data processing instruction in response to touch operation in an operation interface, wherein the operation interface is generated by the fast application engine according to the selected manufacturer, and the data processing instruction carries identification information;
calling an expansion interface configured by a client and based on inter-process communication for the fast application engine, sending the data processing instruction to the client through the expansion interface, after the client receives the data processing instruction, acquiring corresponding target SDK plugins from a plurality of manufacturer SDK plugins included in the client based on identification information in the data processing instruction, calling the target SDK plugins to execute the data processing instruction so as to control the selected manufacturer equipment, wherein the expansion interface comprises an AIDL channel interface, the fast application engine calls the client through an interface function in a jar packet provided by the client, and writes the data processing instruction to be executed into the interface function in a parameter form so as to enable the client to acquire the data processing instruction in a parameter form;
And receiving result information of executing the data processing instruction returned by the client based on the expansion interface.
10. A data processing apparatus, characterized by a client operating in a mobile terminal, the apparatus comprising:
the data receiving unit is used for receiving a data processing instruction sent by the fast application engine through an expansion interface based on process-to-process communication and configured to 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 according to a selected manufacturer, the data processing instruction carries identification information of a target SDK, the expansion interface comprises an AIDL channel interface, the fast application engine calls the client through an interface function in a jar packet provided by the client, and the data processing instruction to be executed is written into the interface function in a parameter form so that the client acquires the data processing instruction in a parameter form;
the data detection unit is used for acquiring corresponding target SDK plug-ins from the SDK plug-ins of a plurality of manufacturers, which are included in the client, based on the identification information;
And the SDK calling unit is used for calling the target SDK plug-in to execute the data processing instruction so as to control the equipment of the selected manufacturer.
11. The apparatus of claim 10, wherein the SDK calling unit is specifically configured to call the target SDK plug-in based on an interface rule defined by the target SDK plug-in to call the target SDK plug-in to execute the data processing instruction.
12. A data processing apparatus operable on a mobile terminal, the apparatus comprising:
the operation detection unit is used for responding to touch operation in an operation interface to generate a data processing instruction, the operation interface is generated by a fast application engine according to a selected manufacturer, and the data processing instruction carries identification information;
the data sending unit is used for calling an expansion interface configured by a client and based on process-to-process communication of the quick application engine, sending the data processing instruction to the client through the expansion interface, acquiring corresponding target SDK plugins from a plurality of manufacturer SDK plugins included by the client based on identification information in the data processing instruction after the client receives the data processing instruction, calling the target SDK plugins to execute the data processing instruction so as to control equipment of the selected manufacturer, wherein the expansion interface comprises an AIDL channel interface, the quick application engine calls the client through an interface function in a jar packet provided by the client, and writes the data processing instruction to be executed into the interface function in a parameter mode so as to enable the client to acquire the data processing instruction in a parameter mode;
And the data receiving unit is used for receiving result information of executing the data processing instruction, which is returned by the client based on the expansion interface.
13. A mobile terminal comprising one or more processors and 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, the one or more programs configured to perform the method of any of claims 1-8 or the method of claim 9.
14. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a program code, wherein the method of any of claims 1-8 or the method of claim 9 is performed when the program code is run.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2019/075943 WO2020168567A1 (en) | 2019-02-22 | 2019-02-22 | Data processing method and device, and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113168332A CN113168332A (en) | 2021-07-23 |
| CN113168332B true CN113168332B (en) | 2023-11-10 |
Family
ID=72144475
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980077010.6A Active CN113168332B (en) | 2019-02-22 | 2019-02-22 | Data processing method and device and mobile terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113168332B (en) |
| WO (1) | WO2020168567A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113821200B (en) * | 2021-08-20 | 2022-08-30 | 浙江时空道宇科技有限公司 | Draggable modeling method and system for big data task, storage medium and terminal |
| CN114501079A (en) * | 2022-01-29 | 2022-05-13 | 京东方科技集团股份有限公司 | Method for processing multimedia data and related device |
| CN117425877A (en) * | 2022-05-18 | 2024-01-19 | 北京小米移动软件有限公司 | Access method and device for web application program |
| CN117519837A (en) * | 2024-01-02 | 2024-02-06 | 暗物智能科技(广州)有限公司 | Interface management method and interface management system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488489A (en) * | 2013-09-30 | 2014-01-01 | 乐视网信息技术（北京）股份有限公司 | Data processing method and device |
| CN106843978A (en) * | 2017-01-23 | 2017-06-13 | 北京乐盟互动科技有限公司 | A kind of SDK cut-in methods and system |
| CN107682238A (en) * | 2017-09-15 | 2018-02-09 | 广州神马移动信息科技有限公司 | Smart home platform device and terminal electronic device |
| CN108768803A (en) * | 2018-05-28 | 2018-11-06 | 北京小米移动软件有限公司 | Add the method, apparatus and storage medium of smart machine |
| CN109032691A (en) * | 2018-06-25 | 2018-12-18 | 腾讯科技（深圳）有限公司 | A kind of small routine operation method, device and storage medium |
| CN109271239A (en) * | 2018-08-10 | 2019-01-25 | 北京达佳互联信息技术有限公司 | Method, apparatus, system, equipment and the medium of data processing |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20140091122A (en) * | 2013-01-07 | 2014-07-21 | 에스케이플래닛 주식회사 | Method for management application of terminal, system and apparatus thereof |
| US20140358958A1 (en) * | 2013-05-29 | 2014-12-04 | Microsoft Corporation | Surfacing direct app actions |
| CN105204894B (en) * | 2015-08-28 | 2019-07-23 | 小米科技有限责任公司 | The method and apparatus for installing the plug-in unit of smart machine |
-
2019
- 2019-02-22 WO PCT/CN2019/075943 patent/WO2020168567A1/en active Application Filing
- 2019-02-22 CN CN201980077010.6A patent/CN113168332B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488489A (en) * | 2013-09-30 | 2014-01-01 | 乐视网信息技术（北京）股份有限公司 | Data processing method and device |
| CN106843978A (en) * | 2017-01-23 | 2017-06-13 | 北京乐盟互动科技有限公司 | A kind of SDK cut-in methods and system |
| CN107682238A (en) * | 2017-09-15 | 2018-02-09 | 广州神马移动信息科技有限公司 | Smart home platform device and terminal electronic device |
| CN108768803A (en) * | 2018-05-28 | 2018-11-06 | 北京小米移动软件有限公司 | Add the method, apparatus and storage medium of smart machine |
| CN109032691A (en) * | 2018-06-25 | 2018-12-18 | 腾讯科技（深圳）有限公司 | A kind of small routine operation method, device and storage medium |
| CN109271239A (en) * | 2018-08-10 | 2019-01-25 | 北京达佳互联信息技术有限公司 | Method, apparatus, system, equipment and the medium of data processing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113168332A (en) | 2021-07-23 |
| WO2020168567A1 (en) | 2020-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113168332B (en) | Data processing method and device and mobile terminal | |
| CN110225487B (en) | Profile generating and acquiring method, related equipment and storage medium | |
| CN109117361B (en) | Remote debugging method, related equipment and system for small program | |
| CN108241500B (en) | Method, device and system for repairing hardware component and storage medium | |
| CN105302587B (en) | Data-updating method and device | |
| CN110032512B (en) | Debugging method of small program, related equipment and terminal | |
| CN107741844B (en) | Method and device for generating application installation package | |
| CN113498594B (en) | Control method and device of smart home system, electronic equipment and storage medium | |
| CN113412469A (en) | Equipment network distribution method and device, electronic equipment and storage medium | |
| CN107526605B (en) | Method and device for realizing application program loading service assembly | |
| CN107766747B (en) | Method for verifying integrity of application program installation package, mobile terminal and server | |
| EP2608585B1 (en) | Method, device and system for triggering terminal operation | |
| KR20100063474A (en) | Method and system for providing fota service | |
| CN107038046B (en) | Method and device for upgrading audio playing system and terminal | |
| WO2023185166A1 (en) | Service call method and apparatus, device and storage medium | |
| CN113938535A (en) | Internet of things equipment access method and device based on multi-protocol adaptation | |
| US20070106770A1 (en) | Managing a remote device by a communication element that does not specify an identifier for the management object | |
| CN113672441A (en) | Method and device for testing intelligent equipment | |
| CN109714195B (en) | Equipment control method and device, electronic equipment and Internet of things system | |
| CN113138852A (en) | Resource loading method and device, chip and electronic equipment | |
| CN107463395B (en) | Component calling method and device | |
| CN111338710A (en) | Application program control method and device, electronic equipment and storage medium | |
| CN112910985B (en) | Protocol conversion method, device, equipment and storage medium based on intelligent contract | |
| KR102506155B1 (en) | Electronic device, application executing system and control methods thereof | |
| CN116567133A (en) | Resource playing method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |