CN108123816B

CN108123816B - System upgrading method and device

Info

Publication number: CN108123816B
Application number: CN201611075435.8A
Authority: CN
Inventors: 詹远; 吴鸣
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2016-11-28
Filing date: 2016-11-28
Publication date: 2021-06-29
Anticipated expiration: 2036-11-28
Also published as: CN108123816A

Abstract

The disclosure relates to a system upgrading method and device. The method comprises the following steps: when detecting that the safety software is started, acquiring the use information of the system and the application; and calculating the safety state score of the system operation according to the use information of the system and the application, wherein the safety state score is used for marking the physical examination level of the system. The technical scheme can effectively avoid the problem that the user can know the safety state score of the equipment only by clicking the physical examination button in the related technology, and the safety state score can be calculated only by acquiring the use information of the system and the application without scanning each file in the equipment one by the equipment, so that the time consumption is short, and the user experience is optimized.

Description

System upgrading method and device

Technical Field

The present disclosure relates to the field of mobile device technologies, and in particular, to a system upgrade method and apparatus.

Background

An Android (Android) mobile phone can upgrade the system in an Over-the-Air Technology (OTA for short) upgrading mode. The system version is divided into a development version and a stable version, the development version is high in push-out frequency and new in function, but a Bug risk may exist, and the stable version is low in push-out frequency but stable in performance.

In the related art, when the system version of the system is pushed out each time, the system update server may push the system version to the user equipment without depending on the user type, and further may cause that the system version integrated with the new function is not pushed to a player user (a user who likes to experience the new function and likes to play a mobile phone), so that the user willing to experience the new function does not have a chance to experience the new function, or the system version integrated with the new function is pushed to a conservative user (a user who does not want to experience the new function), and the user unwilling to undertake the risk of experiencing the new version bears the risk of the new version system, thereby greatly affecting the experience of the user in upgrading the system.

Disclosure of Invention

In order to overcome the problems in the related art, embodiments of the present disclosure provide a system upgrade method and apparatus, so as to solve the problem of poor user experience caused by not upgrading a system according to user types.

According to a first aspect of the embodiments of the present disclosure, there is provided a system upgrade method applied to a first server, the method including:

receiving an account type query message sent by a sender;

and sending an account type response message to the sender according to the account type query message, wherein the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account.

In an embodiment, the method further comprises:

calculating the system updating frequency of each user account in a set time period according to the system updating information uploaded by user equipment logged in by the user account in the set time period;

and determining the system updating priority of each user account according to the system updating frequency of each user account.

In an embodiment, the method further comprises:

calculating the system updating times of each user account in a set time period according to the system updating information uploaded by user equipment logged in by the user account in the set time period;

and determining the system updating priority of each user account according to the system updating times of each user account.

According to a second aspect of the embodiments of the present disclosure, there is provided a system upgrade method applied to a second server, the method including:

sending an account type query message to a first server;

receiving an account type response message returned by the first server, wherein the account type response message carries a system updating priority of a user account, and the system updating priority is determined according to system updating information uploaded by user equipment logged in by the user account;

and executing gray scale upgrading operation on the system to be updated based on the system updating priority of the user account.

In an embodiment, performing a grayscale upgrade operation on a system to be updated based on a system update priority of the user account includes:

preferentially sending a system to be updated to user equipment logged in by a user account with a first priority, wherein the first priority is used for representing the level with the highest priority;

determining whether to send a system to be updated to other user accounts according to the feedback information of the user accounts with the first priority;

and if the system to be updated is determined to be sent to other user accounts, the system to be updated is sent to the user equipment logged in by the user account in sequence from high to low based on the system update priority of the user account.

According to a third aspect of the embodiments of the present disclosure, there is provided a system upgrade method applied to a user equipment, the method including:

sending an account type query message to a first server;

when receiving a system updating message which is sent by a second server and used for updating a preset type of system to be updated, determining whether the system updating priority of a currently logged user account is lower than a preset priority;

and if the system updating priority of the currently logged user account is lower than the preset priority, refusing to execute the operation of displaying the system updating prompt information.

In an embodiment, the method further comprises:

and if the system updating priority of the currently logged user account is not lower than the preset priority, performing the operation of displaying the system updating prompt information.

In an embodiment, the method further comprises:

when receiving a message that a user account successfully logs in user equipment, determining whether the current login is the first login after a system is to be updated;

and if the current login is the first login after the system is to be updated, sending system update information to a first server, wherein the system update information comprises a user account and system update time logged in during system update, and the system update information is used for the first server to determine the system update priority of the user account.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a first server, the apparatus including:

the first receiving module is configured to receive an account type query message sent by a sender;

the first sending module is configured to send an account type response message to the sender according to the account type query message received by the first receiving module, wherein the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account.

In an embodiment, the apparatus further comprises:

