WO2020168568A1 - 数据处理方法、装置、电子设备及可读存储介质 - Google Patents

数据处理方法、装置、电子设备及可读存储介质 Download PDF

Info

Publication number
WO2020168568A1
WO2020168568A1 PCT/CN2019/075944 CN2019075944W WO2020168568A1 WO 2020168568 A1 WO2020168568 A1 WO 2020168568A1 CN 2019075944 W CN2019075944 W CN 2019075944W WO 2020168568 A1 WO2020168568 A1 WO 2020168568A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
quick application
quick
instruction
data information
Prior art date
Application number
PCT/CN2019/075944
Other languages
English (en)
French (fr)
Inventor
成云峰
Original Assignee
深圳市欢太科技有限公司
Oppo广东移动通信有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳市欢太科技有限公司, Oppo广东移动通信有限公司 filed Critical 深圳市欢太科技有限公司
Priority to CN201980078011.2A priority Critical patent/CN113168334A/zh
Priority to PCT/CN2019/075944 priority patent/WO2020168568A1/zh
Publication of WO2020168568A1 publication Critical patent/WO2020168568A1/zh

Links

Images

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

Definitions

  • This application relates to the field of Internet of Things, and more specifically, to a data processing method, device, electronic equipment, and readable storage medium.
  • Smart home is a residential platform, using integrated wiring technology, network communication technology, security technology, automatic control technology, audio and video technology to integrate the facilities related to home life to build an efficient management system for residential facilities and family schedule affairs, and improve Home safety, convenience, comfort, artistry, and to achieve an environmentally friendly and energy-saving living environment.
  • This application proposes a data processing method, device, electronic device, and readable storage medium to improve the aforementioned defects.
  • an embodiment of the present application provides a data processing method, which is applied to a quick application engine in an electronic device, the electronic device further includes a client, and the quick application engine includes multiple quick application pages.
  • the quick application page corresponds to at least one device.
  • the method includes: monitoring whether a startup instruction is obtained, the startup instruction is issued by the client according to an operation of a quick application control acting on the client interactive interface, and the startup instruction corresponds to the device; if When the startup instruction is obtained, the quick application page corresponding to the device is started; the data information input by the user based on the quick application page is obtained; the data information is sent to the manufacturer's server corresponding to the device.
  • an embodiment of the present application also provides a data processing method applied to an electronic device.
  • the electronic device includes a client and a quick application engine.
  • the quick application engine includes multiple quick application pages.
  • the quick application page corresponds to at least one device.
  • the method includes: the client obtains the operation input by the user, and determines the device identification corresponding to the operation; the client sends a startup instruction to the fast application engine, and the startup instruction corresponds to the device;
  • the quick application engine starts the quick application page corresponding to the device; the quick application engine obtains data information input by the user based on the quick application page; the quick application engine sends the data information to the manufacturer corresponding to the device server.
  • an embodiment of the present application also provides a data processing device, which is applied to a quick application engine in an electronic device, the electronic device further includes a client, and the quick application engine includes multiple quick application pages, each The quick application page corresponds to at least one device.
  • the data processing device includes: a monitoring unit, a starting unit, an acquiring unit, and a sending unit.
  • the monitoring unit is configured to monitor whether a startup instruction is acquired, the startup instruction is issued by the client according to an operation input by the user, and the startup instruction corresponds to the device.
  • the activation unit is configured to activate the quick application page corresponding to the device if the activation instruction is acquired.
  • the acquiring unit is configured to acquire data information input by the user based on the quick application page.
  • the sending unit is configured to send the data information to the vendor server corresponding to the device.
  • an embodiment of the present application also provides an electronic device, including: one or more processors; a memory; a fast application engine, the fast application engine includes a plurality of fast application pages, each of the fast application pages Corresponding to at least one device; client; one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the central processing unit, the one or more programs Configuration is used to perform the above method.
  • the embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores program code, and the program code can be invoked by a processor to execute the above method.
  • the quick application engine includes multiple quick application pages, and each of the quick application pages corresponds to at least one device, so that the quick application pages of multiple devices can be integrated on the same quick application to avoid installation
  • the plug-in corresponding to each device in addition, the user can send data to the server through the quick app.
  • the quick app engine starts the quick app page after detecting that the startup instruction is obtained, where the startup instruction is based on the client Acting on the operation of the quick application control in the client interactive interface, and the startup instruction corresponds to the device, the launched quick application page corresponds to the device. Then, the user can input data information on the quick app page and can be obtained by the quick app engine, then the quick app engine sends the data information to the vendor server corresponding to the device.
  • the user can send data to the vendor's server through a quick application page of the quick application engine, and if the quick application engine includes multiple quick application pages, the user can send data to the vendor servers corresponding to multiple devices through one quick application. Avoiding the installation of plug-ins for each device can not only reduce development costs, but also avoid insufficient space caused by excessive plug-ins installed in electronic devices.
  • FIG. 1 shows an application network environment diagram of a data processing method and device proposed in an embodiment of the present application
  • Figure 2 shows an application network environment diagram of a data processing method and device proposed by another embodiment of the present application
  • FIG. 3 shows a method flowchart of a data processing method provided by an embodiment of the present application
  • FIG. 4 shows a block diagram of a fast application engine provided by an embodiment of the present application
  • Figure 5 shows a schematic diagram of a quick application page provided by an embodiment of the present application
  • FIG. 6 shows a method flowchart of a data processing method provided by another embodiment of the present application.
  • FIG. 7 shows a schematic diagram of a data processing system corresponding to a data processing method provided by another embodiment of the present application.
  • FIG. 8 shows a schematic diagram of an interactive interface of a client provided by an embodiment of the present application.
  • FIG. 9 shows a method flowchart of a data processing method provided by another embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a client and a vendor server provided in an embodiment of the present application
  • FIG. 11 shows a schematic diagram of a data processing system corresponding to a data processing method provided by another embodiment of the present application.
  • FIG. 12 shows a schematic diagram of another data processing system corresponding to a data processing method provided by another embodiment of the present application
  • FIG. 13 shows a method flowchart of a data processing method provided by still another embodiment of the present application.
  • FIG. 14 shows a schematic diagram of a login interface of a client provided by an embodiment of the present application.
  • FIG. 15 shows a schematic diagram of a device adding interface of a client provided by an embodiment of the present application.
  • FIG. 16 shows a block diagram of a data processing device according to an embodiment of the present application.
  • FIG. 17 shows a block diagram of a data processing device according to another embodiment of the present application.
  • FIG. 18 shows a structural block diagram of an electronic device provided by an embodiment of the present application for executing the data processing method according to the embodiment of the present application
  • FIG. 19 shows a storage unit used to store or carry program code for implementing the data processing method according to the embodiment of the present 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".
  • IoT technology 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.
  • 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.
  • the electronic device 100 that plays a control role can realize data interaction with the controlled device 99 by directly establishing a wireless connection with the router.
  • the electronic device 100 may also realize data interaction with the controlled device 99 through the data link between the cloud and the router after establishing a connection with the cloud.
  • the controlled device 99 can establish a wireless connection with the router 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 to the mobile terminal or returning the instruction execution result.
  • the data interaction between the mobile terminal and the controlled device can be triggered by a client installed in the mobile terminal.
  • a client is installed in the electronic device 100, and the client may be an application corresponding to a certain device manufacturer, and can control multiple controlled devices corresponding to the device manufacturer.
  • the manufacturer’s product includes multiple devices, and the client can be used as a control architecture for multiple devices corresponding to the manufacturer, the control and interactive functions of each device need to install a plug-in for each device, as shown in Figure 1. As shown, assuming that the two controlled devices 99 are both from the same equipment manufacturer, they can be controlled by the client.
  • the two controlled devices 99 belong to different types of products, for example, one is a TV of brand x , One is a refrigerator of brand x, or different signal products of the same type, for example, one is a TV of brand x of m1 model, and the other is a TV of brand x of m2 model, in order to control two For devices, the plug-in corresponding to each device needs to be installed separately. As shown in Figures 1 and 2, the control plug-in 1 and the control plug-in 2 can respectively control two different controlled devices.
  • an embodiment of the present application provides a data processing method, as shown in FIG. 3, the method is applied to a quick application engine in an electronic device, the electronic device also includes a client, the quick application The engine includes multiple quick application pages, and each quick application page corresponds to at least one device. Specifically, the method includes: S301 to S304.
  • the start instruction is issued by the client according to the operation of the quick application control acting on the client interactive interface, and the start instruction corresponds to the device.
  • the operation is a confirmation instruction that a certain quick application is started, for example, it can be a touch operation.
  • the client interactive interface detects If the display area corresponding to a certain quick application control is touched, a start instruction corresponding to a touch operation will be obtained.
  • the operation may also be a mouse click operation or a selection instruction input by other input devices.
  • this operation is a touch operation.
  • 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.).
  • 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.
  • a client is installed in the electronic device, and the user can add the identification of the device through the client, and can also realize the network access operation of the device through the client.
  • the client includes an interactive interface that includes multiple fast Application controls, the user clicks on the quick application control to input a startup instruction, and each quick application control corresponds to a smart device, then the user clicks on the quick application control to obtain the startup instruction corresponding to the quick application control, and the startup instruction corresponds to one The identification of the device.
  • the device may be a smart device or a smart home.
  • the device can receive a control command input by a user and perform a response operation.
  • the smart home is an embodiment of the Internet of Things under the influence of the Internet.
  • Smart homes connect various devices in the home (such as audio and video equipment, lighting systems, curtain control, air conditioning control, security systems, digital cinema systems, audio and video servers, video cabinet systems, network appliances, etc.) through the Internet of Things technology to provide Home appliance control, lighting control, telephone remote control, indoor and outdoor remote control, anti-theft alarm, environmental monitoring, HVAC control, infrared forwarding and programmable timing control and other functions and methods.
  • smart homes not only have traditional residential functions, but also provide buildings, network communications, information appliances, and equipment automation, provide a full range of information interaction functions, and even save money for various energy costs.
  • the electronic device If the electronic device obtains the start instruction, it starts the quick application page corresponding to the device based on the start instruction.
  • the fast application page runs in the fast application engine.
  • the fast application engine can be used as an application program, which includes the data, architecture and operating environment of the fast application page, as well as some communication interfaces with other applications.
  • the identification of the device can be obtained by the electronic device, and the identification of the device can also be displayed in the designated interface of the client.
  • the background administrator of the client configures a fast
  • the identification of the application page means that the corresponding relationship between the device identification and the identification of the quick application page is stored in the electronic device, and the correspondence relationship includes multiple device identifications, and each device identification corresponds to an identification of the quick application page.
  • the quick application engine includes multiple quick application pages, and each quick application page corresponds to at least one device.
  • the identification of the quick application page corresponding to the device can be determined through the aforementioned correspondence, then after the startup instruction is obtained, the identification of the device corresponding to the startup instruction is determined, and then the quick application corresponding to the identification of the device is determined in the correspondence
  • the logo of the page is then displayed after rendering the page corresponding to the logo of the fast application page.
  • the quick application page can be used as the device page corresponding to the device, and the user can input data information such as control instructions through the device page.
  • data information such as control instructions through the device page.
  • the device is an air-conditioning device
  • Figure 5 what is shown in Figure 5 is the corresponding device page
  • the user can input control instructions for the air conditioner, such as mode switching, switch, temperature adjustment, etc., so that the quick application page
  • the application engine can obtain the data information entered by the user under the quick application page.
  • S304 Send the data information to the vendor server corresponding to the device.
  • Quick App can interact with the vendor's server to send data information to the vendor's server. Specifically, it can send data to the server corresponding to the link address through a link address, that is, the Quick App engine uses the link address corresponding to the vendor's server. Sending the data information to the server may be sending the data information to the server through the SDK corresponding to the manufacturer's server. Specifically, it will be described in the subsequent embodiments.
  • the data information can be some updated data.
  • the user can set some control modes of the device on the quick application page, that is, a scene, in which multiple business schemes can be linked, for example, the control page of the air conditioner shown above.
  • the user Under the control page of the air conditioner, the user can set an air conditioner scene.
  • the user sets a heating mode. In this heating mode, the air conditioner will turn on the heating mode and set the temperature to 30°C and keep it Run at 30°C with maximum air volume for 30 minutes, then at 30°C with automatic air volume for 20 minutes, then lower the temperature to 26°C and run at minimum air volume until the air conditioner is turned off. Then the series of control processes is the heating mode of the air conditioner.
  • the user sends a series of operation data in the heating mode to the corresponding manufacturer's server through the quick application, and the user only needs to click the startup instruction of the heating mode on the quick application page of the electronic device, and the manufacturer's server can follow the mode A series of instructions to control the air conditioner.
  • the updated data is the new data entered by the user when modifying the scene, which can be sent to the vendor's server through the quick application as data information.
  • the data information may also be a control instruction
  • the sending the data information to the manufacturer server corresponding to the device includes: sending the control instruction to the manufacturer server corresponding to the device to instruct the manufacturer server
  • the control instruction is sent to the device, and the device is controlled to perform an operation corresponding to the control instruction.
  • a temperature increase control command which carries the identification of the smart device and temperature control parameters, for example, the current temperature is 26 °C
  • the quick application sends the control command to the manufacturer’s server
  • the manufacturer server parses the control command to obtain the identification of the smart device and temperature control Parameter
  • the quick application page corresponds to a link address, such as a URL address, through which data information can be obtained and sent to the manufacturer's server.
  • FIG. 6 shows an embodiment of the present application
  • a data processing method is provided, which is applied to a quick application engine in an electronic device, the electronic device further includes a client, the quick application engine includes a plurality of quick application pages, and each of the quick application pages at least corresponds to A device.
  • the method includes: S601 to S607.
  • S602 Acquire a link address corresponding to the device.
  • the user connects the device to the network, that is, realizes the communication connection between the device and the manufacturer’s server, and then adds the identification of the device to the client.
  • the user is completing the network configuration of the device.
  • the management background configures a corresponding link address for the device.
  • the link address is the link address of the quick app, and the corresponding vendor server can be accessed according to the link address of the quick app.
  • the link address can be stored in the manufacturer's server or in the cloud server corresponding to the client.
  • the link address is stored in the cloud server, and the management backend can access the cloud server.
  • the identification of the device is stored in the cloud server and sent to the management backend, and the management backend is
  • the device configures a quick application link and sends it to the client. Specifically, it can send the quick application link corresponding to the device's identification to the cloud server, and then the cloud server sends it to the client, so that the client associates the link address with the device
  • the logo corresponds to the storage.
  • a quick application control is configured for the device.
  • the quick application control is used to receive the user's trigger operation, and the quick application control also corresponds to the quick application link address.
  • the quick application control can be a card, as shown in Figure 8, each card corresponds to a device, as shown in Figure 8, device 1, device 2, device 3, etc., can be the card's identification , It can also be the identification of the device.
  • the user can click on the card of the device 1 to obtain a touch operation on the device 1.
  • the touch operation can be used to open the control page corresponding to the device 1, or it can be executed Regarding other operations of the device 1, specifically, it can be set according to requirements.
  • the link address may be a URL address
  • the link address corresponds to a server.
  • the server may be a cloud server corresponding to the client, or a vendor server, and different device identifiers correspond to different link addresses, for example, If the link address is a URL address, the format of the address is aaaa.com/123, where aaaa.com is the address corresponding to the server, and /123 is the storage of the page data corresponding to the specific device identifier in the server position.
  • the link address corresponds to the manufacturer's server
  • the page data is stored in the manufacturer's server
  • the fast application engine can access the server through the link address, and obtain the page at the storage location of the manufacturer's server corresponding to the link address data.
  • S604 Obtain and display a quick application page based on the page data.
  • the page data is rendered into a quick application page and displayed. Specifically, after the user clicks on the card of the device 1 shown in Figure 8, the link address corresponding to the device 1 is obtained, and the device is accessed according to the link address 1 Corresponding manufacturer's server, and obtain the page data stored in the manufacturer's server, and then switch the current page in Figure 8 to the quick application page such as that shown in Figure 5, where the user can enter the data information of the control command in the quick application page .
  • S605 Acquire data information input by the user based on the quick application page.
  • S607 Send the data information to the vendor server corresponding to the link address according to the link address.
  • the fast application can directly access the manufacturer’s server.
  • the fast application shown in Figure 7 can be the fast application engine, that is, the fast application includes the fast application engine and the fast application page, and the fast application page runs in the fast application engine , The actual operation of sending data information is executed by the fast application engine.
  • the fast application engine accesses the vendor server through the link address, thereby sending data information to the vendor server.
  • the overall process is: the background administrator logs in to the management background, and configures the quick application link corresponding to each device model; when the user logs in to the smart home (or opens the mobile phone with a negative screen), the device list is pulled from the server (displayed in the form of a device card) , One card per device) and the quick application link corresponding to the device; the user clicks on the device card and enters the quick application page (ie, the device control page) according to the corresponding quick application link; the user sends a control command on the device control page to the device manufacturer’s server; The server of the device manufacturer issues the instruction to the device.
  • the client is bound to multiple SDK plug-ins, and each SDK plug-in corresponds to a vendor server.
  • the client can communicate with the corresponding vendor server through the SDK plug-in, and the fast app can communicate with the corresponding vendor server through the SDK plug-in.
  • Vendor server communication that is, data information is sent to vendor server through SDK plug-in.
  • Quick application includes quick application engine and multiple quick application pages corresponding to quick application engine. Then, specifically, please refer to FIG. 9, which shows that an embodiment of the present application provides a data processing method, which is applied to a quick application engine in an electronic device, the electronic device further includes a client, and the quick application The engine includes multiple quick application pages, and each quick application page corresponds to at least one device. Specifically, the method includes: S901 to S904.
  • S901 Monitor whether a start instruction is obtained.
  • S902 Start a quick application page corresponding to the device.
  • S903 Acquire data information input by the user based on the quick application page.
  • S904 Transmit a sending instruction to the client through a communication channel, the sending instruction carries data information, and the sending instruction is used to instruct the client to obtain the target SDK plug-in corresponding to the device, and pass the target SDK The plug-in sends the data information to the manufacturer's server.
  • each manufacturer will develop its own SDK plug-in for the client in the electronic device to call.
  • 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.
  • the client 110 shown in FIG. 10 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.
  • the data corresponding to the client can be sent to the server through the SDK plug-in or system collection component.
  • the SDK plug-in is installed in the client, bound with the client, and can be updated with the update of the client.
  • the function of the SDK plug-in is to provide an access interface for other applications to access the client's data, and it can also actively collect the client's data and send it to other clients or servers.
  • the SDK plug-in is bound to the client to collect and report data from the client.
  • the SDK plug-in determines whether the client meets the preset reporting conditions according to a preset strategy. For example, it may send the client's data to the system collection component at a preset interval. Specifically, when it is determined that the time interval between the current moment and the time point when the data was sent last time satisfies the preset interval, it is determined that the client meets the preset reporting condition.
  • the data of the client is sent to the system collection component. Specifically, obtain the data length of the data to be reported by the client at the current moment; determine whether the data length is greater than a preset length; if it is greater, determine that the client meets the preset reporting condition.
  • the electronic device has a local storage space for storing the client's to-be-reported data.
  • the to-be-reported data includes the client's operating data, for example, the startup or exit of the client, and also includes the user's operation behavior data for the client, for example, Close an interface or enter some information, etc.
  • the client's operating data for example, the startup or exit of the client
  • the user's operation behavior data for the client, for example, Close an interface or enter some information, etc.
  • multiple buried points are set in the client, each of which represents the user's operation behavior on the client or the running state of the client.
  • the startup of the client is used as a buried point, and the user opens a certain interface of the client As a buried point, and when these behaviors occur, that is, when the buried point is triggered, the corresponding data can be stored in the local storage space corresponding to the client, and the data to be reported as the client is stored locally.
  • the data in the data to be reported is related to the history of the SDK plug-in collecting and sending data from the client. For example, after the client is started, the generated data A is stored locally, and the SDK plug-in uses A as the data to be reported. Send to the system collection component, and then, as the client continues to run, data B is generated. The data in the client’s local storage space is A and B, but data A has been sent to the system collection component, then the data to be reported this time Is B.
  • a preset length is preset, where the data length can be the number of bytes of data, for example, 3M bytes, or the number of pieces of data, for example, 30.
  • the SDK plug-in can monitor the data length of the client's data to be reported in real time. For example, after the SDK plug-in sent the client data to the system collection component last time, the length of the data to be reported is 0. As the client runs, the data length of the data to be reported on the client gradually increases and accumulates. After setting the length, the SDK plug-in determines that the client meets the preset reporting conditions.
  • the SDK plug-in sent the client's data last time, after the data length of the data to be reported this time has accumulated to a certain length, the preset reporting conditions are met, and then the client's data to be reported can be sent to the system.
  • the operation of the acquisition component After the SDK plug-in sent the client's data last time, after the data length of the data to be reported this time has accumulated to a certain length, the preset reporting conditions are met, and then the client's data to be reported can be sent to the system. The operation of the acquisition component.
  • the status of the client includes running status, background status, and exit status.
  • the running status is running on the display interface of the electronic device. For example, if an activity of the application level is in the topmost state, it means that the client is running. When the user clicks home When the key or the lock screen key is pressed, the client enters the background state. At this time, the client runs in the background of the system. If the process of the client is completely killed, the client enters an exit state. When the client is switched from the running state to the background state, it means that the user may use the client for a period of time. That is to say, the data stored locally on the client may not change for a period of time. When entering the background, the client's data to be reported is reported, that is, after monitoring that the state of the client is switched from the running state to the background state, it is determined that the client meets the preset reporting conditions.
  • the aforementioned data to be reported is data information sent by the fast application to the client, and the data information calls the SDK plug-in to send the data information to the server corresponding to the SDK plug-in.
  • the fast application runs on the fast application engine, and an extended interface provided by the client is set in the fast application engine. And there is an expansion interface for communicating with the expansion interface in the client.
  • the client can call SDK plug-ins of various vendors through the extended interface. For example, the SDK plug-in of manufacturer A, the SDK plug-in of manufacturer B, and the SDK plug-in of manufacturer C in the figure can be called.
  • the data processing instructions triggered in the fast application can be transferred to the extended interface in the client through the expansion interface set in the fast application engine, and then the data processing instructions are transmitted to the SDK plug-ins of various manufacturers.
  • the fast application can implement calling multiple types of application programs or controlling devices of multiple manufacturers.
  • 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.
  • 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.
  • some software functions are encapsulated inside the SDK plug-in, and corresponding functions can be realized through the operation of the software functions.
  • the SDK plug-in will expose its interface so that the SDK plug-in can be called through the interface.
  • 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.
  • 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.
  • the different SDK plugins called in the client can also be SDK plugins belonging to different devices, or SDK plugins belonging to different applications.
  • 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.
  • 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.
  • 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.
  • the fast application engine After the fast application engine obtains the data information, it transmits the sending instruction to the client through the communication channel.
  • the client parses the sending instruction to obtain the data information, and finds the SDK plug-in corresponding to the device, and then the target SDK plug-in
  • the data information is sent to the manufacturer's server.
  • the communication channel may be a communication channel such as AIDL or Messenger.
  • the communication channel is an AIDL channel.
  • the sending instruction also carries the SDK identifier so that the client can determine which SDK to send the data information to.
  • the sending instruction also carries the fast application package name, and the sending instruction is also used to instruct the client based on the The quick application package name searches for the corresponding SDK plug-in, as the target SDK plug-in, and sends the data information to the vendor server through the target SDK plug-in.
  • Quick App will store the package name of the Quick App of the manufacturer, and then obtain the data processing instruction, and then according to the package extracted from the data processing instruction Name to identify the corresponding target SDK plugin.
  • the background administrator logs in to the management background and configures the quick application link corresponding to each device model.
  • the developer uploads the SDK on the developer platform.
  • the SDK corresponding to the manufacturer will be downloaded and loaded into Client.
  • the device is displayed in the form of a card.
  • the user controls the device, and the quick app sends the control command to the quick app engine through the interface ,
  • the fast application engine sends the control command to the client through the transparent transmission channel, and the client sends the control command to the device manufacturer’s SDK plugin through the standard interface implemented by the device manufacturer’s SDK plugin package, and then the SDK plugin sends the control command to the device
  • the vendor server issues instructions to the device, and the device executes the corresponding operation according to the control instruction.
  • the quick application engine is installed in the electronic device as an application program independent of the client. Specifically, the quick application engine is installed in the electronic device as an application program and interacts with the client In contrast, it is an independent application.
  • the fast application engine is installed in the client as a functional component of the client.
  • the program package corresponding to the fast application engine is embedded in the client. It can also be that after the user downloads the client, and when the client is successfully launched for the first time, the client will be The cloud server corresponding to the client downloads the fast application engine.
  • the fast application engine can be used as a functional component of the client after the download and installation is complete, that is, it belongs to the client.
  • FIG. 12 differs from FIG. 11 in that the fast application engine is installed at a different location, and for other embodiments, reference may be made to the description corresponding to FIG. 11.
  • FIG. 11 reference may be made to the foregoing embodiments, and details are not repeated here.
  • an embodiment of the present application also provides a data processing method applied to an electronic device.
  • the electronic device includes a client and a quick application engine.
  • the quick application engine includes multiple quick application pages.
  • the quick application page corresponds to at least one device.
  • this embodiment is the interaction between the fast application engine and the client, and the method includes: S1201 to S1205.
  • the client obtains the touch operation input by the user, and determines the device identifier corresponding to the touch operation.
  • the interactive interface of the client is provided with multiple quick application controls.
  • the interface is an implementation of the interactive interface of the client, and the cards displayed on the interface are those of the quick application space.
  • An implementation Specifically, refer to the description corresponding to FIG. 8 above.
  • multiple cards are provided on the interactive interface of the client, and each of them can be triggered by the user, that is, it can affect the user's touch operation. Then, after the client detects the touch operation on the interactive interface, Determine the quick application control corresponding to the touch operation.
  • each quick application control corresponds to a display position, and the corresponding display position and the identification of the quick application control (that is, the identification of the card) in the past Relationship, you can determine the quick application control corresponding to the past touch operation, that is, you can determine which card is triggered by the user, and since each card corresponds to a device ID, you can determine the device corresponding to the touch operation, that is, After acquiring the touch operation input by the user based on the quick application control, the client determines the target quick application control corresponding to the touch operation; according to the pre-acquired correspondence between the quick application control and the device identifier, finds the target The device ID corresponding to the quick application control.
  • the quick application control displayed on the interactive interface of the client can be obtained from the cloud server corresponding to the client.
  • the management background configures a quick application control for the device, which can be integrated into the existing
  • the newly added device has the same function as the added device, that is, products of different models of the same type, or products of the same model of the same type. It can also configure a new quick application control for the newly added device.
  • the configured quick application control is stored in the cloud server and stored in correspondence with the identification of the device.
  • the client enters a certain page, obtains the display list of quick application controls from the cloud server, and displays it on the designated page of the client.
  • the method further includes: the client judging whether the current interface is a designated interface If it is a designated interface, the cloud server obtains a quick application control display list, the quick application control display list includes multiple quick application controls; the quick application control display list is displayed on the designated interface.
  • the designated interface may be the main interface displayed after the user logs in to the client.
  • FIG. 14 shows the login interface of the client, and the main interface after the login of the client may be the interactive interface shown in FIG. 8, that is, the main interface and the above-mentioned interactive interface may be the same interface.
  • the client After the user logs in the user name in the login interface, and after successfully logging in, the client sends a list acquisition request to the cloud server, and the acquisition request includes the user name.
  • the quick application control stored in the cloud server is not only compatible with
  • the device identification is stored correspondingly, and stored corresponding to the user name, that is, the quick application controls corresponding to multiple devices added under a user name can be correspondingly stored, and the cloud server parses the acquisition request to obtain the user name, and then according to the user name Find the corresponding quick application control by name, use the multiple quick application controls found as the quick application control list, and send the quick application control list to the client, and the client will display the quick application control list, as shown in Figure 8. Of multiple cards.
  • the instruction interface can also be a negative one-screen interface.
  • the negative one-screen interface is an interface called up by swiping gestures from the left user under the main interface after the user has successfully logged in.
  • the cloud server obtains multiple quick application controls corresponding to the user name and displays them on the one-screen negative interface.
  • S1202 The client sends a startup instruction to the fast application engine, where the startup instruction corresponds to the device.
  • S1203 The quick application engine starts the quick application page corresponding to the device based on the start instruction.
  • the quick application engine obtains data information input by the user based on the quick application page.
  • the fast application engine sends the data information to the vendor server corresponding to the device.
  • the fast application engine transmits a sending instruction to the client through a communication channel, and the sending instruction carries data information; the client obtains the target SDK plug-in corresponding to the device; The target SDK plug-in sends the data information to the vendor server.
  • the specific implementation manner for the client to send data information to the vendor server through the target SDK plug-in may be that the client obtains the data encapsulation protocol corresponding to the vendor server; encapsulates the data information according to the data encapsulation protocol Into a data packet; sending the data packet to the vendor server through the target SDK plug-in.
  • the data encapsulation protocol is an agreement between the manufacturer’s server and the client, and the specific encapsulation algorithm is embedded in the SDK plugin.
  • the SDK plugin includes an encapsulation interface, and the encapsulation interface includes an algorithm corresponding to the data encapsulation protocol.
  • the module can encapsulate the data to be sent through the interface according to the algorithm module.
  • the client sends the data information to the SDK plug-in, the SDK plug-in encapsulates the data information into a data packet through the encapsulation interface, and sends the data packet to the vendor server through the target SDK plug-in.
  • the quick application can send data information to the manufacturer’s server through the link address, or it can send the data information to the manufacturer’s server through the SDK plug-in corresponding to the manufacturer’s server.
  • what method is used to send the data information Send it to the manufacturer’s server, and it can be the transmission method corresponding to the quick application page.
  • the quick application engine determines the package name of the quick application page, and then determines the determined quick application based on the preset correspondence between the package name of the quick application page and the transmission mode
  • the transmission method corresponding to the package name of the page is the first method or the second method, where the first method is to send the data information to the vendor server corresponding to the link address according to the link address, and the second method is through communication
  • the channel transmits a sending instruction to the client, the sending instruction carries data information, and the sending instruction is used to instruct the client to obtain the target SDK plug-in corresponding to the device, and transmit the data information through the target SDK plug-in Send to the manufacturer's server.
  • the fast application engine sends the data information to the vendor server corresponding to the link address according to the link address. If it is the second method, the fast application engine transmits the sending instruction to the client through the communication channel, and the sending instruction carries data information; the client obtains the target SDK plug-in corresponding to the device; The client sends data information to the vendor server through the target SDK plug-in.
  • each device corresponds to a transmission method
  • the transmission method is configured for the device after the user adds the device, or it can be configured by the management background
  • the identity of each device corresponds to the transmission method Store in the cloud server.
  • the fast application obtains the data information input by the user, it sends a query instruction to the cloud server.
  • the query instruction includes the identification of the device.
  • the cloud server parses the query instruction to obtain the identification of the device, and searches for the query instruction.
  • the transmission mode corresponding to the device ID, and the transmission mode is sent to the fast application engine, the fast application engine determines whether the transmission mode is the first mode or the second mode, and if it is the first mode, the fast application engine will send all data according to the link address.
  • the data information is sent to the vendor server corresponding to the link address. If it is the second method, the fast application engine transmits the sending instruction to the client through the communication channel, and the sending instruction carries data information; the client obtains the target SDK plug-in corresponding to the device; The client sends data information to the vendor server through the target SDK plug-in.
  • the SDK plug-in may be downloaded by the user after adding the device. Specifically, before the client obtains the target SDK plug-in corresponding to the device, it also includes: when the client obtains the identification of the device in the device addition page , Download and store the SDK plug-in corresponding to the device's identification.
  • the device addition page of the client is shown, in which the user adds the purchased device, and then the management background configures a quick application control for the device, that is, the device card, and then downloads the device
  • Corresponding SDK plug-in specifically, first determine whether the device's SDK plug-in is stored locally, specifically, obtain the device's identification to determine the identification of the SDK plug-in corresponding to the device's identification, and determine whether it is in the local storage space
  • the SDK plug-in identifier is included. If not included, the SDK plug-in is downloaded from the manufacturer’s server. Specifically, the client sends a download request to the cloud server.
  • the download request includes the device identifier, and the cloud server obtains the download After the request, the download request is parsed to obtain the identification of the device, and the manufacturer of the device identification is determined, and then the manufacturer server corresponding to the manufacturer downloads the SDK plug-in corresponding to the identification of the device and sends it to the client.
  • the client obtains the SDK Plug-in and install.
  • FIG. 12 differs from FIG. 11 in that the fast application engine is installed at a different location, and for other embodiments, reference may be made to the description corresponding to FIG. 11.
  • FIG. 11 reference may be made to the foregoing embodiments, and details are not repeated here.
  • FIG. 16 shows a structural block diagram of a data processing apparatus 1500 provided by an embodiment of the present application.
  • the data processing device 1500 may include: a monitoring unit 1501, a starting unit 1502, an acquiring unit 1503, and a sending unit 1504.
  • the monitoring unit 1501 is configured to monitor whether a startup instruction is obtained, the startup instruction is issued by the client according to a touch operation input by a user, and the startup instruction corresponds to the device.
  • the activation unit 1502 is configured to activate the quick application page corresponding to the device if the activation instruction is acquired.
  • the activation unit 1502 is configured to obtain a link address corresponding to the device; obtain page data according to the link address; obtain and display a quick application page based on the page data.
  • the obtaining unit 1503 is configured to obtain data information input by the user based on the quick application page.
  • the sending unit 1504 is configured to send the data information to the vendor server corresponding to the device.
  • the sending unit 1504 is further configured to obtain a link address corresponding to the device; and send the data information to the vendor server corresponding to the link address according to the link address.
  • the sending unit 1504 is further configured to transmit a sending instruction to the client through a communication channel, the sending instruction carries data information, and the sending instruction is used to instruct the client to acquire the device
  • the corresponding target SDK plug-in sends data information to the vendor server through the target SDK plug-in.
  • the communication channel is an AIDL channel.
  • the sending instruction also carries a quick application package name, and the sending instruction is also used to instruct the client to search for the corresponding SDK plug-in based on the quick application package name, as the target SDK plug-in, through the target SDK
  • the plug-in sends the data information to the manufacturer's server.
  • the sending unit 1504 is further configured to send the control instruction to the manufacturer server corresponding to the device, instruct the manufacturer server to send the control instruction to the device, and control the device to execute the control instruction The corresponding operation.
  • the quick application engine is installed in the client as a functional component of the client.
  • the quick application engine is installed in the electronic device as an application program independent of the client.
  • FIG. 17 shows a structural block diagram of a data processing apparatus 1600 provided by an embodiment of the present application.
  • the data processing device 1600 may include: a first acquiring unit 1601, an instruction sending unit 1602, a starting unit 1603, a second acquiring unit 1604, and a data sending unit 1605.
  • the first acquiring unit 1601, the instruction sending unit 1602 are located in the client, and the starting unit 1603, the second acquiring unit 1604, and the data sending unit 1605 are located in the fast application engine.
  • the first obtaining unit 1601 is configured to obtain a touch operation input by a user, and determine a device identifier corresponding to the touch operation.
  • the first obtaining unit 1601 is further configured to, after obtaining the touch operation input by the user based on the quick app control, determine the target quick app control corresponding to the touch operation; according to the pre-acquired correspondence between the quick app control and the device identifier Relationship, search for the device identification corresponding to the target fast application control.
  • the first acquiring unit 1601 is used to determine whether the current interface is a designated interface; if it is a designated interface, the cloud server acquires a quick application control display list, where the quick application control display list includes multiple quick application controls; The fast application control display list is displayed on the specified interface.
  • the designated interface is a main interface displayed after the user logs in to the client. It may also be that the designated interface is a negative one-screen interface of the client.
  • the instruction sending unit 1602 is configured to send a startup instruction to the fast application engine, and the startup instruction corresponds to the device.
  • the activation unit 1603 is configured to activate the quick application page corresponding to the device based on the activation instruction.
  • the second obtaining unit 1604 is configured to obtain data information input by the user based on the quick application page.
  • the data sending unit 1605 is configured to send the data information to the vendor server corresponding to the device.
  • the data sending unit 1605 is further configured to transmit a sending instruction to the client through a communication channel, and the sending instruction carries data information.
  • the client obtains the target SDK plug-in corresponding to the device; the client sends data information to the vendor server through the target SDK plug-in.
  • the client obtains the data encapsulation protocol corresponding to the manufacturer server; encapsulates the data information into a data packet according to the data encapsulation protocol; and sends the data packet to the manufacturer server through the target SDK plug-in.
  • it also includes a downloading unit, which is used to download and store the SDK plug-in corresponding to the device's identity when the client terminal obtains the device's identity in the device adding page.
  • the coupling between the modules may be electrical, mechanical or other forms of coupling.
  • each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • the electronic device 100 may be an electronic device capable of running application programs, such as a smart phone, a tablet computer, or an e-book.
  • the electronic device 100 in this application may include one or more of the following components: a processor 110, a memory 120, a fast application engine 112, a client 113, and one or more application programs, of which one or more application programs may be stored in
  • the memory 120 is configured to be executed by one or more processors 110, and one or more programs are configured to execute the methods described in the foregoing method embodiments.
  • the fast application engine 112 and the client 113 can refer to the above-mentioned embodiments.
  • the processor 110 may include one or more processing cores.
  • the processor 110 uses various interfaces and lines to connect various parts of the entire electronic device 100, and executes by running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and calling data stored in the memory 120.
  • Various functions and processing data of the electronic device 100 may adopt at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), and Programmable Logic Array (Programmable Logic Array, PLA).
  • DSP Digital Signal Processing
  • FPGA Field-Programmable Gate Array
  • PLA Programmable Logic Array
  • the processor 110 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem.
  • 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 110, but may be implemented by a communication chip alone.
  • the memory 120 may include random access memory (RAM) or read-only memory (Read-Only Memory).
  • the memory 120 may be used to store instructions, programs, codes, code sets or instruction sets.
  • the memory 120 may include a program storage area and a data storage area, where the program storage 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 storage data area can also store data created by the electronic device 100 during use (such as phone book, audio and video data, chat record data) and the like.
  • FIG. 19 shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application.
  • the computer-readable storage medium 1800 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 1800 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM.
  • the computer-readable storage medium 1800 includes a non-transitory computer-readable storage medium.
  • the computer-readable storage medium 1800 has storage space for the program code 1810 for executing any method steps in the above methods. These program codes can be read out from or written into one or more computer program products.
  • the program code 1810 may be compressed in a suitable form, for example.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供了一种数据处理方法、装置、电子设备及可读存储介质，涉及物联网领域。该方法包括：监测是否获取到启动指令，启动指令为客户端根据作用于客户端交互界面中的快应用控件的触控操作所发出的，且启动指令与设备对应；若获取到启动指令，则启动与设备对应的快应用页面；获取用户基于快应用页面输入的数据信息；将数据信息发送至设备对应的厂商服务器。快应用引擎包括多个快应用页面，每个快应用页面至少对应一个设备。用户能够通过快应用引擎的一个快应用页面发送数据至厂商服务器，并且，快应用引擎包括多个快应用页面，能够避免安装每个设备的插件，既能够减少开发成本，也能够避免电子设备内安装过度插件而导致空间不足。

Description

数据处理方法、装置、电子设备及可读存储介质 技术领域
本申请涉及物联网领域，更具体地，涉及一种数据处理方法、装置、电子设备及可读存储介质。
背景技术
智能家居是以住宅为平台，利用综合布线技术、网络通信技术、安全防范技术、自动控制技术、音视频技术将家居生活有关的设施集成，构建高效的住宅设施与家庭日程事务的管理***，提升家居安全性、便利性、舒适性、艺术性，并实现环保节能的居住环境。
目前，用户通过安装有控制智能设备的应用程序的移动终端对智能设备进行统一管理，但是，开发者需要针对每个型号的设备开发原生插件，而用户在使用时需要针对不同型号的设备下载对应的原生插件，开发成本高且用户如果有多个不同型号的智能设备则需要下载多个原生插件，过多占用电子设备的存储空间，使得用户体验不高。
发明内容
本申请提出了一种数据处理方法、装置、电子设备及可读存储介质，以改善上述缺陷。
第一方面，本申请实施例提供了一种数据处理方法，应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。该方法包括：监测是否获取到启动指令，所述启动指令为所述客户端根据作用于客户端交互界面中的快应用控件的操作所发出的，且所述启动指令与所述设备对应；若获取到所述启动指令，则启动与所述设备对应的快应用页面；获取用户基于所述快应用页面输入的数据信息；将所述数据信息发送至所述设备对应的厂商服务器。
第二方面，本申请实施例还提供了一种数据处理方法，应用于电子设备，所述电子设备包括客户端和快应用引擎，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。该方法包括：所述客户端获取用户输入的操作，并确定所述操作对应的设备标识；所述客户端发送启动指令至所述快应用引擎，所述启动指令与所述设备对应；所述快应用引擎启动与所述设备对应的快应用页面；所述快应用引擎获取用户基于所述快应用页面输入的数据信息；所述快应用引擎将所述数据信息发送至所述设备对应的厂商服务器。
第三方面，本申请实施例还提供了一种数据处理装置，应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。数据处理装置包括：监测单元、启动单元、获取单元和发送单元。监测单元，用于监测是否获取到启动指令，所述启动指令为所述客户端根据用户输入的操作所发出的，且所述启动指令与所述设备对应。启动单元，用于若获取到启动指令，则启动与所述设备对应的快应用页面。获取单元，用于获取用户基于所述快应用页面输入的数据信息。发送单元，用于将所述数据信息发送至所述设备对应的厂商服务器。
第四方面，本申请实施例还提供了一种电子设备，包括：一个或多个处理器；存储器；快应用引擎，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少 对应一个设备；客户端；一个或多个应用程序，其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述中央处理器执行，所述一个或多个程序配置用于执行上述方法。
第五方面，本申请实施例还提供了一种计算机可读取存储介质，计算机可读取存储介质中存储有程序代码，所述程序代码可被处理器调用执行上述方法。
本申请提供的方案中，快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备，由此能够将多个设备的快应用页面集成在同一个快应用上而避免安装每个设备对应的插件，另外，用户能够通过快应用发送数据至服务器，具体地，快应用引擎在监测到获取到启动指令之后，将快应用页面启动，其中，启动指令为所述客户端根据作用于客户端交互界面中的快应用控件的操作所发出的，且所述启动指令与所述设备对应，则所启动的快应用页面与设备对应。然后，用户可以在快应用页面输入数据信息，并且能够被快应用引擎获取到，则快应用引擎将所述数据信息发送至所述设备对应的厂商服务器。因此，用户能够通过快应用引擎的一个快应用页面发送数据至厂商服务器，并且，快应用引擎包括多个快应用页面，则用户能够通过一个快应用向多个设备对应的厂商服务器发送数据，能够避免安装每个设备的插件，既能够减少开发成本，也能够避免电子设备内安装过度插件而导致空间不足。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了本申请一实施例提出的一种数据处理方法及装置的应用网络环境图；
图2示出了本申请另一实施例提出的一种数据处理方法及装置的应用网络环境图；
图3示出了本申请一实施例提供的一种数据处理方法的方法流程图；
图4示出了本申请实施例提供的快应用引擎的模块框图；
图5示出了本申请实施例提供的快应用页面的示意图；
图6示出了本申请另一实施例提供的一种数据处理方法的方法流程图；
图7示出了本申请另一实施例提供的数据处理方法对应的数据处理***的示意图；
图8示出了本申请实施例提供的客户端的交互界面的示意图；
图9示出了本申请又一实施例提供的一种数据处理方法的方法流程图；
图10示出了本申请实施例提供的客户端与厂商服务器的示意图；
图11示出了本申请又一实施例提供的一种数据处理方法的对应的数据处理***的示意图；
图12示出了本申请又一实施例提供的一种数据处理方法的对应的另一数据处理***的示意图
图13示出了本申请再又一实施例提供的一种数据处理方法的方法流程图；
图14示出了本申请实施例提供的客户端的登录界面的示意图；
图15示出了本申请实施例提供的客户端的设备添加界面的示意图；
图16示出了本申请一实施例提供的一种数据处理装置的模块框图；
图17示出了本申请另一实施例提供的一种数据处理装置的模块框图；
图18示出了本申请实施例提供的用于执行根据本申请实施例的数据处理方法的电子设备的结构框图；
图19示出了本申请实施例的用于保存或者携带实现根据本申请实施例的数据处理方法的程序代码的存储单元。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
物联网是在“互联网概念”的基础上，将其用户端延伸和扩展到任何物品与物品之间，进行信息交换和通信的一种网络概念。随着物联网技术的发展，在物联网***中可以配置一些场景。对于配置的场景，可以涉及到多个受控设备，而且多个受控设备之间具有一定的联动关系，能够协同工作。
其中，受控设备可以为投影仪、投屏幕、智能灯、智能插座、人体传感器、门窗传感器、无线开关、空调伴侣、烟雾报警器、智能窗帘电机、以及空气净化器、智能音箱等移动终端。在一种方式中，如图1所示，起控制作用的电子设备100可以通过直接与路由器建立无线连接的方式实现与受控设备99之间进行数据交互。再者，电子设备100也可以通过与云端建立连接后，通过云端与路由器之间的数据链路实现与受控设备99之间的数据交互。而作为另外一种方式，如图2所示，受控设备99可以通过网关98与路由器建立无线连接。其中，数据交互可以包括移动终端向受控设备发送控制指令，还可以包括受控设备向移动终端返回状态信息或者返回指令执行结果等。其中，移动终端与受控设备之间的数据交互可以由移动终端中安装的客户端来触发。
具体地，电子设备100内安装有客户端，该客户端可以是对应某个设备厂商的应用程序，能够控制该设备厂商对应的多个受控设备。另外，由于厂商的产品包括多个设备，而该客户端可以作为该厂商对应的多个设备的一个控制架构，而针对每个设备的控制以及交互功能需要安装每个设备的插件，如图1所示，假设两个受控设备99都是来在一个设备厂商，则均可以通过客户端控制，但是，由于两个受控设备99属于不同类型的产品，例如，一个是x品牌的电视机，一个是x品牌的电冰箱，或者属于同一个类型的不同信号产品的，例如，一个是x品牌的m1型号的电视机，另一个是x品牌的m2型号的电视机，则为了控制两个设备，需要分别安装每个设备对应的插件，如图1和2所示，可以是控制插件1和控制插件2分别控制两个不同的受控设备。
但是，发明人在研究中发现，上述的一个控制插件对应一个受控设备的方式，会造成开发成本高以及用户操作复杂的缺陷，具体地，开发者需要为每个型号的智能设备开发原生插件，开发成本高；而用户如果有多个不同型号的智能设备则需要下载多个原生插件，并且原生插件包比较大，这样针对每个设备型号，在进入控制页面之前都要等待原生插件下载完成，操作不流畅，用户体验不友好。
因此，为了克服上述缺陷，本申请实施例提供了一种数据处理方法，如图3所示，该方法应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。具体地，该方法包括：S301至S304。
S301：监测是否获取到启动指令。
其中，所述启动指令为所述客户端根据作用于客户端交互界面中的快应用控件的操作所发出的，且所述启动指令与所述设备对应。
其中，该操作为某个快应用被启动的确认指令，例如，可以是一个触控操作，例如，用户点击客户端交互界面中的快应用控件，则该点击操作下，客户端交互界面检测到某个快应用控件对应的显示区域被触控，则将获取到一个触控操作对应的启动指令。
另外，该操作也可以是鼠标的点击操作或者其他的输入设备输入的选中指令。
于本申请实施例中，该操作为触控操作。
其中，快应用是一种基于终端设备硬件平台的新型应用形态，无需安装，即点即用，又兼具原生应用体验(性能、***整合、交互等)。如图4所示的快应用引擎的结构示意图，快应用的前端设计借鉴并整合了主流前端框架(Vue，React等)的设计思路：以组件化的方式构建应用，以数据绑定为核心的MVVM设计模式，以V-DOM的方式提升性能，同时选择了简洁清晰的类Vue的模板。
另外，电子设备内安装有客户端，用户能够通过该客户端添加设备的标识，并且也能够通过该客户端实现设备的入网操作，客户端包括一个交互界面，在该交互界面内包括多个快应用控件，用户点击该快应用控件能够输入启动指令，并且每个快应用控件对应一个智能设备，则用户点击该快应用控件就能够获取该快应用控件对应的启动指令，且该启动指令对应一个设备的标识。
其中，设备可以是智能设备或者智能家居，具体地，该设备能够接收用户输入的控制指令而执行响应的操作，智能家居是在互联网影响之下物联化的体现。智能家居通过物联网技术将家中的各种设备(如音视频设备、照明***、窗帘控制、空调控制、安防***、数字影院***、影音服务器、影柜***、网络家电等)连接到一起，提供家电控制、照明控制、电话远程控制、室内外遥控、防盗报警、环境监测、暖通控制、红外转发以及可编程定时控制等多种功能和手段。与普通家居相比，智能家居不仅具有传统的居住功能，兼备建筑、网络通信、信息家电、设备自动化，提供全方位的信息交互功能，甚至为各种能源费用节约资金。
S302：启动与所述设备对应的快应用页面。
如果电子设备获取到启动指令，则基于该启动指令启动与所述设备对应的快应用页面。而快应用页面在快应用引擎内运行，该快应用引擎可以作为一个应用程序，其内包括运行快应用页面的数据、架构和运行环境，以及一些与其他应用程序通信的接口。
作为一种实施方式，用户在添加设备之后，该设备的标识就能够被电子设备获取，并且还可以在客户端的指定界面内显示该设备的标识，则客户端的后台管理员为该设备配置一个快应用页面的标识，即在电子设备内存储有设备标识与快应用页面的标识的对应关系，该对应关系内包括多个设备标识，且每个设备标识对应一个快应用页面的标识。作为一种实施方式，快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备，具体地，一个品牌下具有相同功能(可能是不同型号)的设备使用同一个快应用页面，通过前述对应关系能够确定设备对应的快应用页面的标识，则在获取到启动指令之后，确定该启动指令对应的设备的标识，再在该对应关系中确定该设备的标识对应的快应用页面的标识，然后，在将该快应用页面的标识对应的页面渲染之后显示。
S303：获取用户基于所述快应用页面输入的数据信息。
其中，快应用页面可以作为设备对应的设备页面，用户能够通过该设备页面输入控制指令等数据信息，如图5所示，假设设备为空调设备，则图5所显示的为该空调设备对应的快应用页面，则该快应用页面内显示有多个数据输入控件，则在该快应用页面下，用户能够输入针对该空调的控制指令，例如，模式切换、开关、温度调节等，从而，快应用引擎就能够获取到用户在该快应用页面下输入的数据信息。
S304：将所述数据信息发送至所述设备对应的厂商服务器。
快应用能够与厂商服务器之间交互，从而将数据信息发送至厂商服务器，具体地，可以是通过一个链接地址将数据发送至该链接地址对应的服务器，即快应用引擎通过厂商服务器对应的链接地址将数据信息发送至服务器，可以是通过厂商服务器对应的SDK将数据信息发送至服务器，具体地，在后续的实施例中介绍。
其中，数据信息可以是一些更新数据，例如，用户能够在快应用页面设置设备的一些控制模式，即场景，在该场景下能够联动多个业务方案，例如，上述所示的空调 的控制页面，在该空调的控制页面下，用户能够设定一个空调的场景，例如，用户设定一个取暖模式，在该取暖模式下，空调会开启加热模式，并且会将温度设定到30℃，并且保持在30℃的温度下，以最大的风量运行30分钟，然后，再以30℃的温度下以自动风量运行20分钟，然后再将温度下降到26℃，并且最小风量运行，直至空调被关闭，则该一系列控制过程就是空调的取暖模式。而用户通过快应用将该取暖模式下的一系列操作数据发送至空调对应的厂商服务器，而用户只需要在电子设备的快应用页面点击该取暖模式的启动指令，就厂商服务器就能够根据该模式下的一系列指令去控制空调。
而更新数据为用户在修改场景的时候，所输入的新的数据，则作为数据信息可以通过快应用发送至厂商服务器。
另外，所述数据信息还可以是控制指令，所述将所述数据信息发送至所述设备对应的厂商服务器包括：将所述控制指令发送至所述设备对应的厂商服务器，指示所示厂商服务器将所述控制指令发送至所述设备，并控制所述设备执行与所述控制指令对应的操作。
以上述的空调举例，用户在空调对应的快应用页面点击温度增加按钮，则输入一个温度升高的控制指令，该控制指令携带有智能设备的标识以及温度调控参数，例如，当前的温度为26℃，在用户点击一下温度增加按钮，温度升高1℃，则温度调控参数+1℃，快应用将控制指令发送至厂商服务器，厂商服务器解析该控制指令，以获得智能设备的标识以及温度调控参数，将控制指令发送至智能设备的标识对应的智能设备，智能设备获得该温度调控参数，依据该温度调控参数调节设备的温度，例如，将温度升高1℃。
作为一种实施方式，快应用页面对应一个链接地址，例如是一个URL地址，则通过该链接地址能够获取将数据信息发送至厂商服务器，具体地，请参阅图6，示出了本申请实施例提供了一种数据处理方法，该方法应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。具体地，该方法包括：S601至S607。
S601：监测是否获取到启动指令。
S602：获取所述设备对应的链接地址。
具体地，用户在获取到设备之后，将设备入网，即实现设备与厂商服务器之间的通信连接，然后，将设备的标识添加至客户端，如图7所示，用户在完成设备的配网的时候，管理后台为设备配置一个对应的链接地址，该链接地址为快应用的链接地址，能够依据该快应用的链接地址访问对应的厂商服务器。该链接地址可以存储在厂商服务器内，也可以存储在客户端对应的云服务器内。
作为一种实施方式，该链接地址存储在云服务器，管理后台能够访问云服务器，则在用户添加了设备之后，该设备的标识存储在云服务器内，并且下发给管理后台，而管理后台为设备配置一个快应用链接并发送至客户端，具体地，可以是将设备的标识所对应的快应用链接发送至云服务器，再由云服务器下发至客户端，从而客户端将链接地址与设备的标识对应存储。
然后，用户在客户端内添加设备的时候，为该设备配置一个快应用控件，该快应用控件用于接收用户的触发操作，并且该快应用控件也对应该快应用链接地址。作为一种实施方式，该快应用控件可以是一个卡片，如图8所示，每个卡片对应一个设备，如图8所示的设备1、设备2、设备3等等，可以是卡片的标识，也可以是设备的标识，用户点击该设备1的卡片就能够获取很对该设备1的触控操作，则该触控操作可以是用于将设备1对应的控制页面打开，也可以是执行关于设备1的其他操作，具体地，可以根据 需求而设定。
S603：根据所述链接地址获取页面数据。
其中，链接地址可以是一个URL地址，该链接地址对应一个服务器，具体地，该服务器可以是客户端对应的云服务器，也可以是厂商服务器，则不同的设备标识对应不同的链接地址，例如，该链接地址为一个URL地址，则该地址的格式为aaaa.com/123,其中，aaaa.com为服务器对应的地址，而/123为具体的该设备的标识对应的页面数据在服务器内的存储位置。
作为一种实施方式，该链接地址对应厂商服务器，而该页面数据存储在厂商服务器内，快应用引擎能够通过该链接地址访问服务器，并且在该链接地址对应的厂商服务器的存储位置处获取该页面数据。
S604：基于所述页面数据获得快应用页面并显示。
在获取到页面数据后，将该页面数据渲染成快应用页面并显示，具体地，用户点击图8所示的设备1的卡片之后，获取该设备1对应的链接地址，并且根据链接地址访问设备1对应的厂商服务器，并获取厂商服务器所存储的页面数据，然后，将当前图8的页面切换到诸如图5所示的快应用页面，用户能够在该快应用页面内输入控制指令的数据信息。
S605：获取用户基于所述快应用页面输入的数据信息。
S607：根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器。
如图7所示，快应用能够直接访问厂商服务器，图7中所示的快应用可以是快应用引擎，即快应用包括快应用引擎和快应用页面，而快应用页面在快应用引擎内运行，则实际发送数据信息的操作由快应用引擎执行。作为一种实施方式，与上述获取页面数据的方式，快应用引擎通过链接地址访问厂商服务器，从而将数据信息发送至厂商服务器。
则整体流程为：后台管理员登陆管理后台，配置每个设备型号对应的快应用链接；用户登陆智能家居(或打开手机负一屏)时，从服务端拉取设备列表(以设备卡片形式展示，一个设备一个卡片)及设备对应的快应用链接；用户点击设备卡片，根据对应的快应用链接进入快应用页面(即设备控制页面)；用户在设备控制页面发送控制指令传到设备厂商服务器；设备厂商服务器将指令下发到设备。
因此，通过链接地址直接将数据信息发送至厂商服务器的方式，更加方便而且更加高效，但是，数据的隐秘性不高，而针对一些需要通过私有协议传输数据的厂商，需要通过SDK组件传输数据信息，具体地，在后续实施例中介绍。
需要说明的是，上述步骤中未详细描述的部分，可参考前述实施例，在此不再赘述
另外，客户端绑定了多个SDK插件，而每个SDK插件对应一个厂商服务器，客户端能够通过该SDK插件与所对应的厂商服务器通信，则快应用可以通过客户端所绑定的SDK与厂商服务器通信，即将数据信息通过SDK插件发送至厂商服务器，其中，快应用包括快应用引擎以及快应用引擎对应的多个快应用页面。则，具体地，请参阅图9，示出了本申请实施例提供了一种数据处理方法，该方法应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。具体地，该方法包括：S901至S904。
S901：监测是否获取到启动指令。
S902：启动与所述设备对应的快应用页面。
S903：获取用户基于所述快应用页面输入的数据信息。
S904：通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息，所述发送指令用于指示所述客户端获取所述设备对应的目标SDK插件，通过所述目标SDK插件将数据信息发送至厂商服务器。
为了便于进行数据的交互，各个厂商都会各自开发自己的SDK插件以便电子设备中的客户端调用。当客户端加载厂商的SDK插件以后，便可以调用所加载的SDK插件，进而通过该SDK插件与厂商的服务器之间进行数据交互。例如，如图10所示，在图10所示的客户端110中加载有厂商A的SDK插件111以及厂商B的SDK插件112，其中客户端110可以通过调用厂商A的SDK插件来与厂商A的服务器210进行数据交互，而客户端110可以通过调用厂商B的SDK插件来与厂商B的服务器220进行数据交互。
具体地，客户端对应的数据可以通过SDK插件或***采集组件发送至服务器。
其中，SDK插件安装在客户端内，与客户端绑定，并且可以随客户端的更新而更新。SDK插件的作用是为其他应用程序访问客户端的数据而提供访问接口，也可以主动采集客户端的数据并发送至其他客户端或服务器。
SDK插件与客户端绑定，用于采集客户端的数据并上报。SDK插件根据预设的策略判断客户端是否满足预设上报条件，例如，可以是按照预设间隔时间将客户端的数据发送至***采集组件。具体地，在判定当前时刻与在上次发送数据的时间点之间的时间间隔满足预设间隔时，就判定客户端满足预设上报条件。
还可以是，在客户端的待上报数据的数据长度满足一定值时，将客户端的数据发送至***采集组件。具体地，获取当前时刻所述客户端的待上报数据的数据长度；判断所述数据长度是否大于预设长度；若大于，判定客户端满足预设上报条件。
电子设备内设有本地存储空间，用于存储客户端的待上报数据，其中，待上报数据包括客户端的运行数据，例如，客户端的启动或退出等，还包括用户针对客户端的操作行为数据，例如，关闭某个界面或输入某些信息等。作为一种实施方式，在客户端内设置多个埋点，每个埋点代表用户针对客户端的操作行为或客户端的运行状态，例如，客户端的启动作为一个埋点，用户打开客户端的某个界面作为一个埋点，而在这些行为发生时，也即埋点被触发，则其对应的数据就能够存储在客户端对应的本地存储空间，作为客户端的待上报数据被存储在本地。
需要说明的是，待上报数据中的数据与SDK插件采集将客户端的数据发送的历史记录有关，例如，客户端启动之后，所产生的数据A存储在本地，而SDK插件将A作为待上报数据发送至***采集组件，然后，随着客户端的继续运行产生了数据B，则客户端的本地存储空间内的数据为A和B，但是数据A已经发送至***采集组件，则本次的待上报数据为B。
预先设置一个预设长度，其中，该数据长度可以是数据的字节数，例如，3M字节，也可以是数据的条数，例如30条。而SDK插件能够实时监测客户端的待上报数据的数据长度。例如，SDK插件上一次将客户端的数据发送至***采集组件之后，待上报数据的长度为0，随着客户端的运行，客户端的待上报数据的数据长度逐渐增大，不断累积，在累积到预设长度之后，SDK插件就判定客户端满足预设上报条件。因此，在SDK插件上一次将客户端的数据发送之后，在本次的待上报数据的数据长度累积到一定长度之后，就满足预设上报条件，则就可以执行将客户端的待上报数据发送至***采集组件的操作。
作为另一种实施方式，还可以是在客户端的状态处于某个状态时，判定客户端满足预设上报条件。具体地，监测所述客户端的状态是否由运行状态切换为后台状态；若监测到所述客户端的状态由运行状态切换为后台状态，则判定客户端满足预设上报条件。
客户端的状态包括运行状态、后台状态和退出状态，其中，运行状态为在电子设备的显示界面上运行，例如，应用程度的一个activity处于topmost状态，则表示客户端处于运行状态，当用户点击home键或者锁屏键时，客户端则进入后台状态，此时，客户端在***后台运行。如果将客户端的进程完全杀死，则客户端进入退出状态。在客 户端由运行状态切换为后台状态时，则表示用户可能会在一段时间内部使用该客户端，也就是说，客户端本地存储的数据可能会在一段时间内无变化，则可以在客户端进入后台的时候，将客户端的待上报数据上报，也就是说，在监测到所述客户端的状态由运行状态切换为后台状态，则判定客户端满足预设上报条件。
于本申请实施中，上述的待上报数据为快应用发送至客户端的数据信息，则数据信息调用SDK插件将数据信息发送至该SDK插件对应的服务器。
电子设备中，运行有快应用以及客户端。其中快应用是运行于快应用引擎上，并且在快应用引擎中设置有客户端提供的扩展接口。而在客户端中设有与扩展接口通信的扩展接口。而客户端可以通过扩展接口调用各个厂商的SDK插件。例如，可以调用图中的厂商A的SDK插件、厂商B的SDK插件以及厂商C的SDK插件。在这种情况下，在快应用中触发的数据处理指令可以通过设置在快应用引擎中的扩展接口传递到客户端中的扩展接口，进而再将数据处理指令传输给各个厂商的SDK插件。
在本申请实施例中快应用可以实现对多种类别的应用程序进行调用或者对多个厂商的设备的进行控制。而在对多个厂商的设备进行控制的过程中，是通过调用客户端中加载的多个厂商各自的SDK插件来实现的。那么客户端在通过提供给快应用引擎接收到数据处理指令后，会首先从该数据处理指令中提取出SDK插件的标识信息，然后从之前记录的多个SDK插件中查找匹配的SDK插件作为目标SDK插件。
其中，作为一种方式，客户端可以在加载某个厂商的SDK插件后就将其所下载的SDK插件进行记录。也可以在将某个下载的SDK插件进行加载以后再进行记录。
具体地，SDK插件的内部都封装有一些软件函数，通过该软件函数的运行可以实现对应的功能。而为了便于外部程序调用SDK插件，SDK插件会暴露其接口，以便通过该接口对SDK插件进行调用。在本申请的实施例中，为了便于统一的进行调用，不同厂商的SDK插件的接口均是按照统一的设定规则封装的。也就是不同的厂商的SDK插件的接口规则是相同的。那么客户端在调用目标SDK插件的过程中，是基于所述目标SDK插件所定义的接口规则调用所述目标SDK插件，以调用所述目标SDK插件执行所述数据处理指令。
需要说明的是，对于客户端中所调用的不同的SDK插件除了可以是属于不同厂商的SDK插件以外，还可以使属于不同设备的SDK插件，也可以是属于不同应用程序的SDK插件。对于客户端中所调用的不同的SDK插件的区别除了厂商、设备以及应用程序外也还可以有其他的区别方式，本申请实施例不做具体限定。
本申请提供的一种数据处理方法，通过在客户端中给快应用引擎配置扩展接口的方式，使得在通过快应用控制SDK插件的过程中，客户端可以通过配置给快应用引擎的扩展接口，接收所述快应用引擎响应于快应用中的触控操作后发送的数据处理指令，基于所述数据处理指令获取对应的目标SDK插件，调用所述目标SDK插件执行所述数据处理指令。从而使得快应用基于跨应用的方式来触发客户端对SDK插件进行控制，进而实现了快应用对SDK插件进行调用，对快应用的功能进行了极大的扩展，以便于通过快应用实现对移动终端中的其他组件进行调用。
则快应用引擎在获取到数据信息之后，通过通信通道将发送指令传输至所述客户端，客户端解析该发送指令获取到数据信息，并且查找设备对应的SDK插件，通过所述目标SDK插件将数据信息发送至厂商服务器。
其中，该通信通道可以是AIDL或者Messenger等通信通道，于本申请实施例中，该通信通道是AIDL通道。
另外，发送指令内还携带有SDK的标识以便客户端能够判定以哪个SDK发送数据信息，具体地，发送指令还携带有快应用包名，所述发送指令还用于指示所述客户端基于 所述快应用包名查找对应的SDK插件，作为目标SDK插件，通过所述目标SDK插件将所述数据信息发送至厂商服务器。作为一种实施方式，快应用对于记录的属于某个厂商的SDK插件，会对应存储该厂商的快应用的包名，然后再获取到数据处理指令后，再根据从数据处理指令中提取的包名来识别对应的目标SDK插件。
如图11所示，后台管理员登陆管理后台，配置每个设备型号对应的快应用链接，开发者在开发者平台上传SDK，用户首次添加某厂商设备时，会下载厂商对应的SDK并加载到客户端。用户添加完设备后，设备以卡片形式展示，用户点击设备卡片，根据后台配置的链接进入对应快应用页面(即设备控制页面)，用户控制设备，快应用通过接口将控制指令发送到快应用引擎，快应用引擎通过透传通道将控制指令发送到客户端，客户端通过设备厂商的SDK插件封装实现的标准接口将控制指令发到设备厂商的SDK插件，然后，SDK插件将控制指令发送至设备对应的厂商服务器，该厂商服务器将指令下发到设备，设备根据该控制指令执行对应的操作。
在图11中所示，快应用引擎安装于所述电子设备内，作为与所述客户端相互独立的应用程序，具体地，快应用引擎作为一个应用程序，安装在电子设备内，与客户端相比，是一个独立的应用程序。
另外，在图12中，快应用引擎安装于所述客户端内，作为所述客户端的一个功能组件。具体地，在开发者开放客户端的时候，就讲快应用引擎对应的程序包嵌入客户端内，还可以是，用户在下载客户端之后，并且在首次成功启动该客户端的时候，客户端会由客户端对应的云服务器下载该快应用引擎，而该快应用引擎作为客户端的一个更新包，则在下且安装完之后，就能够作为客户端的一个功能组件，即属于客户端。
需要说明的是，图12所与图11的区别为快应用引擎所安装的位置不同，而其他的实施例可以参考前述图11所对应的描述。并且上述步骤中未详细描述的部分，可参考前述实施例，在此不再赘述。
请参阅图13，本申请实施例还提供了一种数据处理方法，应用于电子设备，所述电子设备包括客户端和快应用引擎，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备。具体地，本实施例为快应用引擎与客户端之间的交互，则该方法包括：S1201至S1205。
S1201：客户端获取用户输入的触控操作，并确定所述触控操作对应的设备标识。
具体地，所述客户端的交互界面内设置有多个快应用控件，如图8所示，该界面为客户端的交互界面的一种实施方式，且该界面上所显示的卡片为快应用空间的一种实施方式。具体地，可参考上述图8所对应的描述。
作为一种实施方式，在客户端的交互界面上设置有多个卡片，且每个能够被用户触发，即能够影响用户的触控操作，则当客户端在交互界面上检测打触控操作之后，确定该触控操作对应的快应用控件，具体地，在该交互界面上，每个快应用控件都对应一个显示位置，则预先过去显示位置与快应用控件的标识(即卡片的标识)的对应关系，就能够确定所过去的触控操作对应的快应用控件，即能够确定哪个卡片被用户触发了，而又由于每个卡片对应一个设备标识，则就能够确定触控操作对应的设备，即客户端在获取到用户基于快应用控件输入的触控操作之后，确定所述触控操作对应的目标快应用控件；根据预先获取的所述快应用控件与设备标识的对应关系，查找所述目标快应用控件对应的设备标识。
另外，客户端的交互界面所展示的快应用控件可以是从客户端对应的云服务器内获取到的，则在用户添加设备之后，管理后台为该设备配置一个快应用控件，可以是整合到已有的快应用控件，例如，新添加的设备与已添加的设备的功能相同，即属于同一个类型的不同型号的产品，或者同一个类型的相同型号的产品。也可以是为新添 加的设备配置一个新的快应用控件。则作为一种实施方式，所配置的快应用控件存储在云服务器内，并且与设备的标识对应存储。
则在客户端进入到某个页面内，从云服务器内获取快应用控件展示列表，并在客户端的指定页面内显示。则具体地，客户端在获取到用户基于快应用控件输入的触控操作之后，确定所述触控操作对应的快应用控件之前，该方法还包括：所述客户端判断当前界面是否为指定界面；若为指定界面，则由云服务器获取快应用控件展示列表，所述快应用控件展示列表包括多个快应用控件；将所述快应用控件展示列表在所述指定界面展示。
其中，指定界面可以是用户登录所述客户端之后显示的主界面。如图14，示出了客户端的登录界面，而客户端的登录之后的主界面可以是图8所示的交互界面，即主界面与上述的交互界面可以是同一个界面。则用户在登录界面内登录用户名之后，且成功登录之后，客户端发送列表获取请求至云服务器，则该获取请求包括用户名，作为一种实施方式，云服务器所存储的快应用控件不仅与设备的标识对应存储，而且与用户名对应存储，即能够将一个用户名下所添加的多个设备所对应的快应用控件对应存储，则云服务器解析该获取请求得到用户名之后，根据该用户名查找对应的快应用控件，将所查找到的多个快应用控件作为快应用控件列表，并将快应用控件列表发送至客户端，则客户端将快应用控件列表展示，如图8所示的多个卡片。
另外，该指示界面还可以是负一屏界面，则该负一屏界面为用户成功登录之后，在主界面下从左网友滑动手势而调出的界面，则当进入该界面之后，客户端由云服务器内获取该用户名对应的多个快应用控件并在该负一屏的界面上展示。
S1202：客户端发送启动指令至所述快应用引擎，所述启动指令与所述设备对应。
S1203：快应用引擎基于所述启动指令启动与所述设备对应的快应用页面。
S1204：快应用引擎获取用户基于所述快应用页面输入的数据信息。
S1205：快应用引擎将所述数据信息发送至所述设备对应的厂商服务器。
具体地，所述快应用引擎通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息；所述客户端获取所述设备对应的目标SDK插件；所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器。
其中，客户端通过所述目标SDK插件将数据信息发送至厂商服务器的具体实施方式可以是所述客户端获取所述厂商服务器对应的数据封装协议；根据所述数据封装协议将所述数据信息封装成数据包；将所述数据包通过所述目标SDK插件发送至厂商服务器。
其中，该数据封装协议为厂商服务器与客户端之间约定的协议，则具体的封装算法植入SDK插件内，具体地，该SDK插件包括封装接口，该封装接口内包括数据封装协议对应的算法模块，能够将欲通过该接口发送的数据按照算法模块进行封装。客户端在获取到数据信息之后，将数据信息发送至SDK插件，SDK插件通过封装接口将数据信息封装成数据包，将所述数据包通过所述目标SDK插件发送至厂商服务器。
则于本申请实施例中，快应用可以通过链接地址将数据信息发送至厂商服务器，也可以通过厂商服务器对应的SDK插件将数据信息发送至厂商服务器，则具体地，采用何种方式将数据信息发送至厂商服务器，可以是，将传送方式与快应用页面对应。作为一种实施方式，在快应用页面启动之后，快应用引擎确定该快应用页面的包名，然后，根据预设的快应用页面的包名与传送方式的对应关系，确定所确定的快应用页面的包名对应的传送方式是第一方式还是第二方式，其中，第一方式为根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器，第二方式为通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息，所述发送指令用于指示所述客户端获 取所述设备对应的目标SDK插件，通过所述目标SDK插件将数据信息发送至厂商服务器。
如果是第一方式，则快应用引擎根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器。如果是第二方式，则所述快应用引擎通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息；所述客户端获取所述设备对应的目标SDK插件；所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器。
作为另一种实施方式，每个设备对应一个传送方式，而该传送方式在用户将设备添加之后，为该设备配置，也可以是由管理后台来配置，而每个设备的标识对应的传送方式在云服务器内存储。而在快应用获取到用户输入的数据信息之后，发送查询指令至云服务器，该查询指令包括设备的标识，云服务器在获取到该查询指令之后，解析该查询指令获得到设备的标识，查找该设备的标识对应的传送方式，并且传送方式发送至快应用引擎，快应用引擎确定该传送方式是第一方式还是第二方式，如果是第一方式，则快应用引擎根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器。如果是第二方式，则所述快应用引擎通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息；所述客户端获取所述设备对应的目标SDK插件；所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器。
另外，该SDK插件可以是用户在将设备添加之后下载的，具体地，客户端获取所述设备对应的目标SDK插件之前还包括：当所述客户端在设备添加页面内获取到设备的标识时，下载该设备的标识对应的SDK插件并存储。如图15所示，示出了客户端的设备添加页面，在该页面内用户添加所购买的设备，然后，管理后台为该设备配置一个快应用控件，即设备的卡片，然后，由下载该设备对应的SDK插件，具体地，先判定本地是否存储有该设备的SDK插件，具体地，获取该设备的标识，从而确定该设备的标识所对应的SDK插件的标识，在本地存储空间内确定是否包括该SDK插件的标识，如果不包括则由厂商服务器内下载该SDK插件，具体地，可以是客户端发送下载请求至云服务器，该下载请求内包括设备的标识，云服务器在获取到该下载请求之后，解析该下载请求获取到设备的标识，并确定该设备标识的厂商，然后由该厂商对应的厂商服务器下载该设备的标识对应的SDK插件，并发送至客户端，客户端获取该SDK插件并安装。
需要说明的是，图12所与图11的区别为快应用引擎所安装的位置不同，而其他的实施例可以参考前述图11所对应的描述。并且上述步骤中未详细描述的部分，可参考前述实施例，在此不再赘述。
请参阅图16，其示出了本申请实施例提供的一种数据处理装置1500的结构框图。该数据处理装置1500可以包括：监测单元1501、启动单元1502、获取单元1503和发送单元1504。
监测单元1501，用于监测是否获取到启动指令，所述启动指令为所述客户端根据用户输入的触控操作所发出的，且所述启动指令与所述设备对应。
启动单元1502，用于若获取到启动指令，则启动与所述设备对应的快应用页面。
具体地，启动单元1502用于获取所述设备对应的链接地址；根据所述链接地址获取页面数据；基于所述页面数据获得快应用页面并显示。
获取单元1503，用于获取用户基于所述快应用页面输入的数据信息。
发送单元1504，用于将所述数据信息发送至所述设备对应的厂商服务器。
作为一种实施方式，发送单元1504还用于获取所述设备对应的链接地址；根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器。
作为另一种实施方式，发送单元1504还用于通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息，所述发送指令用于指示所述客户端获取所述设备对应的目标SDK插件，通过所述目标SDK插件将数据信息发送至厂商服务器。其中， 所述通信通道为AIDL通道。具体地，所述发送指令还携带有快应用包名，所述发送指令还用于指示所述客户端基于所述快应用包名查找对应的SDK插件，作为目标SDK插件，通过所述目标SDK插件将所述数据信息发送至厂商服务器。
其中，发送单元1504还用于将所述控制指令发送至所述设备对应的厂商服务器，指示所示厂商服务器将所述控制指令发送至所述设备，并控制所述设备执行与所述控制指令对应的操作。
进一步的，所述快应用引擎安装于所述客户端内，作为所述客户端的一个功能组件。
进一步的，所述快应用引擎安装于所述电子设备内，作为与所述客户端相互独立的应用程序。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
请参阅图17，其示出了本申请实施例提供的一种数据处理装置1600的结构框图。该数据处理装置1600可以包括：第一获取单元1601、指令发送单元1602、启动单元1603、第二获取单元1604和数据发送单元1605。其中，第一获取单元1601、指令发送单元1602位于客户端内，启动单元1603、第二获取单元1604和数据发送单元1605位于快应用引擎内。
第一获取单元1601，用于获取用户输入的触控操作，并确定所述触控操作对应的设备标识。
所述客户端的交互界面内设置有多个快应用控件，每个所述快应用控件对应一个设备。第一获取单元1601还用于在获取到用户基于快应用控件输入的触控操作之后，确定所述触控操作对应的目标快应用控件；根据预先获取的所述快应用控件与设备标识的对应关系，查找所述目标快应用控件对应的设备标识。具体地，第一获取单元1601用于判断当前界面是否为指定界面；若为指定界面，则由云服务器获取快应用控件展示列表，所述快应用控件展示列表包括多个快应用控件；将所述快应用控件展示列表在所述指定界面展示。
其中，所述指定界面为用户登录所述客户端之后显示的主界面。还可以是，指定界面为所述客户端的负一屏界面。
指令发送单元1602，用于发送启动指令至所述快应用引擎，所述启动指令与所述设备对应。
启动单元1603，用于基于所述启动指令启动与所述设备对应的快应用页面。
第二获取单元1604，用于获取用户基于所述快应用页面输入的数据信息。
数据发送单元1605，用于将所述数据信息发送至所述设备对应的厂商服务器。
数据发送单元1605还用于通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息。所述客户端获取所述设备对应的目标SDK插件；所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器。具体地，客户端获取所述厂商服务器对应的数据封装协议；根据所述数据封装协议将所述数据信息封装成数据包；将所述数据包通过所述目标SDK插件发送至厂商服务器。
进一步，还包括下载单元，用于当所述客户端在设备添加页面内获取到设备的标识时，下载该设备的标识对应的SDK插件并存储。
在本申请所提供的几个实施例中，模块相互之间的耦合可以是电性，机械或其它形式的耦合。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
请参考图18，其示出了本申请实施例提供的一种电子设备的结构框图。该电子设备100可以是智能手机、平板电脑、电子书等能够运行应用程序的电子设备。本申请中的电子设备100可以包括一个或多个如下部件：处理器110、存储器120、快应用引擎112、客户端113以及一个或多个应用程序，其中一个或多个应用程序可以被存储在存储器120中并被配置为由一个或多个处理器110执行，一个或多个程序配置用于执行如前述方法实施例所描述的方法。快应用引擎112和客户端113可参考上述实施例。
处理器110可以包括一个或者多个处理核。处理器110利用各种接口和线路连接整个电子设备100内的各个部分，通过运行或执行存储在存储器120内的指令、程序、代码集或指令集，以及调用存储在存储器120内的数据，执行电子设备100的各种功能和处理数据。可选地，处理器110可以采用数字信号处理(Digital Signal Processing，DSP)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)、可编程逻辑阵列(Programmable Logic Array，PLA)中的至少一种硬件形式来实现。处理器110可集成中央处理器(Central Processing Unit，CPU)、图像处理器(Graphics Processing Unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作***、用户界面和应用程序等；GPU用于负责显示内容的渲染和绘制；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器110中，单独通过一块通信芯片进行实现。
存储器120可以包括随机存储器(Random Access Memory，RAM)，也可以包括只读存储器(Read-Only Memory)。存储器120可用于存储指令、程序、代码、代码集或指令集。存储器120可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作***的指令、用于实现至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现下述各个方法实施例的指令等。存储数据区还可以存储电子设备100在使用中所创建的数据(比如电话本、音视频数据、聊天记录数据)等。
请参考图19，其示出了本申请实施例提供的一种计算机可读存储介质的结构框图。该计算机可读存储介质1800中存储有程序代码，所述程序代码可被处理器调用执行上述方法实施例中所描述的方法。
计算机可读存储介质1800可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM、硬盘或者ROM之类的电子存储器。可选地，计算机可读存储介质1800包括非易失性计算机可读介质(non-transitory computer-readable storage medium)。计算机可读存储介质1800具有执行上述方法中的任何方法步骤的程序代码1810的存储空间。这些程序代码可以从一个或者多个计算机程序产品中读出或者写入到这一个或者多个计算机程序产品中。程序代码1810可以例如以适当形式进行压缩。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不驱使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (20)

  1. 一种数据处理方法，其特征在于，应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备，所述方法包括：
    监测是否获取到启动指令，所述启动指令为所述客户端根据作用于客户端交互界面中的快应用控件的操作所发出的，且所述启动指令与所述设备对应；
    若获取到所述启动指令，则启动与所述设备对应的快应用页面；
    获取用户基于所述快应用页面输入的数据信息；
    将所述数据信息发送至所述设备对应的厂商服务器。
  2. 根据权利要求1所述的方法，其特征在于，所述将所述数据信息发送至所述设备对应的厂商服务器，包括：
    获取所述设备对应的链接地址；
    根据所述链接地址将所述数据信息发送至所述链接地址对应的厂商服务器。
  3. 根据权利要求1所述的方法，其特征在于，所述将所述数据信息发送至所述设备对应的厂商服务器，包括：
    通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息，所述发送指令用于指示所述客户端获取所述设备对应的目标SDK插件，通过所述目标SDK插件将数据信息发送至厂商服务器。
  4. 根据权利要求3所述的方法，其特征在于，所述通信通道为AIDL通道。
  5. 根据权利要求3所述的方法，其特征在于，所述发送指令还携带有快应用包名，所述发送指令还用于指示所述客户端基于所述快应用包名查找对应的SDK插件，作为目标SDK插件，通过所述目标SDK插件将所述数据信息发送至厂商服务器。
  6. 根据权利要求1所述的方法，其特征在于，所述启动与所述设备对应的快应用页面，包括：
    获取所述设备对应的链接地址；
    根据所述链接地址获取页面数据；
    基于所述页面数据获得快应用页面并显示。
  7. 根据权利要求1所述的方法，其特征在于，所述数据信息为控制指令，所述将所述数据信息发送至所述设备对应的厂商服务器包括：
    将所述控制指令发送至所述设备对应的厂商服务器，指示所示厂商服务器将所述控制指令发送至所述设备，并控制所述设备执行与所述控制指令对应的操作。
  8. 根据权利要求1-7任一所述的方法，其特征在于，所述快应用引擎安装于所述客户端内，作为所述客户端的一个功能组件。
  9. 根据权利要求1-7任一所述的方法，其特征在于，所述快应用引擎安装于所述电子设备内，作为与所述客户端相互独立的应用程序。
  10. 一种数据处理方法，其特征在于，应用于电子设备，所述电子设备包括客户端和快应用引擎，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备，所述方法包括：
    所述客户端获取用户输入的操作，并确定所述操作对应的设备标识；
    所述客户端发送启动指令至所述快应用引擎，所述启动指令与所述设备对应；
    所述快应用引擎基于所述启动指令启动与所述设备对应的快应用页面；
    所述快应用引擎获取用户基于所述快应用页面输入的数据信息；
    所述快应用引擎将所述数据信息发送至所述设备对应的厂商服务器。
  11. 根据权利要求10所述的方法，其特征在于，所述客户端的交互界面内设置有 多个快应用控件，每个所述快应用控件对应一个设备；所述客户端获取用户输入的操作，并确定所述操作对应的设备标识，包括：
    所述客户端在获取到用户基于快应用控件输入的触控操作之后，确定所述触控操作对应的目标快应用控件；
    根据预先获取的所述快应用控件与设备标识的对应关系，查找所述目标快应用控件对应的设备标识。
  12. 根据权利要求11所述的方法，其特征在于，所述客户端在获取到用户基于快应用控件输入的触控操作之后，确定所述触控操作对应的快应用控件之前，还包括：
    所述客户端判断当前界面是否为指定界面；
    若为指定界面，则由云服务器获取快应用控件展示列表，所述快应用控件展示列表包括多个快应用控件；
    将所述快应用控件展示列表在所述指定界面展示。
  13. 根据权利要求12所述的方法，其特征在于，所述指定界面为用户登录所述客户端之后显示的主界面。
  14. 根据权利要求12所述的方法，其特征在于，所述指定界面为所述客户端的负一屏界面。
  15. 根据权利要求10所述的方法，其特征在于，所述快应用引擎将所述数据信息发送至所述设备对应的厂商服务器，包括：
    所述快应用引擎通过通信通道将发送指令传输至所述客户端，所述发送指令携带有数据信息；
    所述客户端获取所述设备对应的目标SDK插件；
    所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器。
  16. 根据权利要求15所述的方法，其特征在于，所述客户端通过所述目标SDK插件将数据信息发送至厂商服务器，包括：
    所述客户端获取所述厂商服务器对应的数据封装协议；
    根据所述数据封装协议将所述数据信息封装成数据包；
    将所述数据包通过所述目标SDK插件发送至厂商服务器。
  17. 根据权利要求15所述的方法，其特征在于，所述客户端获取所述设备对应的目标SDK插件之前还包括：
    当所述客户端在设备添加页面内获取到设备的标识时，下载该设备的标识对应的SDK插件并存储。
  18. 一种数据处理装置，其特征在于，应用于电子设备内的快应用引擎，所述电子设备还包括客户端，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备，所述数据处理装置包括：
    监测单元，用于监测是否获取到启动指令，所述启动指令为所述客户端根据用户输入的操作所发出的，且所述启动指令与所述设备对应；
    启动单元，用于若获取到启动指令，则启动与所述设备对应的快应用页面；
    获取单元，用于获取用户基于所述快应用页面输入的数据信息；
    发送单元，用于将所述数据信息发送至所述设备对应的厂商服务器。
  19. 一种电子设备，其特征在于，包括：
    一个或多个处理器；
    存储器；
    快应用引擎，所述快应用引擎包括多个快应用页面，每个所述快应用页面至少对应一个设备；
    客户端；
    一个或多个应用程序，其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述一个或多个处理器执行，所述一个或多个程序配置用于执行如权利要求1-9任一项所述的方法。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读取存储介质中存储有程序代码，所述程序代码可被处理器调用执行所述权利要求1-9任一项所述方法。
PCT/CN2019/075944 2019-02-22 2019-02-22 数据处理方法、装置、电子设备及可读存储介质 WO2020168568A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980078011.2A CN113168334A (zh) 2019-02-22 2019-02-22 数据处理方法、装置、电子设备及可读存储介质
PCT/CN2019/075944 WO2020168568A1 (zh) 2019-02-22 2019-02-22 数据处理方法、装置、电子设备及可读存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/075944 WO2020168568A1 (zh) 2019-02-22 2019-02-22 数据处理方法、装置、电子设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2020168568A1 true WO2020168568A1 (zh) 2020-08-27

Family

ID=72143996

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/075944 WO2020168568A1 (zh) 2019-02-22 2019-02-22 数据处理方法、装置、电子设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN113168334A (zh)
WO (1) WO2020168568A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113656093A (zh) * 2021-08-02 2021-11-16 珠海格力电器股份有限公司 插件配置方法、装置、设备及存储介质
CN114006885A (zh) * 2021-11-17 2022-02-01 印象(山东)大数据有限公司 一种基于智能设备的数据采集方法、装置及电子设备
CN114327678B (zh) * 2021-12-29 2023-05-12 中电福富信息科技有限公司 一种支持多引擎的实时数据处理***及方法
CN116800726A (zh) * 2022-03-15 2023-09-22 广州汽车集团股份有限公司 一种车载交互内容调用控制方法及***、交互引擎、计算机可读存储介质
CN114895898A (zh) * 2022-04-29 2022-08-12 北京百度网讯科技有限公司 一种指令处理方法、装置、设备以及存储介质
CN114860483B (zh) * 2022-06-17 2023-05-30 中国人民解放军陆军炮兵防空兵学院 一种快速采集设备数据并高效率持久化方法及***
CN116737405B (zh) * 2022-10-24 2024-03-05 荣耀终端有限公司 一种快应用卡片的数据通信的方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014107003A1 (ko) * 2013-01-07 2014-07-10 에스케이플래닛 주식회사 단말기의 어플리케이션 관리 방법, 이를 위한 시스템 및 장치
CN105204894A (zh) * 2015-08-28 2015-12-30 小米科技有限责任公司 安装智能设备的插件的方法和装置
CN108768803A (zh) * 2018-05-28 2018-11-06 北京小米移动软件有限公司 添加智能设备的方法、装置及存储介质
CN109032691A (zh) * 2018-06-25 2018-12-18 腾讯科技（深圳）有限公司 一种小程序运行方法、装置及存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8793697B2 (en) * 2012-02-23 2014-07-29 Qualcomm Incorporated Method and system for scheduling requests in a portable computing device
CN102662703B (zh) * 2012-03-29 2015-07-29 北京奇虎科技有限公司 一种应用程序插件加载方法及装置
US10389835B2 (en) * 2017-01-10 2019-08-20 A10 Networks, Inc. Application aware systems and methods to process user loadable network applications
CN108337279B (zh) * 2017-01-20 2021-01-29 阿里巴巴集团控股有限公司 一种智能设备的控制方法及装置
CN107682238B (zh) * 2017-09-15 2020-10-16 阿里巴巴（中国）有限公司 智能家居平台设备及终端电子设备
CN107896256B (zh) * 2017-12-18 2020-03-24 Oppo广东移动通信有限公司 信息推送方法、装置、移动终端、服务器及可读存储介质
CN108958074B (zh) * 2018-06-20 2019-11-29 维沃移动通信有限公司 一种智能设备控制方法及移动终端
CN109032491B (zh) * 2018-07-23 2021-03-12 Oppo广东移动通信有限公司 数据处理方法、装置以及移动终端
CN109284144B (zh) * 2018-08-27 2021-08-27 维沃移动通信有限公司 一种快应用处理方法及移动终端
CN109358936B (zh) * 2018-09-29 2021-09-10 Oppo广东移动通信有限公司 信息处理方法、装置、存储介质、电子设备及***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014107003A1 (ko) * 2013-01-07 2014-07-10 에스케이플래닛 주식회사 단말기의 어플리케이션 관리 방법, 이를 위한 시스템 및 장치
CN105204894A (zh) * 2015-08-28 2015-12-30 小米科技有限责任公司 安装智能设备的插件的方法和装置
CN108768803A (zh) * 2018-05-28 2018-11-06 北京小米移动软件有限公司 添加智能设备的方法、装置及存储介质
CN109032691A (zh) * 2018-06-25 2018-12-18 腾讯科技（深圳）有限公司 一种小程序运行方法、装置及存储介质

Also Published As

Publication number Publication date
CN113168334A (zh) 2021-07-23

Similar Documents

Publication Publication Date Title
WO2020168568A1 (zh) 数据处理方法、装置、电子设备及可读存储介质
WO2020223854A1 (zh) 设备配网方法、装置、电子设备及存储介质
CN105471686B (zh) 终端控制方法、装置及***
CN108702389B (zh) 用于遥控iot(物联网)设备的架构
US10003654B2 (en) Universal internet of things (IoT) smart translator
RU2602982C2 (ru) Способ, аппарат и система для интеллектуального управления устройством и самонастраиваемое устройство
CN102932695B (zh) 一种遥控方法、智能终端及智能遥控***
CN103023681B (zh) 智能家居控制设备、更新方法
WO2016058246A1 (zh) 家庭智能网关及智能家居***
US11782590B2 (en) Scene-operation method, electronic device, and non-transitory computer readable medium
CN107294793B (zh) 智能家居设备的替换方法、装置、设备及存储介质
CN113348725B (zh) 设备操作方法、装置、网关、电子设备及计算机可读介质
CN109617963B (zh) 设备控制方法、装置以及物联网***
US20220052866A1 (en) Smart home system control method and apparatus, electronic device
CN113572799B (zh) 设备接入控制平台的方法、装置和服务器
CN112468595B (zh) 基于网关的设备控制方法、装置和***
CN113572862A (zh) 一种集群部署方法、装置、电子设备及存储介质
AU2013388030A1 (en) Method, apparatus, and system for intelligently controlling device, and plug-and-play device
CN105049339A (zh) 一种加载智能设备的控制界面的方法和装置
WO2020228033A1 (zh) Sdk插件的加载方法、装置、移动终端以及存储介质
CN113986349A (zh) 数据处理方法、装置、计算机可读存储介质和计算机设备
CN113391559A (zh) 智慧家居设备控制方法和终端设备
CN107807619A (zh) 基于虚拟服务器模块的智能家居控制***及其工作方法
WO2020168570A1 (zh) 快应用的添加方法、装置、电子设备及存储介质
CN113300920A (zh) 基于家电控制群组的智能家电控制方法与控制设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19915741

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19915741

Country of ref document: EP

Kind code of ref document: A1