CN117009023A

CN117009023A - Method for displaying notification information and related device

Info

Publication number: CN117009023A
Application number: CN202311160473.3A
Authority: CN
Inventors: 朱立国
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-09-11
Filing date: 2023-09-11
Publication date: 2023-11-07
Anticipated expiration: 2043-09-11
Also published as: CN117009023B

Abstract

The application provides a method and a related device for displaying notification information. In the method, the electronic device may display a notification of the OUC and store the notification in the electronic device. The electronic device then updates the OUC via the updater. During the OUC update process, the electronic device does not display the stored notification. After the OUC update is completed, the electronic device may again display the stored notification. In this way, the user can be prevented from missing notification information.

Description

Method for displaying notification information and related device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method and a related device for displaying notification information.

Background

Various notification information generated by the application may be displayed in the electronic device. In the use process of the electronic device, an application program (such as a software update application program) needs to be updated and upgraded. There are cases where an application will delete a displayed notification message during and after an upgrade. That is, the application program after the update deletes the notification message generated by the application program before the update, so that the electronic device does not display the notification message generated by the application program before the update after the application program is updated. Thus, the user can miss some information, and the user experience is bad.

Disclosure of Invention

The application provides a method for displaying notification information and a related device. The electronic device may display notifications generated prior to the OUC update after the OUC update, which may prevent the user from missing certain notifications.

In a first aspect, an embodiment of the present application provides a method for displaying notification information, where the method includes: starting a first version of software update application OUC; displaying a first notification at a first time, the first notification generated by the first version of OUC; downloading the second version of OUC; installing the second version of OUC to the first directory and not displaying the first notification; starting the second version of OUC; displaying the first notification at a second time, the second time being later than the first time; displaying a second notification at a third time, the second notification generated by the second version of OUC; downloading a third version of OUC; installing the third version of OUC to a second directory and not displaying the second notification; starting the third version of OUC; the second notification is not displayed at a fourth time, which is later than the third time.

As can be seen from the above method, the electronic device can display the notification generated before the OUC update after the OUC update. In this way, the user can observe the notification related to the questionnaire in time and complete the questionnaire. To some extent, the recycling amount of the questionnaire can be increased, so that the manufacturer of the electronic device can receive the relevant feedback information. And the user can also observe the notification related to the system update in time, so that the electronic equipment can complete the system update in time.

With reference to the first aspect, in some implementations, the displaying the first notification at the second time specifically includes: the OUC based on the second version is downloaded by the system application updater, and the first notification is displayed at the second time.

With reference to the first aspect, in some implementations, the not displaying the second notification at the fourth time specifically includes: the second notification is not displayed at the fourth time based on the OUC of the third version not being downloaded by the system application updater.

With reference to the first aspect, in some implementations, the first directory indicates a data partition and the second directory indicates a system partition.

With reference to the first aspect, in some implementations, the first directory is used to store applications downloaded by the system application updater, and the second directory is used to store applications downloaded by the non-system application updater.

With reference to the first aspect, in some implementations, after the displaying the first notification at the first time, the method further includes: storing the first notification; before the displaying the first notification at the second time, the method further comprises: the stored first notification is read.

With reference to the first aspect, in some implementations, before the downloading the second version of OUC, the method further includes: displaying a third notification at the first time, the third notification generated by the first version of OUC; receiving and responding to the first operation, deleting and not displaying the third notification; after the initiating the second version of OUC, the method further comprises: the third notification is not displayed at the second time.

With reference to the first aspect, in some implementations, before the downloading the second version of OUC, the method further includes: transmitting a first message to a server at regular time intervals, the first message for querying the server whether to generate OUCs of other versions than the first version; a second message is received indicating that the server has generated the second version of OUC.

With reference to the first aspect, in some implementations, before installing the second version of OUC into the first directory, the method further includes: the first version of OUC is offloaded.

In a second aspect, the present application provides an electronic device comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, the one or more memories being operable to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the electronic device to perform the method of the first aspect or any of the embodiments of the first aspect.

In a third aspect, embodiments of the present application provide a chip comprising one or more processors. The computer instructions, when executed by one or more processors, cause the electronic device to perform the method of the first aspect or any implementation of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the method of the first aspect or any implementation of the first aspect.

Drawings

FIG. 1A is a user interface of an OUC provided by an embodiment of the present application.

FIGS. 1B-1E are several user interfaces for displaying notifications of OUCs provided by embodiments of the present application.

Fig. 2 is a flowchart of a method for displaying notification information according to an embodiment of the present application.

Fig. 3 is a flowchart of a method for determining an update mode of an update OUC according to an embodiment of the present application.

Fig. 4 is an OS interaction diagram of a notification set of an electronic device management OUC according to an embodiment of the present application.

Fig. 5 is an OS interaction diagram of the electronic device according to the embodiment of the present application, where the OUC notification is displayed again after the OUC is updated.

Fig. 6 is a schematic hardware architecture of the electronic device 100 according to an embodiment of the present application.

Fig. 7 is a schematic software architecture of the electronic device 100 according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly and thoroughly described below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B; the text "and/or" is merely an association relation describing the associated object, and indicates that three relations may exist, for example, a and/or B may indicate: the three cases where a exists alone, a and B exist together, and B exists alone, and furthermore, in the description of the embodiments of the present application, "plural" means two or more than two.

The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the application, unless otherwise indicated, the meaning of "a plurality" is two or more.