the frequency calculation module is configured to calculate the system update frequency of each user account in a set time period according to the system update information uploaded by user equipment logged in by the user account in the set time period;

a first determining module configured to determine a system update priority of each user account according to the system update frequency of each user account calculated by the frequency calculating module.

In an embodiment, the apparatus further comprises:

the number calculating module is configured to calculate the system updating times of each user account in a set time period according to the system updating information uploaded by user equipment logged in by the user account in the set time period;

and the second determining module is configured to determine the system update priority of each user account according to the system update times of each user account calculated by the time calculating module.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a second server, the apparatus including:

the second sending module is configured to send an account type query message to the first server;

a second receiving module, configured to receive an account type response message returned by the first server according to the account type query message sent by the second sending module, where the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account;

the upgrading module is configured to execute a grayscale upgrading operation on the system to be updated based on the system updating priority of the user account carried in the account type response message received by the second receiving module.

In one embodiment, the upgrade module includes:

the system updating method comprises a first sending submodule and a second sending submodule, wherein the first sending submodule is configured to send a system to be updated to user equipment logged in by a user account with a first priority, and the first priority is used for representing the level with the highest priority;

the first determining submodule is configured to determine whether to send the system to be updated to other user accounts according to feedback information returned by the system to be updated by the user accounts with the first priority;

and the second sending submodule is configured to send the to-be-updated systems to the user equipment logged in by the user account in sequence from high to low based on the system updating priority of the user account when the first determining submodule determines to send the to-be-updated systems to other user accounts.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a user equipment, the apparatus including:

a third sending module configured to send an account type query message to the first server;

a third receiving module, configured to receive an account type response message returned by the first server according to the account type query message sent by the third sending module, where the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account;

the third determining module is configured to determine whether the system update priority of the currently logged-in user account is lower than a preset priority or not when receiving a system update message which is sent by the second server and used for updating a preset type of system to be updated;

and the display rejection module is configured to reject to perform the operation of displaying the system update prompt information when the third determination module determines that the system update priority of the currently logged-in user account is lower than a preset priority.

In an embodiment, the apparatus further comprises:

and the display module is configured to execute the operation of displaying the system update prompt information when the third determination module determines that the system update priority of the currently logged user account is not lower than the preset priority.

In an embodiment, the apparatus further comprises:

the fourth determination module is configured to determine whether the current login is the first login after the system is to be updated when a message that the user account successfully logs in the user equipment is received;

a fourth sending module, configured to send system update information to the first server when the fourth determining module determines that the current login is a first login after a system is to be updated, where the system update information includes a user account and system update time logged in during system update, and the system update information is used by the first server to determine a system update priority of the user account.

According to a seventh aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a first server, the apparatus including:

a first processor;

a first memory for storing first processor-executable instructions;

wherein the first processor is configured to:

receiving an account type query message sent by a sender;

According to an eighth aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a second server, the apparatus including:

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

sending an account type query message to a first server;

According to a ninth aspect of the embodiments of the present disclosure, there is provided a system upgrade apparatus applied to a user equipment, the apparatus including:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

sending an account type query message to a first server;

when receiving a system updating message which is sent by a second server and used for updating a preset type of system to be updated, determining whether to display system updating prompt information or not according to the system updating priority of a currently logged user account;

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: when receiving an account type query message sent by a sender, such as a second server, a first server can send a system update priority of a user account determined according to system update information uploaded by user equipment to the sender, so that when pushing a system to be updated, the second server receiving the system update priority of the user account can preferentially send the system to be updated to user equipment logged in by a user account with high priority, and the experience of a user willing to experience a new function is improved; in addition, or the first server may also send the system update priority of the user account to the user equipment, the user equipment that receives the system update priority of the user account may determine whether to display the system update prompt information according to the priority of the user equipment, and if the system update priority of the user account is lower, the system update prompt information may not be displayed, so that the system to be updated pushed by the second server is not updated, and the problem that the risk of experiencing the system to be updated may exist is avoided.

Moreover, the first server can calculate the system updating frequency or times of each user account by receiving the system updating information uploaded by the user equipment within a set time period, and further determine the system updating priority of each user account, so that the user type can be determined according to the actual system updating frequency or times of the user, the system updating can better accord with the actual use habits of the user, and the user experience is optimized.

The method comprises the steps of sending a system to be updated to user equipment logged in by a user account with a first priority preferentially, determining whether to send the system to be updated to other user accounts according to feedback information of the user account with the first priority, if the feedback information of the system to be updated indicates that the system to be updated has no risk and problem, determining to send the system to be updated to other user accounts, and sending the system to be updated to the user equipment logged in by the user account in sequence from high to low based on the system updating priority of the user account, so that the problem that the risk possibly existing in the system to be updated is not experienced can be avoided.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

FIG. 1A is a flow diagram illustrating a method of system upgrade, according to an example embodiment.

