CN116708394A - Terminal upgrading method, electronic equipment and computer readable storage medium - Google Patents

Terminal upgrading method, electronic equipment and computer readable storage medium Download PDF

Info

Publication number
CN116708394A
CN116708394A CN202211342499.5A CN202211342499A CN116708394A CN 116708394 A CN116708394 A CN 116708394A CN 202211342499 A CN202211342499 A CN 202211342499A CN 116708394 A CN116708394 A CN 116708394A
Authority
CN
China
Prior art keywords
packet
level
patch
ota
priority
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202211342499.5A
Other languages
Chinese (zh)
Other versions
CN116708394B (en
Inventor
彭光明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to CN202211342499.5A priority Critical patent/CN116708394B/en
Publication of CN116708394A publication Critical patent/CN116708394A/en
Application granted granted Critical
Publication of CN116708394B publication Critical patent/CN116708394B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/658—Incremental updates; Differential updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides a terminal upgrading method, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: when the packet searching result sent by the server indicates that an OTA packet and a patch packet exist, acquiring current state information of the user terminal; determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal; downloading the target package and upgrading according to the target package. By the method in the embodiment of the application, the stability of the user terminal system is improved, and the user experience is improved.

Description

Terminal upgrading method, electronic equipment and computer readable storage medium
Technical Field
The present application relates to the field of terminals, and in particular, to a terminal upgrade method, an electronic device, and a computer readable storage medium.
Background
The Over The Air (OTA) technology is a technology for downloading data through a wireless network, and is widely used for upgrading terminal equipment. The OTA technology is mainly used for automatic upgrading by downloading an OTA upgrading packet, the OTA upgrading speed is high, and the influence on data is small, so that the OTA technology is used for upgrading to become a main mode for upgrading the functions of the terminal equipment.
The upgrade of the terminal equipment comprises system basic version upgrade and patch upgrade. At present, the upgrade of the terminal equipment usually presets the upgrade priority of the basic version or the upgrade priority of the patch, the upgrade scheme cannot be adjusted adaptively, the upgrade failure, repeated upgrade and other conditions easily occur, the stability of the user terminal system is affected, and the user experience is reduced.
Disclosure of Invention
The application provides a terminal upgrading method, electronic equipment and a computer readable storage medium, which improve the stability of a user terminal system and improve the user experience.
In order to achieve the above purpose, the application adopts the following technical scheme:
in a first aspect, a method for upgrading a terminal is provided, including:
when the packet searching result sent by the server indicates that an OTA packet and a patch packet exist, acquiring current state information of the user terminal;
determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal;
downloading the target package and upgrading according to the target package.
In the embodiment of the application, aiming at the situation that the patch package and the OTA package exist at the same time, the user terminal selects the optimal upgrade package for upgrading according to the state information of the user terminal, and the upgrade scheme can be adaptively adjusted according to various application scenes of the user terminal, so that the flexibility of upgrading the user terminal is improved, the conditions of repeated upgrade, upgrade failure and the like caused by the fact that the server determines the upgrade scheme are avoided, the stability of a user terminal system is ensured, and the user experience is improved.
In an implementation manner of the first aspect, the status information of the user terminal includes a bandwidth network status, a user space status, a severity level of a patch problem, and an importance level of a system version;
and determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal, wherein the method comprises the following steps:
and determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity level of the patch problem and the importance level of the system version.
In one implementation of the first aspect, the bandwidth network state includes a first network state, a second network state, and a third network state, the first network state being better than the second network state, the second network state being better than the third network state;
the user spatial states include a first spatial state, a second spatial state, and a third spatial state, the first spatial state being better than the second spatial state, the second spatial state being better than the third spatial state;
the severity of the patch problem includes a first degree, a second degree, and a third degree, the first degree being greater than the second degree, the second degree being greater than the third degree;
The importance levels of the system version comprise a first level, a second level and a third level, wherein the priority of the first level is higher than that of the second level, and the priority of the second level is higher than that of the third level;
the determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity level of the patch problem, and the importance level of the system version includes:
when a first condition is met, determining the patch package as the target package;
when the first condition is not met, determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity of the patch problem and the importance level of the system version;
wherein the first condition includes at least one of: the severity of the patch problem is the first degree, the bandwidth network state is the third network state, and the user space state is the third space state.
When the first condition is met, the user terminal is in an extreme environment and is poor in state, and the OTA packet upgrading is not suitable. In the embodiment of the application, when the first condition is met, the patch package is downloaded preferentially. Compared with the application scene of the OTA packet priority, the situation of failure in downloading the OTA packet caused by deadly patch problem, insufficient user space and poor bandwidth network state is avoided; in addition, when the system has a fatal problem, the fatal problem can be quickly repaired, the running stability of the system is effectively ensured, and the user experience is improved.
In an implementation manner of the first aspect, when the first condition is not satisfied, the determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity of the patch problem, and the importance level of the system version includes:
if the second condition is met, determining the OTA packet as the target packet;
if the second condition is not met, determining a target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version;
wherein the second condition includes the bandwidth network state being the first network state and the user space state being the first space state.
In the embodiment of the application, the severity of the patch problem is not fatal, the bandwidth network state is good, the user space is sufficient, and under the condition, the OTA packet is downloaded preferentially and the system basic version is updated; when the overall state of the user terminal is good, the OTA packet is preferentially adopted for upgrading, so that the system of the user terminal is upgraded to the latest version, and the system is comprehensively updated.
In an implementation manner of the first aspect, if the second condition is not satisfied, determining, according to the severity of the patch problem and the importance level of the system version, a target packet from the OTA packet and the patch packet includes:
If a third condition is met, determining the target packet from the OTA packet and the patch packet according to a first priority order, wherein the third condition comprises that the bandwidth network state is the first network state and the user space state is the second space state;
the first priority order includes a priority of the first level being lower than a priority of the first level and higher than a priority of the second level being lower than a priority of the second level and higher than a priority of the third level being lower than a priority of the third level.
In an implementation manner of the first aspect, if the third condition is met, the determining the target packet from the OTA packet and the patch packet according to the first priority order includes:
if the severity of the patch problem is the second degree and the importance level of the system version is the first level, determining the OTA packet as the target packet;
if the severity of the patch problem is the third level and the importance level of the system version is not the third level, determining the OTA packet as the target packet;
If the severity of the patch problem is the second level and the importance level of the system version is not the first level, determining the patch package as the target package;
and if the severity of the patch problem is the third degree and the importance level of the system version is the third level, determining the patch package as the target package.
In an implementation manner of the first aspect, if the second condition is not satisfied, determining, according to the severity of the patch problem and the importance level of the system version, a target packet from the OTA packet and the patch packet includes:
if a fourth condition is met, determining the target packet from the OTA packet and the patch packet according to a second priority order, wherein the fourth condition comprises that the bandwidth network state is the second network state;
the second order of priority includes the first level of priority being lower than the second level of priority and higher than a third level of priority, the second level of priority being lower than the second level of priority and higher than the third level of priority, the third level of priority being lower than the third level of priority.
In an implementation manner of the first aspect, if the fourth condition is met, the determining the target packet from the OTA packet and the patch packet according to the second priority order includes:
if the severity of the patch problem is the second degree, determining the patch package as the target package;
if the severity of the patch problem is the third level and the importance level of the system version is not the third level, determining the OTA packet as the target packet;
and if the severity of the patch problem is the third degree and the importance level of the system version is the third level, determining the patch package as the target package.
In the embodiment of the application, different priority orders are set for the patch problem and the system version according to the different bandwidth network states and the different user space states, and the target packet is selected according to the different priority orders. By the method, various states of the user terminal are comprehensively considered, and the proper upgrade package is selected according to different states, so that the adaptability adjustment of an upgrade scheme is realized, the flexibility of the upgrade of the user terminal is improved, the conditions of repeated upgrade, upgrade failure and the like caused by the fact that a server determines the upgrade scheme are avoided, the stability of a user terminal system is ensured, and the user experience is improved.
In one implementation manner of the first aspect, the method further includes:
and when the searching result sent by the server indicates that an OTA packet exists and no patch packet exists, downloading the OTA packet, and upgrading according to the OTA packet.
In one implementation manner of the first aspect, the method further includes:
and when the packet searching result sent by the server indicates that a patch packet exists and an OTA packet does not exist, downloading the patch packet, and upgrading according to the patch packet.
In one implementation manner of the first aspect, the method further includes:
and stopping upgrading when the packet searching result sent by the server indicates that no patch packet exists and no OTA packet exists.
In a second aspect, an electronic device is provided, comprising a processor for executing a computer program stored in a memory, implementing the method according to any of the first aspects of the application.
In a third aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program which, when executed by one or more processors, implements the method according to any one of the first aspects of the application.
In a fourth aspect, embodiments of the present application provide a computer program product which, when run on a device, causes the device to perform the method of any one of the first aspects above.
In a fifth aspect, a system on a chip is provided, comprising a processor coupled to a memory, the processor executing a computer program stored in the memory, to implement the method according to any of the first aspects of the present application.
It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.
Drawings
Fig. 1 is a system architecture diagram of a terminal upgrade method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an upgrade process according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of a search strategy in a server according to an embodiment of the present application;
fig. 4 is a schematic flow chart of a terminal upgrading method according to an embodiment of the present application;
FIG. 5 is a schematic diagram of an upgrade process according to another embodiment of the present application;
FIG. 6 is a flowchart of a search strategy in a server according to another embodiment of the present application;
fig. 7 is a schematic flow chart of an upgrade policy in a user terminal according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that in embodiments of the present application, "one or more" means one, two, or more than two; "and/or", describes an association relationship of the association object, indicating that three relationships may exist; for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Furthermore, the terms "first," "second," "third," and the like in the description of the present specification and in the appended claims, are used for distinguishing between descriptions and not necessarily for indicating or implying a relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
Referring to fig. 1, a system architecture diagram of a terminal upgrade method according to an embodiment of the present application is shown. As shown in fig. 1, the system includes a server 100 and at least one user terminal 200. In the embodiment of the present application, the number of servers 100 and user terminals 200 is not limited, and one server 100 may be connected to one or more user terminals 200 (only one server 100 is shown in fig. 1 to connect 2 user terminals 200), and one user terminal 200 may be connected to one or more servers 100 (only one user terminal 200 is shown in fig. 1 to connect one server 100).
The server 100 may be a server or a server cluster composed of a plurality of servers. Specifically, the server 100 may be a server including several storage upgrade packages, or may be a server cluster including distributed storage upgrade packages, grouping configuration information, or upgrade policy information. For example, the distributed server may be a server cluster composed of a plurality of servers, which may include cloud computer servers, content delivery network (Content Delivery Network, CDN) servers, network time protocol (Network Time Protocol, NTP), domain name resolution system (Domain Name System, DNS) servers, and so on; the servers in the server cluster coordinate with each other to complete the functions of calculation, data storage, communication and the like. For convenience of description, in the embodiment of the present application, a single server, a distributed server, and a server cluster are collectively referred to as a server. In fig. 1, the server 100 appears as a cloud server.
In The embodiment of The present application, the server 100 is configured to provide an Over The Air (OTA) service, and is specifically configured to send upgrade notification information to The user terminal 200 to be upgraded, or send an upgrade package to The user terminal 200, and The like, which is not limited herein. In some application scenarios, the server 100 may be referred to as an OTA server or as an OTA cloud.
Among them, OTA is a technology for downloading data through a wireless network, and is widely used for upgrading terminal equipment. The OTA technology is mainly used for automatic upgrading by downloading an OTA upgrading packet, the OTA upgrading speed is high, and the influence on data is small, so that the OTA upgrading is gradually a main mode of terminal equipment function upgrading.
The wireless network on which the OTA depends may be a network based on a fourth generation mobile information technology (the 4th generation mobile communication technology,4G), a network based on a fifth generation mobile information technology (the 5th generation mobile communication technology,5G), a network based on a sixth generation mobile information technology (the 6th generation mobile communication technology,6G), and may even be applicable to future communication networks, without specific limitation.
The user terminal 200 in the embodiment of the present application is a device capable of providing various service functions such as corresponding voice, video, shooting, data connectivity, etc. to a user by installing application software. A user equipment (ue) may also be referred to as a terminal device, a Mobile Station (MS), a Mobile Terminal (MT), etc. For convenience of description, the embodiment of the present application is collectively referred to as a user terminal. The user terminal 200 in the embodiment of the present application may receive the upgrade notification information sent by the server 100, or download a patch file or an OTA upgrade package from the server 100 to perform an upgrade by using the patch file or the OTA upgrade package.
The user terminal may be a mobile device, a non-mobile device, etc. having a wireless connection function. For example, the user terminal may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a personal computer, a mobile internet device (mobile Internet device, MID), a Point Or Sale (POS), a wearable device, a virtual reality device (VR), an augmented reality device (augmented reality, AR), a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in teleoperation, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, various smart meters (smart water meter, smart electricity meter, smart gas meter, etc.), a smart car in the internet of vehicles, an On Board Unit (OBU), a road test unit (road test device (road side equipment, RSE), a remote communication science BOX (T-BOX), and an electronic control unit (electronic control unit, ECU), or the like.
The presentation form of the user terminal is also different according to different application scenes. For example, in a conventional mobile communication application scenario, the user terminal may be a mobile phone, a tablet computer, or the like. In an application scenario of internet of things communication, the user terminal may be a mobile internet device, a wearable device, a wireless terminal in a smart home, or the like. In an application scenario of internet of vehicles or vehicle-to-object (vehicle to everything, V2X) communication, the user terminal may be a vehicle, OBU, RSE, ECU, or the like.
In the system provided by the embodiment of the present application, the user terminal 200 may establish communication connection with the server 100 through the mobile communication network, so as to perform communication interaction. The user terminal 200 may also perform communication interaction by establishing a communication connection with the server 100 through at least one relay device and then through the mobile communication network. For example, as shown in fig. 1, in a conventional mobile communication application scenario, when the user terminal 200 is a mobile phone or a tablet computer, the mobile phone or the tablet computer is communicatively connected to and communicatively interacted with the server 100 through a mobile communication network. For another example, in the V2X application scenario, when the user terminal is the ECU, the ECU may sequentially pass through the relay devices of the domain controller, the gateway, and the T-BOX, and finally connect to the server 100.
Referring to fig. 2, an upgrade flow chart provided in an embodiment of the present application is shown. As shown in fig. 2, in some application scenarios, the update flow of the user terminal system is as follows:
the user terminal initiates a packet searching request to the server, wherein the packet searching request can comprise basic information of the user terminal (such as a terminal identifier, a system version number, a system patch version number, a country code and the like of the user terminal); after receiving the packet searching request of the user terminal, the server searches the upgrade packet information matched with the basic information of the user terminal and feeds back the search result to the user terminal; after receiving the search result sent by the server, the user terminal analyzes the search result; if the search result indicates that the upgrade package exists, the user terminal sends an acquisition request to the server; after receiving the acquisition request of the user terminal, the server sends an upgrade package to the user terminal through an OTA technology; and after the user terminal downloads the upgrade package from the server, the upgrade package is utilized for upgrading.
In the related art, a packet searching policy is generally configured in a server. Referring to fig. 3, a flow chart of a search strategy in a server according to an embodiment of the present application is shown. As shown in fig. 3, when the server receives the packet searching request of the user terminal, searching packets according to a preset packet searching strategy. Specifically, first, searching an upgrade path of a cold/hot patch Ding Bao (hereinafter, referred to as a patch package) matched with basic information of the user terminal, and if the patch package is not searched, searching an upgrade path of a basic version upgrade package (hereinafter, referred to as an OTA package) matched with the basic information of the user terminal to determine whether the OTA package exists; if the OTA packet exists, the OTA packet is returned to the user terminal, so that the user terminal downloads the OTA packet; if the OTA packet does not exist, the search result which indicates that the upgrade information is not searched is fed back to the user terminal. If the patch package is searched, the following two cases are classified:
In one case, patch prioritization is configured in the search policy. In this case, the search result of the patch package is preferentially fed back to the user terminal, so that the user terminal preferentially downloads the patch package and performs patch upgrading.
In another case, patch prioritization (default OTA packet prioritization) is not configured in the search policy. In this case, the upgrade path of the OTA packet matched with the basic information of the user terminal is continuously searched to determine whether the OTA packet exists. If the OTA packet exists, the search result of the OTA packet is fed back to the user terminal, so that the user terminal downloads the OTA packet and upgrades the system. If the OTA packet does not exist, the patch packet is fed back to the user terminal, so that the user terminal downloads the patch packet.
As described above, it is often necessary to configure patch packet priorities or OTA packet priorities in the search policy of the server. Whichever strategy, the search results fed back to the user terminal by the server include the following three types: and returning an OTA packet, a patch packet or not searching upgrading information. The user terminal can only process according to the search result fed back by the server, namely, if the server returns an OTA packet, the user terminal can only download the OTA packet to upgrade the system; if the server returns the patch package, the user terminal can only download the patch package to repair the vulnerability.
It can be understood that the basic version upgrade is a process from an old version to a new version, and generally, an OTA packet required by the basic version upgrade of the system is larger, a time required by the user terminal for downloading the OTA packet is longer, and a required storage space is larger, but the basic version upgrade can repair various problems in the system, so that the overall upgrade is realized. Patch upgrade is a process of repairing vulnerabilities on the basis of an old version (a current version), and is generally smaller in patch package, shorter in time required by a user terminal for downloading the patch package, smaller in storage space required by the user terminal, and capable of rapidly repairing a problem in a system.
In some application scenarios, the network condition of the user terminal is poor. In this scenario, if the search policy with the priority of the OTA packet is adopted, the search result fed back by the server is the OTA packet, and since the OTA packet required by the upgrade system is larger, the time required for the user terminal to download the OTA packet is longer, which is likely to reduce the upgrade willingness of the user.
In other application scenarios, the user space of the user terminal is insufficient. Under the scene, if the search strategy with the priority of the OTA packet is adopted, the search result fed back by the server is the OTA packet, and because the OTA packet required by the upgrading system is large, the user needs to clear the user space of the user terminal to meet the downloading and upgrading requirements of the OTA packet, and the upgrading willingness of the user is likely to be reduced. In addition, if the system version of the current user terminal has a vulnerability, the patch package cannot be downloaded preferentially to repair the vulnerability, so that the stability of the user terminal system is affected, and the user must clean the user space of the user terminal, download the OTA package to upgrade the system to repair the vulnerability, so that the user experience is affected.
In other application scenarios, the user terminal has a system deadly problem, which may be a network problem, affecting data downloading. Under the scene, if the search strategy with the priority of the OTA packet is adopted, the server feeds back the OTA packet, and the user terminal cannot download the patch packet for repairing the network problem preferentially, so that the user terminal cannot repair the network problem, and the user terminal cannot download the OTA packet in the current network state, so that the system cannot be upgraded, the vulnerability is repaired, the stability of the user terminal system is influenced, and the user experience is influenced.
In other application scenarios, the vulnerability problem of the repair of the OTA package and the patch package in the server is the same. In this scenario, if the patch package priority is configured, the user terminal needs to download the patch package to repair the vulnerability, then download the OTA package upgrade system, and upgrade twice continuously, so as to affect the user experience.
As described above, patch priority or OTA packet priority is configured in the search policy of the server in advance, that is, the search policy is fixed and cannot be adaptively adjusted according to various application scenarios of the user terminal, so that the situations of upgrade failure, repeated upgrade and the like are easy to occur, the stability of the user terminal system is affected, and the user experience is reduced.
In order to solve the above problems, an embodiment of the present application provides a terminal upgrade method, where in the embodiment of the present application, a search policy can be adaptively adjusted according to a state of a user terminal, so as to select an OTA packet upgrade or a patch packet upgrade. By the method provided by the embodiment of the application, the running stability of the user terminal system can be ensured, and the user experience degree is improved.
Referring to fig. 4, a flow chart of a terminal upgrading method provided by an embodiment of the present application is shown. The terminal upgrading method provided by the embodiment of the application is applied to the user terminal 200 shown in fig. 1. As shown in fig. 4, by way of example and not limitation, the terminal upgrade method may include the steps of:
s401, when the packet searching result sent by the server indicates that an OTA packet and a patch packet exist, current state information of the user terminal is obtained.
In the embodiment of the application, the state information of the user terminal indicates the state related to the OTA packet upgrade and the patch packet upgrade on the user terminal, which can influence the state information of the OTA packet upgrade and the patch packet upgrade. For example, the status information of the user terminal may include a bandwidth network status, a user space status, a severity level of the patch problem, an importance level of the system version, and the like, which are not particularly limited herein.
The bandwidth network status may be determined based on bandwidth network data, including bandwidth data and network data. The bandwidth data is determined according to different countries and regions, and the network data can be obtained according to the historical network data prediction of the user terminal.
In some application scenarios, after the processor of the user terminal gathers bandwidth network data, the bandwidth network state of the current user terminal is determined according to a preset threshold corresponding to the bandwidth network data. Illustratively, the bandwidth network state is divided into better, general and worse. When the bandwidth network data is in a first preset threshold range, judging that the bandwidth network state is better; when the bandwidth network data is within a second preset threshold range, judging that the bandwidth network state is general; and when the bandwidth network data is within the third preset threshold range, judging that the bandwidth network state is poor.
In other application scenarios, bandwidth network status may also be assessed based on quality of experience (Quality of Experience, QOE). QOE refers to the subjective perception of quality and performance by a user of a device, network and system, application or service. Illustratively, the bandwidth network state is divided into better, general and worse. The user terminal provides the user with the option of the bandwidth network state through the interaction device, and the user selects the current bandwidth network state of the mobile phone terminal according to the option.
In other application scenarios, the judgment can be integrated. Specifically, the bandwidth network state selected by the user is preferentially considered, and then the judgment is further carried out according to a preset threshold corresponding to the bandwidth network data. Illustratively, the bandwidth network state is divided into better, general and worse. If the option selected by the user is 'poor', judging that the bandwidth network state is 'poor'; if the option selected by the user is 'better' or 'general', further judging according to a preset threshold value corresponding to the bandwidth network data; if the result of the further judgment is better, judging the bandwidth network state to be better; if the result of the further judgment is 'bad', the bandwidth network state is judged to be bad.
The above-mentioned user space state refers to the remaining space of the user space in the user terminal. In an operating system, virtual memory is generally divided into a user space and a kernel space, and applications and the like run in the user space. The processor may read a remaining space value of the user space and determine the user space state based on the remaining space value and the size of the OTA packet/patch packet. For example, two threshold values of 10GB and 5GB may be set, where 10GB represents the minimum data amount of the OTA packet and 5GB represents the minimum data amount of the patch packet. If the residual space value is greater than 10GB, judging that the space state of the user is sufficient; if the residual space value is more than 5GB and less than 10GB, judging that the user space state is general; if the residual space value is smaller than 5GB, the user space state is judged to be insufficient. By the method, whether the downloading requirement of the OTA package or the patch package is met can be judged according to the space state of the user.
The severity level of the patch problem described above represents the severity of the current cold and hot patch repair problem. For example, the WiFi problem and the system update problem indicate that the severity level of the patch problem is fatal, the user terminal stability problem indicates that the severity level of the patch problem is serious, the experience class problem indicates that the severity level of the patch problem is general, and the like, which can be preset by a developer. The processor may determine patch problems via the log file.
The importance level of the system version indicates the characteristics of the new version of the system corresponding to the OTA packet searched by the server. Illustratively, the importance level of the system version is classified into three types of heavy characteristics, problem repair, and regular update. The significant characteristic indicates that a new version of the system has significant characteristic change, the problem repair indicates that the new version of the system repairs the vulnerability of the current version, and the regular update indicates that the new version of the system is a regular update version (such as an SMR version with a Google patch, a regular update version, etc.).
It will be appreciated that the above only shows the state information that affects the upgrade of the OTA packet/patch packet, and other state information may be included in the actual application, which is not limited herein.
S402, determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal.
The implementation of step S402 can be seen from the description in the following embodiments.
S403, downloading the target packet and upgrading according to the target packet.
Referring to fig. 5, an upgrade process according to another embodiment of the present application is shown. As shown in fig. 5, the upgrade procedure of the user terminal is as follows:
the user terminal initiates a packet searching request to the server, wherein the packet searching request can comprise basic information of the user terminal (such as a terminal identifier, a system version number, a system patch version number, a country code and the like of the user terminal); after receiving the packet searching request of the user terminal, the server searches the upgrade packet information matched with the basic information of the user terminal and feeds back the search result to the user terminal; after receiving the search result sent by the server, the user terminal analyzes the search result; selecting an upgrade package according to the search result; specifically, if the search result indicates that the OTA packet and the patch packet exist, the user terminal selects an upgrade packet (target packet) according to the method in steps S401-S403, and then sends an acquisition request to the server; after receiving the acquisition request of the user terminal, the server sends a target packet to the user terminal; and after the user terminal downloads the target packet from the server, upgrading by using the target packet.
It should be noted that, in the embodiment of fig. 5, the search policy of the server is not configured with patch priority or OTA packet priority, but searches for both patch packets and OTA packets, and the search result is fed back to the user terminal. Referring to fig. 6, a flowchart of a search strategy in a server according to another embodiment of the present application is shown. As shown in fig. 6, the search results of the server include the following cases: first, patch package exists and OTA package does not exist; secondly, an OTA packet exists and a patch packet does not exist; thirdly, no patch package and no OTA package exist, namely no upgrade information is searched; fourth, there are OTA packets and patch packets.
As shown in fig. 5, corresponding to the packet searching result sent by the server, the user terminal analyzes the received packet searching result and selects an upgrade packet according to the packet searching result. Referring to fig. 7, a flow chart of an upgrade policy in a user terminal according to an embodiment of the present application is shown. As shown in fig. 7, the user terminal selects the upgrade package according to the package searching result in the following cases:
in the first case, when the searching result sent by the server indicates that a patch package exists and an OTA package does not exist, the upgrade package selected by the user terminal is the patch package.
And in the second case, when the packet searching result sent by the server indicates that an OTA packet exists and a patch packet does not exist, the upgrade packet selected by the user terminal is the OTA packet.
And in the third case, when the packet searching result sent by the server indicates that the upgrade information is not searched, the user terminal ends the packet searching request and does not upgrade.
And in the fourth case, that is, when the searching result sent by the server indicates that the patch package and the OTA package exist, the user terminal selects the upgrade package from the patch package and the OTA package according to the method in S401-S403.
In contrast, in the embodiment of fig. 2, the information fed back to the user terminal after the server searches the packet is divided into three types: and returning a patch packet, returning an OTA packet or not searching upgrading information, and determining which upgrading is carried out by the user terminal by the server under the condition that the patch packet and the OTA packet exist simultaneously. In the embodiment of fig. 5, the information that the server searches for the package and feeds back to the user terminal is divided into the four types, and when the patch package and the OTA package exist at the same time, the user terminal selects the upgrade package from the patch package and the OTA package according to the state information of the user terminal.
The terminal upgrading method shown in the embodiments of fig. 4 to fig. 7, aiming at the situation that the patch package and the OTA package exist at the same time, the user terminal selects the optimal upgrading package to upgrade according to the state information of the user terminal, and can adaptively adjust the upgrading scheme according to various application scenes of the user terminal, so that the flexibility of upgrading the user terminal is improved, the situations of repeated upgrading, upgrading failure and the like caused by the fact that the server determines the upgrading scheme are avoided, the stability of a user terminal system is ensured, and the user experience is improved.
As described in the S401 embodiment, the status information of the user terminal includes a bandwidth network status, a user space status, a severity level of the patch problem, and an importance level of the system version.
The bandwidth network state includes a first network state, a second network state, and a third network state, wherein the first network state is superior to the second network state, and the second network state is superior to the third network state. For example, a first network state may be a good representation of a bandwidth network state, a second network state may be a general representation of a bandwidth network state, and a third network state may be a poor representation of a bandwidth network state.
The user spatial states include a first spatial state, a second spatial state, and a third spatial state, wherein the first spatial state is superior to the second spatial state, and the second spatial state is superior to the third spatial state. For example, a first spatial state indicates that the user space is sufficient, a second spatial state indicates that the user space is general, and a third spatial state indicates that the user space is insufficient.
The severity of the patch problem includes a first level, a second level, and a third level, wherein the first level is greater than the second level, and the second level is greater than the third level. For example, a first level indicates that the patch problem is fatal, a second level indicates that the patch problem is severe, and a third level indicates that the patch problem is general.
The importance levels of the system version include a first level, a second level, and a third level. Wherein the first level is higher in priority than the second level, and the second level is higher in priority than the third level. For example, a first level indicates that the system version is a heavy property level, a second level indicates that the system version is a problem repair level, and a third level indicates that the system version is a regular update level.
In some embodiments, in S402, the determining, according to the current state information of the user terminal, the target packet from the OTA packet and the patch packet includes: and determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity level of the patch problem and the importance level of the system version.
In some embodiments, determining the target packet from the OTA packet and the patch packet according to the bandwidth network status, the user space status, the severity level of the patch problem, and the importance level of the system version may include:
s11, when the first condition is met, determining the patch package as a target package.
And S12, when the first condition is not met, determining a target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity of the patch problem and the importance level of the system version.
Wherein the first condition comprises at least one of: the severity of the patch problem is a first degree, the bandwidth network state is a third network state, and the user space state is a third space state. Accordingly, the first condition being not satisfied means that the severity of the patch problem is not a first degree, the bandwidth network state is not a third network state, and the user space state is not a third space state.
In some application scenarios as described in the embodiment of fig. 3, the user terminal has a system deadly problem (i.e. the severity of the patch problem is the first level), which will affect the normal operation of the system. In other application scenarios, the network condition of the ue is poor (i.e., the bandwidth network state is the third network state), and in such scenarios, the bandwidth network state cannot support the downloading of the OTA packet. In other application scenarios, the user space of the user terminal is insufficient (i.e. the user space state is the third space state), and in such scenarios, the user space cannot meet the storage requirement of the OTA packet.
As described in the application scenario, when the first condition is satisfied, the user terminal is in an extreme environment and has a poor state, and is not suitable for upgrading by using the OTA packet. In the embodiment of the application, when the first condition is met, the patch package is downloaded preferentially. Compared with the application scenario of the OTA packet priority described in the embodiment of FIG. 3, the situation of failure in downloading the OTA packet caused by deadly patch problem, insufficient user space and poor bandwidth network state is avoided; in addition, when the system has a fatal problem, the fatal problem can be quickly repaired, the running stability of the system is effectively ensured, and the user experience is improved.
In some embodiments, the step S12, when the first condition is not satisfied, determines the target packet from the OTA packet and the patch packet according to the bandwidth network status, the user space status, the severity of the patch problem, and the importance level of the system version, may include the following steps:
s21, if the second condition is met, determining the OTA packet as a target packet;
s22, if the second condition is not met, determining a target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version.
Wherein the second condition includes the bandwidth network state being a first network state and the user space state being a first space state. Accordingly, the first condition not being met means that the bandwidth network state is not the first network state and/or that the user space state is not the first space state.
In the embodiment of the application, the severity of the patch problem is not fatal, the bandwidth network state is good, the user space is sufficient, and under the condition, the OTA packet is downloaded preferentially and the system basic version is updated; when the overall state of the user terminal is good, the OTA packet is preferentially adopted for upgrading, so that the system of the user terminal is upgraded to the latest version, and the system is comprehensively updated.
In some embodiments, if the second condition is not satisfied, the step S22 of determining the target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version may include the following steps:
and S31, if the third condition is met, determining a target packet from the OTA packet and the patch packet according to the first priority order, wherein the third condition comprises that the bandwidth network state is a first network state and the user space state is a second space state.
As described in the S401 embodiment, the severity of the patch problem includes a first degree, a second degree, and a third degree, the first degree having a priority higher than the second degree, the second degree having a priority higher than the third degree. The importance levels of the system version include a first level, a second level, and a third level, the first level having a priority higher than the second level, the second level having a priority higher than the third level.
In the embodiment of the present application, the first priority order includes a priority of the first level lower than a priority of the first level and higher than a priority of the second level, a priority of the second level lower than a priority of the second level and higher than a priority of the third level, and a priority of the third level lower than a priority of the third level.
Specifically, in the case where the third condition is satisfied, the following cases are classified:
1-1, if the severity of the patch problem is at the second level and the importance level of the system version is at the first level, determining the OTA packet as the target packet because the priority of the first level is higher than the priority of the second level.
1-2, if the severity of the patch problem is at a second level and the importance level of the system version is at the second level, determining the patch package as the target package because the priority of the second level is lower than the priority of the second level.
1-3, if the severity of the patch problem is at the second level and the importance level of the system version is at the third level, determining the patch package as the target package because the priority of the third level is lower than the priority of the third level, and the priority of the third level is lower than the second level, i.e. the priority of the third level is lower than the priority of the second level.
1-4, if the severity of the patch problem is at the third level and the importance level of the system version is at the first level, determining the OTA packet as the target packet because the priority of the first level is higher than the priority of the second level, which is higher than the priority of the third level, i.e. the priority of the first level is higher than the priority of the third level.
1-5, if the severity of the patch problem is a third level and the importance level of the system version is a second level, determining the OTA packet as a target packet because the priority of the second level is higher than the priority of the third level.
1-6, if the severity of the patch problem is at a third level and the importance level of the system version is at the third level, determining the patch package as the target package because the priority of the third level is lower than the priority of the third level.
And S32, if the fourth condition is met, determining a target packet from the OTA packet and the patch packet according to the second priority order, wherein the fourth condition comprises that the bandwidth network state is the second network state.
It is understood that in the fourth condition, the user space state may be the first state or the second state.
In the embodiment of the present application, the second priority order includes that the priority of the first level is lower than the priority of the second level and higher than the priority of the third level, the priority of the second level is lower than the priority of the second level and higher than the priority of the third level, and the priority of the third level is lower than the priority of the third level.
Specifically, in the case where the fourth condition is satisfied, the following cases are classified:
2-1, if the severity of the patch problem is at the second level, determining the patch package as the target package because the priority of the first level is lower than the priority of the second level.
2-2, if the severity of the patch problem is a third level and the importance level of the system version is a first level, determining the OTA packet as a target packet because the priority of the first level is higher than the priority of the third level.
2-3, if the severity of the patch problem is a third level and the importance level of the system version is a second level, determining the OTA packet as a target packet because the priority of the second level is higher than the priority of the third level.
2-4, if the severity of the patch problem is at the third level and the importance level of the system version is at the third level, determining the patch package as the target package because the priority of the third level is lower than the priority of the third level.
In the embodiment of the application, different priority orders are set for the patch problem and the system version according to the different bandwidth network states and the different user space states, and the target packet is selected according to the different priority orders. By the method, various states of the user terminal are comprehensively considered, and the proper upgrade package is selected according to different states, so that the adaptability adjustment of an upgrade scheme is realized, the flexibility of the upgrade of the user terminal is improved, the conditions of repeated upgrade, upgrade failure and the like caused by the fact that a server determines the upgrade scheme are avoided, the stability of a user terminal system is ensured, and the user experience is improved.
Illustratively, as shown in the following table, a rule table for selecting an upgrade package according to status information of a user terminal is provided.
As shown in the above table, states 1-3 satisfy the first condition in S11 described above, that is, at least one of: the severity of the patch problem is a first degree (deadly), the bandwidth network state is a third network state (poor), and the user space state is a third space state (insufficient). States 1-3 correspond to the user terminal being in an extreme state in which the patch package is determined to be the target package.
States 4-9, the second condition in S21 above is satisfied, i.e., the bandwidth network state is the first network state (better), and the user space state is the first space state (sufficient). States 4-9 correspond to the user terminal being in a better state in which the OTA packet is determined to be the target packet regardless of the severity of the patch problem and the importance of the system version.
States 10-15, the third condition in S31 above is satisfied, namely, the bandwidth network state is the first network state (better), and the user space state is the second space state (general). In states 10-15, the OTA packets may be prioritized. In this state, the target packet is determined in the first priority order, that is, in accordance with steps 1-1 to 1-6 in the above-described S31 embodiment. Specifically, as shown in the above table, when the severity of the patch problem is a second level (severe) and the importance level of the system version is a first level (significant characteristic), the OTA packet is determined as the target packet; when the severity of the patch problem is a third degree (general), the importance level of the system version is a first level (significant feature) or a second level (problem repair), determining the OTA packet as a target packet; when the severity of the patch problem is a second level (severity), the importance level of the system version is a second level (problem repair) or a third level (regular update), determining the patch package as a target package; when the severity of the patch problem is a third level (general) and the importance level of the system version is a third level (regular update), the patch package is determined to be the target package.
The states 16-21 satisfy the fourth condition in S32 described above, namely that the bandwidth network state is the second network state (general), and the user space state is the first space state (sufficient). In states 16-21, the patch package may be prioritized. In this state, the target packet is determined in the second priority order, that is, in accordance with steps 2-1 to 2-4 in the above-described S32 embodiment. Specifically, as shown in the above table, when the severity of the patch problem is a second degree (severity), the patch package is determined as the target package regardless of the importance level of the system version; when the severity of the patch problem is a third level (general) and the importance level of the system version is a first level (significant feature) or a second level (problem repair), determining the OTA packet as a target packet; when the severity of the patch problem is a third level (general) and the importance level of the system version is a third level (regular update), the patch package is determined to be the target package.
States 22-27 satisfy the fourth condition of S32 described above, namely that the bandwidth network state is the second network state (general) and the user space state is the second space state (general). In states 22-27, the patch package may be prioritized. In this state, the target packet is determined in the second priority order, that is, in accordance with steps 2-1 to 2-4 in the above-described S32 embodiment. Specifically, as shown in the above table, when the severity of the patch problem is a second degree (severity), the patch package is determined as the target package regardless of the importance level of the system version; when the severity of the patch problem is a third level (general) and the importance level of the system version is a first level (significant feature) or a second level (problem repair), determining the OTA packet as a target packet; when the severity of the patch problem is a third level (general) and the importance level of the system version is a third level (regular update), the patch package is determined to be the target package.
As described above, in the states 1-3, the user terminal is in an extreme state, and the downloading and upgrading of the OTA packet cannot be satisfied, and in this case, patch upgrading is performed, so that the stable operation of the user terminal system can be ensured. In the states 4-9, the user terminal is in a good state, so that the downloading and upgrading of the OTA packet can be met, and in the case, the OTA packet is upgraded, so that the overall upgrading of the user terminal system can be ensured. In the state 10-15, the bandwidth network state of the user terminal is better, but the user space is general, under the condition, the user terminal adopts a first priority order, and selects an upgrade package according to the severity of the patch problem and the importance level of the system version, thereby realizing self-adaptive upgrade; when the system version is of significant characteristics or problem repair, the OTA packet is preferentially selected for upgrading, and the severe patch is not required to be upgraded first, and then the OTA packet of significant characteristics or problem repair is not required to be upgraded, so that the stable operation of the system is ensured, the repeated upgrading condition is avoided, and the user experience is improved. In the states 16-27, the bandwidth network state of the user terminal is general, in this case, the user terminal adopts the second priority order to select the upgrade package according to the severity of the patch problem and the importance level of the system version, so as to realize the self-adaptive upgrade; when the patch problem is serious, the patch package is preferentially selected for upgrading, so that the condition of upgrading failure caused by poor state of the user terminal is avoided, and the stable operation of the system is ensured.
In the above embodiments, the state information including the bandwidth network state, the user space state, the severity level of the patch problem, and the importance level of the system version are described as an example. It may be understood that the status information of the user terminal may further include other information, and accordingly, the upgrade package may also be selected according to the other status information. The embodiment of the application is not particularly limited, and the method for selecting the upgrade package according to the state of the user terminal can be embodied and is within the protection scope of the embodiment of the application.
It will be appreciated that the various status information in the above embodiments may be determined in parallel or in series. For example, when judging serially, it may be judged whether the patch problem is fatal; if yes, selecting a patch package; if not, continuing to judge whether the user space is insufficient; if yes, selecting a patch package; if not, continuing to judge whether the bandwidth network state is worse; if yes, selecting a patch package; if not, determining which priority order is adopted according to the bandwidth network state and the user space state, and then selecting an upgrade package according to the severity of the patch problem and the importance level of the system version. The embodiment of the application does not specifically limit the judging sequence in the process of selecting the upgrade package.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 8, the electronic device 8 of this embodiment includes: at least one processor 80 (only one shown in fig. 8), a memory 81, and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, the steps of any of the various terminal upgrade method embodiments described above being implemented when the processor 80 executes the computer program 82.
The electronic equipment can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The electronic device may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the electronic device 8 and is not meant to be limiting as the electronic device 8, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may in some embodiments be an internal storage unit of the electronic device 8, such as a hard disk or a memory of the electronic device 8. The memory 81 may in other embodiments also be an external storage device of the electronic device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the electronic device 8. The memory 81 is used for storing an operating system, application programs, boot Loader (Boot Loader), data, other programs, etc., such as program codes of the computer program. The memory 81 may also be used to temporarily store data that has been output or is to be output.
The embodiments of the present application also provide a computer readable storage medium storing a computer program, which when executed by a processor, implements the steps of the above-described method embodiments.
Embodiments of the present application also provide a computer program product enabling an electronic device to carry out the steps of the various method embodiments described above, when the computer program product is run on the electronic device.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above-described embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of the method embodiments described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a first device, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The embodiment of the application also provides a chip system, which comprises a processor, wherein the processor is coupled with the memory, and the processor executes a computer program stored in the memory to realize the steps of any method embodiment of the application. The chip system can be a single chip or a chip module composed of a plurality of chips.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the elements and method steps of the examples described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or as a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Finally, it should be noted that: the foregoing is merely illustrative of specific embodiments of the present application, and the scope of the present application is not limited thereto, but any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (13)

1. A method for upgrading a terminal, comprising:
when the packet searching result sent by the server indicates that an OTA packet and a patch packet exist, acquiring current state information of the user terminal;
determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal;
downloading the target package and upgrading according to the target package.
2. The terminal upgrade method according to claim 1, wherein the status information of the user terminal includes a bandwidth network status, a user space status, a severity level of a patch problem, and an importance level of a system version;
and determining a target packet from the OTA packet and the patch packet according to the current state information of the user terminal, wherein the method comprises the following steps:
and determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity level of the patch problem and the importance level of the system version.
3. The terminal upgrade method according to claim 2, wherein the bandwidth network state includes a first network state, a second network state, and a third network state, the first network state being better than the second network state, the second network state being better than the third network state;
The user spatial states include a first spatial state, a second spatial state, and a third spatial state, the first spatial state being better than the second spatial state, the second spatial state being better than the third spatial state;
the severity of the patch problem includes a first degree, a second degree, and a third degree, the first degree being greater than the second degree, the second degree being greater than the third degree;
the importance levels of the system version comprise a first level, a second level and a third level, wherein the priority of the first level is higher than that of the second level, and the priority of the second level is higher than that of the third level;
the determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity level of the patch problem, and the importance level of the system version includes:
when a first condition is met, determining the patch package as the target package;
when the first condition is not met, determining the target packet from the OTA packet and the patch packet according to the bandwidth network state, the user space state, the severity of the patch problem and the importance level of the system version;
Wherein the first condition includes at least one of: the severity of the patch problem is the first degree, the bandwidth network state is the third network state, and the user space state is the third space state.
4. The terminal upgrade method according to claim 3, wherein the determining the target packet from the OTA packet and the patch packet according to the bandwidth network status, the user space status, the severity of the patch problem, and the importance level of the system version when the first condition is not satisfied comprises:
if the second condition is met, determining the OTA packet as the target packet;
if the second condition is not met, determining a target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version;
wherein the second condition includes the bandwidth network state being the first network state and the user space state being the first space state.
5. The method for upgrading a terminal according to claim 4, wherein if the second condition is not satisfied, the determining a target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version includes:
If a third condition is met, determining the target packet from the OTA packet and the patch packet according to a first priority order, wherein the third condition comprises that the bandwidth network state is the first network state and the user space state is the second space state;
the first priority order includes a priority of the first level being lower than a priority of the first level and higher than a priority of the second level being lower than a priority of the second level and higher than a priority of the third level being lower than a priority of the third level.
6. The method for upgrading a terminal according to claim 5, wherein if a third condition is satisfied, the determining the target packet from the OTA packet and the patch packet according to the first priority order includes:
if the severity of the patch problem is the second degree and the importance level of the system version is the first level, determining the OTA packet as the target packet;
if the severity of the patch problem is the third level and the importance level of the system version is not the third level, determining the OTA packet as the target packet;
If the severity of the patch problem is the second level and the importance level of the system version is not the first level, determining the patch package as the target package;
and if the severity of the patch problem is the third degree and the importance level of the system version is the third level, determining the patch package as the target package.
7. The method for upgrading a terminal according to claim 4, wherein if the second condition is not satisfied, the determining a target packet from the OTA packet and the patch packet according to the severity of the patch problem and the importance level of the system version includes:
if a fourth condition is met, determining the target packet from the OTA packet and the patch packet according to a second priority order, wherein the fourth condition comprises that the bandwidth network state is the second network state;
the second order of priority includes the first level of priority being lower than the second level of priority and higher than a third level of priority, the second level of priority being lower than the second level of priority and higher than the third level of priority, the third level of priority being lower than the third level of priority.
8. The method for upgrading a terminal according to claim 7, wherein if the fourth condition is satisfied, the determining the target packet from the OTA packet and the patch packet according to the second priority order includes:
if the severity of the patch problem is the second degree, determining the patch package as the target package;
if the severity of the patch problem is the third level and the importance level of the system version is not the third level, determining the OTA packet as the target packet;
and if the severity of the patch problem is the third degree and the importance level of the system version is the third level, determining the patch package as the target package.
9. The terminal upgrade method according to any one of claims 1 to 8, further comprising:
and when the searching result sent by the server indicates that an OTA packet exists and no patch packet exists, downloading the OTA packet, and upgrading according to the OTA packet.
10. The terminal upgrade method according to any one of claims 1 to 9, further comprising:
and when the packet searching result sent by the server indicates that a patch packet exists and an OTA packet does not exist, downloading the patch packet, and upgrading according to the patch packet.
11. The terminal upgrade method according to any one of claims 1 to 10, further comprising:
and stopping upgrading when the packet searching result sent by the server indicates that no patch packet exists and no OTA packet exists.
12. An electronic device comprising a processor for running a computer program stored in a memory to implement the method of any one of claims 1 to 11.
13. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by one or more processors, implements the method of any one of claims 1 to 11.
CN202211342499.5A 2022-10-31 2022-10-31 Terminal upgrading method, electronic equipment and computer readable storage medium Active CN116708394B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211342499.5A CN116708394B (en) 2022-10-31 2022-10-31 Terminal upgrading method, electronic equipment and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211342499.5A CN116708394B (en) 2022-10-31 2022-10-31 Terminal upgrading method, electronic equipment and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN116708394A true CN116708394A (en) 2023-09-05
CN116708394B CN116708394B (en) 2024-06-14

Family

ID=87826361

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211342499.5A Active CN116708394B (en) 2022-10-31 2022-10-31 Terminal upgrading method, electronic equipment and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN116708394B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116962376A (en) * 2023-09-20 2023-10-27 季华实验室 NB-IOT terminal upgrading method, device, electronic equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110865842A (en) * 2018-08-28 2020-03-06 成都鼎桥通信技术有限公司 OTA (over the air) upgrading method and device
CN112073994A (en) * 2020-09-03 2020-12-11 百度在线网络技术（北京）有限公司 Method and device for over-the-air upgrading, electronic equipment and readable storage medium
CN113176902A (en) * 2021-04-15 2021-07-27 常州易控汽车电子股份有限公司 OTA (over the air) upgrading method of vehicle ECU (electronic control Unit), electronic equipment, vehicle and readable storage medium
US20210273968A1 (en) * 2020-02-27 2021-09-02 International Business Machines Corporation Vulnerability remediation complexity (VRC) system
CN113342376A (en) * 2021-06-23 2021-09-03 支付宝(杭州)信息技术有限公司 Method and device for upgrading operating system of Internet of things equipment
CN114489706A (en) * 2020-10-23 2022-05-13 北京小米移动软件有限公司 Upgrading method, device and storage medium
CN114895940A (en) * 2022-05-23 2022-08-12 珠海格力电器股份有限公司 Upgrading method, device, equipment and storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110865842A (en) * 2018-08-28 2020-03-06 成都鼎桥通信技术有限公司 OTA (over the air) upgrading method and device
US20210273968A1 (en) * 2020-02-27 2021-09-02 International Business Machines Corporation Vulnerability remediation complexity (VRC) system
CN112073994A (en) * 2020-09-03 2020-12-11 百度在线网络技术（北京）有限公司 Method and device for over-the-air upgrading, electronic equipment and readable storage medium
CN114489706A (en) * 2020-10-23 2022-05-13 北京小米移动软件有限公司 Upgrading method, device and storage medium
CN113176902A (en) * 2021-04-15 2021-07-27 常州易控汽车电子股份有限公司 OTA (over the air) upgrading method of vehicle ECU (electronic control Unit), electronic equipment, vehicle and readable storage medium
CN113342376A (en) * 2021-06-23 2021-09-03 支付宝(杭州)信息技术有限公司 Method and device for upgrading operating system of Internet of things equipment
CN114895940A (en) * 2022-05-23 2022-08-12 珠海格力电器股份有限公司 Upgrading method, device, equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116962376A (en) * 2023-09-20 2023-10-27 季华实验室 NB-IOT terminal upgrading method, device, electronic equipment and storage medium
CN116962376B (en) * 2023-09-20 2024-04-05 季华实验室 NB-IOT terminal upgrading method, device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN116708394B (en) 2024-06-14

Similar Documents

Publication Publication Date Title
CN110149370B (en) Method and device for downloading upgrade file
US10630548B2 (en) Update file download method, device, and system
CN104410665B (en) A kind of method for down loading and equipment upgrading bag
CN107087038A (en) A kind of method of data syn-chronization, synchronizer, device and storage medium
CN116708394B (en) Terminal upgrading method, electronic equipment and computer readable storage medium
CN102185920A (en) Network-based downloading method and system, and terminal
CN111629371B (en) Screen projection method and system
CN115335803B (en) Equipment upgrading method, intelligent equipment and computer readable storage medium
CN102457574A (en) Method and system for intelligent multi-address downloading of installation package
CN109639555B (en) Link layer message generation method, link layer message generation device and terminal equipment
CN109672756B (en) Data transmission method and related device, server and storage medium
CN112532664A (en) Data upgrading method and device
CN113746851B (en) Proxy system and method supporting real-time analysis of GRPC request
CN110912717B (en) Broadcasting method and server of centerless multi-channel concurrent transmission system
CN102130786B (en) Method and device for updating characteristics of single board
CN112448839B (en) Network card configuration method and device and computer storage medium
US11368871B2 (en) System and method for generating groups of filtering rules
CN115102804A (en) Data routing method and device for vehicle-mounted gateway, vehicle-mounted gateway and storage medium
US11057489B2 (en) Content deployment method and delivery controller
CN109548020B (en) Compensation method and device after authentication failure, server and storage medium
CN113448744A (en) Application program selection method and device
CN112422305B (en) Upgrading method and device of communication equipment
US10938671B2 (en) Mapping service capabilities
CN115499382B (en) Traffic scheduling method, device, equipment and medium based on Internet of vehicles
CN108810078B (en) Node selection method, terminal device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant