CN117827228A

CN117827228A - Quick application deployment method and related equipment

Info

Publication number: CN117827228A
Application number: CN202310158058.8A
Authority: CN
Inventors: 纪德祥; 张怡; 邹纯纯
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-02-15
Filing date: 2023-02-15
Publication date: 2024-04-05

Abstract

The application provides a quick application deployment method and related equipment, and relates to the technical field of terminals. In response to an operation of adding the first fast application to the desktop of the electronic device, the electronic device may send a request for downloading an application package of the first fast application to the first preset server, the electronic device may download the application package of the first fast application based on a first download address returned by the first preset server, install the application package of the first fast application after the downloading is completed, and may further create a client icon of the first fast application at the desktop. When the quick application is added to the desktop, the experience that the quick application can be started by clicking the desktop icon as in the existing desktop shortcut of the quick application is realized by downloading the application package for installing the quick application to the desktop, the quick application client installed based on the application package of the quick application has an independent message channel function, and the client icon of the quick application of the desktop is required to be confirmed secondarily by a user when the user deletes the client icon of the quick application of the desktop.

Description

Quick application deployment method and related equipment

Technical Field

The application relates to the technical field of terminals, in particular to a quick application deployment method and related equipment.

Background

The quick application is an application which is downloaded in time when a user uses the quick application without being installed in advance. An operating system of an electronic device (e.g., a smart phone) may be pre-deployed with a fast application engine through which the start and running of the fast application is implemented. Existing quick applications only support desktop additions to electronic devices in the form of desktop shortcuts, and the user experience is poor.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a quick application deployment method, which can implement quick application deployment on an electronic device by installing an application package (application package), so as to improve the quick application use experience of a user.

The first aspect of the embodiment of the application discloses a quick application deployment method, which is applied to electronic equipment and comprises the following steps: responding to the operation of adding the first quick application to the desktop of the electronic equipment, and sending a request for downloading an application program package of the first quick application to a first preset server; downloading an application program package of a first quick application based on a first downloading address returned by a first preset server; an application package for installing the first fast application, and creating a client icon for the first fast application on a desktop of the electronic device.

By adopting the technical scheme, when the quick application is added to the desktop of the electronic device, the electronic device downloads the application package for installing the quick application to the desktop from the first preset server (for example, a server for providing quick application racking service), so that the experience of clicking as well as quickly starting the quick application as the existing desktop shortcut can be realized, the application package can be a lightweight application package generated based on the application package of the quick application, the application package has an independent message channel function, the user needs to perform secondary confirmation for deleting the client icon of the first quick application of the desktop, the mistaken deleting operation can be avoided, the application package of the quick application can be installed in a silent mode, no perception is available for the user, and the electronic device can respond to the operation of adding the quick application to the desktop by the user, so that the client icon of the quick application can be generated on the desktop.

In some embodiments, after installing the application package of the first fast application, further comprising: and displaying a message prompt box containing the installation result of the application program package of the first fast application.

By adopting the technical scheme, the installation result of the application package of the quick application can be informed to the user through the Toast prompt box or other forms of prompt boxes, so that the user can know the installation result of the application package in time.

In some embodiments, the method for deploying the quick application further includes, after the electronic device installs the application package of the first quick application, obtaining a first quick application client: the method comprises the steps that a fast application engine of the electronic equipment receives a push message sent by a second preset server and sends a notification of the push message to a first fast application client, wherein the push message is associated with a first fast application; and if the notification authority of the first fast application client is in an open state, the first fast application client displays the notification of the push message in a notification bar.

By adopting the technical scheme, the quick application client obtained by installing the application package has an independent message notification channel, and can perform independent notification authority management and control, such as starting notification authority, closing notification authority and the like, when receiving the push message associated with a certain quick application and issued by a second preset server (such as a message push server), the quick application engine can send the notification of the push message to the quick application client of the quick application, the quick application client displays the notification of the push message on a notification column (the notification authority of the quick application client is in an on state), and if the notification authority of the quick application client is in an off state, the quick application client does not perform notification display of the push message.

In some embodiments, before the notification of the quick application engine push message is sent to the first quick application client, the quick application deployment method further comprises: the first fast application client sends a registration application of the push message notification to the fast application engine.

By adopting the technical scheme, the fast application client can receive the push message notification sent by the fast application engine by sending the registration application of the push message notification to the fast application engine, for example, the fast application client can send the registration application of the push message notification to the fast application engine through the push.

In some embodiments, the fast application deployment method further comprises: responsive to a click operation on the notification displayed in the notification bar, the quick application engine obtains a deep link of the clicked notification, the clicked notification being a notification associated with the first quick application; the fast application engine starts a first fast application client based on the deep link; the first fast application client opens a page corresponding to the deep link.

By adopting the technical scheme, when the user clicks the notification associated with a certain fast application in the notification bar, the electronic device can pull up the fast application client of the fast application, and the fast application client opens a page corresponding to the notification, for example, the fast application client opens the page based on the deep link of the clicked notification acquired by the fast application engine, so that the user can view the detailed push message.

In some embodiments, the fast application deployment method further comprises: the method comprises the steps that a fast application engine obtains the number of unread push messages, sets the number of unread red points based on the number of the unread push messages, and sends the number of the unread red points to a first fast application client; the first fast application client sets a reddish dot number based on the unread reddot number and displays the reddish dot number on the client icon.

By adopting the technical scheme, the quick application client installed based on the application program package has the function of displaying the unread push messages, for example, the quick application client can display the number of the unread push messages on the client icon through the small red dot number, so that a user can determine that the unread push messages exist in the quick application based on the small red dot number.

In some embodiments, the fast application deployment method further comprises: responsive to exiting the operation or application switching operation of the first fast application client, the fast application engine re-obtains the number of unread push messages, generates an instruction to refresh the small red dot number or cancel the small red dot number based on the re-obtained number of unread push messages, and sends the generated instruction to the first fast application client; the first quick application client updates the small red point number on the client icon based on the instruction for refreshing the small red point number, or cancels the small red point number on the client icon based on the instruction for canceling the small red point number.

By adopting the technical scheme, a user can start the quick application client to check unread push messages, the push messages checked by the user can be marked as read, after the user exits the quick application client or performs application switching operation (for example, the interface of the quick application client is switched to another APP interface, and the quick application client is switched to background operation), the quick application engine can reacquire the quantity of the unread push messages, and an instruction for refreshing the small red dot number or canceling the small red dot number is generated based on the reacquired quantity of the unread push messages, so that the quick application client can update the small red dot number displayed on the client icon, or cancel the small red dot number.

In some embodiments, generating an instruction to refresh or cancel the small red dot number based on the number of re-acquired unread push messages includes: if the number of the unread push messages obtained again is greater than or equal to one, generating an instruction for refreshing the small red point number; and if the number of the unread push messages acquired again is zero, generating an instruction for canceling the small red point number.

By adopting the technical scheme, after a user exits the quick application client or performs application switching operation, if the number of unread push messages obtained by the quick application engine again is greater than or equal to one, an instruction for refreshing the reddish dots can be generated, so that the quick application client can update the reddish dots displayed on the client icon, and if the number of unread push messages obtained by the quick application engine again is zero, indicating that no unread push messages exist, an instruction for canceling the reddish dots can be generated, so that the quick application client can cancel the reddish dots displayed on the client icon.