Fig. 1B is a first application scenario diagram illustrating a system upgrade method according to an example embodiment.

Fig. 1C is a diagram illustrating an application scenario of a system upgrade method according to an exemplary embodiment.

FIG. 2 is a flow diagram illustrating a method of system upgrade, according to an example embodiment.

FIG. 3 is a flowchart illustrating a system upgrade method according to an example embodiment two.

FIG. 4 is a flowchart of a system upgrade method according to a third illustrative embodiment.

FIG. 5 is a flowchart illustrating a system upgrade method according to an example embodiment.

FIG. 6 is a flow diagram of a system upgrade method according to an example embodiment.

FIG. 7 is a block diagram illustrating a system upgrade apparatus according to an example embodiment.

FIG. 8 is a block diagram illustrating another system upgrade apparatus according to an example embodiment.

FIG. 9 is a block diagram illustrating a system upgrade apparatus according to an example embodiment.

FIG. 10 is a block diagram illustrating another system upgrade apparatus according to an example embodiment.

FIG. 11 is a block diagram illustrating a system upgrade apparatus according to an example embodiment.

FIG. 12 is a block diagram illustrating another system upgrade apparatus according to an example embodiment.

FIG. 13 is a block diagram illustrating a suitable system upgrade apparatus, according to an example embodiment.

FIG. 14 is a block diagram illustrating a suitable system upgrade apparatus, according to an example embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.

FIG. 1A is a flowchart illustrating a system upgrade method according to an example embodiment, FIG. 1B is a first application scenario diagram illustrating the system upgrade method according to an example embodiment, and FIG. 1C is a second application scenario diagram illustrating the system upgrade method according to an example embodiment; the system upgrading method may be applied to a first server, such as an account server, as shown in fig. 1A, and includes the following steps:

in step 101, an account type query message sent by a sender is received.

In an embodiment, the sender may be a second server, i.e. a system push server, which may be referred to in the description of the exemplary scenario shown in fig. 1B and will not be described in detail herein; in yet another embodiment, the sender may be a user equipment, which may be referred to in the description of the exemplary scenario illustrated in fig. 1C, and will not be described in detail here.

In step 102, an account type response message is sent to the sender according to the account type query message, the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account.

In one embodiment, the system update priority is used to indicate a priority level of updating the system by the user equipment in which the user account is logged, for example: the system update priority of the user who is very fond of flashing is higher than that of the user who is not fond of flashing.

In one embodiment, the system update priority for each user account may be determined by the user's historical system update information, as seen in the embodiment shown in fig. 2, which will not be described in detail herein.

In an exemplary embodiment, referring to fig. 1B, when receiving an account type query message sent by the second server 120, the first server 110 may send an account type response message to the second server 120, where the response message carries a system update priority of a user account, the second server 120 may perform a grayscale upgrading operation on the system to be updated based on the system update priority of the user account, that is, preferentially send the system to be updated to the

user equipment

130, 131 8513N logged in by the user account with the highest priority, count feedback information sent by the

user equipment

130, 131 … N, determine whether the system to be updated can continue to be pushed to other user accounts according to the feedback information, for example, the feedback information is good, that is, the system to be updated has no big problem, then push the system to other user accounts may be performed, otherwise, push the system to be updated may be stopped, and pushed again when a problem with the system to be updated is fixed. Wherein the system update priority of each user device may be determined by the first server 110 according to the system update information uploaded by each user.

In yet another exemplary embodiment, referring to fig. 1C, when the first server 110 receives the account type query message sent by the user device 130, the account type response message may be sent to the user equipment 130, where the response message carries the system update priority of the user account, and the user equipment 130 may determine whether to display the system update prompting information based on the system update priority of the user account when receiving the system update message for updating the preset type of system to be updated, if the system update priority of the user account is lower than the preset priority, for example, the system update priority of the user account is 4, and the preset priority is 5, it may be determined that the system update prompt message is not presented, therefore, the user is prevented from updating the system to be updated according to the system updating prompt information, and in the embodiment, the system to be updated of the preset type can be understood as the system to be updated of the development version with poor stability.

In this embodiment, when receiving an account type query message sent by a sender, such as a second server, a first server may send a system update priority of a user account determined according to system update information uploaded by user equipment to the sender, so that when pushing a system to be updated, the second server receiving the system update priority of the user account may preferentially send the system to be updated to user equipment logged in by a user account with a high priority, thereby improving user experience willing to experience a new function; in addition, or the first server may also send the system update priority of the user account to the user equipment, the user equipment that receives the system update priority of the user account may determine whether to display the system update prompt information according to the priority of the user equipment, and if the system update priority of the user account is lower, the system update prompt information may not be displayed, so that the system to be updated pushed by the second server is not updated, and the problem that the risk of experiencing the system to be updated may exist is avoided.

In an embodiment, the method further comprises:

according to system updating information uploaded by user equipment logged in by a user account in a set time period, calculating the system updating times of each user account in the set time period;

Please refer to the following embodiments for the specific case of upgrading the system.

Therefore, the method provided by the embodiment of the disclosure can enable a user willing to actively experience a new function to experience all the systems to be updated as early as possible, and can greatly reduce the risk of the user unwilling to bear the risk of the new system.

The technical solutions provided by the embodiments of the present disclosure are described below with specific embodiments.

FIG. 2 is a flow diagram illustrating a method of system upgrade in accordance with an illustrative embodiment; in this embodiment, by using the method provided by the embodiment of the present disclosure, an example is given by taking the first server determining the system update priority of the user account, as shown in fig. 2, including the following steps:

in step 201, according to the system update information uploaded by the user equipment logged in by the user account within the set time period, the system update frequency/times of each user account within the set time period is calculated.

In an embodiment, the set time period may be a time period (e.g., within the last three months) during which the user account has recently logged into the user device.

In one embodiment, the system update information may include information such as an update time, a user account registered when the system is updated, and the like.

In an embodiment, the system update times are total times of updating the system on the premise that the user account logs in the user equipment within a set time period.

In an embodiment, the system update frequency may be determined according to the total number of system updates in the set time period and the length of the set time period, for example: the set time period is 3 months, the system updating times are 9 times, and the system updating frequency is three times per month.

In step 202, the system update priority of each user account is determined according to the system update frequency/times of each user account.

In an embodiment, all the user accounts may be divided into N priority levels in advance, for example, the user accounts are divided into three priority levels, and each priority level corresponds to a system update frequency interval or a system update time interval. For example: the system updating frequency is that the user accounts updated for more than three times in a month are of a first priority, the user accounts updated for one to three times in a month are of a second priority, and the user accounts updated for less than one time in a month are of a third priority. In another embodiment, the method for dividing the user types according to the system update times can be referred to as a method for dividing the user types according to the system update frequency, and will not be described in detail here.

In this embodiment, the first server may calculate the system update frequency or frequency of each user account by receiving the system update information uploaded by the user equipment within a set time period, and further determine the system update priority of each user account, thereby determining the user type according to the actual system update frequency or frequency of the user, so that the system update may better conform to the actual usage habits of the user, and the user experience may be optimized.

Fig. 3 is a flowchart of a system upgrade method according to an exemplary embodiment, where the system upgrade method may be applied to a second server, and the present embodiment is described below with reference to the exemplary scenario shown in fig. 1B, where as shown in fig. 3, the system upgrade method includes the following steps:

in step 301, an account type query message is sent to a first server.

In an embodiment, the second server may send an account type query message to the first server when the system to be updated needs to be pushed.

In step 302, an account type response message returned by the first server is received, where the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by the user equipment logged in by the user account.

In one embodiment, the system update priority of the user account is used to indicate the priority level of the user equipment to which the user account is logged in to update the system, for example: the system update priority of the user who is very fond of flashing is higher than that of the user who is not fond of flashing.

In step 303, based on the system update priority of the user account, a grayscale upgrade operation is performed on the system to be updated.

In one embodiment, the method for performing the gray scale upgrade operation on the system to be updated can be referred to the embodiment shown in fig. 4, which will not be described in detail herein.

In an exemplary embodiment, referring to fig. 1B, after the second server 120 sends the account type query message to the first server 110, the account type response message may be received, the response message carries the system update priority of the user account, the second server 120 may perform a grayscale upgrade operation on the system to be updated based on the system update priority of the user account, that is, the system to be updated is preferentially sent to the

user equipment

130, 131 … 13N logged in by the user account with the highest priority level, and the feedback information sent by the

user equipment

130, 131 … 13N is counted, and determining whether the system to be updated can continue to push to other user accounts according to the feedback information, for example, the feedback information is good, and if the system to be updated has no big problems, pushing the system to be updated to other user accounts, otherwise, stopping pushing the system to be updated, and pushing the system to be updated when the problems of the system to be updated are repaired.

In one embodiment, performing a grayscale upgrade operation on a system to be updated based on a system update priority of a user account includes:

Please refer to the following embodiments for details of how to upgrade the system.

FIG. 4 is a flowchart of a system upgrade method according to a third illustrative embodiment; in this embodiment, by using the method provided by the embodiment of the present disclosure, an example is given in which the second server performs gray scale upgrading on the system to be updated based on the system update priority of the user account, as shown in fig. 4, the method includes the following steps:

in step 401, a system to be updated is preferentially sent to a user equipment logged in by a user account with a first priority, where the first priority is used to indicate a level with a highest priority.

In step 402, it is determined whether to send a system to be updated to other user accounts according to the feedback information of the user account with the first priority.

In an embodiment, after sending the system to be updated to the user equipment logged in to the user account with the first priority, the second server may count the feedback information of each user equipment for the system to be updated after a preset time, for example, count the feedback information after a week after sending the system to be updated.

