WO2020168570A1 - 快应用的添加方法、装置、电子设备及存储介质 - Google Patents

快应用的添加方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2020168570A1
WO2020168570A1 PCT/CN2019/075946 CN2019075946W WO2020168570A1 WO 2020168570 A1 WO2020168570 A1 WO 2020168570A1 CN 2019075946 W CN2019075946 W CN 2019075946W WO 2020168570 A1 WO2020168570 A1 WO 2020168570A1
Authority
WO
WIPO (PCT)
Prior art keywords
quick application
quick
client
application
sdk
Prior art date
Application number
PCT/CN2019/075946
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 PCT/CN2019/075946 priority Critical patent/WO2020168570A1/zh
Priority to CN201980081078.1A priority patent/CN113196235A/zh
Publication of WO2020168570A1 publication Critical patent/WO2020168570A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating

Definitions

  • This application relates to the technical field of electronic equipment, and more specifically, to a fast application adding method, device, electronic equipment and storage medium.
  • Electronic devices such as computers and mobile phones, have become one of the most commonly used consumer electronic products in people's daily lives. Users can install applications on electronic devices to implement various functions. For example, they can install information aggregation applications on electronic devices, so as to obtain rich various types of information through the aggregation applications, such as news information, audio and video Information etc. At present, there are some infrequently used applications such as government affairs applications. Users need to implement some special functions through such applications, such as online appointments. However, it is precisely because of its particularity that after the user realizes the required function, it usually does not use it again for a long time, resulting in unnecessary waste of the storage space of the electronic device.
  • this application proposes a fast application adding method, device, electronic equipment and storage medium to solve the above-mentioned problems.
  • an embodiment of the present application provides a method for adding a quick application, which is applied to a client, and the method includes: monitoring purchase records of equipment purchased through an HTML5 mall page embedded in the client; In the purchase record of a device, confirm the quick application identifier corresponding to the at least one device; according to the quick application identifier, add the quick application corresponding to the quick application identifier to the client.
  • an embodiment of the present application provides a quick application adding device, which is characterized in that it is applied to a client, and the device includes: a record monitoring module, a quick application acquisition module, and a quick application adding module, wherein the The record monitoring module is used to monitor the purchase record of the device purchased through the HTML5 mall page embedded in the client; the quick application acquisition module is used to confirm that it corresponds to the at least one device when the purchase record of at least one device is monitored The quick application identification; the quick application adding module is used to add the quick application corresponding to the quick application identification to the client according to the quick application identification.
  • an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more application programs, wherein the one or more application programs are stored in the memory and It is configured to be executed by the one or more processors, and the one or more programs are configured to execute the quick application adding method provided in the first aspect described above.
  • an embodiment of the present application provides a computer-readable storage medium, and the computer-readable storage medium stores program code, and the program code can be called by a processor to execute the fast speed provided in the first aspect. How to add the application.
  • the solution provided by this application monitors the purchase record of the device purchased through the HTML5 mall page embedded in the client.
  • the quick application identification corresponding to the at least one device is confirmed, according to the quick application identification , Add the quick app corresponding to the quick app identifier to the client.
  • the quick application corresponding to the device can be added, saving adding time and improving user experience.
  • Fig. 1 shows a schematic structural diagram of a smart home system proposed in an embodiment of the present application.
  • FIG. 2 shows a schematic structural diagram of another smart home system proposed by an embodiment of the present application
  • FIG. 3 shows a schematic diagram of a fast application engine architecture proposed by an embodiment of the present application.
  • FIG. 4 shows a schematic diagram of the operating environment of the method for adding a quick application proposed in an embodiment of the present application.
  • Fig. 5 shows a flowchart of a method for adding a quick application according to an embodiment of the present application.
  • Fig. 6 shows a flowchart of a method for adding a quick application according to another embodiment of the present application.
  • Fig. 7 shows a flowchart of step S220 in the method for adding a quick application according to an embodiment of the present application.
  • Fig. 8 shows a schematic diagram of a display effect provided according to an embodiment of the present application.
  • Fig. 9 shows a flowchart of a method for adding a quick application according to another embodiment of the present application.
  • Fig. 10 shows a flowchart of step S370 in the method for adding a quick application according to an embodiment of the present application.
  • Fig. 11 shows a block diagram of a fast application adding device according to an embodiment of the present application.
  • Fig. 12 shows a block diagram of a quick application adding module in a quick application adding device according to an embodiment of the present application.
  • Fig. 13 is a block diagram of an electronic device for executing a method for adding a quick application according to an embodiment of the present application.
  • Fig. 14 is a storage unit for storing or carrying program code for implementing the method for adding a quick application according to the embodiment of the present application.
  • Smart home connects various smart home devices in the home (such as air conditioners, lights, refrigerators, washing machines, 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, and environmental monitoring , HVAC control, infrared forwarding and programmable timing control and other controls.
  • various smart home devices in the home such as air conditioners, lights, refrigerators, washing machines, etc.
  • the Internet of Things technology to provide home appliance control, lighting control, telephone remote control, indoor and outdoor remote control, anti-theft alarm, and environmental monitoring , HVAC control, infrared forwarding and programmable timing control and other controls.
  • household equipment can be air conditioners, lighting fixtures, smart lights, smart cameras, smart sockets, wireless switches, smart curtain motors, smart speakers, and various sensors (such as human sensors, door and window sensors, smoke alarms, etc.).
  • the home equipment is managed and controlled through electronic equipment.
  • the electronic equipment 100 can establish a wireless connection with the smart gateway 300, and the home equipment 200 can establish a wireless connection with the smart gateway 300 to realize the electronic equipment Data interaction between 100 and household equipment.
  • the electronic device 100 and the smart gateway 300 are in communication connection with the server 400, and the electronic device 100 can perform data interaction with household equipment through the server 400 and the smart gateway 300.
  • the electronic device 100 may communicate with the first cloud server 402 to realize data interaction with the first cloud server 402.
  • the household equipment 200 communicates with the second cloud server 401 through the smart gateway 300 to realize data interaction between the second and the server 401.
  • data interaction can be performed between the first cloud server 402 and the second cloud server 401, so that the electronic device 100 can communicate with the home device 200 through the first cloud server 402, the second cloud server 404, and the smart gateway 300. Data interaction.
  • the home equipment of different manufacturers usually needs to be controlled by different applications. That is to say, the communication between the applications of the home equipment of different manufacturers and the servers of different manufacturers requires more applications to be installed, which occupies the electronic equipment. More storage space.
  • 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 the 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.
  • the inventor found that when adding a quick application of a device, the user is required to select the device manufacturer, type, model and other messages according to the operation, and therefore the user is required to perform cumbersome operations. Therefore, the inventor proposes to add a quick application of the device according to the purchase record of the device purchased by the user on the mall page, which saves the user's operation, and facilitates subsequent operations on the household device, thereby improving the user experience.
  • a fast application and a client 110 are running.
  • the fast application runs on the fast application engine, and an extended interface 97 provided by the client is set in the fast application engine.
  • the client 110 is provided with an extension interface 96 that communicates with the extension interface 97.
  • the client 110 can call software development kit (SDK, Software Development Kit) plug-ins of various manufacturers through an extended interface.
  • SDK plug-in 111 of manufacturer A, the SDK plug-in 112 of manufacturer B, and the SDK plug-in 113 of manufacturer C in the figure can be called.
  • the data processing instructions triggered in the fast application can be transferred to the extended interface 96 in the client through the extension interface 97 set in the fast application engine, and then the data processing instructions are transmitted to the SDK plug-ins of various manufacturers .
  • the client 110 may provide an entrance to the fast application, that is, the client 110 can enter the fast application.
  • the communication between the fast application and the client 110 may be through a cross-application communication method, such as using AIDL interaction.
  • a parameter transfer interface can be set between the client 110 and the embedded fast application for data transfer between the client 110 and the fast application.
  • a channel class can be defined between the fast application and the client 110 Interface, all interface functions are implemented using a channel class interface.
  • the client 110 may instruct the quick application engine to access the corresponding quick application according to the link of the quick application, thereby displaying the interface of the quick application.
  • the interface of the quick app can receive control information, and after the client 110 learns the control information, it transmits the control information to the server of the home device through the above-mentioned SDK to realize the management and control of the home device.
  • the quick application engine can also receive the information transmitted by the client 110, and display the information that needs to be displayed on the quick application control page.
  • an embodiment of the present application provides a method for adding a quick application, which can be applied to an electronic device, and the method for adding a quick application may include:
  • Step S110 Monitor the purchase record of the device purchased through the HTML5 mall page embedded in the client.
  • HTML5 mall pages refer to HyperText Markup Language 5 (HTML5) pages that implement mall functions.
  • HTML5 is the HTML standard version used to replace the HTML 4.01 and XHTML 1.0 standards formulated in 1999. .
  • HTML5 refers to a combination of technologies including HTML, CSS, and JavaScript.
  • HTML5 can reduce the browser's need for plug-in-based rich internet application services (plug-in-based rich internet application, RIA), such as Adobe Flash, Microsoft Silverlight, Oracle JavaFX, and provide more standard sets that can effectively enhance web applications .
  • RIA plug-in-based rich internet application
  • HTML5 pages can be referred to as H5 pages.
  • the client in the embodiment of the present application may support H5 page embedding, that is, the H5 page may be embedded in the client.
  • H5 page embedding that is, the H5 page may be embedded in the client.
  • webview is a browser component.
  • the Webkit rendering engine is used internally.
  • webview is based on webkit core and can support html5.
  • a control corresponding to the HTML5 mall page can be set in the client, and the control can correspond to the link of the HTML5 mall page.
  • the control is triggered by a trigger operation, the HTML5 mall page can be accessed, and the HTML5 mall page can be rendered , So as to realize the HTML5 mall page displayed in the client. After the HTML5 mall page is displayed, the purchase of goods can be realized through the HTML5 mall page.
  • the HTML5 mall page corresponds to the server of the mall.
  • the server of the mall is accessed to realize the purchase of online goods.
  • the HTML5 mall page is used to provide users to purchase equipment.
  • the mall server can obtain the purchase record of the purchased equipment.
  • the above-mentioned device may be a device that can be managed and controlled through a quick application in the client, that is, the client may provide a quick application for managing the devices sold in the above-mentioned mall.
  • the purchase record may include equipment information, quantity, and price of the purchased equipment, and the equipment information may include manufacturer information, type information, and model information of the equipment.
  • the specific purchase record may not be limited in the embodiment of this application.
  • the client may obtain the purchase record of the device purchased through the HTML5 mall page from the server of the mall through the server corresponding to the client, so as to monitor the purchase record of the device purchased through the HTML5 mall page.
  • the acquisition of the purchase record of the device purchased through the HTML5 mall page may be acquired in real time, or acquired at a specified interval, or acquired based on a detected control operation.
  • the specific method of obtaining the above-mentioned purchase record may not be limited in the embodiment of the present application.
  • the client may obtain the purchase record of the device purchased through the HTML5 mall page from the mall server in real time through the server corresponding to the client, so as to accurately monitor the purchase record.
  • Step S120 When the purchase record of at least one device is monitored, confirm the quick application identifier corresponding to the at least one device.
  • the quick application corresponding to the purchased at least one device may be added.
  • Different devices may have different manufacturers, and when managing and controlling the device, the server corresponding to the device needs to be passed. Therefore, the devices of different manufacturers have different applications.
  • the quick application may correspond to the quick application identification, and the quick application identification is used as the identification information of the quick application to distinguish different quick applications.
  • the specific quick application identifier may not be limited in the embodiment of the present application.
  • the quick application identifier may be the identity ID of the quick application.
  • the corresponding relationship between the quick application identification and the device can be established, so that when the quick application is added, the quick application identification corresponding to the device can be determined.
  • the correspondence between the identifier and the device can be quickly applied, and can be stored in the electronic device where the client is installed in the form of a list. In the list, each device corresponds to a quick application logo.
  • the quick application when adding a quick application corresponding to the purchased at least one device, the quick application can be added according to the quick application identifier to add the quick application corresponding to the purchased at least one device for subsequent use of the quick application management And control the purchased equipment. Therefore, the quick application identifier corresponding to the purchased at least one device can be determined to add the quick application corresponding to the quick application identifier.
  • the corresponding relationship between the quick app ID and the device information can be used to determine the quick app ID corresponding to the device based on the device information in the purchase record mentioned above, so that the quick app ID can be subsequently used according to the quick app ID.
  • the quick application corresponding to the logo is added to the client.
  • Step S130 Add a fast application corresponding to the fast application identifier to the client according to the fast application identifier.
  • the quick application identification corresponding to the quick application identification can be searched for according to the quick application identification, and the quick application identification corresponding to the quick application identification
  • the quick application is added to the client, that is, the quick application corresponding to the device is added, so that the user can subsequently manage and control the purchased device through the quick application of the added device.
  • control refers to the encapsulation of data and methods. Controls can have their own properties and methods. Properties are simple visitors of control data, and methods are simple and visible functions of the control.
  • the control creation process includes design and development. , Debugging (the so-called 3Ds development process, namely Design, Develop, Debug) work, and then the use of controls.
  • the method for adding a quick application is to confirm the quick application identifier corresponding to the purchased at least one device when the purchase record of at least one device purchased through the HTML5 mall page embedded in the client is monitored, and then The quick app corresponding to the quick app logo is added to the client, so that when the user purchases the device through the HTML5 mall page, the quick app corresponding to the purchased device can be added to the client, avoiding the user's subsequent need to go through tedious steps to add Fast application improves user experience.
  • FIG. 6 another embodiment of the present application provides a quick application adding method, which can be applied to electronic devices, and the quick application adding method may include:
  • Step S210 Monitor the purchase record of the device purchased through the HTML5 mall page embedded in the client.
  • step S210 can refer to the content of the above-mentioned embodiment, which will not be repeated here.
  • Step S220 When the purchase record of at least one device is monitored, confirm the quick application identifier corresponding to the at least one device.
  • step S220 may include:
  • Step S221 Obtain device information of the device, where the device information includes at least one of manufacturer information, type information, and model information.
  • the device information of the device may be obtained according to the foregoing purchase record.
  • the device information may include at least one of manufacturer information, type information, and model information.
  • the device information of the device can be obtained, so as to obtain the quick application identifier corresponding to the device according to the device information of the device.
  • the specific method for acquiring the manufacturer information of the device may not be limited in the embodiment of the present application.
  • Step S222 Based on the device information, obtain a quick application identifier corresponding to the device.
  • the electronic device where the client is installed stores the quick application identifier corresponding to each device information, and the corresponding relationship between the device information and the quick application.
  • the device information of the device can be used to find the quick application identifier corresponding to the device information of the device from the multiple quick application identifiers by using the above-mentioned corresponding relationship.
  • the client can also query the fast application identifier corresponding to the device information from the server according to the device information.
  • the specific method for obtaining the quick application identifier corresponding to the device based on the device information may not be limited.
  • Step S230 Add an entry control corresponding to the quick application identifier and display it on the interactive interface of the client.
  • the entry control corresponding to the quick application identification can be added to the interactive interface of the client, and the entry control is displayed on the interaction of the client Interface.
  • the portal control serves as the portal to access the quick application corresponding to the quick application identification.
  • the entry control corresponding to the quick application identifier can be searched for, and then the found entry control can be added to the interactive interface of the client.
  • the interactive interface that the entry control is specifically added to the client is not limited, and it may be the main interface of the client or other interfaces of the client.
  • the icons corresponding to the portal controls of different devices are different, and the portal controls corresponding to the device can be found through the quick application identification corresponding to the device.
  • the entry control added to the interactive interface of the client can include the device information of the device, for example, the manufacturer of the device, the type of the device, the model of the device, etc., that is to say, the icon corresponding to the entry control can include the above-mentioned devices information.
  • the device name of the device purchased above is "Device 7”.
  • the displayed icon of the entry control 155 can show the name of the device "Device 7" . Therefore, among the portal controls of all devices displayed on the client side, it is convenient for the user to know the device corresponding to each portal control.
  • Step S240 Establish a correspondence between the entry control and the quick application link corresponding to the quick application identifier, and the quick application link is used to access the quick application corresponding to the quick application identifier.
  • the quick application link is used to access the quick application corresponding to the quick application identifier. That is to say, it is necessary to bind the quick application identification and the quick application link corresponding to the quick application identification, so that when the portal control is triggered, the quick application corresponding to the above quick application identification can be accessed according to the quick application link bound to the portal control.
  • the aforementioned quick app link used to access the quick app may be a link address corresponding to the startup page of the quick app, or may be a link address corresponding to other pages of the quick app.
  • the aforementioned quick application link may be a link address corresponding to the control interface of the device.
  • Step S250 When a trigger operation on the entry control is monitored, a software development kit (SDK) corresponding to the quick application identifier is obtained.
  • SDK software development kit
  • the quick application can be subsequently used.
  • subsequent users need to manage and control the device through the quick application, and also need to perform operations such as network access.
  • the manufacturer When entering the network, the manufacturer’s network configuration process uses a private protocol. In order not to expose the protocol, it is necessary to use the SDK provided by the manufacturer to implement the equipment network configuration.
  • the subsequent fast application interface detects a control instruction, the client will receive an instruction instruction from the fast application to pass the fast application engine, and the instruction instruction is used to instruct the client to send the control instruction to the server by calling the SDK.
  • the quick application identifier can be used to obtain the SDK corresponding to the quick application identifier. Since the above quick application identifier corresponds to the device information, the manufacturer SDK corresponding to the device can be obtained.
  • obtaining the SDK corresponding to the fast application identifier may include:
  • the device of the same manufacturer may have been added before the purchase of the device.
  • the device of the same manufacturer may have been added before, so before loading the SDK this time, the SDK corresponding to the application ID has been loaded, that is, the manufacturer's SDK. Therefore, it can be judged whether the client has currently loaded the SDK corresponding to the fast application identifier to determine whether it is necessary to obtain the SDK from the server of the manufacturer.
  • the SDK corresponding to the quick application identifier can be obtained from the server. Specifically, the SDK can be obtained from the manufacturer's server through the server corresponding to the client, and then after the server corresponding to the client receives the SDK, it sends it to the client, so that the client can receive the SDK correspondingly.
  • Step S260 Load the SDK on the client.
  • the SDK after obtaining the SDK corresponding to the aforementioned quick application identifier, the SDK can be loaded on the client.
  • the corresponding relationship between the SDK and the aforementioned fast application can be established, so that when the fast application needs to use the SDK, the loaded SDK can be called to complete the corresponding operation.
  • the adding method of the quick application may also include:
  • prompt information for prompting the user to enter the network for the device is output; and the device enters the network according to the received network entry operation and the SDK.
  • a prompt message prompting the user to access the network can be output, so that the user can access the device according to the prompt information.
  • the prompt information may include prompting the control device to enter the network configuration mode, select a connected wifi hotspot or enter wifi information (such as name, password, etc.), so that the mobile terminal can send the wifi information to the device entering the network configuration mode .
  • the above prompt information is only an example, and does not represent a limitation on the prompt information that prompts the user to connect the device to the network in the embodiment of the present application.
  • the specific prompt information can be set according to the network distribution method.
  • Network access operations may include wifi information input operations, wifi information selection operations, etc.
  • the specific network access operations may not be limited.
  • the network access operation can send network access information containing wifi information to the device according to the network access operation, so that the device can connect to the network according to the wifi information, and use the SDK to send device information, address information and other information to the manufacturer's server , So that the manufacturer’s server can control the device.
  • quick applications can be added to the purchased device, and the device can be connected to the network.
  • the user can quickly access the device to the network, which is convenient for subsequent control of the device.
  • Step S270 Query whether the electronic device where the client is installed has a client corresponding to the device.
  • the client corresponding to the purchased device refers to the manufacturer of the device.
  • the corresponding client After adding the above quick application, it means that the device of the manufacturer can be controlled through the quick application, without the need to control the device through the client corresponding to the device.
  • the client corresponding to the aforementioned device can be deleted. Therefore, it is possible to query whether the electronic device has a client corresponding to the purchased device.
  • the program installation list can be obtained by requesting system permissions, and then according to the installation list, it is determined whether the client corresponding to the device is installed.
  • Step S280 If the client corresponding to the device is installed, output a prompt message for prompting the user whether to delete the client corresponding to the device.
  • the user may be prompted to delete the client to save the storage space of the electronic device.
  • a pop-up prompt or voice prompt can be used to prompt the user whether to delete the prompt information of the client corresponding to the aforementioned device.
  • Step S290 When receiving an instruction to delete the client corresponding to the device, request the system to delete the client corresponding to the device.
  • the instruction input by the user can be detected.
  • the system can be requested to delete the client corresponding to the above device, so as to save the storage space of the electronic device. effect.
  • the method for adding a quick application is to confirm the quick application identifier corresponding to the purchased at least one device when the purchase record of at least one device purchased through the HTML5 mall page embedded in the client is monitored, and then The entry space corresponding to the quick app logo is added to the interactive interface of the client, and the corresponding relationship between the entry control and the quick app link is established.
  • the quick application corresponding to the purchased device can be added to the client, which avoids the user's subsequent need to go through tedious steps to add a quick application, which improves the user experience.
  • the user is also prompted to delete the client corresponding to the previously installed purchased device, which can save the storage space of the electronic device.
  • FIG. 9 another embodiment of the present application provides a quick application adding method, which can be applied to electronic devices, and the quick application adding method may include:
  • Step S310 Monitor the purchase record of the device purchased through the HTML5 mall page embedded in the client.
  • Step S320 When the purchase record of at least one device is monitored, confirm the quick application identifier corresponding to the at least one device.
  • Step S330 Add an entry control corresponding to the quick application identifier and display it on the interactive interface of the client.
  • Step S340 Establish a corresponding relationship between the entry control and the quick application link corresponding to the quick application identifier, and the quick application link is used to access the quick application corresponding to the quick application identifier.
  • steps S310 to S340 can refer to the content in the previous embodiment, which will not be repeated here.
  • Step S350 Obtain a software development kit (SDK) corresponding to the fast application identifier.
  • SDK software development kit
  • the SDK corresponding to the quick application identifier can be actively acquired and the SDK can be loaded.
  • the SDK corresponding to the quick application identifier please refer to the content of the previous embodiment, which will not be repeated here.
  • Step S360 Load the SDK on the client.
  • step S360 can refer to the content in the previous embodiment, which will not be repeated here.
  • the user after loading the SDK, the user can also be prompted to connect to the device and perform the network access process. In addition, the user can also be prompted to delete the client corresponding to the above device. For details, please refer to the content of the above embodiment , I won’t repeat it here.
  • Step S370 Arrange entry controls corresponding to all quick applications in the client according to the set rules.
  • the portal controls may be arranged so that the user can find the portal controls corresponding to the corresponding device. Therefore, the entry controls corresponding to all quick apps can be arranged according to the set rules.
  • step S370 may include:
  • Step S371 Classify all the entry controls of the quick application.
  • classifying all quick apps may include: classifying the entry controls of all quick apps according to the attribute information of the quick apps, the attribute information includes: the adding time of the quick apps, the manufacturer of the device corresponding to the quick apps, or The frequency of use of fast apps. For example, when the attribute information is the adding time of the quick app, it is divided into multiple time periods according to the time period to which the added time belongs, and each time period is used as a category to classify the entry controls of the quick app.
  • the quick app corresponding to the device of the same manufacturer can be used as a category to classify the entry controls of the quick app.
  • the attribute information is the frequency of use of the quick application, it can be divided into multiple levels according to the order of the use frequency from high to low, and each level corresponds to a category to classify the entry controls of the quick application.
  • Step S372 According to the classification result, move the entry controls of all the quick apps to the folder corresponding to the corresponding classification.
  • the classification result is obtained, and then the multiple entry controls of the quick application are moved to the folder corresponding to the corresponding classification according to the classification result.
  • the folder can be automatically generated according to the category that appears in the classification result. For example, when five categories of quick application entry controls appear in the classification result, five folders are automatically generated so that the entry controls of different categories of quick application can be placed Into folders corresponding to different categories. After the move is complete, you can also name each folder, either based on the category name of the above classification, or user-defined naming. The specific naming method is not limited.
  • the method for adding a quick application is to confirm the quick application identifier corresponding to the purchased at least one device when the purchase record of at least one device purchased through the HTML5 mall page embedded in the client is monitored, and then The entry space corresponding to the quick app logo is added to the interactive interface of the client, and the corresponding relationship between the entry control and the quick app link is established, and the SDK is also loaded to facilitate subsequent network access operations.
  • the quick application corresponding to the purchased device can be added to the client, which avoids the user's subsequent need to go through tedious steps to add the quick application and enhance the user experience.
  • the entry controls are arranged to increase the cleanliness of the interface so that users can quickly find the corresponding controls.
  • the quick application adding device 500 is applied to electronic equipment.
  • the quick application adding device 500 includes: a record monitoring module 510, a quick application acquiring module 520, and a quick application adding module 530 .
  • the record monitoring module 510 is used to monitor purchase records of devices purchased through the HTML5 mall page embedded in the client; the quick application acquisition module 520 is used to confirm the purchase records of at least one device when the purchase records of at least one device are monitored.
  • a quick application identifier corresponding to at least one device; the quick application adding module 530 is configured to add a quick application corresponding to the quick application identifier to the client according to the quick application identifier.
  • the quick application adding module 530 includes: a control adding unit 531 and a control binding unit 532.
  • the control adding unit 531 is used to add the entry control corresponding to the quick application identifier and display it on the interactive interface of the client;
  • the control binding unit 532 is used to establish the entry control and the quick application The corresponding relationship of the quick application link corresponding to the application identifier, where the quick application link is used to access the quick application corresponding to the quick application identifier.
  • the device 400 for adding a quick application may also include a toolkit acquisition module and a toolkit loading module.
  • the toolkit obtaining module is used to obtain the software development kit (SDK) corresponding to the fast application identifier when the trigger operation of the entry control is monitored; the toolkit loading module is used to load the SDK in the Client.
  • SDK software development kit
  • the quick application adding module 530 may be specifically configured to: add an entry control corresponding to the quick application identification and display it on the interactive interface of the client; establish the entry control corresponding to the quick application identification The corresponding relationship of the quick application link, the quick application link is used to access the quick application corresponding to the quick application identification; obtain the software development kit (SDK) corresponding to the quick application identification; load the SDK in all The client.
  • SDK software development kit
  • the toolkit acquisition module or the quick application adding module 530 acquiring the software development kit (SDK) corresponding to the quick application identifier may include: determining whether the client has currently loaded the quick application Identify the corresponding SDK; if it is not loaded, obtain the SDK corresponding to the fast application identifier from the device server; if the SDK has been loaded, obtain the loaded SDK.
  • the device 500 for adding a quick application may further include a network access prompt module.
  • the network entry prompt module is used for outputting prompt information for prompting the user to enter the network for the device when a trigger operation on the entry control is detected.
  • the device 500 for adding a quick application may further include a network access execution module.
  • the network access execution module is used to perform network access to the device according to the received network access operation and the SDK.
  • the quick application acquisition module 520 may be specifically configured to: acquire device information of the device, where the device information includes at least one of manufacturer information, type information, and model information; based on the device information, Obtain the quick application identifier corresponding to the device.
  • the device 500 for adding a quick application may further include an application query module and an application prompt module.
  • the application query module is used to query whether the electronic device on which the client is installed has the client corresponding to the device; the application prompt module is used to output a prompt to prompt the user whether to delete the device if the client corresponding to the device is installed The prompt information of the client corresponding to the device.
  • the device 500 for adding a quick application may further include an application deletion module.
  • the application deletion module is configured to request the system to delete the client corresponding to the device when receiving an instruction to delete the client corresponding to the device.
  • the quick application adding device 500 may further include: a control arrangement module.
  • the control arrangement module may include an application classification unit and a control movement unit.
  • the application classification unit is used to classify the entry controls of all the quick applications; the control moving unit is used to move the entry controls of all the quick applications to the folder corresponding to the corresponding category according to the classification result.
  • the application classification unit may be specifically configured to: classify all the entry controls of the quick application according to the attribute information of the quick application, and the attribute information includes: the adding time of the quick application and the information of the device corresponding to the quick application The frequency of use by the manufacturer or fast app.
  • 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 solution provided by this application monitors the purchase record of a device purchased through the HTML5 mall page embedded in the client, and when the purchase record of at least one device is monitored, confirm the quick application identifier corresponding to the at least one device , According to the quick application identification, add the quick application corresponding to the quick application identification to the client. In this way, when a device is purchased online through the client, the quick application corresponding to the device can be added, saving adding time and improving user experience.
  • 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, and one or more application programs.
  • One or more application programs may be stored in the memory 120 and configured to be Or multiple processors 110 execute, and one or more programs are configured to execute the method described in the foregoing method embodiment.
  • 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 data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.
  • FIG. 14 shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application.
  • the computer-readable medium 800 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 800 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 800 includes a non-transitory computer-readable storage medium.
  • the computer-readable storage medium 800 has a storage space for the program code 810 for executing any method steps in the above-mentioned methods. These program codes can be read out from or written into one or more computer program products.
  • the program code 810 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)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种快应用的添加方法、装置、电子设备及存储介质,该快应用添加方法应用于客户端,该快应用添加方法包括:监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。本方法可以快捷的添加快应用。