In some embodiments, the electronic device is provided with a fast application engine and a first fast application client, the first fast application client is obtained by installing an application package of a first fast application, and the fast application deployment method further comprises: in response to an operation to uninstall the first fast application client, the fast application engine deletes the data and usage record associated with the first fast application client.

With the adoption of the technical scheme, when the quick application client is uninstalled from the electronic device, the quick application engine can delete the data (such as local cache data, application packages, installation files of the application packages and the like) associated with the quick application client together with the usage record. If the process of the fast application client is running during unloading, the fast application engine can stop the running process of the fast application client.

In some embodiments, the electronic device is provided with a fast application engine, a first fast application client, and an application store, the first fast application client is obtained by installing an application package of a first fast application, and the fast application deployment method further comprises: when the application store acquires unloading information of the first quick application client, the unloading information is sent to a quick application engine; the fast application engine deletes data and usage records associated with the first fast application client based on the offload information.

By adopting the technical scheme, when the user uninstalls the quick application client from the electronic equipment, the application store can respond to the uninstallation operation of the quick application client to acquire the uninstallation information (for example, the uninstallation information can comprise the name of the quick application client and the package name of the application program package) of the quick application client, and the application store forwards the uninstallation information to the quick application engine, so that the quick application engine can delete the data and the usage record associated with the quick application client based on the uninstallation information.

In some embodiments, the first preset server is provided with an application package of the first fast application and an application package of the first fast application, and the application package of the first fast application is generated based on the application package of the first fast application and a preset application package template.

By adopting the technical scheme, the application package of the fast application and the application program package of the fast application are stored in the first preset server in a shelf mode, so that the electronic equipment can open the fast application on line, or the application program package is downloaded and the fast application client with the independent message channel function is installed in response to the operation of adding the fast application to the desktop of the electronic equipment.

In some embodiments, the fast application deployment method further comprises: responding to the operation of starting the first fast application, and sending a request for downloading an application package of the first fast application to a first preset server; downloading an application package of the first quick application based on a second download address returned by the first preset server; the first fast application is started based on an application package of the first fast application.

By adopting the technical scheme, when a user opens a certain quick application online (for example, clicks a link or an icon in a certain application to open a certain quick application), the electronic device can download an application package of the quick application from a first preset server, and start the quick application based on the downloaded application package.

In some embodiments, the fast application deployment method further comprises: and based on the information which is returned by the first preset server and prompts the absence of the application program package of the first quick application, creating a shortcut icon of the first quick application on the desktop of the electronic equipment.

By adopting the technical scheme, when the quick application is added to the desktop of the electronic device, if the first preset server determines that the application program package of the on-shelf quick application does not exist, the first preset server can return information prompting that the application program package of the quick application does not exist to the electronic device, and the electronic device can create a shortcut icon of the quick application on the desktop based on the information so as to facilitate a user to quickly start the quick application subsequently.

In a second aspect, embodiments of the present application provide a computer-readable storage medium comprising computer instructions that, when run on an electronic device, cause the electronic device to perform the fast application deployment method according to the first aspect.

In a third aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor and a memory, where the memory is configured to store instructions, and the processor is configured to invoke the instructions in the memory, so that the electronic device performs the fast application deployment method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a computer program product which, when run on an electronic device (e.g. a computer), causes the electronic device to perform the fast application deployment method as described in the first aspect.

In a fifth aspect, there is provided an apparatus having a function of implementing the behavior of the electronic device in the method provided in the first aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

It will be appreciated that the computer readable storage medium according to the second aspect, the electronic device according to the third aspect, the computer program product according to the fourth aspect, and the apparatus according to the fifth aspect correspond to the method according to the first aspect, and therefore, the advantages achieved by the apparatus according to the fifth aspect may refer to the advantages in the corresponding method provided above, and will not be described herein.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 2 is a schematic software structure of an electronic device according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a conventional fast-application on-shelf scenario;

FIG. 4 is a schematic diagram of an on-shelf scenario of a fast application according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a fast application system according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a process of loading an application package of a fast application according to an embodiment of the present disclosure;

FIG. 7 is a flowchart of an application package of an electronic device installation fast application according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an interface for offloading a fast application client according to an embodiment of the present application;

FIG. 9 is a flowchart of a fast application client receiving a push message according to an embodiment of the present application;

FIG. 10 is a flow chart illustrating a method for a fast application client to display the number of unread messages according to an embodiment of the present application;

FIG. 11 is a schematic diagram showing the number of unread messages by a client icon according to an embodiment of the present application;

FIG. 12 is a flowchart of an unloading a fast application client according to an embodiment of the present application;

Fig. 13 is a flowchart illustrating steps of a fast application deployment method according to an embodiment of the present application.

Detailed Description

It should be noted that "at least one" in this application means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and the representation may have three relationships, for example, a and/or B may represent: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In order to facilitate understanding of the technical solutions in the embodiments of the present application, the following first explains some terms related to the embodiments of the present application:

fast application: the method is an application which is downloaded in time when a user uses the application without being installed in advance.

Engine (engine): is a core component of a development program or system on an electronic platform. With the engine, a developer can quickly build, lay out functions required by the program, or assist in the operation of the program. Generally, an engine is a supporting part of a program or a set of systems. Common program engines are game engines, search engines, disinfection engines, and the like. In the embodiment of the application, the fast application needs to be interpreted and executed by the fast application engine.

Integrated development environment (integrated development environment, IDE): the application software is used for assisting a program developer in developing software, source code text can be assisted in writing, compiling and packaging into usable programs in a development tool, and a graphic interface can be designed. IDE typically includes programming language editors, automated build tools, debuggers, and the like. Some IDEs contain compilers/interpreters, others do not. These IDEs may implement the compilation work of the code by invoking a third party compiler. Optionally, the IDE will also contain a version control system and some tools that can design a graphical user interface. Many modern IDEs that support object-oriented also include category browsers, object viewers, object structure diagrams, and the like. In embodiments of the present application, the express application is typically developed in a particular IDE, e.g., the IDE may be the IDE of the express application.

Application package (application package application package): the application package file format is used by an operating system of the electronic device and is used for distributing and installing mobile applications and middleware, wherein the operating system can be an Android operating system, an iOS operating system, a Windows operating system and a hong Mongolian operating system.

The quick application deployment method provided by the embodiment of the application can be applied to electronic equipment, and the electronic equipment comprises but is not limited toIs mounted onWindows />Or other operating system. The following electronic device is mounted->Or->An example is described.

The electronic device may communicate with other electronic devices or servers over a communication network. The electronic device of the present application may include at least one of a cell phone, a foldable electronic device, a tablet computer, a personal computer (personal computer, PC), a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (personal digital assistant, PDA), an augmented reality (augmented reality, AR) device, a Virtual Reality (VR) device, an artificial intelligence (artificial intelligence, AI) device, a wearable device, an intelligent home device, a smart city device, etc., and the specific type of the electronic device is not particularly limited in the embodiments of the present application. The communication network may be a wired network or a wireless network. For example, the communication network may be a local area network (local area networks, LAN) or a wide area network (wide area networks, WAN), such as the internet. When the communication network is a local area network, the communication network may be, for example, a wireless fidelity (wireless fidelity, wi-Fi) hotspot network, a Wi-Fi P2P network, a bluetooth network, a zigbee network, or a near field communication (near field communication, NFC) network, or the like. When the communication network is a wide area network, the communication network may be, for example, a third generation mobile communication technology (3 rd-generation wireless telephone technology, 3G) network, a fourth generation mobile communication technology (the 4th generation mobile communication technology,4G) network, a fifth generation mobile communication technology (5 th-generation mobile communication technology, 5G) network, a future evolution public land mobile network (public land mobile network, PLMN), the internet, or the like.