In an embodiment, if the feedback information indicates that the system to be updated has a huge problem, pushing the system to be updated may be temporarily stopped, and the system to be updated is pushed after the problem is repaired.

In step 403, if it is determined that the system to be updated is sent to other user accounts, the system to be updated is sent to the user devices logged in by the user accounts in sequence from high to low based on the system update priority of the user accounts.

In an embodiment, if the feedback information of the user with the first priority indicates that the system to be updated does not have the problem of stopping pushing the system, the system to be updated may be sequentially sent to the user equipment to which the user accounts log in according to the system update priorities from high to low, for example, the system to be updated may be sent to the user equipment to which the user accounts with the second priority and the third priority log in next time, and after the system to be updated is sent to the user equipment to which the user account with one priority logs in each time, the feedback information sent by the corresponding user equipment may be counted, and it may be determined whether to continue to push the system to be updated to the user equipment to which the user account with the next priority logs in according to the feedback information.

In this embodiment, by performing the grayscale upgrading operation on the system to be updated according to the system update priority of the user account, it can be achieved that the user account with the highest priority first upgrades the system of the new version, and the user with the lowest priority finally upgrades the system of the new version, so that the system risk borne is also lowest.

Fig. 5 is a flowchart of a system upgrade method according to an exemplary embodiment, where the system upgrade method may be applied to a user equipment, as shown in fig. 5, and the present embodiment is described with reference to the exemplary scenario shown in fig. 1C, where the system upgrade method includes the following steps:

in step 501, an account type query message is sent to a first server.

In step 502, an account type response message returned by the first server is received, where the account type response message carries the system update priority of the user account.

In an embodiment, the system update priority is determined according to system update information uploaded by user equipment logged in by a user account.

In an embodiment, the account type response message may carry a system update priority corresponding to a user account that sends the account type query message.

In step 503, when a system update message for updating a preset type of system to be updated, which is sent by the second server, is received, it is determined whether the system update priority of the currently logged-in user account is lower than a preset priority, and if the system update priority of the user account is lower than the preset priority, step 504 is executed.

In one embodiment, the system to be updated of the preset type can be understood as a development version system with lower stability.

In one embodiment, the predetermined priority may be understood as a level with a lower priority.

In step 504, the operation of updating the prompt information by the display system is refused to be executed.

In one embodiment, the system update prompting message may be a notification message for reminding the user that a new system version is currently available.

In an exemplary scenario, referring to fig. 1C, when the first server 110 receives the account type query message sent by the user equipment 130, the account type response message may be sent to the user equipment 130, where the response message carries the system update priority of the user account, and the user equipment 130 may determine whether to display the system update prompting information based on the system update priority of the user account when receiving the system update message for updating the preset type of system to be updated, if the system update priority of the user account is lower than the preset priority, for example, the system update priority of the user account is 4, and the preset priority is 5, it may be determined that the system update prompt message is not presented, therefore, the user is prevented from updating the system to be updated according to the system updating prompt information, and in the embodiment, the system to be updated of the preset type can be understood as the system to be updated of the development version with poor stability.

In this embodiment, the user equipment may obtain the system update priority of the user account from the first server, and then may determine whether to display the system update prompt information according to the priority of the user equipment, and if the system update priority of the user account is lower, the system update prompt information may not be displayed, so that the system to be updated pushed by the second server is not updated, and a problem that a risk possibly existing in experiencing the system to be updated is not assumed is avoided.

In an embodiment, the method further comprises:

and if the current login is the first login after the system is to be updated, sending system updating information to the first server, wherein the system updating information comprises a user account and system updating time logged in during system updating, and the system updating information is used for the first server to determine the system updating priority of the user account.

Please refer to the following embodiments for details of how to implement system upgrade.

FIG. 6 is a flow diagram of a system upgrade method according to an example embodiment; in this embodiment, an exemplary description is given by taking a user equipment upgrade system as an example by using the above method provided by the embodiment of the present disclosure, as shown in fig. 6, including the following steps:

in step 601, an account type query message is sent to a first server.

In step 602, an account type response message returned by the first server is received, where the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by the user equipment logged in by the user account.

In one embodiment, each time the user equipment upgrades the system, the time for upgrading the system and the user account (such as the millet account) logged in before the provincial system can be recorded into the nonvolatile storage part of the mobile phone.

In step 603, when a system update message for updating a preset type of system to be updated, which is sent by the second server, is received, it is determined whether the system update priority of the currently logged-in user account is lower than a preset priority, if the system update priority of the currently logged-in user account is lower than the preset priority, step 604 is executed, and if the system update priority of the currently logged-in user account is not lower than the preset priority, step 605 is executed.

In step 604, the operation of updating the prompt information by the display system is refused to be executed, and the process ends.