Description

快应用的添加方法、装置、电子设备及存储介质 技术领域
本申请涉及电子设备技术领域,更具体地,涉及一种快应用的添加方法、装置、电子设备及存储介质。
背景技术
电子设备,例如电脑、手机等,已经成为人们日常生活中最常用的消费型电子产品之一。使用者可以在电子设备上安装应用来实现各种各样的功能,比如,可以在电子设备安装信息聚合类应用,从而通过该聚合类应用获得丰富的各类型信息,如新闻类信息、音视频信息等。目前,存在着一些如政务应用之类的不常用应用,使用者需要通过这类应用来实现一些特殊的功能,比如在线预约等。然而,正是由于其特殊性,使用者在实现需要的功能之后,通常在很长的时间内不会再次使用,导致电子设备存储空间的不必要浪费。
发明内容
鉴于上述问题,本申请提出了一种快应用的添加方法、装置、电子设备及存储介质,以解决上述问题。
第一方面,本申请实施例提供了一种快应用的添加方法,应用于客户端,所述方法包括:监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
第二方面,本申请实施例提供了一种快应用的添加装置,其特征在于,应用于客户端,所述装置包括:记录监测模块、快应用获取模块以及快应用添加模块,其中,所述记录监测模块用于监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;所述快应用获取模块用于在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;所述快应用添加模块用于根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
第三方面,本申请实施例提供了一种电子设备,包括:一个或多个处理器;存储器;一个或多个应用程序,其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述一个或多个处理器执行,所述一个或多个程序配置用于执行上述第一方面提供的快应用的添加方法。
第四方面,本申请实施例提供了一种计算机可读取存储介质,所述计算机可读取存储介质中存储有程序代码,所述程序代码可被处理器调用执行上述第一方面提供的快应用的添加方法。
本申请提供的方案,监测通过嵌入在客户端内的HTML5商城页面购买设备的购买记录,在监测到至少一个设备的购买记录时,确认与该至少一个设备对应的快应用标识,根据快应用标识,将与快应用标识对应的快应用添加于客户端。从而实现通过客户端线上购买设备时,即可将设备对应的快应用进行添加,节省添加时间,提升用户体验。
附图说明
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例, 对于本领域技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1示出了本申请实施例提出的一种智能家居系统的架构示意图。
图2示出了本申请实施例提出的另一种智能家居系统的架构示意图;
图3示出了本申请实施例提出的一种快应用引擎架构的示意图。
图4示出了本申请实施例提出的快应用的添加方法运行环境示意图。
图5示出了根据本申请一个实施例的快应用的添加方法流程图。
图6示出了根据本申请另一个实施例的快应用的添加方法流程图。
图7示出了根据本申请实施例的快应用的添加方法中步骤S220的流程图。
图8示出了根据本申请实施例提供的一种显示效果示意图。
图9示出了根据本申请又一个实施例的快应用的添加方法流程图。
图10示出了根据本申请实施例的快应用的添加方法中步骤S370的流程图。
图11示出了根据本申请一个实施例的快应用的添加装置的一种框图。
图12示出了根据本申请一个实施例的快应用的添加装置中快应用添加模块的框图。
图13是本申请实施例的用于执行根据本申请实施例的快应用的添加方法的电子设备的框图。
图14是本申请实施例的用于保存或者携带实现根据本申请实施例的快应用的添加方法的程序代码的存储单元。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案,下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述。
随着科技水平的进步,智能家居深入各个家庭中,由于其带来的便利性,深受众多家庭的喜爱。智能家居通过物联网技术将家中的各种智能家居设备(如空调、照明灯、冰箱、洗衣机等)连接到一起,提供家电控制、照明控制、电话远程控制、室内外遥控、防盗报警、环境监测、暖通控制、红外转发以及可编程定时控制等多种控制。
由于电子设备上安装应用来实现各种各样的功能,通过安装用于管理和控制家居设备的应用程序于电子设备,可以远程实现对于家居设备的管理和控制。其中,家居设备可以是空调、照明灯具、智能灯、智能摄像头、智能插座、无线开关、智能窗帘电机、智能音箱以及各类传感器(例如人体传感器、门窗传感器、烟雾报警器等)。
请参见图1,目前通过电子设备对家居设备进行管理和控制,通常是通过电子设备100可以通过与智能网关300建立无线连接,并且家居设备200与智能网关300建立无线连接的方式,实现电子设备100与家居设备之间的数据交互。另外,电子设备100以及智能网关300与服务器400通信连接,电子设备100可以通过服务器400以及智能网关300,与家居设备进行数据交互。
请参见图2,电子设备100可以与第一云服务器402通信连接,实现与第一云服务器402之间的数据交互。家居设备200通过智能网关300,与第二云服务器401通信连接,实现与第二与服务器401之间的数据交互。另外,第一云服务器402与第二云服务器401之间可以进行数据交互,从而电子设备100可以通过第一云服务器402、第二云服务器404以及智能网关300,实现与家居设备200之间的数据交互。
目前不同厂商的家居设备通常需要通过不同的应用程序进行控制,也就是说,不同厂商的家居设备的应用程序与不同厂商的服务器之间通信,需要安装较多的应用程序,从而占用了电子设备的较多的存储空间。
而随着快应用的普及,移动终端开发者更期望通过快应用来实现与前述客户端相同的功能,以便提升智能家居功能的开发效率,并同时节约移动终端的存储空间。其 中,快应用是一种基于终端设备硬件平台的新型应用形态,无需安装,即点即用,又兼具原生应用体验(性能、系统整合、交互等)。如图3所示的快应用引擎的结构示意图,快应用的前端设计借鉴并整合了主流前端框架(Vue,React等)的设计思路:以组件化的方式构建应用,以数据绑定为核心的MVVM设计模式,以V-DOM的方式提升性能,同时选择了简洁清晰的类Vue的模板。
发明人经过长期的研究发现,在添加设备的快应用时,需要用户根据操作选择设备的厂商、类型、型号等消息,因此需要用户进行繁琐的操作。因此,发明人提出了根据用户在商城页面购买设备的购买记录,添加设备的快应用,节省用户的操作,并且便于后续对家居设备进行相关操作,提升了用户体验。
下面先结合附图对本申请实施例的应用环境进行介绍。
如图4所示,图4所示的电子设备100中,运行有快应用以及客户端110。其中快应用是运行于快应用引擎上,并且在快应用引擎中设置有客户端提供的扩展接口97。而在客户端110中设有与扩展接口97通信的扩展接口96。而客户端110可以通过扩展接口调用各个厂商的软件开发工具包(SDK,Software Development Kit)插件。例如,可以调用图中的厂商A的SDK插件111、厂商B的SDK插件112以及厂商C的SDK插件113。在这种情况下,在快应用中触发的数据处理指令可以通过设置在快应用引擎中的扩展接口97传递到客户端中的扩展接口96,进而再将数据处理指令传输给各个厂商的SDK插件。
进一步的,客户端110可以提供进入快应用的入口,也就是说,可以由客户端110进入快应用。快应用与该客户端110之间的通讯可以通过跨应用的通讯方式,如使用AIDL交互。具体的,客户端110与内嵌的快应用之间可以设置有参数传递的接口,用于客户端110与快应用之间的数据传递,例如,快应用与客户端110之间可以定义通道类接口,所有的接口函数使用一个通道类接口实现。在通过客户端110进入快应用时,客户端110可以指示快应用引擎,根据快应用的链接,访问相应的快应用,从而展示出快应用的界面。快应用的界面可以接收控制信息,并客户端110在获知该控制信息后,通过上述的SDK将控制信息传至家居设备的服务器,实现对家居设备的管理和控制。另外,快应用引擎还可以接收客户端110传递的信息,并且将需要显示的信息在快应用控制页面显示。
下面对本申请实施例的快应用的添加方法进行详细介绍。
请参阅图5,本申请实施例提供了一种快应用的添加方法,可应用于电子设备,该快应用的添加方法可以包括:
步骤S110:监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录。
在本申请实施例中,客户端内可以嵌入有HTML5商场页面。可以理解的,HTML5商城页面是指实现商城功能的超级文本标记语言5(HyperText Markup Language 5,HTML5)页面,HTML5是用于取代1999年所制定的HTML4.01和XHTML1.0标准的HTML标准版本。广义的HTML5指的是包括HTML、CSS和JavaScript在内的一套技术组合。HTML5可以减少浏览器对于需要插件的丰富性网络应用服务(plug-in-based rich internet application,RIA),如Adobe Flash、MicrosoftSilverlight、Oracle JavaFX的需求,并且提供更多能有效增强网络应用的标准集。其中,HTML5页面可简称H5页面。本申请实施例中的客户端可以支持H5页面嵌入,即H5页面可以嵌入在客户端内。作为一种方式,可以通过android webview控件加载html5页面部分,放置到客户端中,其中,webview是一个浏览器组件,在Android 4.3系统及其以下,内部采用Webkit渲染引擎。webview基于webkit内核,可以支持html5。
进一步的,客户端内可以设置与HTML5商城页面对应的控件,该控件可以与HTML5商城页面的链接对应,当该控件被触发操作所触发之后,可以访问该HTML5商城页面,并渲染出HTML5商城页面,从而实现在客户端内展示出HTML5商城页面。 在HTML5商城页面展示后,通过HTML5商城页面可以实现商品的购买。
在本申请实施例中,HTML5商城页面对应于商城的服务器,在访问HTML5商城页面时,则访问商城的服务器,以实现网上商品的购买。HTML5商城页面用于提供给用户购买设备,在用户通过HTML5商城页面购买设备后,商城的服务器可以获取到购买设备的购买记录。其中,上述设备可以是能够通过客户端中的快应用进行管理和控制的设备,也就是说,客户端中可以提供用于管理上述商城所出售的设备的快应用。购买记录可以包括购买的设备的设备信息、数量及价格等,设备信息可以包括设备的厂商信息、类型信息以及型号信息等。当然,具体的购买记录在本申请实施例中可以不作为限定。
在本申请实施例中,客户端可以通过客户端对应的服务器,从商城的服务器获取通过上述HTML5商城页面购买设备的购买记录,以实现监测通过上述HTML5商城页面购买设备的购买记录。其中,获取通过上述HTML5商城页面购买设备的购买记录,可以是实时获取,也可以是间隔指定时长获取,还可以是根据检测到的控制操作获取。当然,具体获取通过上述购买记录的方式在本申请实施例中可以不作为限定。可选的,客户端可以通过客户端对应的服务器,从商城服务器处实时获取通过上述HTML5商城页面购买设备的购买记录,以便准确的监测上述购买记录。
步骤S120:在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识。
在本申请实施例中,可以在监测到通过上述HTML5商城页面,购买至少一个设备的购买记录时,对购买的至少一个设备所对应的快应用进行添加。不同的设备由于厂商可能不同,而在管理和控制设备时,需要通过设备所对应的厂商服务器,因此,不同厂商的设备所对应的快应用不同。其中,快应用可以对应有快应用标识,快应用标识作为快应用的身份信息,用于区分不同的快应用。具体的快应用标识在本申请实施例中可以不作为限定,例如,快应用标识可以为快应用的身份ID。
另外,可以建立快应用标识与设备的对应关系,以便在添加快应用时,确定与设备所对应的快应用标识。作为一种方式,可以快应用标识与设备的对应关系,可以以列表的形式存储于安装客户端的电子设备内。列表中,每个设备均对应有一个快应用标识。
进一步的,在对购买的至少一个设备所对应的快应用进行添加时,可以根据快应用标识添加快应用,以将购买的至少一个设备所对应的快应用进行添加,以便后续使用该快应用管理和控制购买的设备。因此,可以确定购买的至少一个设备所对应的快应用标识,以添加快应用标识所对应的快应用。
在本申请实施例中,可以根据上述的购买记录中的设备信息,利用上述快应用标识与设备信息的对应关系,确定与该设备对应的快应用标识,以便后续根据快应用标识,将快应用标识所对应的快应用添加于客户端。
步骤S130:根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
在本申请实施例中,在获取到购买的至少一个设备所对应的快应用标识之后,则可以根据快应用标识,查找与快应用标识所对应的快应用,并将与快应用标识所对应的快应用添加于客户端,即添加与设备对应的快应用,以便用户后续通过添加的设备的快应用,对购买的设备进行管理和控制。
进一步的,在客户端内添加快应用标识所对应的快应用时,可以将快应用所对应的入口控件,并将该入口控件与需要访问的快应用进行绑定,以便在客户端内,可以通过快应用的入口控件访问到该快应用,展示出快应用界面,通过快应用界面实现对购买的设备进行管理和控制。其中,控件是指对数据和方法的封装,控件可以有自己的属性和方法,其中属性是控件数据的简单访问者,方法则是控件的一些简单而可见 的功能、控件创建过程包括设计、开发、调试(所谓的3Ds开发流程,即Design、Develop、Debug)工作,然后是控件的使用。
本申请实施例提供的快应用的添加方法,通过在监测到通过嵌入客户端内的HTML5商城页面购买的至少一个设备的购买记录时,确认与购买的至少一个设备对应的快应用标识,然后将与快应用标识对应的快应用添加于客户端,实现用户通过HTML5商城页面购买设备时,即可将购买的设备所对应的快应用添加于客户端,避免了用户后续需要通过繁琐的步骤,添加快应用,提升了用户体验。
请参阅图6,本申请另一个实施例提供了一种快应用的添加方法,可应用于电子设备,该快应用的添加方法可以包括:
步骤S210:监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录。
在本申请实施例中,步骤S210可以参阅上述实施例的内容,在此不再赘述。
步骤S220:在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识。
在本申请实施例中,由于不同厂商的设备可以通过不同厂商的快应用进行管理和控制,并且相同厂商的不同设备对应快应用中的控制界面不同,即不同设备的控制界面不同,因此在确认与购买的至少设备对应的快应用标识时,可以通过设备的设备信息,获取设备对应的快应用标识,以便添加设备对应的快应用。因此,请参见图7,步骤S220可以包括:
步骤S221:获取所述设备的设备信息,所述设备信息包括厂商信息、类型信息以及型号信息中的至少一种。
可以理解的是,由于监测到的购买至少一个设备的购买记录可以包括设备的设备信息,因此,可以根据上述购买记录,获取设备的设备信息。其中,设备信息可以包括厂商信息、类型信息以及型号信息中的至少一种。从而可以获取到设备的设备信息,以便根据设备的设备信息,获取与设备对应的快应用标识。当然,具体获取设备的厂商信息的方式在本申请实施例中可以不作为限定。
步骤S222:基于所述设备信息,获取与所述设备对应的快应用标识。
在本申请实施例中,作为一种方式,安装客户端的电子设备中存储有各个设备信息对应的快应用标识,以及设备信息与快应用的对应关系。在获取到设备的设备信息之后,则可以根据设备的设备信息,利用上述对应关系,即可从多个快应用标识中,查找与该设备的设备信息对应的快应用标识。作为另一种方式,客户端也可以根据设备信息,从服务器查询与该设备信息对应的快应用标识。具体基于设备信息获取与设备对应的快应用标识的方式可以不作为限定。
步骤S230:将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面。
在本申请实施例中,在根据快应用标识,添加快应用标识对应的快应用于客户端时,可以添加快应用标识对应的入口控件至客户端的交互界面,并将入口控件显示于客户端的交互界面中。其中,入口控件作为访问快应用标识对应的快应用的入口,在检测到对该入口控件的触发操作时,例如,按压操作、点击操作、单指滑动操作、双指滑动操作等,可以访问上述快应用,展示出快应用的界面。在一些实施方式中,可以根据快应用标识与入口控件的对应关系,查找与快应用标识所对应的入口控件,然后将查找到的入口控件添加于客户端的交互界面中。其中,入口控件具体添加于客户端的交互界面可以不作为限定,可以是客户端的主界面,也可以是客户端的其他界面。另外,不同设备的入口控件对应的图标不同,通过与设备对应的快应用标识,可以查找到与该设备对应的入口控件。并且添加于客户端的交互界面中的入口控件,可以包括有设备的设备信息,例如,设备的厂商、设备的类型、设备的型号等,也就是说入口控件对应的图标中可以包括有上述的设备信息。例如请参见图8,上述购买的设备的 设备名称为“设备7”,在添加入口控件155于客户端的交互界面154后,显示出的入口控件155的图标可以展示出设备的名称“设备7”。从而在客户端显示的所有设备的入口控件中,可以便于用户获知每个入口控件所对应的设备。
步骤S240:建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用。
在本申请实施例中,在添加上述快应用标识对应的控件后,还需要建立入口控件与快应用标识对应的快应用链接的对应关系,快应用链接用于访问快应用标识对应的快应用。也就是说,需要将快应用标识与快应用标识对应的快应用链接绑定,以便在触发入口控件时,根据入口控件绑定的快应用链接,访问上述快应用标识对应的快应用。
进一步的,上述用于访问快应用的快应用链接可以是该快应用的启动页面对应的链接地址,也可以是该快应用的其他页面对应的链接地址。可选的,由于在触发上述入口控件后,需要进入与设备对应的控制界面,因此,上述快应用链接可以是与设备的控制界面对应的链接地址。
步骤S250:在监测到对所述入口控件的触发操作时,获取与所述快应用标识对应的软件开发工具包(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。
步骤S260:将所述SDK加载于所述客户端。
在本申请实施例中,在获取到上述快应用标识对应的SDK之后,则可以将SDK加载于该客户端。另外,可以建立起该SDK与该上述快应用的对应关系,以便在快应用需要使用该SDK时,可以调用已加载的SDK完成相应的操作。
在本申请实施例中,在加载上述SDK之后,可以提示用户对设备进行入网。也可 以是后续检测到对入口控件的触发操作后,提示用户对设备进行入网。因此,该快应用的添加方法还可以包括:
当检测到对所述入口控件的触发操作时,输出用于提示用户对所述设备进行入网的提示信息;根据接收到的入网操作以及所述SDK对所述设备进行入网。
可以理解的是,在加载快应用标识对应的SDK,即厂商的SDK之后,如果检测到对入口控件的触发操作时,表示后续用户可能已经收到通过HTML5商城页面购买的设备,并且需要添加设备进行配网。因此可以输出提示用户进行入网的提示信息,以便用户根据提示信息对设备进行入网。作为一种方式,提示信息可以包括提示控制设备进入配网模式,选择已连接wifi热点或者输入wifi的信息(例如名称、密码等)等,以便移动终端将wifi信息发送至进入配网模式的设备。当然,上述提示信息仅为举例,并不代表对本申请实施例中提示用户对设备进行入网的提示信息的限定,具体的提示信息可以根据配网方法而设定。
进一步的,在输出用于提示用户对设备进行入网的提示信息之后,则可以检测用户的入网操作。入网操作可以包括wifi信息输入操作、wifi信息选择操作等,具体的入网操作可以不作为限定。在检测到入网操作时,则可以根据入网操作,发送包含wifi信息的入网信息至设备,使设备可以根据wifi信息连接至网络,并且利用SDK将设备信息、地址信息等信息,发送至厂商的服务器,以便厂商的服务器对设备进行控制。
从而通过上述的方法,实现对购买的设备添加快应用,并且可以对设备进行入网。在设备入网后,则可以利用上述快应用对设备进行控制。也就是说,在用户通过HTML5商城页面购买设备后,即可添加上述快应用,而无需用户在收到设备后,添加设备时需要进行繁琐的操作,才能对快应用进行添加。另外,使得用户可以在接收到设备后,对设备可以快速入网,便于后续对设备进行控制。
步骤S270:查询安装所述客户端的电子设备是否安装有所述设备对应的客户端。
在本申请实施例中,在添加用于管理和控制购买的设备的快应用之前,可能存在安装有该购买的设备所对应的客户端,购买的设备所对应的客户端指该设备的厂商所对应的客户端。而在添加上述快应用之后,表示可以通过快应用对该厂商的设备进行控制,无需通过该设备所对应的客户端,对设备进行控制。为节省电子设备的存储空间,可以删除先上述设备对应的客户端。因此,可以查询电子设备是否安装有购买的设备对应的客户端,具体可以通过请求系统权限,获取程序安装列表,然后根据安装列表,判断是否安装有上述设备对应的客户端。
步骤S280:如果安装有所述设备对应的客户端,则输出用于提示用户是否删除所述设备对应的客户端的提示信息。
可以理解的是,当查询到电子设备安装有上述设备对应的客户端时,则可以提示用户删除客户端,以节省电子设备的存储空间。具体可以通过弹窗提示,或者语音提示等方式,提示用户是否删除上述设备对应的客户端的提示信息。
步骤S290:当接收到指示删除所述设备对应的客户端的指令时,请求所述系统删除所述设备对应的客户端。
在本申请实施例中,在进行上述输出用于提示用户是否删除客户端的提示信息之后,则可以对用户输入的指令进行检测。当检测到指示删除上述设备对应的客户端的指令时,由于客户端没有卸载或者删除上述设备对应的客户端的权限,因此,可以请求系统删除上述设备对应的客户端,达到节省电子设备的存储空间的效果。
本申请实施例提供的快应用的添加方法,通过在监测到通过嵌入客户端内的HTML5商城页面购买的至少一个设备的购买记录时,确认与购买的至少一个设备对应的快应用标识,然后将与快应用标识对应的入口空间添加于客户端的交互界面,并建立入口控件与快应用链接的对应关系。实现用户通过HTML5商城页面购买设备时,即可将购买的设备所对应的快应用添加于客户端,避免了用户后续需要通过繁琐的步骤, 添加快应用,提升了用户体验。另外,还对提示用户删除此前安装的购买的设备对应的客户端,可以节省电子设备的存储空间。
请参阅图9,本申请又一个实施例提供了一种快应用的添加方法,可应用于电子设备,该快应用的添加方法可以包括:
步骤S310:监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录。
步骤S320:在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识。
步骤S330:将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面。
步骤S340:建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用。
在本申请实施例中,步骤S310至步骤S340可以参阅上个实施例中的内容,在此不再赘述。
步骤S350:获取与所述快应用标识对应的软件开发工具包(SDK)。
与上个实施例不同的是,本实施例中可以在建立上述入口控件与快应用标识对应的快应用链接的对应关系之后,可以主动获取快应用标识对应的SDK,并对SDK进行加载。具体获取与快应用标识对应的SDK,可以参阅上个实施例的内容,在此不再赘述。
步骤S360:将所述SDK加载于所述客户端。
在本申请实施例中,步骤S360可以参阅上个实施例中的内容,在此不再赘述。
在本申请实施例中,在加载SDK后,也可以提示用户对设备进行入网,并进行入网等过程,另外,也可以进行提示用户删除上述设备对应的客户端,具体可以参阅上述实施例的内容,在此不再赘述。
步骤S370:根据设定规则,对所述客户端内的所有快应用对应的入口控件进行排布。
在本申请实施例中,在添加上述入口控件之后,可以将入口控件进行排布,以便于用户查找相应的设备对应的入口控件。因此,可以根据设定规则,对所有快应用对应的入口控件进行排布。
作为一种方式,请参见图10,步骤S370可以包括:
步骤S371:对所述所有快应用的入口控件进行分类。
可以理解的是,可以对快应用分类,以便后续将所有快应用的入口控件按照分类结果进行排布。其中,对所有快应用分类可以包括:根据快应用的属性信息,对所述所有快应用的入口控件进行分类,所述属性信息包括:快应用的添加时间、快应用对应的设备的厂商、或者快应用的使用频率。例如,属性信息为快应用的添加时间时,按照添加时间所属的时间段,分成多个时间段,每个时间段作为一个类别,对快应用的入口控件进行分类。又例如,属性信息为快应用对应的设备的厂商时,可以将相同厂商的设备对应的快应用作为一个类别,对快应用的入口控件进行分类。再例如,属性信息为快应用的使用频率时,可以按照使用频率从高到低的顺序,分为多个等级,每个等级则对应一个类别,对快应用的入口控件进行分类。
步骤S372:根据分类结果,将所述所有快应用的入口控件移动至相应分类对应的文件夹中。
将所有快应用的入口控件分类完成后得到分类结果,再根据该分类结果将多个快应用的入口控件移至相应分类对应的文件夹中。其中,文件夹可以是根据分类结果出现的类别自动生成,例如,分类结果中出现五种类别的快应用的入口控件时,则自动生成五个文件夹,以便不同类别的快应用的入口控件放入不同类别对应的文件夹中。在移动完成后,还可以对每个文件夹进行命名,可以是根据上述分类的类别名称进行 命名,也可以是用户自定义命名,具体命名的方式可以不作为限定。
本申请实施例提供的快应用的添加方法,通过在监测到通过嵌入客户端内的HTML5商城页面购买的至少一个设备的购买记录时,确认与购买的至少一个设备对应的快应用标识,然后将与快应用标识对应的入口空间添加于客户端的交互界面,并建立入口控件与快应用链接的对应关系,还对SDK进行加载,便于后续的入网操作。实现用户通过HTML5商城页面购买设备时,即可将购买的设备所对应的快应用添加于客户端,避免了用户后续需要通过繁琐的步骤,添加快应用,提升了用户体验。另外,还在添加新的入口控件后,对入口控件进行排布,增加界面的整洁感,便于用户可以快速查找相应控件。
请参阅图11,图11示出了本申请一个实施例提供的快应用的添加装置500的模块框图。该快应用的添加装置500应用于电子设备,下面将针对图11所示的装置进行阐述,所述快应用的添加装置500包括:记录监测模块510、快应用获取模块520以及快应用添加模块530。所述记录监测模块510用于监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;所述快应用获取模块520用于在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;所述快应用添加模块530用于根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
作为一种方式,请参见图12,所述快应用添加模块530包括:控件添加单元531以及控件绑定单元532。其中,所述控件添加单元531用于将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面;所述控件绑定单元532用于建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用。
进一步的,该快应用的添加装置400还可以包括工具包获取模块以及工具包加载模块。工具包获取模块用于在监测到对所述入口控件的触发操作时,获取与所述快应用标识对应的软件开发工具包(SDK);工具包加载模块用于将所述SDK加载于所述客户端。
作为另一种方式,快应用添加模块530可以具体用于:将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面;建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用;获取与所述快应用标识对应的软件开发工具包(SDK);将所述SDK加载于所述客户端。
在本申请实施例中,工具包获取模块或者快应用添加模块530获取与所述快应用标识对应的软件开发工具包(SDK),可以包括:判断所述客户端当前是否已加载所述快应用标识对应的SDK;如果没有加载,则从设备服务器获取所述快应用标识对应的SDK;如果已加载了所述SDK,则获取已加载的所述SDK。
在本申请实施例中,该快应用的添加装置500还可以包括入网提示模块。入网提示模块用于当检测到对所述入口控件的触发操作时,输出用于提示用户对所述设备进行入网的提示信息。
在本申请实施例中,该快应用的添加装置500还可以包括入网执行模块。入网执行模块用于根据接收到的入网操作以及所述SDK对所述设备进行入网。
在本申请实施例中,快应用获取模块520可以具体用于:获取所述设备的设备信息,所述设备信息包括厂商信息、类型信息以及型号信息中的至少一种;基于所述设备信息,获取与所述设备对应的快应用标识。
在本申请实施例中,该快应用的添加装置500还可以包括:应用查询模块以及应用提示模块。应用查询模块用于查询安装所述客户端的电子设备是否安装有所述设备对应的客户端;应用提示模块用于如果安装有所述设备对应的客户端,则输出用于提示用户是否删除所述设备对应的客户端的提示信息。
进一步的,该快应用的添加装置500还可以包括:应用删除模块。应用删除模块用于当接收到指示删除所述设备对应的客户端的指令时,请求所述系统删除所述设备对应的客户端。
在本申请实施例中,该快应用的添加装置500还可以包括:控件排布模块。控件排布模块可以包括应用分类单元以及控件移动单元。应用分类单元用于对所述所有快应用的入口控件进行分类;控件移动单元用于根据分类结果,将所述所有快应用的入口控件移动至相应分类对应的文件夹中。
进一步的,应用分类单元可以具体用于:根据所述快应用的属性信息,对所述所有快应用的入口控件进行分类,所述属性信息包括:快应用的添加时间、快应用对应的设备的厂商、或者快应用的使用频率。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述装置和模块的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,模块相互之间的耦合可以是电性,机械或其它形式的耦合。
另外,在本申请各个实施例中的各功能模块可以集成在一个处理模块中,也可以是各个模块单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
综上所述,本申请提供的方案,监测通过嵌入在客户端内的HTML5商城页面购买设备的购买记录,在监测到至少一个设备的购买记录时,确认与该至少一个设备对应的快应用标识,根据快应用标识,将与快应用标识对应的快应用添加于客户端。从而实现通过客户端线上购买设备时,即可将设备对应的快应用进行添加,节省添加时间,提升用户体验。
请参考图13,其示出了本申请实施例提供的一种电子设备的结构框图。该电子设备100可以是智能手机、平板电脑、电子书等能够运行应用程序的电子设备。本申请中的电子设备100可以包括一个或多个如下部件:处理器110、存储器120以及一个或多个应用程序,其中一个或多个应用程序可以被存储在存储器120中并被配置为由一个或多个处理器110执行,一个或多个程序配置用于执行如前述方法实施例所描述的方法。
处理器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在使用中所创建的数据(比如电话本、音视频数据、聊天记录数据)等。
请参考图14,其示出了本申请实施例提供的一种计算机可读存储介质的结构框图。该计算机可读介质800中存储有程序代码,所述程序代码可被处理器调用执行上述方法实施例中所描述的方法。
计算机可读存储介质800可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM、硬盘或者ROM之类的电子存储器。可选地,计算机可读存储介质800包括非易失性计算机可读介质(non-transitory computer-readable storage medium)。计算机可读存储介质800具有执行上述方法中的任何方法步骤的程序代码810的存储空间。这些程序代码可以从一个或者多个计算机程序产品中读出或者写入到这一个或者多个计算机程序产品中。程序代码810可以例如以适当形式进行压缩。
最后应说明的是:以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不驱使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (20)

  1. 一种快应用的添加方法,其特征在于,应用于客户端,所述方法包括:
    监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;
    在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;
    根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
  2. 根据权利要求1所述的方法,其特征在于,所述将与所述快应用标识对应的快应用添加于所述客户端,包括:
    将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面;
    建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用。
  3. 根据权利要求2所述的方法,其特征在于,在所述建立所述入口控件与所述快应用标识对应的快应用链接的对应关系之后,所述方法还包括:
    在监测到对所述入口控件的触发操作时,获取与所述快应用标识对应的软件开发工具包(SDK,Software Development Kit);
    将所述SDK加载于所述客户端。
  4. 根据权利要求1所述的方法,其特征在于,所述将与所述快应用标识对应的快应用添加于所述客户端,包括:
    将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面;
    建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用;
    获取与所述快应用标识对应的软件开发工具包(SDK);
    将所述SDK加载于所述客户端。
  5. 根据权利要求3或4所述的方法,其特征在于,所述获取与所述快应用标识对应的软件开发工具包(SDK),包括:
    判断所述客户端当前是否已加载所述快应用标识对应的SDK;
    如果没有加载,则从设备服务器获取所述快应用标识对应的SDK。
  6. 根据权利要求5所述的方法,其特征在于,所述获取与所述快应用标识对应的软件开发工具包(SDK),还包括:
    如果已加载了所述SDK,则获取已加载的所述SDK。
  7. 根据权利要求3-6任一项所述的方法,其特征在于,在将与所述快应用标识对应的快应用添加于所述客户端之后,所述方法还包括:
    当检测到对所述入口控件的触发操作时,输出用于提示用户对所述设备进行入网的提示信息。
  8. 根据权利要求7所述的方法,其特征在于,在所述当检测到对所述入口控件的触发操作时,输出用于提示用户对所述设备进行入网的提示信息之后,所述方法还包括:
    根据接收到的入网操作以及所述SDK对所述设备进行入网。
  9. 根据权利要求1-8任一项所述的方法,其特征在于,所述确认与所述至少一个设备对应的快应用标识,包括:
    获取所述设备的设备信息,所述设备信息包括厂商信息、类型信息以及型号信息中的至少一种;
    基于所述设备信息,获取与所述设备对应的快应用标识。
  10. 根据权利要求1-9任一项所述的方法,其特征在于,将与所述快应用标识对应的快应用添加于所述客户端之后,所述方法还包括:
    查询安装所述客户端的电子设备是否安装有所述设备对应的客户端;
    如果安装有所述设备对应的客户端,则输出用于提示用户是否删除所述设备对应的客户端的提示信息。
  11. 根据权利要求10所述的方法,其特征在于,在所述如果安装有所述设备对应的客户端,则输出用于提示用户是否删除所述设备对应的客户端的提示信息之后,所述方法还包括:
    当接收到指示删除所述设备对应的客户端的指令时,请求系统删除所述设备对应的客户端。
  12. 根据权利要求1-11任一项所述的方法,其特征在于,在将与所述快应用标识对应的快应用添加于所述客户端之后,所述方法还包括:
    当检测到对所述快应用的删除操作时,将所述快应用从所述客户端内删除。
  13. 根据权利要求1-4任一项所述的方法,其特征在于,在将与所述快应用标识对应的快应用添加于所述客户端之后,所述方法还包括:
    根据设定规则,对所述客户端内的所有快应用对应的入口控件进行排布。
  14. 根据权利要求13所述的方法,其特征在于,所述根据设定规则,对所述客户端内的所有快应用对应的入口控件进行排布,包括:
    对所述所有快应用的入口控件进行分类;
    根据分类结果,将所述所有快应用的入口控件移动至相应分类对应的文件夹中。
  15. 根据权利要求14所述的方法,其特征在于,所述对所述所有快应用的入口控件进行分类,包括:
    根据所述快应用的属性信息,对所述所有快应用的入口控件进行分类,所述属性信息包括:快应用的添加时间、快应用对应的设备的厂商、或者快应用的使用频率。
  16. 一种快应用的添加装置,其特征在于,应用于客户端,所述装置包括:记录监测模块、快应用获取模块以及快应用添加模块,其中,
    所述记录监测模块用于监测通过嵌入所述客户端内的HTML5商城页面购买设备的购买记录;
    所述快应用获取模块用于在监测到至少一个设备的购买记录时,确认与所述至少一个设备对应的快应用标识;
    所述快应用添加模块用于根据所述快应用标识,将与所述快应用标识对应的快应用添加于所述客户端。
  17. 根据权利要求16所述的装置,其特征在于,所述快应用添加模块包括:控件添加单元以及控件绑定单元,其中,
    所述控件添加单元用于将与所述快应用标识对应的入口控件添加并显示于所述客户端的交互界面;
    所述控件绑定单元用于建立所述入口控件与所述快应用标识对应的快应用链接的对应关系,所述快应用链接用于访问所述快应用标识对应的快应用。
  18. 根据权利要求17所述的装置,其特征在于,所述装置还包括工具包获取模块以及工具包加载模块,其中,
    所述工具包获取模块用于在监测到对所述入口控件的触发操作时,获取与所述快应用标识对应的软件开发工具包(SDK,Software Development Kit);
    所述工具包加载模块用于将所述SDK加载于所述客户端。
  19. 一种电子设备,其特征在于,包括:
    一个或多个处理器;
    存储器;
    一个或多个应用程序,其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述一个或多个处理器执行,所述一个或多个程序配置用于执行如权利要求 1-16任一项所述的方法。
  20. 一种计算机可读取存储介质,其特征在于,所述计算机可读取存储介质中存储有程序代码,所述程序代码可被处理器调用执行如权利要求1-16任一项所述的方法。
PCT/CN2019/075946 2019-02-22 2019-02-22 快应用的添加方法、装置、电子设备及存储介质 WO2020168570A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/075946 WO2020168570A1 (zh) 2019-02-22 2019-02-22 快应用的添加方法、装置、电子设备及存储介质
CN201980081078.1A CN113196235A (zh) 2019-02-22 2019-02-22 快应用的添加方法、装置、电子设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/075946 WO2020168570A1 (zh) 2019-02-22 2019-02-22 快应用的添加方法、装置、电子设备及存储介质

Publications (1)

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

Family

ID=72143989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/075946 WO2020168570A1 (zh) 2019-02-22 2019-02-22 快应用的添加方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN113196235A (zh)
WO (1) WO2020168570A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115633058A (zh) * 2022-09-30 2023-01-20 中国第一汽车股份有限公司 车载设备的处理方法及处理装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130231991A1 (en) * 2012-03-05 2013-09-05 Ingersoll-Rand Company Apparatus, method, and system for conducting a transaction
CN109284144A (zh) * 2018-08-27 2019-01-29 维沃移动通信有限公司 一种快应用处理方法及移动终端

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107682238B (zh) * 2017-09-15 2020-10-16 阿里巴巴(中国)有限公司 智能家居平台设备及终端电子设备
CN108469968A (zh) * 2018-02-08 2018-08-31 维沃移动通信有限公司 一种应用程序处理方法及移动终端
CN108549568B (zh) * 2018-04-18 2020-01-31 Oppo广东移动通信有限公司 应用入口处理方法、装置、存储介质及电子设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130231991A1 (en) * 2012-03-05 2013-09-05 Ingersoll-Rand Company Apparatus, method, and system for conducting a transaction
CN109284144A (zh) * 2018-08-27 2019-01-29 维沃移动通信有限公司 一种快应用处理方法及移动终端

Also Published As

Publication number Publication date
CN113196235A (zh) 2021-07-30

Similar Documents

Publication Publication Date Title
WO2020223854A1 (zh) 设备配网方法、装置、电子设备及存储介质
US10402483B2 (en) Screenshot processing device and method for same
CN108289110B (zh) 设备关联方法、装置、终端设备和操作系统
US11204681B2 (en) Program orchestration method and electronic device
US20200357007A1 (en) Page data acquisition method, apparatus, server, electronic device and computer readable medium
US9372885B2 (en) System and methods thereof for dynamically updating the contents of a folder on a device
TW201814510A (zh) 介面移動方法、裝置、智慧型終端機、伺服器和操作系統
CN109428911A (zh) 设备控制方法、装置、终端设备和操作系统
CN107948231B (zh) 基于场景的服务提供方法、系统和操作系统
CN108614689B (zh) 场景服务的生成方法、装置和终端设备
CN107741844B (zh) 一种应用安装包的生成方法和装置
WO2020228013A1 (zh) 账号关联方法、装置、系统、服务器以及存储介质
TW201814545A (zh) 多服務集成方法、裝置、智慧型終端、伺服器和操作系統
CN109800135B (zh) 一种信息处理方法及终端
WO2020228033A1 (zh) Sdk插件的加载方法、装置、移动终端以及存储介质
CN102946343A (zh) 访问音视频社区虚拟房间的方法和系统
WO2020168568A1 (zh) 数据处理方法、装置、电子设备及可读存储介质
CN105786455B (zh) 一种数据处理方法、装置及终端
WO2022228156A1 (zh) 一种策略编排处理方法、装置、设备、系统及存储介质
CN105183493A (zh) 网络信息的显示方法和装置
TWI738832B (zh) 基於場景的應用操作方法、裝置、終端設備和操作系統
WO2020168570A1 (zh) 快应用的添加方法、装置、电子设备及存储介质
CN111552606B (zh) 数据处理方法、装置及电子设备
CN107197088A (zh) 基于安卓移动设备的截图方法与装置
CN112306723B (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: 19915802

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: 19915802

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19915802

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.05.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19915802

Country of ref document: EP

Kind code of ref document: A1