In some embodiments, the electronic device may install one or more APP (Application). APP may be abbreviated as an application, a software program capable of performing some or more specific functions. Such as communication-type applications, video-type applications, audio-type applications, image capture-type applications, cloud desktop-type applications, and the like. The communication application may include, for example, a short message application. Image capture class applications may include, for example, a capture application (system camera or third party capture application). Video-type applications may include, for example, bloom as video. The audio class application may include, for example, hua as music. The application mentioned in the following embodiments may be a system application installed when the electronic device leaves the factory, or may be a third party application that is downloaded from a network or obtained from other electronic devices by a user during the process of using the electronic device.

Existing android devices (on-board)Operating system's device) APP is obtained by downloading an installation application package. The code amount of the application package of the APP is large, and is generally tens of Megabytes (MB) or hundreds of MB, and the APP obtained by installing the application package can be directly arranged in ++>Running in an operating system. The code amount of the application package of the fast application related to the application is small, and is generally tens of Kilobytes (KB) or hundreds of KB, and the electronic device can obtain the fast application client through downloading the application package for installing the fast application, and the fast application client runs based on a fast application engine.

The existing quick application support is added to the terminal desktop in the form of desktop shortcut, so that a user can conveniently and quickly start the quick application. Since the quick application is added to the desktop in the form of a desktop shortcut, there are the following drawbacks: when the shortcut icon of the quick application is deleted by long-time pressing, no secondary confirmation exists, so that the user can delete the shortcut icon by mistake; the shortcut icon of the shortcut application does not have a small red dot function for displaying the notification or the message, so that the user may miss the important message; the user unloads the quick application through the shortcut icon of the quick application, the use record and the data of the quick application are still stored in the quick application engine, and the user data can be leaked, so that the storage space is occupied. For a plurality of different fast applications, the fast application engine receives and sends message notification, so that when a user disables the notification authority of one fast application, the notification authority of the whole fast application engine may be disabled, and other fast applications cannot normally send/receive notification messages.

In order to solve the above technical problems, some embodiments of the present application provide a quick application deployment method, when a user adds a quick application opened online to a desktop, by downloading an application package of the quick application from an application store and installing the application package to the desktop for subsequent use by the user, a quick application client obtained based on installation of the application package has independent notification management authority, has a small red point capability of unloading a secondary confirmation and displaying notification or a message, and when the user unloads the quick application client, the user can also be notified to a quick application engine to delete data associated with the quick application client.

Fig. 1 illustrates a schematic structure of an electronic device 10.

The electronic device 10 may include a processor 110, an external memory interface 120, an internal memory 121, an antenna 1, an antenna 2, a mobile communication module 130, a wireless communication module 140, an audio module 150, a sensor module 160, a camera module 170, a display screen 180, and the like.

It should be understood that the illustrated structure of the present embodiment does not constitute a specific limitation on the electronic device 10. In other embodiments of the present application, the electronic device 10 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 may be a cache memory. The memory may hold instructions or data that are used or used more frequently by the processor 110. If the processor 110 needs to use the instructions or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include inter-integrated circuit (inter-integrated circuit, I2C) interfaces, inter-integrated circuit built-in audio (inter-integrated circuit sound, I2S) interfaces, pulse code modulation (pulse code modulation, PCM) interfaces, universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interfaces, mobile industry processor interfaces (mobile industry processor interface, MIPI), general-purpose input/output (GPIO) interfaces, subscriber identity module (subscriber identity module, SIM) interfaces, and/or universal serial bus (universal serial bus, USB) interfaces, among others. The processor 110 may be connected to modules such as an audio module, a wireless communication module, a display, a camera, etc. through at least one of the above interfaces.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative and not limiting on the structure of the electronic device 10. In other embodiments of the present application, the electronic device 10 may also employ different interfacing manners, or a combination of interfacing manners, as in the above embodiments.

The wireless communication function of the electronic device 10 may be implemented by the antenna 1, the antenna 2, the mobile communication module 130, the wireless communication module 140, a modem processor, a baseband processor, and the like.