In step 605, the operation of presenting the system update prompt message is performed.

In one embodiment, after presenting the system update prompting message, the user equipment may receive an instruction triggered by the user to perform a system upgrade operation, and perform the system update operation.

In step 606, when receiving a message that the user account successfully logs in the user equipment, determining whether the current login is the first login after the system is to be updated, if the current login is the first login after the system is to be updated, executing step 607, and if the current login is not the first login after the system is to be updated, not executing any operation, and ending the process.

In one embodiment, the first login refers to the first login of the user account after the system is upgraded.

In step 607, system update information is sent to the first server, where the system update information includes the logged user account and the system update time when the system is updated, the system update information is used by the first server to determine the system update priority of the user account, and the process is ended.

In this embodiment, when receiving a system update message for updating a preset type of system to be updated, the user equipment may determine whether to display the system update prompt information according to the system update priority, thereby automatically determining whether to update the preset type of system to be updated according to the system update priority of the user account, and avoiding a problem that a risk possibly existing in experiencing the system to be updated is not assumed.

Fig. 7 is a block diagram illustrating a system upgrade apparatus according to an exemplary embodiment, as shown in fig. 7, the system upgrade apparatus including:

a first receiving module 710 configured to receive an account type query message sent by a sender;

the first sending module 720 is configured to send an account type response message to the sender according to the account type query message received by the first receiving module 710, where the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by the user equipment logged in by the user account.

Fig. 8 is a block diagram of another system upgrade apparatus according to an exemplary embodiment, as shown in fig. 8, on the basis of the above embodiment shown in fig. 7, in an embodiment, the apparatus further includes:

the frequency calculation module 730 is configured to calculate the system update frequency of each user account within a set time period according to the system update information uploaded by the user equipment logged in by the user account within the set time period;

the first determining module 740 is configured to determine a system update priority of each user account according to the system update frequency of each user account calculated by the frequency calculating module 730.

In an embodiment, the apparatus further comprises:

the number calculating module 750 is configured to calculate the number of system updates of each user account in a set time period according to the system update information uploaded by the user equipment logged in by the user account in the set time period;

the second determining module 760 is configured to determine the system update priority of each user account according to the system update times of each user account calculated by the time calculating module 750.

Fig. 9 is a block diagram illustrating a system upgrade apparatus according to an exemplary embodiment, as shown in fig. 9, the system upgrade apparatus including:

a second sending module 910 configured to send an account type query message to the first server;

a second receiving module 920, configured to receive an account type response message returned by the first server according to the account type query message sent by the second sending module 910, where the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by the user equipment logged in by the user account;

the upgrading module 930 is configured to perform a grayscale upgrading operation on the system to be updated based on the system update priority of the user account carried in the account type response message received by the second receiving module 920.

Fig. 10 is a block diagram of another system upgrading apparatus according to an exemplary embodiment, and as shown in fig. 10, on the basis of the embodiment shown in fig. 9, in an embodiment, the upgrading module 930 includes:

a first sending submodule 931 configured to send the system to be updated to the user equipment logged in by the user account with the first priority, where the first priority is used to indicate a level with the highest priority;

the first determining submodule 932 is configured to determine whether to send the system to be updated to other user accounts according to feedback information returned by the system to be updated according to the user account with the first priority;

the second sending submodule 933 is configured to, when the first determining submodule 932 determines to send the system to be updated to other user accounts, send the system to be updated to the user equipment logged in by the user account in order from high to low based on the system update priority of the user account.

Fig. 11 is a block diagram illustrating a system upgrade apparatus according to an exemplary embodiment, as shown in fig. 9, the system upgrade apparatus including:

a third sending module 1110 configured to send an account type query message to the first server;

a third receiving module 1120, configured to receive an account type response message returned by the first server according to the account type query message sent by the third sending module 1110, where the account type response message carries a system update priority of the user account, and the system update priority is determined according to system update information uploaded by the user equipment logged in by the user account;

a third determining module 1130, configured to determine, when receiving a system update message for updating a preset type of system to be updated, sent by a second server, whether a system update priority of a currently logged-in user account is lower than a preset priority;

a refusal presentation module 1140, configured to refuse to perform the operation of presenting the system update prompting message when the third determination module 1130 determines that the system update priority of the currently logged-in user account is lower than the preset priority.

Fig. 12 is a block diagram of another system upgrade apparatus according to an exemplary embodiment, as shown in fig. 12, on the basis of the above embodiment shown in fig. 11, in an embodiment, the apparatus further includes:

the presentation module 1150 is configured to perform an operation of presenting the system update prompt information when the third determination module 1130 determines that the system update priority of the currently logged-in user account is not lower than the preset priority.

In an embodiment, the apparatus further comprises:

a fourth determining module 1160, configured to determine whether the current login is the first login after the system is to be updated when receiving a message that the user account successfully logs in the user equipment;