The term "User Interface (UI)" in the following embodiments of the present application is a media interface for interaction and information exchange between an application program or an operating system and a user, which enables conversion between an internal form of information and a form acceptable to the user. The user interface is a source code written in a specific computer language such as java, extensible markup language (extensible markup language, XML) and the like, and the interface source code is analyzed and rendered on the electronic equipment to finally be presented as content which can be identified by a user. A commonly used presentation form of the user interface is a graphical user interface (graphic user interface, GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It may be a visual interface element of text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc., displayed in a display of the electronic device.

First, application programs in several electronic devices are described. Over-the-air technology updates client applications (OUCs), also known as software update applications, where OUCs may refer to a stand-alone application. For example, the electronic device may enter the OUC in response to a click operation of an application icon that acts on the OUC in the desktop. OUC may also be integrated in additional system applications of the setup application. For example, the electronic device may enter the OUC in response to a click operation on an application icon that sets the OUC in the application. In the embodiment of the present application, this is not limited. In particular, OUC is used to update the system of an electronic device, rather than updating a single system software. OUC may also be used to generate and display notification information related to updating the system to alert the user that the current electronic device may be updated with the system.

The OUC and the notification information generated by the OUC are described below in connection with a user interface displayed by the electronic device.

Fig. 1A illustrates a user interface provided by an OUC in an electronic device.

As shown in fig. 1A, user interface 200 may include, but is not limited to: return control 201, title name 202, version logo203, current version number 204, and check update control 205. In embodiments of the present application, the content included in the user interface 200 is merely illustrative, and the user interface 200 may include more or less content, which is not limited thereto.

Wherein the title name 202 may refer to the name of the application program comprising the current user interface 200, the title name 202 is illustratively displayed with the text "software update". The return control 201 is used to return to the previous level user interface. For example, the electronic device can display a user interface included in the setup application for displaying various lists of functions in response to a click operation on the return control 201. Version logo203 may display an image logo representing the version of the current system.

The current version number 204 may refer to the version number of the current system in the electronic device, and the version numbers of the systems before and after updating in the same electronic device are different. Illustratively, the current version number 204 is displayed with "3.0.0.150," which represents the version number of the system in the electronic device. Where "3.0.0" in "3.0.0.150" represents a major version number, typically used to represent large version updates done by the system in the electronic device. Large version updates may refer to systems after the update that may have large functional and/or interface variations. "150" in "3.0.0.150" represents a minor version number, typically used to represent a minor version update completed by a system in an electronic device. Small version updates may refer to some bugs in the repair system and/or optimizing system performance, etc. In the present application, large version updates and small version updates are a relative concept, not limitations of specific update content.

The check update control 205 may be used to check whether the system of the electronic device has a new version. For example, the electronic device can query the server as to whether the server generated a new version of the system in response to a click operation to check update control 205. If the server has generated a new version of the system, the electronic device may receive a determination message sent by the server, and then generate and display a notification to alert the consumer that the electronic device may perform a system update. For example, the notification may be text information "detect that the system has a new version, click to update", and the display form of the notification may refer to the subsequent notification display form shown in fig. 1D, which is not described herein. If the server does not generate the new version of the system, the electronic device may receive the denial message sent by the server, and then generate and display a notification that the electronic device does not need to perform system update. For example, the notification may be the text information "the current version is the latest version, and no update is required", and the display form of the notification may refer to the subsequent notification display form shown in fig. 1D, which is not described herein.

In some implementations, the OUC in the electronic device may also automatically detect whether a new version of the system of the electronic device is available without user-operated triggers. If the server has generated a new version of the system, the electronic device may receive a determination message sent by the server, and then generate and display a notification to alert the consumer that the electronic device may perform a system update. In addition to the notifications described above, the OUC in the electronic device may generate various other notifications.

In some implementations, in addition to the display form of the notifications described above (abbreviated interface display form), the electronic device can use a status bar to display notifications generated by various applications. In one possible implementation, if the electronic device displays the notification in the form of an interface display for a period of time (e.g., 3 s) and no user operation is detected for the notification, the electronic device does not display the notification in the form of an interface display but displays the notification in the notification bar. In the embodiment of the application, two modes and sequences for displaying the notification are not limited, for example, the notification can be displayed in the notification bar after being played in a voice playing mode, and the like, so long as the requirement that a user can observe or perceive the notification is met.

Illustratively, the electronic device may display the user interface 210 in response to an operation that acts on the top down slide in the user interface 200. As shown in fig. 1B, user interface 210 may include, but is not limited to: notification 211, notification 212, notification 213, and close control 214. Among them, the notification 211 and the notification 212 are notification information generated by OUC, and the notification 213 is notification information generated by other applications (e.g., social applications). The notification 211 may display the text information "honest invited you to NPS questionnaire", the notification 212 may display the text information "detect new version of the system, click to update", the notification 213 displays the text information "[ someone @ me ] 1 contacts send 6 messages. The electronic device may delete the notification 211 in response to a user operation to slide left or right on the notification 211. The electronic device may also display a user interface for filling out a net recommendation value questionnaire (Net Promoter Score, NPS) in response to a click operation by the user on the notification 211. The electronic device may delete the notification 212 in response to a user action on the left or right sliding of the notification 212. The electronic device may also begin updating the system in response to a click operation by the user on notification 212. The electronic device can display a superior user interface, i.e., user interface 200, in response to a click operation on the close control 214.

In one possible implementation, the electronic device may display the user interface 220 in response to an operation that acts on the top down slide in the user interface 200. As shown in fig. 1C, the user interface 220 may include: and a notification 221. The notification 221 is notification information generated by the OUC. The notification 221 displays a text message "75% of the system being updated". The electronic device can delete the notification 221 in response to a user operation to slide left or right on the notification 221. The notification 221 may be used to alert the user that the system of the current electronic device is being updated. Typically, a notification (e.g., notification 212) for alerting the user that the electronic device can download a new version of the system will not appear in the status bar at the same time as a notification (e.g., notification 221) for alerting the user that the system of the current electronic device is being updated. For example, after the electronic device displays the notification 212, the electronic device starts updating the system in response to a click operation by the user on the notification 212, and then the electronic device may display the notification 221.

Illustratively, when the text information displayed in the notification 221 in the user interface 220 is "100% of the system being updated," it is indicated that the electronic device has completed the update of the system. The electronic device may display the user interface 230. As shown in fig. 1D, the user interface 230 may be a desktop. The user interface 230 includes a notification 231. The notification 231 is notification information generated by the OUC. The notification 231 displays a text message "the system has completed updating, click restart". In one possible implementation, the electronic device may display a user interface 240 as shown in FIG. 1E in response to an operation that acts on a top down slide in the user interface 230. The user interface 240 may include, but is not limited to: notification 241, notification 242. Notification 241 and notification 242 are notification information generated by OUC. The notification 231 and the notification 241 are used for reminding the user that the system of the electronic device has completed updating, and the display forms of the notification and the notification are different. Notification 241 may display the text information "the system has completed updating, click to restart" and notification 242 may display the text information "honest invited you to NPS questionnaire". The electronic device may delete notification 241 in response to a user action on the left or right sliding of notification 241. The electronic device may also restart the new version of the system in response to a click operation by the user on notification 241. The electronic device may delete the notification 242 in response to a user operation to slide left or right on the notification 242. The electronic device can also display a user interface for filling out the NPS in response to a click operation by the user on the notification 242. Typically, a notification (e.g., notification 241) to alert the user that the system of the electronic device has completed an update does not appear in the status bar at the same time as a notification (e.g., notification 221) to alert the user that the system of the current electronic device is updating. For example, after the electronic device displays notification 221, the electronic device completes the update of the system, and then the electronic device may display notification 241.

In some implementations, not only does the system of the electronic device require an update upgrade, but the OUC also requires an update upgrade. Some ways of updating OUC include, but are not limited to, any of the following: 1. the electronic device updates the OUC through the system application updater. The system application updater is used to update various applications in the system in the electronic device and not just to update the OUC. Optionally, the system application updater is a system application in the electronic device that is not visible to a typical user. 2. The electronic device updates OUC by OUC. Since OUC is suitable for updating system versions, natural OUC may also be used to update one or more system applications. In the embodiment of the present application, the method is not limited to the update method, but may include more methods, which are not limited thereto.

Based on the above description, the following may occur:

the status bar of the electronic device displays notifications (e.g., notification 211) generated by the OUC. The electronic device then updates the OUC via the system application updater. After the OUC update is completed, the status bar of the electronic device no longer displays the notification (e.g., notification 211) that was previously generated by the OUC. This may result in the user not having observed notifications associated with the questionnaire, thereby resulting in the user not completing the associated questionnaire and reducing the amount of recovery of the questionnaire. And further, the manufacturer of the electronic equipment cannot receive the relevant feedback information of the user in time, which affects the improvement of the electronic equipment. Also, the user may not observe notifications related to system updates, thereby causing the electronic device to be unable to update the system in a timely manner.

The embodiment of the application provides a method for displaying notification information. In the method, the electronic device may display a first notification of the OUC and store the first notification in the electronic device. The electronic device then updates the OUC via the updater. During the OUC update, the electronic device does not display the first notification. After the OUC update is completed, the electronic device can redisplay the first notification of OUC.

The method for displaying notification information provided by the embodiment of the application is described below.

Fig. 2 illustrates a method for displaying notification information according to an embodiment of the present application. The method comprises the following steps:

s201, the electronic device displays the notification of OUC and stores the notification of OUC.

In some implementations, the manner in which the electronic device displays the notification may include: the notification is displayed by a status bar and hovered above the user interface. For example, the notification may be displayed in a status bar by referring to the user interface 210, and the notification may be displayed in a floating manner at an upper layer of the user interface by referring to the user interface 230. In one possible implementation, the electronic device may first hover display the notification at an upper layer of the user interface, and no user operation for the notification is detected for a period of time, and then display the notification through the status bar. In the embodiment of the present application, a method for displaying a notification is described by taking a manner of displaying a notification through a status bar as an example.

In some implementations, the notification of the OUC may include, but is not limited to: NPS questionnaire notification, ROM satisfaction questionnaire notification, new version system download notification, new version system install notification, restart notification, accessory (e.g., keyboard, headset, stylus, etc.) update notification, and so forth.

Wherein the NPS questionnaire notification may be used to alert the user to complete the NPS questionnaire. NPS is a customer's loyalty score to brands/products that is used to gauge how likely a customer will recommend a business or service to others. The NPS questionnaire may refer to a questionnaire generated by an electronic device at intervals after purchase of the electronic device (abbreviated as a shopping machine). For example, the electronic device may generate four types of NPS questionnaires based on the purchase time period, which may be divided into: 30 days, 90 days, 180 days and 360 days. For example, when the time of purchase reaches 30 days, the OUC of the electronic device may generate a NPS questionnaire of the first type; when the time period of the purchase reaches 180 days, the OUC of the electronic device may generate a third type of NPS questionnaire.

NPS questionnaires may include, but are not limited to: questionnaires scored for accurate characteristics and questionnaires for the system as a whole.

Wherein, the questionnaire scored for accurate characteristics may include: scoring for a function, reasons for scoring, advice, and so forth. For example, a questionnaire scored for accurate characteristics may include: the question "whether you are satisfied with the overall experience of the express mail retrieval reminder, please score according to your satisfaction" and 11 scoring options of options "0-10"; the problem "please describe in detail how to satisfy you, help us make better", etc.

The questionnaire for the system as a whole may include: recommendation score, recommendation cause, etc. For example, a questionnaire for the system as a whole may include: the question "comprehensively consider how much you are likely to recommend products to your friends or colleagues" factors of how many aspects you are currently using the product? 11 scoring options "and options" 0-10 "; the question "why do you like to recommend products to your friends or colleagues? "options" appearance: the appearance is good, the weight is moderate, the hand feeling is good, and the charging speed is high: fast charging speed "," communication: good communication effect, stable signal, quick internet surfing speed, and the like; the question "do you not want to recommend to your friends or co-workers that the reason for the product is? "options" appearance: the appearance is unsightly, the weight is heavier, the hand feeling is poor, and the charging speed is high: slow charging speed "," communication: poor communication effect, unstable signals, slow internet surfing speed, etc. In the embodiment of the present application, the types of the NPS questionnaires and the specific contents of the NPS questionnaires are only described by way of example, and may further include more contents, which are not limited thereto.

The ROM satisfaction questionnaire notification may be used to alert the user to complete the ROM satisfaction questionnaire. The ROM satisfaction questionnaire may refer to a questionnaire generated by an electronic device after a period of use by a user (e.g., 7 days) each time the system of the electronic device is upgraded to a new version of the system. The ROM satisfaction questionnaire may include: overall impact, feedback and advice, contact means. For example, the ROM satisfaction questionnaire may include: the question "how do you have an overall impression of the upgraded system? "and options" 5 points (very satisfactory) "," 4 points (satisfactory) "," 3 points (general) "," 2 points (less satisfactory) "," 1 points (very unsatisfactory) ", 5 options, question" please you give a score, we will continue to optimize, and continuously promote the user experience ", question" we will use a telephone return visit if willing, please leave a cell phone number ", etc. In the embodiment of the application, the specific content of the ROM satisfaction questionnaire is only described by way of example, and may further include more content, which is not limited.

The new version system download notification may be used to alert the consumer electronic device that the new version system is detected, and the new version system may be downloaded. For example, the new version system download notification may refer to the related description above with respect to notification 212. The new version system installation notification can be used for reminding the user of the completion of the new version system downloading of the electronic equipment, and the new version system can be installed. For example, a new version system installation notification may display text content "system has completed downloading, click install". The restart notification may be used to alert the user that the electronic device has installed the new version of the system, the electronic device may be restarted, and then the new version of the system is run. For example, a restart notification may display text content "the system has completed installation, click restart". In one possible implementation, the electronic device may generate a system update completion notification after the new version is downloaded and installed, where the system update completion notification is used to alert the user that the electronic device has downloaded and installed the new version of the system, and may restart the electronic device and then run the new version of the system. For example, the system update completion notification may refer to the relevant description regarding notification 231.

In the embodiment of the present application, the above-mentioned notification related to the new version system and the specific content are only exemplary, which is not limited thereto.

In some implementations, new versions of the system can be divided into the following types: first kind: system after upgrade for basic functions of system, second: and (3) aiming at the system after the system has single-point problem repair, and the third type: system after upgrade for system type (e.g. overseas version), fourth: the system after upgrade is performed for system customization (e.g., enterprise customization). When most of the functions of the system in the electronic device require further optimization, for example, optimization of the desktop layout in the electronic device, the electronic device may acquire a new version of the system of the first type. The first type is more common, and generally, more acquired new versions of systems in a user's electronic device are all of the first type. When a specific function of the system in the electronic device is problematic, for example, the bluetooth function in the electronic device cannot be used normally, the electronic device may acquire a new version of the system of the second type, and the new version of the system may be used to repair the situation that the bluetooth function cannot be used. When a system in the electronic device needs to be updated to a different type, for example, the electronic device needs to be updated to a system of a type of overseas version or mobile carrier version or telecom carrier version, etc., the electronic device may acquire a new version system of a third type. When a system in the electronic device needs to be updated to an enterprise-specific version, the electronic device may acquire a new version of the system of the fourth type. In general, an enterprise customized system has unique settings for some function that characterize the enterprise, such as ring tones, boot animation, etc.

The notifications generated by the electronic device regarding the new version of the system may also vary for different types of systems of the new version detected by the electronic device. For example, in the case where the new version system is the first one, the new version system download notification may be displayed as "detect that the system has a new version 3.0.0.151, click to update"; in the case that the new version system is the second type, the new version system download notification can be displayed as "new version with repair problem of system detected, click to update"; in the case that the new version system is the third type, the new version system download notification may be displayed as "detect that the system has a new version for overseas version, click to update"; in the case that the new version system is the fourth, the new version system download notification may be displayed as "detect that the system has a new version for a certain enterprise, click to update". In the embodiment of the present application, the specific content of the system-related notification for different types of new versions is only described as an example, which is not limited thereto.

In some implementations, the electronic device may display notifications of one or more OUCs, and may also store the notifications of OUCs generated by the electronic device in the electronic device. For example, the electronic device may store the notifications of OUCs in a file under the OUC directory in aggregate. For example, the electronic device may store text information, function, etc. information for each of the OUC's notifications, so that the electronic device may resume displaying the OUC's notifications by reading the stored OUC's notifications later.

In some implementations, the electronic device can also manage notifications of stored OUCs. Specifically, the electronic device may store the displayed notifications of OUCs in a notification set of OUCs. The electronic device can also delete the notifications of OUCs from the collection of notifications of OUCs. Illustratively, notification A and Notification B are notifications in the OUC notification set. The electronic device may delete the notification a of OUC from the notification set of OUC in response to a user deleting the notification a. Notification B is a new version of the system download notification. The electronic device may delete the notification B of OUC from the notification set of OUC in response to the user clicking on the notification B. The electronic device may also initiate downloading of the new version system in response to the user clicking on a control in the OUC to download the new version system. Since the electronic device has already begun downloading the new version of the system, the notification B of OUC also needs to be deleted from the notification set of OUC, depending on the business logic.

S202, the electronic equipment detects that the OUC with the new version exists.

In some implementations, a system in the electronic device applies an updater to detect if the OUC has a new version. The mechanism for updating the system application by the system application updater is as follows: and detecting whether the OUC with the new version exists in the server, and if so, directly downloading the OUC into the electronic equipment. The above mechanism may be understood as a mechanism for silent updating.

In some implementations, the system application updater can detect if a new version of OUC exists in the server if any of the following conditions are met:

1. in the case where the electronic device initiates the WIFI function and connects to the charger, the system application updater may detect if a new version of OUC exists in the server. In one possible implementation, the system application updater may detect up to 2 times within 24 hours.

2. Under the condition that the WIFI connected with the electronic equipment is changed, the system application updater can detect whether the OUC with the new version exists in the server. In one possible implementation, the system application updater may detect up to 4 times within 24 hours.

3. In the event of a fluctuation in the network to which the electronic device is connected, the system application updater may detect whether a new version of OUC exists in the server.

4. In the event that the electronic device provides an update software development kit (Software Development Kit, SDK) and/or downloads an SDK interface processing service, the system application updater may detect whether a new version of OUC exists in the server.

5. In the case where the user interface displayed by the electronic device is an update list page or a setup page in the system application updater, the system application updater may detect whether a new version of OUC exists in the server.

6. The system application updater may detect whether a new version of OUC exists in the server between a segment of the electronic device that completes the power-on broadcast.

In some implementations, in the event that the system application updater detects that a new version of OUC exists in the server, the electronic device can directly download the new version of OUC through the system application updater. The electronic device may also display a notification of the OUC during the download of the new version of the OUC. Specifically, the electronic device downloading the new version of the OUC may refer to downloading an upgrade package of the OUC. In one possible implementation, the upgrade package of the OUC may be an entire application package, directly used to generate a new version of the OUC. In another possible implementation, the upgrade package of OUCs may be a differential patch package, and new versions of OUCs may be generated in conjunction with old versions of OUCs. In the embodiment of the present application, this is not limited.

S203, the electronic device updates the OUC, and does not display a notification of the OUC.

In some implementations, the electronic device may update the OUC through a system updater.

In one possible implementation, the electronic device may also update OUC via OUC. In the embodiments of the present application, the way in which OUC is updated by OUC is not described in detail.

In an embodiment of the present application, the electronic device uses the system application updater to update the reason for the OUC: 1. other update channels update OUCs with the possibility of errors. For example, an old version OUC updates the old version OUC to a new version OUC by updating the new version of the system. However, in the case where the old version of OUC has a problem, the old version of OUC cannot be normally used. The OUC cannot be updated at this time. 2. Updating OUC using a system application updater may shorten the update period of OUC. This is because the OUC is updated in other update modes depending on the system update, and the system update period is long (e.g., about 120 days). The electronic device may update the OUC in a shorter period by the system application updater.

In some implementations, the updating of the OUC by the electronic device through the system updater may refer to: the electronic device uninstalls the old version of OUC and reinstalls the new version of OUC.

In some implementations, the electronic device needs to update OUC if the following conditions are met:

1. the electronic device downloads a new version of OUC.

2. The electronic device initiates an automatic update function. The automatic update functionality may be provided by a system setup application, for example. The automatic updating function can be set to be automatically updated under all network conditions or automatically updated under the condition of WIFI connection.

3. The situation in which the electronic device is connected to the network meets the setting in condition 2 described above. The method specifically comprises the following steps: the setting in the condition 2 can be automatically updated under all network conditions, and the electronic equipment is connected with a network (wifi or mobile network); the setting in the above condition 2 is that the electronic device can be automatically updated under the condition of WIFI connection, and the electronic device is connected with a WIFI network.

4. The power of the electronic device is greater than or equal to the power threshold. Illustratively, the power threshold may take a value of 10%.

5. The surface temperature of the electronic device is below a temperature threshold. For example, the temperature threshold may take on a value of 40 ℃.

In the embodiment of the present application, the above conditions are merely exemplary, and are not limited thereto.

In some implementations, the electronic device can uninstall the old version of OUC and reinstall the new version of OUC if the above is met. After unloading the old version of OUC, the electronic device has not displayed a notification of the OUC before installing the new version of OUC. That is, since the old version of OUC is offloaded, the electronic device does not have the old version of OUC, so that the electronic device does not have a function of displaying the notification of OUC, and thus the electronic device does not display the notification of OUC, but the electronic device still stores the notification of OUC.

In some implementations, the stored set of notifications of OUCs may still be managed in the electronic device based on user operations or business logic before unloading the old version of the OUCs. The specific management manner may refer to the description related to S201, which is not described herein.

S204, the electronic device starts the OUC and judges whether the OUC is updated by the system application updater.

In some implementations, the electronic device may quiesce to initiate a new version of OUC, and the electronic device may also initiate the OUC with the user interface 200 described above displayed. In the embodiment of the application, the condition for starting the OUC by the electronic device is only exemplified, and the OUC can also be started under the condition that the electronic device is connected with wifi, which is not limited.

In some implementations, after the electronic device initiates the new version OUC, a determination is also made as to how to update the OUC. In the embodiment of the present application, it is necessary to determine whether the OUC is updated by the system application updater because: if the OUC is updated through other update channels, the electronic device need not resume the OUC's notification display.

The following describes why the electronic device updates OUC through other update channels without restoring the notification display of OUC. Illustratively, the OUC detects a new version of system A that includes the new version of OUC. OUC may generate a download notification for the new version of system a. And the electronic equipment responds to the user operation and downloads the new version of the system A. The electronic device may then replace the new version OUC with the old version OUC. In this case, the notification generated by the OUC is the above download notification for the new version system a, and the above description shows that the electronic device has completed downloading the new version system a, and the download notification for the new version system a has implemented its function. Therefore, in the case of updating OUC, the electronic device does not need to resume displaying the download notification of the new version system a.

In some implementations, the electronic device can determine whether the OUC is updated by the system application updater by determining an android application package (Android application package, APK) version number of the new version of the OUC and an installation path of the APK. Wherein APK is an application package file format used by the operating system for distributing and installing mobile applications and middleware. By way of example, the electronic device may employ the following code examples to make the determination:

oldVersionCode != -1&&verCode>oldVersionCode&&isInstallInData()

where "oldVersionCode +.1" can indicate that the old version of OUC is present. This is because the electronic device can store notifications of old versions of OUCs only if old versions of OUCs exist. This field can be understood to improve the accuracy of the judgment. "verCode > oldVersioncode" may indicate that the APK version number of the current OUC is greater than the APK version number of the old version OUC. The two fields are used to indicate that the electronic device has updated the OUC.

"IsInstalInData ()" may indicate that the current OUC is installed in the data partition. This field is used to indicate that the current OUC is updated by the system application update.

How the electronic device determines whether the OUC is updated by the system application updater is described below in connection with fig. 3.

S301, the electronic device stores an APK version number of the old version OUC.

In some implementations, the electronic device will store the APK version number of the OUC after startup, i.e., after startup. That is, S301 may be performed before S201 described above.

S302, the electronic equipment starts OUC.

In some implementations, the electronic device may quiesce to initiate the OUC, which may also be initiated by the electronic device with the user interface 200 described above displayed. In the embodiment of the application, the condition for starting the OUC by the electronic device is only exemplified, and the OUC can also be started under the condition that the electronic device is connected with wifi, which is not limited.

S303, the electronic equipment reads the APK version number of the current OUC.

In some implementations, after the electronic device starts the OUC, the APK version number of the current OUC may be read.

S304, the electronic equipment judges whether the APK version number of the current OUC is larger than the APK version number of the OUC of the old version.

In some implementations, in the case where the current OUC is a new version of OUC, that is, before S302, the electronic device updates the old version of OUC to the new version of OUC, the electronic device may determine that the APK version number of the current OUC is greater than the APK version number of the old version of OUC. Then, S305 is performed.

In the case where the current OUC is an old version, that is, before S302, the electronic device does not update the old version of the OUC to the new version of the OUC, the electronic device may determine that the APK version number of the current OUC is equal to the APK version number of the old version of the OUC. Then, S307 is performed.

S305, the electronic device judges whether the current OUC is installed in the data partition of the electronic device.

The data partition is a partition of the electronic device for storing various APKs, and the silent installed APKs are stored under the data/app directory. The system partition is the partition that the electronic device uses to update the ROM, and the system/app directory stores the system's own APK.

In some implementations, S306 is performed in the case where the electronic device determines that the current OUC is installed in the data partition of the electronic device, i.e., the electronic device determines that the upgrade package of the downloaded OUC is installed in the data partition.

In some implementations, S308 is performed in the event that the electronic device determines that the current OUC is not installed in the data partition of the electronic device, e.g., in the event that the upgrade package of the downloaded OUC may be installed in a system partition.

S306, the electronic device determines that the old version of OUC is updated to the new version of OUC by the system application updater.

In some implementations, since the application updated by the system application updater is installed under the data/app directory, it can be determined that the old version of OUC is updated to a new version of OUC by the system application updater by determining that the current OUC is installed in the data partition of the electronic device.

S307, the electronic device determines that the current OUC is an old version of OUC, i.e. the OUC has no update.

S308, the electronic device determines that the old version of OUC is not updated to the new version of OUC by the system application updater.

In some implementations, because the application updated by other update pathways (e.g., system version upgrades via the OUC) is installed under the system/app directory, the electronic device can determine that the old version of the OUC is not updated to a new version of the OUC by the system application updater by determining that the current OUC is not installed on the data partition of the electronic device.

S309, the electronic device stores the APK version number of the current OUC.

In some implementations, after performing S306, S307, and S308 described above, S309 may be performed.

In some implementations, the above-described electronic device determining whether the OUC is updated by the system application updater may be performed after the electronic device starts the OUC. In one possible implementation, the electronic device determines whether updating the OUC by the system application updater is performed periodically, and the electronic device may perform the above determination each time the OUC is started.

In some implementations, after the electronic device determines that the OUC is updated by the system application updater, S205 may be performed.

In some implementations, the electronic device does not display a notification of the OUC after determining that the OUC is not updated by the system application updater.

S205, the electronic device reads out the notification of OUC, and displays the notification of OUC.

In some implementations, after the electronic device determines that the OUCs are updated by the system application updater, notifications of all the OUCs may be read from a collection of notifications of the OUCs and displayed. Since the electronic device does not judge the notification type of the OUC, i.e., does not judge what function each notification of the OUC is for indicating. So that only one or more of the notifications of all OUCs are not selected, one or more of which are displayed.

As can be seen from the above method flow, the electronic device can display the notification generated before the OUC update after the OUC update. In this way, the user can observe the notification related to the questionnaire in time and complete the questionnaire. To some extent, the recycling amount of the questionnaire can be increased, so that the manufacturer of the electronic device can receive the relevant feedback information. And the user can also observe the notification related to the system update in time, so that the electronic equipment can complete the system update in time.

An Operating System (OS) interaction diagram of the notification set of the electronic device management OUC provided by the implementation of the present application is described below in conjunction with fig. 4. Managing the notification set of OUCs may include, but is not limited to: store notifications, display notifications, delete notifications, and so forth. Wherein the System application updater, OUC, system UI belongs to an application of an application layer in the electronic device, the notification manager service (Notification Manager Service, NMS), and the package manager service (Package Manager Service, PMS) belongs to a module of an application framework layer in the electronic device. The definition of the above modules or software may also refer to the detailed description at the software architecture of the electronic device, and the specific roles of these modules are described in the following flow, which is not repeated herein.

The SystemUI is a system application that may include a user interface for a drop down panel in an electronic device, a user interface for a notification bar, and a user interface for a shortcut control. The SystemUI may be used to display notification bar, status bar, power, etc. controls.

S401, OUC generates a first notification and stores the first notification.

In some implementations, the first notification may have one or more. The first notification may include, but is not limited to: NPS questionnaire notification, ROM satisfaction questionnaire notification, new version system download notification, new version system install notification, restart notification, accessory update notification, and so forth. The related description of the first notification may refer to the detailed description in S201, which is not described herein.

The first notification may be stored in a local file (e.g., local sharedreferences) under the OUC directory, in a collection, specifically in a hard disk, rather than just in a cache.

S402, the OUC creates a notification object based on the first notification.

In some implementations, after the OUC generates the first notification, the first notification needs to be displayed. But OUC cannot interact directly with the SystemUI, but rather requires NMS to deliver notifications. And because the type of the message received by the NMS is a notification object. Therefore, the OUC needs to create a notification object, and the notification object created in S402 carries information about the first notification.

In some implementations, since the OUC may generate notifications at any time, the OUC may also create notification objects based on the first notification at any time.

S403, the OUC calls a notification method to transmit the notification object to the NMS.

In some implementations, after the OUC creates the notification object based on the first notification, the notification method may be invoked to transmit the notification object carrying the information of the first notification to the NMS.

S404, the NMS transmits the notification object to the System UI.

In some implementations, the NMS may transmit the notification object carrying the information of the first notification to the System UI. The NMS can act as a transport tool and it can ensure that the System UI can display notifications of various applications in order.

S405, displaying a first notification by the System UI.

In some implementations, the System UI of the electronic device can display the first notification within the status bar.

S406, the System UI receives the operation of deleting the first notification.

In some implementations, the operation of deleting the first notification may include, but is not limited to: click operations, swipe operations, voice commands, gesture commands, etc. Specifically, the System UI may receive a left-slide or right-slide operation of the user with respect to the first notification, and may also receive a click operation of the user with respect to the delete control of the first notification.

S407, the System UI transmits a message to delete the first notification to the OUC.

In some implementations, the System UI sends a message to the OUC to delete the first notification after receiving the operation to delete the first notification. Specifically, the System UI deletes the message of the first notification is broadcast transmission, and pendingintelt is set for the operation of deleting the first notification. PendingIntent may be viewed as a package to Intent, but rather than performing a certain action immediately, it does so after certain conditions are met or certain events are triggered. In the embodiment of the present application, the effect of pendingIntent can be understood as follows: after the event triggering the deletion of the first notification, the System UI will send a broadcast deleting the first notification, not all at the moment. And OUC statically registers broadcast reception, a broadcast to delete the first notification sent by the System UI may be received.

S408, OUC deletes the stored first notification.

In some implementations, the OUC deletes the first notification from the set of OUC notifications in the local SharedPreferences according to the message obtained in S407 to delete the first notification.

Optionally, S409 and OUC receive an operation of clicking on the first notification, and delete the stored first notification.

In some implementations, after the electronic device receives the operation of clicking the first notification, a function of the OUC is performed, for example: filling out NPS questionnaires, filling out ROM satisfaction questionnaires, downloading new version systems, installing new version systems, restarting electronic devices, and so forth. The OUC may directly receive the operation of clicking on the first notification. Since the function indicated by the first notification has already been implemented, it is logically also necessary to delete the first notification.

Optionally, S410, OUC receives an operation to start the function indicated by the first notification, and deletes the stored first notification.

In some implementations, the electronic device may perform the function of the OUC, which may be the function indicated by the first notification, in response to a user operation directly in the relevant user interface of the OUC, for example: filling out NPS questionnaires, filling out ROM satisfaction questionnaires, downloading new version systems, installing new version systems, restarting electronic devices, and so forth. Since the function of the first notification has already been implemented, it is logically also necessary to delete the first notification.

From the foregoing, it is appreciated that the electronic device can implement real-time management of stored OUC notifications. The method comprises the following steps: store notifications, display notifications, delete notifications, and so forth. This allows the stored OUC notifications to be read directly when the subsequent electronic device redisplays the OUC notifications.

An OS interaction diagram of the present application is described below with reference to fig. 5, in which the electronic device updates OUC and then displays the OUC notification again. The System application updater, OUC, system UI, NMS, and PMS may refer to the above detailed description, and will not be described herein.

S501, a system application updater periodically detects whether a new version of OUC exists.

In some implementations, the system application updater detecting whether a new version of OUC exists may refer to: the system application updater sends a message to the server for generating the new version of OUC asking if the new version of OUC is generated. And, the system application updater is periodically detected. The mechanism for detecting the periodicity of the system application updater may refer to the description related to S202, which is not described herein.

S502, the system application updater detects that a new version of OUC exists.

In some implementations, after the system application updater sends a message to the server for generating the new version of OUC, the message being used to query the server as to whether the new version of OUC has been generated, the system application updater may receive a confirmation message sent by the server, i.e., the system application updater detects that the new version of OUC exists.

S503, the system application updater downloads the new version of OUC.

In some implementations, when the system application updater detects that a new version of OUC exists, the system application updater downloads the new version of OUC from the server.

S504, the system application updater sends update information to the PMS when the update condition is met.

In some implementations, the system application updater may begin updating the new version of OUC if the update condition is met, i.e., may send update information to the PMS instructing the PMS to uninstall the old version of OUC and install the new version of OUC. The update condition may refer to the related description in S203, which is not described herein.

S505, PMS uninstalls old version of OUC.

In some implementations, the PMS uninstalls the old version of the OUC after receiving the update information.

S506, the PMS sends a packet unloading broadcast.

In some implementations, the PMS may send a packet offload broadcast after offloading the old version of OUC.

S507, system UI does not display all notifications of OUC.

In some implementations, the System UI may not display all notifications of OUC after receiving the PMS-sent packet offload broadcast. If the System UI displays notifications of other applications, for example, the notification 213, the System UI is not affected to display notifications of other applications.

S508, the PMS installs the OUC of the new version.

In some implementations, the PMS may install the downloaded new version of OUC after unloading the old version of OUC.

In some implementations, S407 and S408 may be performed simultaneously, or S407 may be performed before S408 is performed. In the embodiment of the present application, this is not limited.

S509, the OUC after the update is started.

In some implementations, the electronic device may quiesce to initiate the OUC, which may also be initiated by the electronic device with the user interface 200 described above displayed. In the embodiment of the application, the conditions of the OUC after the electronic device starts updating are only illustrated by way of example, and the OUC can also be started under the condition that the electronic device is connected with wifi, which is not limited.

S510, the OUC judges whether the OUC is updated by the system application updater.

In some implementations, the OUC may refer to the description related to S204 above for determining whether the OUC is updated by the system application updater, which is not described herein. After the OUC determines that the OUC is updated by the system application updater, S411 is performed.

S511, OUC determines whether to store the notification of OUC.

In some implementations, the preconditions for the electronic device to resume displaying notifications of OUCs are: the electronic device has stored therein a notification of the OUC. If the notifications of the stored OUCs in the electronic device have been completely deleted before the PMS uninstalls the old version, the OUCs determine that the set of stored notifications of the OUCs is an empty set, i.e., no notifications of any OUCs are currently stored. Then, the flow is ended.

If the old version of OUC is produced with a notification of OUC and the notification of OUC stored in the electronic device is not all deleted before the PMS uninstalls the old version, the OUC determines that the notification of OUC is stored. Then, S512 is performed.

S512, the OUC creates a notification object based on the stored notification of the OUC.

In some implementations, after the OUC determines that the notification of the OUC is stored, the restoration of the notification of the display of the OUC may begin. But OUC cannot interact directly with the SystemUI, but rather requires NMS to deliver notifications. And because the type of the message received by the NMS is a notification object. Therefore, the OUC needs to create a notification object, and the notification object created in S512 carries information about the first notification.

S513, the OUC calls the notification method to transmit the notification object to the NMS.

In some implementations, after the OUC creates a notification object based on the stored OUC notification, a notification method may be invoked to transmit the notification object with the information of the stored OUC notification carried by it to the NMS.

S514, the NMS transmits the notification object to the System UI.

S515, system UI displays the stored notification of the OUC.

In some implementations, the currently launched OUC may be a new version of the OUC. The System UI may also display notifications generated by old versions of OUCs, i.e., notifications of stored OUCs. In addition, the new version of OUC may also generate a notification of the OUC, and display the notification of the new version of OUC, and the process may refer to the flow shown in fig. 4 and will not be described herein.

In one possible implementation, the interaction diagram shown in fig. 4 above may be performed prior to S505 in fig. 5. I.e. the electronic device can manage notifications generated by the old version of OUC if the old version of OUC is installed. In another possible implementation, the interaction diagram shown in fig. 4 may be performed after S508 in fig. 5. That is, the electronic device may manage notifications generated by the old version of OUC and notifications generated by the new version of OUC if the new version of OUC is installed.

In the embodiment of the present application, the content in the user interface is merely illustrated, and may further include more or less content, which is not limited thereto.

In some implementations, the old version of OUC may be referred to as a first version of OUC, the notification of the display of OUC in S201 may be referred to as a first notification, the data partition may be referred to as a first directory, the system partition may be referred to as a second partition, the new version of OUC may be referred to as a second version of OUC, and the notification of the deletion may be referred to as a third notification. The message sent by the electronic device to the server to query the server as to whether the server generated a new version of OUC may be referred to as a first message, and the message sent by the server to the electronic device to determine that there is a new version of OUC may be referred to as a second message.

Fig. 6 shows a schematic structural diagram of the electronic device 100.

The electronic device 100 may be a portable terminal device having an iOS, android, microsoft, halony, or other operating system mounted thereon, and the electronic device 100 may be a mobile phone, a tablet, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (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, a vehicle-mounted device, a smart home device, and/or a smart city device, but the electronic device 100 may also include a non-portable terminal device such as a laptop computer (laptop) having a touch-sensitive surface or a touch panel, a desktop computer having a touch-sensitive surface or a touch panel, and the like. The embodiment of the application does not limit the specific type of the electronic device.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 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 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can 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 an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 communicates with the touch sensor 180K through an I2C bus interface to implement a touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface to implement a function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through a UART interface, to implement a function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing functions of electronic device 100. The processor 110 and the display 194 communicate via a DSI interface to implement the display functionality of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal or as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, an MIPI interface, etc.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices, etc.

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

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

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

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (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 to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates and filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. 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 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 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 display screen 194 is used to display images, videos, and the like. The display 194 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 (flex), 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 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The internal memory 121 may include one or more random access memories (random access memory, RAM) and one or more non-volatile memories (NVM).

The random access memory may include a static random-access memory (SRAM), a dynamic random-access memory (dynamic random access memory, DRAM), a synchronous dynamic random-access memory (synchronous dynamic random access memory, SDRAM), a double data rate synchronous dynamic random-access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, such as fifth generation DDR SDRAM is commonly referred to as DDR5 SDRAM), etc.; the nonvolatile memory may include a disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. divided according to an operation principle, may include single-level memory cells (SLC), multi-level memory cells (MLC), triple-level memory cells (TLC), quad-level memory cells (QLC), etc. divided according to a storage specification, may include universal FLASH memory (english: universal FLASH storage, UFS), embedded multimedia memory cards (embedded multi media Card, eMMC), etc. divided according to a storage specification.

The random access memory may be read directly from and written to by the processor 110, may be used to store executable programs (e.g., machine instructions) for an operating system or other on-the-fly programs, may also be used to store data for users and applications, and the like.

The nonvolatile memory may store executable programs, store data of users and applications, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 may be used to connect external non-volatile memory to enable expansion of the memory capabilities of the electronic device 100. The external nonvolatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and video are stored in an external nonvolatile memory.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 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 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the invention, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

Fig. 7 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present invention.

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 four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

The application package may include camera, gallery, calendar, talk, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications. As shown in fig. 7, the application package may further include: system application updates, OUC, system UI.

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.

The application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, and the like. As shown in fig. 7, the application framework layer may further include: a notification manager service (Notification Manager Service, NMS), a packet manager service (Package Manager Service, PMS).

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

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 telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

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

The NMS allows the application to display notification information in the status bar, can be used to convey 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 PMS may be used to uninstall applications and install applications. PMS may also be used to send packet offload broadcasts.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries 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.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

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.

The workflow of the electronic device 100 software and hardware is illustrated below in connection with capturing a photo scene.

When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into the original input event (including information such as touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as an example of a control of a camera application icon, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera driver by calling a kernel layer, and captures a still image or video by the camera 193.

The embodiments of the present application may be arbitrarily combined to achieve different technical effects.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

In summary, the foregoing description is only exemplary embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention should be included in the protection scope of the present invention.

Claims

1. A method of displaying notifications, the method comprising:

starting a first version of software update application OUC;

displaying a first notification at a first time, the first notification generated by the first version of OUC;

downloading the second version of OUC;

installing the second version of OUC to a first directory and not displaying the first notification;

starting the OUC of the second version;

displaying the first notification at a second time, the second time being later than the first time;

Displaying a second notification at a third time, the second notification generated by the second version of OUC;

downloading a third version of OUC;

installing the third version of OUC to a second directory and not displaying the second notification;

starting the third version of OUC;

and not displaying the second notification at a fourth time, wherein the fourth time is later than the third time.

2. The method of claim 1, wherein displaying the first notification at the second time comprises:

based on the second version of OUC being downloaded by a system application updater, the first notification is displayed at the second time.

3. The method according to claim 1 or 2, wherein said not displaying the second notification at the fourth moment in time comprises:

based on the third version of OUC not being downloaded by the system application updater, the second notification is not displayed at the fourth time.

4. The method of claim 3, wherein the first directory indicates a data partition and the second directory indicates a system partition.

5. The method of claim 4, wherein the first directory is for storing applications downloaded by a system application updater and the second directory is for storing applications downloaded by a non-system application updater.

6. The method of claim 5, wherein after the displaying the first notification at the first time, the method further comprises:

storing the first notification;

before said displaying said first notification at the second time, said method further comprises:

and reading the stored first notification.

7. The method of claim 6, wherein prior to said downloading the second version of OUC, the method further comprises:

displaying a third notification at the first time, the third notification generated by the first version of OUC;

receiving and responding to the first operation, deleting and not displaying the third notification;

after the initiating the second version of OUC, the method further comprises:

and not displaying the third notification at the second moment.

8. The method of claim 7, wherein prior to said downloading the second version of OUC, the method further comprises:

sending a first message to a server at fixed time intervals, the first message for querying the server whether to generate OUCs of other versions than the first version;

a second message is received indicating that the server has generated the second version of OUC.

9. The method of claim 8, wherein prior to installing the second version of OUC into the first directory, the method further comprises:

unloading the first version of OUC.

10. An electronic device comprising a memory, one or more processors; the memory is coupled with the one or more processors, the memory for storing computer program code comprising computer instructions that the one or more processors invoke to cause the electronic device to perform the method of any of claims 1-9.

11. A chip for application to an electronic device, characterized in that the chip comprises one or more processors for invoking computer instructions to cause the electronic device to perform the method according to any of claims 1-9.

12. A computer readable storage medium comprising instructions which, when run on an electronic device, cause the electronic device to perform the method of any of claims 1-9.