The mobile communication module 130 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied on the electronic device 10. The mobile communication module 130 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. In some embodiments, at least some of the functional modules of the mobile communication module 130 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 130 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 140 may provide solutions for wireless communication including wireless local area networks (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) networks), bluetooth (BT), bluetooth low energy (bluetooth low energy, BLE), ultra Wide Band (UWB), global navigation satellite systems (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied on the electronic device 10. The wireless communication module 140 may be one or more devices integrating at least one communication processing module.

In some embodiments, the electronic device 10 may communicate with networks and other electronic devices through wireless communication technology. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The electronic device 10 may implement display functions via a GPU, a display screen 180, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 180 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The camera module 170 includes a camera. The display screen 180 is used for displaying images, videos, etc., and the display screen 180 may be a touch screen. The display 180 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (FLED), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 10 may include 1 or more display screens 180.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 10. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions.

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 10, etc. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional methods or data processing of the electronic device 10 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The audio module 150 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 150 may also be used to encode and decode audio signals. In some embodiments, the audio module 150 may be disposed in the processor 110, or some functional modules of the audio module 150 may be disposed in the processor 110.

The software system of the electronic device 10 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Taking an Android system with a layered architecture as an example, the embodiment of the application illustrates a software structure of the electronic device 10.

Fig. 2 is a software block diagram of the electronic device 10 according to an embodiment of the present application.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into five layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (ART) and native C/c++ libraries, a hardware abstraction layer (Hardware Abstract Layer, HAL), and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layer may include a window manager, a content provider, a view system, a resource manager, a notification manager, an activity manager, an input manager, and so forth.

The window manager provides window management services (Window Manager Service, WMS) that may be used for window management, window animation management, surface management, and as a transfer station to the input system.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

The activity manager may provide activity management services (Activity Manager Service, AMS) that may be used for system component (e.g., activity, service, content provider, broadcast receiver) start-up, handoff, scheduling, and application process management and scheduling tasks.

The input manager may provide input management services (Input Manager Service, IMS), which may be used to manage inputs to the system, such as touch screen inputs, key inputs, sensor inputs, and the like. The IMS retrieves events from the input device node and distributes the events to the appropriate windows through interactions with the WMS.

The android runtime includes a core library and An Zhuoyun rows. The android runtime is responsible for converting source code into machine code. Android runtime mainly includes employing Advanced Or Time (AOT) compilation techniques and Just In Time (JIT) compilation techniques.

The core library is mainly used for providing the functions of basic Java class libraries, such as basic data structures, mathematics, IO, tools, databases, networks and the like. The core library provides an API for the user to develop the android application.

The native C/c++ library may include a plurality of functional modules. For example: surface manager (surface manager), media Framework (Media Framework), libc, openGL ES, SQLite, webkit, etc.

The surface manager is used for managing the display subsystem and providing fusion of 2D and 3D layers for a plurality of application programs. Media frames support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc. OpenGL ES provides for drawing and manipulation of 2D graphics and 3D graphics in applications. SQLite provides a lightweight relational database for applications of the electronic device 10.

The hardware abstraction layer runs in a user space (user space), encapsulates the kernel layer driver, and provides a call interface to the upper layer.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

An exemplary description of the existing fast-application set-up scenario is presented below in conjunction with fig. 3.

In this embodiment, an electronic device 10, a development device 11, and a first application server 12 may be included. The first application server 12 may be used to provide services for application packages for quick applications to be put on-shelf, upgraded, maintained, stored, etc. The first application server 12 may be a cloud server.

The development device 11 may be an electronic device equipped with an IDE, such as a notebook computer or a desktop computer. A program developer may write source code for a quick application by means of the development device 11. After the source code of the quick application is written, the development device 11 may generate application packages of the quick application according to the source code, and put the application packages on shelf to the first application server 12 for the user to download. The application package is a set of files that can be decompressed by itself, and can parse out files needed by the running application, and the application package is stored in the first application server 12 in the form of a Resource Package (RPK).

In some embodiments, each application package stored on the first application server 12 may have a corresponding download address, and the electronic device 10 may be a smart phone, a tablet computer, or the like, which may support fast application running. The electronic device 10 may send a request for downloading an application package of the fast application to the first application server 12, where the request for downloading may include an identifier of the fast application, and the first application server 12 may return a download address of the application package to the electronic device 10, where the electronic device 10 implements downloading of the application package based on the download address.

In some embodiments, when the first application server 12 receives a request for downloading an application package of the fast application sent by the electronic device 10, the first application server 12 may also send the application package of the fast application to the electronic device 10.

The electronic device 10 may also create a shortcut icon for the quick application at the desktop in response to a user adding the online opened quick application to the desktop, so that the quick application may be opened directly at the desktop at a later time.

An exemplary description of the fast-application set-up scenario of the present application is presented below in conjunction with fig. 4.

In this embodiment, an electronic device 10, a development device 11, and a second application server 13 may be included. The second application server 13 may be used to provide services such as fast application management (e.g., fast application search management, configuration management, card management, plug-in management, etc.), application package compilation, packaging and signing of fast applications, application package and application package racking, upgrading, maintenance, storage, etc. of fast applications. The second application server 13 may be a cloud server. In the embodiment of the present application, the second application server 13 may be a specific implementation example of the first preset server described below.

A program developer may write source code for a quick application by means of the development device 11. After the source code writing of the quick application is completed, the development device 11 may generate an application package of the quick application from the source code.

In some embodiments, the second application server 13 may prepare an application package template required by the fast application in advance, have an android compiling and packaging environment, and deploy tools required by signing, the second application server 13 may compile, package and sign an application package of the fast application to obtain an application package corresponding to the fast application, and the application package of the fast application may be stored in the second application server 13 in a shelf for the user to download. The application package of the quick application has the capability of sending a notification, displaying a reddish dot of a message and the like.

In some embodiments, the application packages of each quick application stored on the second application server 13 may have a corresponding download address. I.e. the putting on shelf of the fast application of the present application is stored in the form of an application package in the second application server 13, whereas the putting on shelf of the existing fast application is stored in the form of an RPK in the first application server 12.

In some embodiments, the application packages of the quick application may also be stored in the second application server 13 on-shelf to facilitate the user's online opening of the quick application via the electronic device 10. If the user requests to add the quick application to the desktop during the process of using the online opened quick application, the electronic device 10 may download and install the application package of the quick application from the second application server 13 in response to the operation of adding the quick application to the desktop, and may create an icon of the quick application client on the desktop, so that the user may directly open the quick application on the desktop.

The quick application client side obtained by installing the application package based on the quick application also needs to be interpreted and executed through a quick application engine, but compared with the existing quick application on the desktop shortcut icon, the quick application client side has the characteristics of the application package (secondary confirmation is needed for unloading), and has independent notification authority management and message notification channels and the capability of displaying the message through small red dots.

An exemplary description of a fast application system according to an embodiment of the present application is provided below in conjunction with fig. 5. The fast application system may include two parts, a server side and an electronic device side.

The server side may comprise a second application server 13 and a message push server 14. The message push server 14 may be used to push messages to the electronic device 10. For example, the message push server 14 may push messages to the electronic device 10 on which the fast application client is installed, and push messages that need to be sent may be preconfigured on the message push server 14 by the program developer of the first fast application. The message push server 14 may be a specific implementation example of the second preset server described below.

Taking the application package of the first quick application as an example, the first quick application may be an electronic commerce quick application, an electronic book quick application, a news quick application, a travel quick application, and the like, which is not limited in this application.

The second application server 13 may receive an application package of the first fast application issued by the program developer, and the second application server 13 may detect whether a fast application packaging task exists at regular time, and if it is detected that the fast application packaging task exists, the second application server 13 compiles, packages and signs the application package of the fast application. For example, the second application server 13 may perform detection once every preset time, and the preset time may be set according to the actual requirement, which is not limited in this application.

The second application server 13 may compile, package and sign the application package of the first fast application based on the pre-fabricated application package template, to obtain an application package corresponding to the first fast application. The application packages corresponding to the first fast application may be stored on shelf in the second application server 13. For example, a background person or an automatic auditing system for application packages deployed by the second application server 13 may audit the application packages that are on shelf, and the application packages that pass the auditing may be stored in the second application server 13. The second application server 13 may not store the application packages for which the audit is not passed.

The electronic device side may include an APP and a quick APP engine installed on the electronic device 10. The APP store may be upgraded to a version that supports application package downloads for fast applications.

Taking the example of the electronic device 10 downloading the application package of the first quick application from the second application server 13 in response to a user operation. In the process of using the online opened first quick application (loaded based on the application package of the first quick application), the user actively clicks to add to the desktop, the quick application engine can respond to the user operation and transmit the information of the first quick application to be installed to the application store APP, and the application store APP can request the second application server 13 to download the application package of the first quick application based on the received information of the first quick application. If the second application server 13 determines that there is an application package of the first fast application that is on-shelf, the second application server 13 may return the download address of the application package of the latest version of the first fast application to the application store APP. The APP may download the application package of the first fast application based on the download address, and after the downloading is completed, may silence the installation of the application package of the first fast application, and generate a client icon of the first fast application on the desktop. After the application package based on the first fast application is installed to obtain the first fast application client, the fast application engine may also inform the user of the installation result through a message prompt box (Toast prompt box).

In some embodiments, when the fast application engine receives a message pushed by the message pushing server 14, the notification of the message may be passed to a first fast application client that has independent notification rights management (e.g., close application notification, open application notification, set top application notification, etc.) and message notification channels, and the notification of the received message may be presented in a notification bar. For example, the fast application engine may communicate a notification of a subscription message or notification message to the first fast application client, which may also present and update a reddish number (the reddish number characterizes the number of unread messages) based on the number of messages transmitted by the fast application engine. When the user uninstalls the first fast application client, the application framework layer of the operating system may send an uninstall message of the first fast application client to the application store APP or the application store APP may acquire the uninstall message of the first fast application client in response to an operation of the user uninstalling the first fast application client. The APP may forward the offload message for the first fast application client to the fast application engine, which may purge data associated with the first fast application client (e.g., an application package of the first fast application, a file installed based on the application package of the first fast application, cached data, etc.) and the usage record based on the offload message for the first fast application client.

Referring to fig. 6, an exemplary process diagram of loading an application package of a quick application according to an embodiment of the present invention is shown. Taking the quick application as the first quick application as an example, the process of putting the application package of the quick application on shelf may include the following steps, and it will be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

60. The second application server 13 receives the application package of the first fast application uploaded by the development device 11.

In some embodiments, a program developer may write or update source code for a quick application via the development device 11. After the source code writing of the quick application is completed, the development device 11 may generate an application package of the latest version of the quick application from the source code. The program developer may upload the application package of the first fast application of the latest version to the second application server 13 through the development device 11 to implement the release of the first fast application of the latest version (application package ).

61. The second application server 13 regularly detects whether a fast application packaging task exists, and if so, the second application server 13 performs a task of packaging the application package of the first fast application into an application program package.

In some embodiments, the second application server 13 may perform detection of the fast application packaging task at regular time, and when detecting that the application package of the first fast application needs to be packaged, the second application server 13 may perform a task of packaging the application package of the first fast application into an application package. If there are a plurality of fast application packaging tasks, the second application server 13 may perform packaging sequentially according to the reception time of the application packet, or perform packaging in parallel through multithreading.

62. The second application server 13 decompresses the compilation environment package, deploying a compilation packaging environment for compiling an application package that packages the first quick application.

63. The second application server 13 fills the application package information of the first fast application into the application package template to obtain the application package engineering code corresponding to the first fast application.

In some embodiments, the application package template may be capable of sending a notification, displaying a reddish dot, and the like, and by filling application package information (e.g., information such as an application name, a package name, a version number, and the like) of the first fast application into the application package template, application package engineering code corresponding to the first fast application may be obtained.

64. The second application server 13 executes the compilation packaging script based on the deployed compilation packaging environment and the application package engineering code to generate an application package corresponding to the first quick application.

In some embodiments, an application package corresponding to the first fast application may be generated by executing a compile packaging script on the application package engineering code in a deployed compile packaging environment.

65. The second application server 13 signs the application package of the first fast application.

In some embodiments, by uniquely signing the application package of the first fast application, it may be ensured that the authenticity of the source of the application package of the first fast application and the application package of the first fast application is not tampered with by a third party. When the electronic device 10 installs the application package of the first fast application, the integrity of the application package of the first fast application may be determined by comparing the signature information, so as to determine whether the application package of the first fast application may be installed, so as to improve system security.

66. The second application server 13 stores the signed application package of the first fast application on shelf.

In some embodiments, the second application server 13 may perform a shelf audit on the signed application package of the first quick application (e.g., the audit includes performing virus and compatibility tests, determining whether there is a violation of a name, content, etc.), and the application package of the first quick application that passes the shelf audit may be stored in the second application server 13, so that the electronic device 10 may download the application package of the first quick application through the application store APP.

Compared with the existing quick application which only supports the addition to the desktop in the form of a desktop shortcut and does not have the characteristic of an application package (such as unloading secondary confirmation), an application package updating mechanism is generally full-volume update, the server load pressure is high, the application package of the quick application has the general characteristic of the application package of the existing APP (such as unloading secondary confirmation), the on-shelf or updated application package can be stored on the second application server 13 in advance at regular time, the load pressure of the second application server 13 can be reduced, the capacity of the second application server 13 for coping with the peak period of the on-shelf quick application is improved, the workload of a program developer is not increased, and the program developer is not perceived.

Referring to fig. 7, a flowchart of an application package for installing a quick application in an electronic device 10 according to an embodiment of the present invention is shown. In this embodiment, taking the quick application as the first quick application as an example, the installation process may include the following steps, and it will be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

To facilitate subsequent quick launch of the first quick application, the user may actively add the first quick application to the desktop during use of the online launched first quick application, and the electronic device 10 may obtain an operation of adding the first quick application to the desktop by the user, for example, the user clicks an icon added to the desktop during use of the online launched first quick application, so as to implement adding the first quick application to the desktop.

71. The quick application engine transmits information of the first quick application to the application store APP in response to an operation to add the first quick application to the desktop.

In some embodiments, the APP engine may send information of the first APP to the APP store in response to a user's operation to add the first APP to the desktop, such that the APP store APP may request that the APP package of the first APP be downloaded.

72. The application store APP sends a request to download an application package of the first fast application to the second application server 13.

In some embodiments, the application store APP may send a request to download an application package of the first fast application to the second application server 13 to obtain a download address of the application package of the first fast application.

73. After determining that the application package of the first fast application exists, the second application server 13 transmits the download address of the application package of the first fast application back to the application store APP.

In some embodiments, the second application server 13 may determine whether an application package of the first fast application exists based on the application package up-to-rack record after receiving the request for downloading the application package of the first fast application sent by the application store APP, and return the download address of the latest version of the first fast application to the application store APP after determining that the application package of the first fast application exists. The application store APP receives the download address of the application package of the first fast application sent by the second application server 13.

In some embodiments, if it is determined that the application package of the first quick application does not exist, the second application server 13 may return information prompting that the application package corresponding to the first quick application does not exist to the APP in the application store APP, where the quick application engine may create a shortcut icon of the first quick application on the desktop, so that the user may quickly start the first quick application subsequently. For example, after receiving the information sent by the second application server 13 and prompting that the application package corresponding to the first quick application does not exist, the application store APP may control the quick application engine to create a shortcut icon of the first quick application on the desktop.

74. The application store APP downloads an application package of the first fast application based on the download address.

In some embodiments, the application store APP, after receiving the download address of the application package of the first fast application returned by the second application server 13, may download the application package of the first fast application based on the download address.

In some embodiments, after determining that the application package of the first fast application exists, the second application server 13 may further transmit the application package information of the first fast application and the download address of the application package back to the application store APP, where the application store APP may verify the application package information of the first fast application returned by the second application server 13, and determine whether the application package is the application package of the first fast application, so as to avoid downloading the application package that is not the application package of the first fast application. After the application store APP verifies that the application package information of the first fast application passes, the application package of the first fast application is downloaded based on the download address.

75. The application store APP installs an application package for the first fast application.

In some embodiments, after downloading the application package of the first fast application, the application store APP may install the application package of the first fast application to obtain the first fast application client.

In some embodiments, the operating system or application store APP may verify (e.g., signature verification) the downloaded application package of the first fast application to determine that the downloaded application package of the first fast application is a legitimate, untampered application package prior to installation of the application package of the first fast application. After verification passes, silent installation may be performed on the application package of the first fast application, and a client icon for the first fast application may be created on the desktop.

As shown in fig. 8, taking the first quick application as an example, when the user uninstalls the first quick application client, a prompt box for carrying out uninstallation confirmation can be popped up to realize the secondary confirmation of the uninstallation.

In some embodiments, the installation procedure may further include step 76 and step 77.

76. The application store APP transmits the installation result of the application package of the first fast application back to the fast application engine.

77. The fast application engine generates an installation result notification.

In some embodiments, the quick application engine may perform installation result notification display through a Toast prompt box or other form of information prompt mode, so as to inform the user of the installation result.

In some embodiments, the quick application engine may also not inform the user of the installation result through the Toast prompt box, and the user may determine that the installation is completed through the client icon of the first quick application generated by the desktop.

Compared with the prior art that the quick application exists on the desktop in the form of desktop shortcut, the shortcut icon of the quick application of the desktop is deleted by the user without secondary confirmation, the application package of the quick application is installed on the desktop, the experience that the quick application can be started just by clicking the application package as the desktop shortcut can be achieved, the user needs to conduct secondary confirmation when deleting the client icon of the quick application of the desktop, the false deleting operation can be avoided, the installation of the application package of the quick application is not perceived by the user, the user only conducts the operation of adding the quick application to the desktop, the client icon of the quick application can be generated on the desktop, and the application package of the quick application can have an independent message channel function.

Referring to fig. 9, a flowchart of a fast application client receiving a push message according to an embodiment of the present invention is shown. In this embodiment, taking the fast application client as the first fast application client as an example, the flow of receiving the push message by the fast application client may include the following steps, and it may be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

90. The first fast application client sends a registration application of the push message notification to the fast application engine.

In some embodiments, the first fast application client may send a registration application of the push message notification to the fast application engine through a preset interface, e.g., the first fast application client may send a registration application of the push message notification to the fast application engine through a push.

91. The fast application engine returns a message notification token (token) corresponding to the first fast application client based on the registration application of the first fast application client.

In some embodiments, the fast application engine may return a message notification token corresponding to the first fast application client after receiving the registration request of the first fast application client. The fast application engine may send a notification of the push message to the first fast application client based on the message notification token.

92. The fast application engine receives push messages issued by the message push server 14.

In some embodiments, push messages that need to be sent may be preconfigured on the message push server 14 by the program developer of the first fast application, such as campaign information, advertisement information, subscription information, etc. associated with the first fast application.

93. The fast application engine sends a notification of the push message to the first fast application client when determining that the first fast application client obtained based on the installation of the application package exists.

In some embodiments, the fast application engine may send a notification of the push message to the first fast application client through a preset interface when it is determined that there is the first fast application client installed based on the application package, e.g., the fast application engine may send a notification of the push message to the first fast application client through an Android interface definition language (Android interface definition language, AIDL).

In some embodiments, the fast application engine may further send a notification of the push message to the first fast application client via AIDL after determining that there is a first fast application client based on the application package installation and the information verification passes.

In some embodiments, the information verification may include verifying whether a package name, signature of an application package corresponding to the first fast application client is consistent to determine validity of the first fast application client.

In some embodiments, if the quick application engine determines that there is no first quick application client installed based on the application package, indicating that the first quick application may exist on the desktop in the form of a desktop shortcut, the quick application engine may call a system API to display a notification of the push message on the notification bar.

94. The first fast application client performs notification display of the push message.

In some embodiments, after receiving the notification of the push message forwarded by the fast application engine, the first fast application client may call the system API to display the notification of the push message on the notification bar, call the system API to display the notification of the push message on the status bar, or call the system API to display the notification of the push message in the form of a prompt box.

In some embodiments, the operating system supports individual management of notification rights of the fast application client by a user for the fast application client installed based on the application package. I.e. the user may choose to open or close the notification rights of the first fast application client.

After receiving the notification of the push message forwarded by the fast application engine, the first fast application client can also check whether the first fast application client has notification authority. If the first quick application client has the notification authority, the first quick application client can call the system API to display the notification of the push message on a notification bar, or call the system API to display the notification of the push message on a status bar, or call the system API to display the notification of the push message in a prompt box mode. If the notification authority is not provided, the notification of the push message is not displayed.

In some embodiments, taking the example of a notification of a push message being displayed on the notification bar, if the user sees the notification of a message associated with the first quick application in the notification bar, the user may click on the notification to view the details of the push message. The electronic device 10 may obtain an operation in which the user clicks on the notification associated with the first fast application in the notification bar.

In some embodiments, the flow of the fast application client receiving the push message may further include step 95, step 96, and step 97.

95. The fast application engine obtains a deep link of the notification in response to clicking on the notification associated with the first fast application in the notification bar.

In some embodiments, if the user clicks on a notification of a message associated with a first quick application after the notification bar sees the notification, the quick application engine may obtain a deep link for the notification in response to clicking on the notification. The deep link may include a uniform resource locator (uniform resource locator, URL) of the page and a quick application identification.

96. The fast application engine initiates the first fast application client based on the notified deep link.

97. The first fast application client opens a page corresponding to the deep link.

Compared with the existing quick application notification, the quick application notification is shared by one notification channel (the quick application engine calls the system API to display the notification of the push message on the notification bar), so that the user can synchronously inhibit the notification authority of the quick application engine after disabling the notification authority of a certain quick application, and other quick applications can not receive the notification of the message.

Referring to fig. 10, a flowchart of an exemplary presentation of the number of unread messages by a fast application client according to an embodiment of the present invention is shown. In this embodiment, taking the fast application client as the first fast application client as an example, the flow of the fast application client displaying the number of unread messages may include the following steps, and it may be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

101. The fast application engine receives push messages issued by the message push server 14.

102. The fast application engine sends a notification of the push message to the first fast application client.

In some embodiments, the fast application engine may, after receiving a push message associated with the first fast application issued by the message push server 14, send a notification of the push message to the first fast application client via a preset interface (e.g., AIDL).

In some embodiments, the fast application engine may send a notification of the push message to the first fast application client via AIDL after determining that there is a first fast application client based on the application package installation and the information verification passes.

103. The first fast application client performs notification display of the push message.

In some embodiments, the first fast application client may also check first whether it has notification rights, and when it has notification rights, may call the system API to display a notification of the push message on the notification bar.

In some embodiments, the first fast application client may also call the system API to display a notification of the push message on the status bar, or call the system API to display the notification of the push message in the form of a prompt box.

104. The fast application engine obtains the number of unread push messages, sets the number of unread red dots based on the number of unread push messages, and sends the number of unread red dots to the first fast application client.

In some embodiments, the fast application engine may send the number of unread red points to the first fast application client via AIDL.

In some embodiments, step 102 and step 104 may also be performed in parallel.

105. The first fast application client sets a little red point number of itself based on the unread red point number and displays the little red point number on the client icon.

In some embodiments, the first fast application client may set its own small red dot number based on the unread red dot number call system API.

As shown in fig. 11, assuming that the number of unread push messages is 8, the client icon at the first fast application client on the desktop may show the small red dot number "8".

In some embodiments, a user may have a need to use other fast application clients or APP while using the first fast application client, and the electronic device 10 may exit the first fast application client in response to a user operation. In some embodiments, the flow of the fast application client displaying the number of unread messages may further include step 106, step 107 and step 108.

106. The fast application engine re-acquires the number of unread push messages in response to the operation of exiting the first fast application client.

107. The fast application engine generates an instruction for refreshing the small red point number or canceling the small red point number based on the number of the unread push messages which are acquired again, and transmits the instruction to the first fast application client.

In some embodiments, the user may launch the first fast application client by clicking on a client icon of the desktop. After the first fast application client is started, the user can click on the unread push message and enter the interface of the push message. The fast application engine may identify push messages that have been read by the user (the push messages that have been read may be marked as read), and when the user exits the first fast application client, the fast application engine may retrieve the number of unread push messages, and generate an instruction to refresh the reddish dot number or cancel the reddot number based on the retrieved number of unread push messages, and transmit the instruction to the first fast application client.

In some embodiments, after the user performs an application switching operation (e.g., switching from the interface of the first fast application client to another APP interface, the first fast application client switching to background operation), the fast application engine may also retrieve the number of unread push messages and generate an instruction to refresh the reddish dot number or cancel the reddot number based on the retrieved number of unread push messages.

If the number of unread push messages is greater than or equal to one, the fast application engine may generate an instruction to refresh the small red dot number (the instruction may include the number of unread red dots) and transmit the instruction to the first fast application client, so that the first fast application client may update the small red dot number on the client icon. If the number of unread push messages is zero, the fast application engine can generate an instruction for canceling the small red dot number and transmit the instruction to the first fast application client, so that the first fast application client can cancel the small red dot number displayed on the client icon.

108. The first fast application client updates or cancels the display of the reddish dot numbers on the client icon based on the instructions transmitted by the fast application engine.

The existing quick application exists on a desktop in the form of a desktop shortcut, and the shortcut icon does not have the capability of displaying the small red dot numbers of the unread information.

Referring to fig. 12, a flowchart of an unloading fast application client according to an embodiment of the present invention is schematically described. Taking the first fast application client as an example in this embodiment, the process of unloading the fast application client may include the following steps, and it will be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

After the electronic device 10 obtains the first fast application client based on the application package installation of the first fast application, there may be a need to uninstall the first fast application client for use experience, remaining storage space of the device, or other reasons, and the user may perform secondary confirmation of uninstallation by pressing the first fast application client icon for a long time, and the electronic device 10 may obtain an uninstallation operation of the first fast application client performed by the user.

121. And the application store APP responds to the operation of unloading the first quick application client and acquires the unloading information of the first quick application client.

In some embodiments, as shown in fig. 8, a user may pop up an "uninstall" icon through a client icon of a first fast application client of a long-press desktop, after clicking the "uninstall" icon, the user may pop up a prompt box for uninstallation, and the user clicks uninstall in the prompt box again, and may trigger an operation of uninstalling the first fast application client. The application program framework layer of the operating system can transmit the unloading information of the first quick application client to the application store APP, so that the application store APP can acquire the unloading information of the first quick application client. The offload information may include a package name of an application package corresponding to the first fast application client.

In some embodiments, the application store APP may also obtain offload information for the first fast application client in response to an offload operation for the first fast application client. 122. The application store APP forwards the offload information for the first fast application client to the fast application engine.

123. The fast application engine deletes the process of the running first fast application client and deletes the data and usage record associated with the first fast application client.

In some embodiments, the fast application engine may delete data (e.g., locally cached data, application packages, installation files for application packages, etc.) and usage records associated with the first fast application client based on the offload information of the first fast application client. If there is a process of the running first fast application client, the fast application engine may also stop the process of the running first fast application client based on the offloading information of the first fast application client.

In some embodiments, the application framework layer of the operating system may also directly pass the offload information of the first fast application client to the fast application engine, which may stop the running process of the first fast application client based on the received offload information, and delete the data and usage records associated with the first fast application client.

In some embodiments, after the first quick application client is completely uninstalled, if the user opens the first quick application online again based on the quick application engine, no previous usage record exists for the online opened first quick application, and if the user needs to add the first quick application to the desktop, the application package of the first quick application needs to be downloaded again and installed.

Compared with the existing shortcut icon for deleting the shortcut icon of the shortcut application on the desktop, the usage record and the data of the shortcut application are still stored in the shortcut application engine, and when the application executes the unloading of the shortcut application client, the data associated with the shortcut application client and the usage record can be deleted together.

Referring to fig. 13, an embodiment of the present application provides a quick application deployment method, which is applied to an electronic device 10. In this embodiment, the quick application deployment method may include the following steps, and it will be understood that the order of the steps may be changed and some steps may be omitted according to different requirements.

In step S131, in response to the operation of adding the first quick application to the desktop of the electronic device 10, a request for downloading the application package of the first quick application is sent to the first preset server.

In some embodiments, the first preset server may be a server for providing services of application packages, putting on shelves of application packages, upgrading, maintaining, storing, etc. of the quick application, for example, the first preset server may be the second application server 13 described above. The first preset server is exemplified as the second application server 13 in the following. During online use of the first APP by the user (e.g., launching the first APP in a certain APP), the user may add the first APP to the desktop of the electronic device in order to quickly launch the first APP next time. The electronic device 10 may send a request to download an application package of the first fast application to the second application server 13 in response to the operation of adding the first fast application to the desktop. The specific type of the first quick application is not limited in this application, for example, the first quick application may be an electronic commerce quick application, an electronic book quick application, a news quick application, a travel quick application, and the like.

Step S132, based on the first download address returned by the first preset server, downloading the application package of the first fast application.

In some embodiments, the second application server 13 may first confirm whether the application package of the first fast application that is on the shelf exists after receiving the request for downloading the application package of the first fast application sent by the electronic device 10. If it is determined that the application package exists, the second application server 13 may return the download address (first download address) of the application package of the latest version of the first fast application to the electronic device 10, and the electronic device 10 may download the application package of the first fast application based on the first download address.

If the second application server 13 determines that the application package of the first quick application does not exist, information prompting that the application package corresponding to the first quick application does not exist may be returned to the electronic device 10, where in this case, the electronic device 10 may create a shortcut icon of the first quick application on the desktop, so as to facilitate the user to quickly start the first quick application subsequently.

In step S133, an application package of the first fast application is installed, and a client icon of the first fast application is created on the desktop of the electronic device 10.

In some embodiments, after the electronic device 10 downloads the application package of the first quick application, the application package of the first quick application may be silently installed to obtain the first quick application client, and the electronic device 10 may create a client icon of the first quick application on the desktop, so as to facilitate the user to quickly start the first quick application later. After the electronic device 10 installs the application package of the first quick application, a message prompt box containing the installation result of the application package of the first quick application may also be displayed to remind the user that the installation is completed.

In some embodiments, the electronic device 10 is also pre-installed with a fast application engine that may receive push messages issued by a second preset server (e.g., the second preset server may be the message push server 14 described above). If the push message is a push message associated with a first fast application, the fast application engine may send a notification of the push message to the first fast application client. If the notification authority of the first fast application client is in an open state, the first fast application client can display the notification of the push message on a notification bar, so that the display of the message notification is realized. If the notification authority of the first fast application client is in the closed state, the first fast application client does not display the message notification (i.e., does not display the notification of the push message on the notification bar).

In some embodiments, to enable the fast application engine to send the notification of the push message to the first fast application client, the first fast application client may send a registration application of the push message notification to the fast application engine, e.g., the first fast application client may send the registration application of the push message notification to the fast application engine through a push.

In some embodiments, the user may click on a notification displayed in the notification bar while browsing the notification on the notification bar, and the quick application engine may obtain a deep link of the clicked notification. If the clicked notification is a notification associated with a first quick application, the quick application engine may launch a first quick application client based on the deep link, the first quick application client opening a page corresponding to the deep link.

In some embodiments, the fast application engine may also obtain a number of unread push messages, set a number of unread red dots based on the number of unread push messages, and send the number of unread red dots to the first fast application client. The first fast application client can set the small red point number based on the unread red point number, and display the small red point number on the client icon to realize the reminding of the unread message.

In some embodiments, the user may open the first fast application client by clicking on the client icon of the desktop to view unread notification messages. If the user exits the first fast application client or switches from the interface of the first fast application client to the interface of the other application, the fast application engine may retrieve the number of unread push messages and generate an instruction to refresh the small red dot number or cancel the small red dot number based on the retrieved number of unread push messages. The fast application engine may send the generated instructions to the first fast application client. The first fast application client may update the small red dot number on the client icon based on an instruction to refresh the small red dot number sent by the fast application engine, or cancel the small red dot number on the display client icon based on an instruction to cancel the small red dot number sent by the fast application engine. For example, if the number of unread push messages re-acquired by the fast application engine is greater than or equal to one, the fast application engine generates an instruction for refreshing the small red point number; if the number of unread push messages acquired by the fast application engine is zero, the fast application engine generates an instruction for canceling the small red dot number.

In some embodiments, if the user presses the client icon of the desktop for a long time to uninstall the first fast application client, the fast application engine may delete the data (locally cached data, application packages, files based on installation of the application packages, etc.) and usage records associated with the first fast application client.

In some embodiments, the electronic device 10 may also enable online launching of the first fast application by: in response to a user launching an operation of the first fast application (e.g., clicking a link or icon in an application), the electronic device 10 sends a request to download an application package of the first fast application to the second application server 13, and the electronic device 10 downloads the application package of the first fast application based on a second download address (download address of the application package of the latest version of the first fast application) returned by the second application server 13; after the download is completed, the electronic device 10 may launch the first fast application based on the application package of the first fast application.

The electronic device 10 provided in the embodiments of the present application, the internal memory 121 may be used to store instructions, and the processor 110 may be used to invoke the instructions in the internal memory 121, so that the electronic device 10 performs the above-mentioned related method steps to implement the quick application deployment method in the above-mentioned embodiments.

The present embodiment also provides a computer storage medium, where computer instructions are stored, and when the computer instructions are executed on the electronic device 10, the electronic device 10 is caused to execute the related method steps to implement the quick application deployment method in the foregoing embodiment.

The embodiment of the application also provides a computer program product, which when running on an electronic device, causes the electronic device to execute the related steps so as to realize the quick application deployment method in the embodiment.

In addition, the embodiment of the application also provides a device, which can be a chip, a component or a module, and the device can comprise a processor and a memory which are connected; the memory is used for storing computer-executable instructions, and when the device runs, the processor can execute the computer-executable instructions stored in the memory, so that the chip executes the quick application deployment method in the method embodiments.

The computer storage medium, the computer program product, or the chip provided in the embodiments of the present application are used to perform the corresponding methods provided above, and therefore, the beneficial effects achieved by the computer storage medium, the computer program product, or the chip can refer to the beneficial effects in the corresponding methods provided above, and are not described herein.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are illustrative, and the module or unit is divided into a logic function, and there may be other division manners in actual implementation, for example, multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solutions may be embodied in the form of a software product stored in a storage medium, where the software product includes several instructions to cause a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application.

Claims

1. A quick application deployment method applied to an electronic device, the method comprising:

responding to the operation of adding a first quick application to a desktop of the electronic equipment, and sending a request for downloading an application program package of the first quick application to a first preset server;

downloading an application program package of the first quick application based on a first downloading address returned by the first preset server;

and installing the application program package of the first quick application, and creating a client icon of the first quick application on a desktop of the electronic device.

2. The quick application deployment method of claim 1, wherein after installing the application package of the first quick application, further comprising:

and displaying a message prompt box containing the installation result of the application program package of the first fast application.

3. The quick application deployment method according to claim 1 or 2, wherein the first quick application client is obtained after the electronic device installs the application package of the first quick application, the method further comprising:

The fast application engine of the electronic equipment receives a push message issued by a second preset server and sends a notification of the push message to the first fast application client, wherein the push message is a push message associated with the first fast application;

and if the notification authority of the first fast application client is in an open state, the first fast application client displays the notification of the push message in a notification column.

4. The quick application deployment method of claim 3, wherein before the quick application engine sends the notification of the push message to the first quick application client, further comprising:

and the first fast application client sends a registration application of the push message notification to the fast application engine.

5. The quick application deployment method of claim 3, wherein the method further comprises:

responsive to a click operation on a notification displayed in the notification bar, the quick application engine obtains a deep link of a clicked notification, the clicked notification being a notification associated with the first quick application;

the fast application engine starts the first fast application client based on the deep link;

The first fast application client opens a page corresponding to the deep link.

6. The quick application deployment method of claim 3, wherein the method further comprises:

the fast application engine obtains the number of unread push messages, sets the number of unread red points based on the number of unread push messages, and sends the number of unread red points to the first fast application client;

the first fast application client sets a reddish dot number based on the unread reddot number and displays the reddish dot number on the client icon.

7. The quick application deployment method according to claim 6, wherein the method further comprises:

responsive to exiting the operation or application switching operation of the first fast application client, the fast application engine re-obtains the number of unread push messages, generates an instruction to refresh the small red dot number or cancel the small red dot number based on the re-obtained number of unread push messages, and sends the generated instruction to the first fast application client;

and the first quick application client updates the small red point number on the client icon based on the instruction for refreshing the small red point number, or cancels the display of the small red point number on the client icon based on the instruction for canceling the small red point number.

8. The quick application deployment method of claim 7 wherein the generating an instruction to refresh the small red dot number or cancel the small red dot number based on the number of reacquired unread push messages comprises:

if the number of the unread push messages obtained again is greater than or equal to one, generating an instruction for refreshing the small red point number;

and if the number of the unread push messages acquired again is zero, generating an instruction for canceling the small red point number.

9. The quick application deployment method of claim 1 or 2, wherein the electronic device is installed with a quick application engine and a first quick application client, the first quick application client being obtained by installing an application package of the first quick application, the method further comprising:

in response to an operation to uninstall the first fast application client, the fast application engine deletes data and usage records associated with the first fast application client.

10. The quick application deployment method of claim 1 or 2, wherein the electronic device is installed with a quick application engine, a first quick application client, and an application store, the first quick application client being obtained by installing an application package for the first quick application, the method further comprising:

When the application store acquires unloading information of the first fast application client, the unloading information is sent to the fast application engine;

the fast application engine deletes data and usage records associated with the first fast application client based on the offload information.

11. The quick application deployment method according to any one of claims 1 to 10, wherein the first preset server is provided with an application package of the first quick application and an application package of the first quick application, and the application package of the first quick application is generated based on the application package of the first quick application and a preset application package template.

12. The quick application deployment method of claim 11, wherein the method further comprises:

responding to the operation of starting the first fast application, and sending a request for downloading an application package of the first fast application to the first preset server;

downloading an application package of the first quick application based on a second download address returned by the first preset server;

and starting the first fast application based on the application package of the first fast application.

13. The quick application deployment method according to claim 1, wherein the method further comprises:

And creating a shortcut icon of the first shortcut application on a desktop of the electronic equipment based on the information which is returned by the first preset server and prompts the absence of an application program package of the first shortcut application.

14. A computer readable storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the fast application deployment method of any one of claims 1 to 13.

15. An electronic device comprising a processor and a memory, the memory for storing instructions, the processor for invoking the instructions in the memory to cause the electronic device to perform the fast application deployment method of any of claims 1-13.

16. A computer program product comprising computer instructions which, when run on a processor, cause an electronic device to perform the fast application deployment method of any one of claims 1 to 13.