a fourth sending module 1170, configured to send system update information to the first server when the fourth determining module 1160 determines that the current login is the first login after the system is to be updated, where the system update information includes the user account and the system update time logged in during system update, and the system update information is used by the first server to determine the system update priority of the user account.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. One of ordinary skill in the art can understand and implement it without inventive effort.

According to an embodiment of the present disclosure, there is also provided a system upgrade apparatus including any one of the system upgrade apparatuses of fig. 7 to 8 described above. The system upgrading device is described in detail above and will not be described in detail here.

According to an embodiment of the present disclosure, there is also provided a system upgrade apparatus including the system upgrade apparatus of fig. 9 to 10. The system upgrading device is described in detail above, and is not described in detail here.

According to an embodiment of the present disclosure, there is also provided a system upgrade apparatus including the system upgrade apparatus of fig. 11 to 12. The system upgrading device is described in detail above, and is not described in detail here.

According to an embodiment of the present disclosure, there is also provided a system upgrade apparatus applied to a first server, the apparatus including:

a first processor;

a first memory for storing first processor-executable instructions;

wherein the first processor is configured to:

receiving an account type query message sent by a sender;

and sending an account type response message to the sender according to the account type query message, wherein the account type response message carries a system updating priority of the user account, and the system updating priority is determined according to system updating information uploaded by user equipment logged in by the user account.

According to an embodiment of the present disclosure, there is also provided a system upgrade apparatus applied to a second server, the apparatus including:

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

sending an account type query message to a first server;

and performing gray scale upgrading operation on the system to be updated based on the system updating priority of the user account.

According to an embodiment of the present disclosure, a system upgrade apparatus is provided, which is applied to a user equipment, and includes:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

sending an account type query message to a first server;

FIG. 13 is a block diagram illustrating a suitable system upgrade apparatus, according to an example embodiment. For example, apparatus 1300 may be a user device (e.g., a smartphone, a tablet, etc.).

Referring to fig. 13, the apparatus 1300 may include one or more of the following components: a processing component 1302, a memory 1304, a power component 1306, a multimedia component 1308, an audio component 1310, an input/output (I/O) interface 1312, a sensor component 1314, and a communication component 1316.

The processing component 1302 generally controls the overall operation of the device 1300, such as operations associated with display, voice playback, data communication, and recording operations. The processing element 1302 may include one or more processors 1320 to execute instructions to perform all or part of the steps of the method described above. Further, the processing component 1302 can include one or more modules that facilitate interaction between the processing component 1302 and other components. For example, the processing component 1302 may include a multimedia module to facilitate interaction between the multimedia component 1308 and the processing component 1302.

The memory 1304 is configured to store various types of data to support operation at the device 1300. Examples of such data include instructions, messages, pictures, etc. for any application or method operating on device 1300. The memory 1304 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

Power supply component 1306 provides power to the various components of device 1300. The power components 1306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the apparatus 1300.

The multimedia component 1308 includes a screen that provides an output interface between the device 1300 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The audio component 1310 is configured to output and/or input audio signals. For example, the audio component 1310 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 1300 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 1304 or transmitted via the communication component 1316. In some embodiments, the audio component 1310 also includes a speaker for outputting audio signals.

The I/O interface 1312 provides an interface between the processing component 1302 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 1314 includes one or more sensors for providing various aspects of state assessment for the device 1300. For example, the sensor assembly 1314 may detect an open/closed state of the device 1300, the relative positioning of components, such as a display and keypad of the apparatus 1300, the sensor assembly 1314 may also detect a change in position of the apparatus 1300 or a component of the apparatus 1300, the presence or absence of user contact with the apparatus 1300, orientation or acceleration/deceleration of the apparatus 1300, and a change in temperature of the apparatus 1300. The sensor assembly 1314 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a distance sensor, a pressure sensor, or a temperature sensor.

The communication component 1316 is configured to facilitate communications between the apparatus 1300 and other devices in a wired or wireless manner. The device 1300 may access a wireless network based on a communication standard, such as WIFI, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1316 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1316 also includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 1300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the following methods:

sending an account type query message to a first server;

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1304 comprising instructions, executable by the processor 1320 of the apparatus 1300 to perform the method described above is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

FIG. 14 is a block diagram illustrating a suitable system upgrade apparatus, according to an example embodiment. For example, the apparatus 1400 may be a first server or a second server push server.

Referring to fig. 14, the apparatus 1400 includes a processing component 1422 that further includes one or more processors and memory resources, represented by memory 1432, for storing instructions, such as applications, that are executable by the processing component 1422.

The application programs stored in memory 1432 may include one or more modules each corresponding to a set of instructions. Further, the processing component 1422 is configured to execute the instructions to perform the above system upgrade method, wherein the first server performs:

receiving an account type query message sent by a sender;

The second server performs:

sending an account type query message to a first server;

The device 1400 may also include a power component 1426 configured to perform power management of the device 1400, a wired or wireless network interface 1450 configured to connect the device 1400 to a network, and an input output (I/O) interface 1458. The apparatus 1400 may operate based on an operating system stored in the memory 1432, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1432 comprising instructions, executable by the processing component 1422 of the apparatus 1400 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

A non-transitory computer readable storage medium, wherein instructions in the storage medium, when executed by a processor of a mobile terminal/server, enable the server to execute to perform the above method.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A system upgrade method applied to a second server, the method comprising:

sending an account type query message to a first server;

receiving an account type response message returned by the first server, where the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account, and the method includes: according to the system updating information, calculating the system updating times or the system updating frequency of the user account in a set time period, and according to the system updating times or the system updating frequency, determining the system updating priority of the user account, wherein the system updating priority is used for indicating the priority level of a user equipment logged in by the user account for updating a system;

based on the system updating priority of the user account, executing gray scale upgrading operation on the system to be updated, wherein the gray scale upgrading operation comprises the following steps: and preferentially sending the system to be updated to the user equipment logged in by the user account with the first priority, and further determining whether to send the system to be updated to other user accounts according to the feedback information of the user account with the first priority.

2. The method of claim 1, wherein performing a grayscale upgrade operation on a system to be updated based on the system update priority of the user account comprises:

3. A method for system upgrade, applied to a user equipment, the method comprising:

sending an account type query message to a first server;

and if the system updating priority of the currently logged user account is lower than the preset priority, refusing to execute the operation of displaying the system updating prompt information, and if the system updating priority of the currently logged user account is not lower than the preset priority, executing the operation of displaying the system updating prompt information.

4. The method of claim 3, further comprising:

when receiving a message that a user account successfully logs in user equipment, determining whether the current login is the first login after the system is updated;

and if the current login is the first login after the system is updated, sending system updating information to a first server, wherein the system updating information comprises a user account and system updating time logged in during system updating, and the system updating information is used for the first server to determine the system updating priority of the user account.

5. A system upgrade apparatus, for application on a second server, the apparatus comprising:

a second receiving module, configured to receive an account type response message returned by the first server according to the account type query message sent by the second sending module, where the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account, and the method includes: according to the system updating information, calculating the system updating times or the system updating frequency of the user account in a set time period, and according to the system updating times or the system updating frequency, determining the system updating priority of the user account, wherein the system updating priority is used for indicating the priority level of a user equipment logged in by the user account for updating a system;

the upgrading module is configured to execute a grayscale upgrading operation on the system to be updated based on the system updating priority of the user account carried in the account type response message received by the second receiving module, and the grayscale upgrading operation includes: and preferentially sending the system to be updated to the user equipment logged in by the user account with the first priority, and further determining whether to send the system to be updated to other user accounts according to the feedback information of the user account with the first priority.

6. The apparatus of claim 5, wherein the upgrade module comprises:

7. A system upgrade apparatus, for application on a user equipment, the apparatus comprising:

a third receiving module, configured to receive an account type response message returned by the first server according to the account type query message sent by the third sending module, where the account type response message carries a system update priority of a user account, and the system update priority is determined according to system update information uploaded by user equipment logged in by the user account, and the method includes: according to the system updating information, calculating the system updating times or the system updating frequency of the user account in a set time period, and according to the system updating times or the system updating frequency, determining the system updating priority of the user account, wherein the system updating priority is used for indicating the priority level of a user equipment logged in by the user account for updating a system;

the display rejection module is configured to reject to perform the operation of displaying the system update prompt information when the third determination module determines that the system update priority of the currently logged-in user account is lower than a preset priority;

8. The apparatus of claim 7, further comprising:

the fourth determination module is configured to determine whether the current login is the first login after the system is updated when a message that the user account successfully logs in the user equipment is received;

a fourth sending module, configured to send system update information to the first server when the fourth determining module determines that the current login is a first login after updating the system, where the system update information includes a user account and system update time logged in during system update, and the system update information is used by the first server to determine a system update priority of the user account.

9. A system upgrade apparatus, for application on a second server, the apparatus comprising:

a second processor;

a second memory for storing second processor-executable instructions;

wherein the second processor is configured to:

sending an account type query message to a first server;

10. A system upgrade apparatus, for application on a user equipment, the apparatus comprising:

a third processor;

a third memory for storing third processor-executable instructions;

wherein the third processor is configured to:

sending an account type query message to a first server;

when a system updating message sent by a second server is received, whether system updating prompt information is displayed or not is determined according to the system updating priority of the currently logged user account;

if the system updating priority of the currently logged user account is lower than the preset priority, refusing to execute the operation of displaying the system updating prompt information; and if the system updating priority of the currently logged user account is not lower than the preset priority, performing the operation of displaying the system updating prompt information.