WO2018188336A1 - 软件升级方法、前端服务器及计算机可读存储介质 - Google Patents

软件升级方法、前端服务器及计算机可读存储介质 Download PDF

Info

Publication number
WO2018188336A1
WO2018188336A1 PCT/CN2017/111560 CN2017111560W WO2018188336A1 WO 2018188336 A1 WO2018188336 A1 WO 2018188336A1 CN 2017111560 W CN2017111560 W CN 2017111560W WO 2018188336 A1 WO2018188336 A1 WO 2018188336A1
Authority
WO
WIPO (PCT)
Prior art keywords
upgrade
client
terminal
information
preset
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.)
Ceased
Application number
PCT/CN2017/111560
Other languages
English (en)
French (fr)
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.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen 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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018188336A1 publication Critical patent/WO2018188336A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Definitions

  • the present application provides a software upgrade method, where the software upgrade method is applied to a front-end server, and the upgrade method includes the following steps:
  • the step of receiving the upgrade query information sent by the terminal, and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy further includes:
  • the step of returning the upgrade information to the terminal according to the preset upgrade policy includes:
  • the upgrade type is a major upgrade, returning the first upgrade information to the terminal according to the preset upgrade policy, to completely update the client;
  • the present application further provides a front-end server, where the front-end server is configured with a preset upgrade policy, and the front-end server includes:
  • the information returning module is configured to return the upgrade information to the terminal according to the preset upgrade policy if the client needs to be upgraded.
  • the present application further provides a front-end server, where the front-end server includes: a processor, a memory, and a software upgrade program stored on the memory and executable by the processor, the software upgrade When the program is executed by the processor, the following steps are implemented:
  • the present application further provides a computer readable storage medium, where the software upgrade program is stored, and when the software upgrade program is executed by the processor, the following steps are implemented:
  • the application is configured to receive the upgrade query information sent by the terminal, and determine, according to the upgrade query information and the preset upgrade policy, whether the client in the terminal needs to be upgraded, where the preset upgrade policy is configured in the front-end server; If the client needs to be upgraded, the upgrade information is returned to the terminal according to the preset upgrade policy.
  • the software upgrade method of the present application configures the version upgrade policy of the client on the front-end server.
  • the client performs the version upgrade query
  • the client does not need to access the database and directly performs an upgrade query on the front end.
  • the upgrade is required, the client directly returns to the related upgrade.
  • Information in the pure front end to complete the upgrade operation, simple and convenient. Therefore, the present application simplifies the process of software upgrade, and at the same time, because the upgrade is completed at the front end, it is convenient for personnel maintenance.
  • FIG. 2 is a schematic diagram of a refinement process of determining whether the client in the terminal needs to be upgraded according to the upgrade query information sent by the receiving terminal in FIG. 1 according to the upgrade query information and the preset upgrade policy;
  • FIG. 3 is a schematic diagram showing a refinement process of the upgrade request information sent by the receiving terminal in FIG. 1 and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy;
  • FIG. 4 is a schematic diagram of a refinement process of returning upgrade information to the terminal according to the preset upgrade policy, if the client needs to be upgraded as shown in FIG. 1;
  • FIG. 6 is a schematic diagram of a refinement function module of the upgrade judging module in FIG. 5;
  • FIG. 7 is a schematic diagram of a refinement function module of the upgrade judging module in FIG. 5;
  • the memory 1005 as a computer readable storage medium may include an operating system, a network communication module, and a software upgrade program.
  • the network communication module is mainly used for connecting the client terminal and performing data communication with the client terminal; and the processor 1001 can call the software upgrade program stored in the memory 1005 and perform the following operations:
  • the upgrade information is returned to the terminal according to the preset upgrade policy.
  • the step of receiving the upgrade query information sent by the terminal, and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy further includes:
  • the step of returning the upgrade information to the terminal according to the preset upgrade policy includes:
  • the upgrade type is a major upgrade, returning the first upgrade information to the terminal according to the preset upgrade policy, to completely update the client;
  • the second upgrade information is returned to the terminal according to the preset upgrade policy, so that the client is partially updated.
  • processor 1001 may also invoke a software upgrade program stored in the memory 1005 and perform the following operations:
  • FIG. 1 is a schematic flowchart of a first embodiment of a software upgrade method according to the present application.
  • the software upgrade method is applied to a front-end server, and the upgrade method includes the following steps:
  • Step S10 Receive the upgrade query information sent by the terminal, and determine, according to the upgrade query information and the preset upgrade policy, whether the client in the terminal needs to be upgraded, where the preset upgrade policy is configured in the front-end server.
  • the traditional app upgrade method is to upgrade the software by the background server.
  • the back-end database is configured with a version upgrade policy corresponding to each version of the app.
  • the app sends version number information to the background server.
  • the background server searches for the corresponding version upgrade policy in the back-end database according to the version number information to determine whether it is needed.
  • Upgrade and upgrade methods This upgrade method involves both the front-end, the back-end, and the database. The upgrade process is complicated, and the related upgrade strategy is configured in the database, which is not conducive to maintenance by the staff.
  • the client's upgrade policy is configured in the front-end server, so that when the client performs the upgrade and update, the front-end server is directly accessed, and the background server and the database are not involved, and the client upgrade operation is completed on the front end.
  • the client's upgrade policy is configured in the memory of the front-end server, and the upgrade policy file is in the form of a json file.
  • Json is a lightweight data format with small footprint and fast transfer speed.
  • json supports multiple languages, including C, C#, Java, JavaScript, PHP, Python and other languages.
  • the format is simple, easy to read and write, and easy to parse. With good readability and compatibility, the use of json files can greatly simplify the amount of code development and is easy to maintain.
  • each version of the client can be individually mapped with an upgrade policy file. For personnel maintenance, you can also configure all versions of the upgrade policy in the same upgrade policy file to reduce memory usage.
  • the upgrade policy file can also be in the form of an xml file, and xml is the standard universal markup language.
  • xml is the standard universal markup language.
  • the terminal collects the relevant version information of the client, where the terminal includes the mobile terminal and the PC terminal; when the version information is collected, the terminal sends the upgrade query information to the front-end server, where the query information includes the collected client version information, To confirm if the client needs an upgrade.
  • the front-end server compares the client version information in the upgrade query information with the upgrade policy in the memory, and determines whether the current version of the client in the terminal meets the requirements.
  • the client needs to perform an upgrade update, and the process proceeds to step S20.
  • Step S20 If the client needs to be upgraded, return the upgrade information to the terminal according to the preset upgrade policy.
  • the front-end server determines that the client in the terminal needs to perform the upgrade update according to the upgrade query information and the upgrade policy, the front-end server returns the corresponding upgrade information to the terminal according to the upgrade path included in the upgrade policy.
  • the front-end server may return an upgrade link to the terminal, and open the link to enter the client upgrade interface, and download a new version client in the upgrade interface to perform client replacement to complete the upgrade update, or perform online update on the upgrade interface;
  • the front-end server can also directly return the data required for the upgrade to the terminal, so that the client of the terminal completes the upgrade and update.
  • the front-end server determines that the client in the terminal does not need to perform an upgrade update according to the upgrade query information and the upgrade policy, the corresponding unavailable upgrade information is returned to the terminal.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the terminal sends the upgrade query information to the front-end server to determine whether the client needs to perform the upgrade update operation, which may be performed when the user opens the client; or the terminal may automatically send the upgrade query information to the front-end server. To ensure that the client is in the latest version.
  • the upgrade query information sent by the terminal is received, and the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy, where the preset upgrade policy is configured in the
  • the front-end server returns the upgrade information to the terminal according to the preset upgrade policy if the client needs to be upgraded.
  • the software upgrade method in this embodiment configures the version upgrade policy of the client on the front-end server, and the client does not need to access the database when performing the version upgrade query, and directly performs the upgrade query on the front end; Returning the relevant upgrade information and completing the upgrade operation on the pure front end is simple and convenient.
  • the software upgrade process is simplified by the above manner, and at the same time, the upgrade is completed at the front end, which is convenient for personnel maintenance.
  • FIG. 2 is a schematic diagram of a refinement process of the upgrade request information sent by the receiving terminal in FIG. 1 and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy.
  • step S10 includes:
  • Step S11 Receive upgrade query information sent by the terminal, and parse the upgrade query information according to the first preset parsing rule to obtain version number information of the client in the terminal.
  • the terminal collects the version information of the client, where the client version information includes the version number information of the client; when the version information is collected, the terminal encrypts the version information according to the preset encryption rule to prevent the version information from being encrypted.
  • the version information is falsified and cannot be correctly upgraded, and the data leakage of the terminal is also prevented.
  • the terminal sends the upgrade inquiry information including the encrypted version information to the front-end server.
  • the front-end server parses the upgrade query information according to the first preset parsing rule, and obtains the original version number information collected by the terminal.
  • Step S12 Search for a preset upgrade policy of the corresponding version according to the version number information of the client.
  • the front-end server when the front-end server obtains the original version number information, it searches the memory for the upgrade policy corresponding to the version according to the version number information.
  • step S13 it is determined whether the client needs to be upgraded according to the version number information of the client and the preset upgrade policy of the corresponding version.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the V1 version of the client's corresponding upgrade policy was originally upgraded from V1 to V2.
  • V3 was released, the V1 version of the client's corresponding upgrade policy was changed to V1 to V3, and the V2 version of the client upgrade strategy (V2 liter) was added. To V3).
  • the terminal before sending the upgrade query information, the terminal encrypts the version information in the upgrade query information to prevent the version information from being falsified and cannot be correctly upgraded, and also prevents data leakage of the terminal; the terminal will version number of the client. Send to the front-end server to determine whether the client needs to be upgraded, without having to access the database, simplifying the software upgrade process.
  • FIG. 3 is a schematic diagram of a refinement process of the upgrade request information sent by the receiving terminal in FIG. 1 and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy.
  • step S10 further includes:
  • Step S14 Receive upgrade query information sent by the terminal, and parse the upgrade query information according to the second preset parsing rule to obtain data directory information of the client in the terminal.
  • the terminal collects the version information of the client, where the client version information includes the data directory information of the client; when the version information is collected, the terminal encrypts the version information according to the preset encryption rule to prevent the version information from being encrypted.
  • the version information is falsified and cannot be correctly upgraded, and the data leakage of the terminal is also prevented.
  • the terminal sends the upgrade inquiry information including the encrypted version information to the front-end server.
  • the front-end server parses the upgrade query information according to the second preset parsing rule, and obtains the original data directory information collected by the terminal.
  • Step S15 Determine, according to the data directory information of the client and the data directory information included in the preset upgrade policy, whether the client needs to be upgraded.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the data directory in the original upgrade policy includes ab data.
  • the data directory in the original upgrade policy is modified to include abc data according to the new data of the V2 version.
  • the terminal before sending the upgrade query information, the terminal first encrypts the version information in the upgrade query information, prevents the version information from being tampered and causes the data to be incorrectly upgraded, and prevents the data leakage of the terminal; the terminal sets the data directory of the client.
  • the information is sent to the front-end server and compared with the data directory in the front-end server to determine whether the client needs to be upgraded, without having to access the database, and simplifying the software upgrade process.
  • step S20 includes:
  • step S21 if the client needs to be upgraded and the upgrade type is a major upgrade, the first upgrade information is returned to the terminal according to the preset upgrade policy, so that the client is completely updated.
  • the front-end server determines that the client in the terminal needs to be upgraded according to the upgrade query information and the upgrade policy, and the upgrade type is a major upgrade, and the client needs to be completely replaced, the first step is returned to the terminal according to the upgrade policy. Upgrade information.
  • the terminal can completely update the client through the first upgrade information.
  • step S22 if the client needs to be upgraded and the upgrade type is normal upgrade, the second upgrade information is returned to the terminal according to the preset upgrade policy, so that the client is partially updated.
  • the front-end server provides different upgrade methods for different versions of the client, completely replaces the client during a major upgrade, and modifies and/or increases or decreases part of the client content during the normal upgrade to simplify the client. End upgrade process, and convenient for personnel maintenance.
  • the application further provides a front end server.
  • FIG. 5 is a schematic diagram of functional modules of a front end server according to a first embodiment of the present application.
  • the front-end server is configured with a preset upgrade policy, and the front-end server includes:
  • the upgrade judging module 10 is configured to receive the upgrade query information sent by the terminal, and determine, according to the upgrade query information and the preset upgrade policy, whether the client in the terminal needs to be upgraded.
  • the traditional app upgrade method is to upgrade the software by the background server.
  • the back-end database is configured with a version upgrade policy corresponding to each version of the app.
  • the app sends version number information to the background server.
  • the background server searches for the corresponding version upgrade policy in the back-end database according to the version number information to determine whether it is needed.
  • Upgrade and upgrade methods This upgrade method involves both the front-end, the back-end, and the database. The upgrade process is complicated, and the related upgrade strategy is configured in the database, which is not conducive to maintenance by the staff.
  • the client's upgrade policy is configured in the front-end server, so that when the client performs the upgrade and update, the front-end server is directly accessed, and the background server and the database are not involved, and the client upgrade operation is completed on the front end.
  • the client's upgrade policy is configured in the memory of the front-end server, and the upgrade policy file is in the form of a json file.
  • Json is a lightweight data format with small footprint and fast transfer speed.
  • json supports multiple languages, including C, C#, Java, JavaScript, PHP, Python and other languages.
  • the format is simple, easy to read and write, and easy to parse. With good readability and compatibility, the use of json files can greatly simplify the amount of code development and is easy to maintain.
  • each version of the client can be individually mapped with an upgrade policy file. For personnel maintenance, you can also configure all versions of the upgrade policy in the same upgrade policy file to reduce memory usage.
  • the upgrade policy file can also be in the form of an xml file, and xml is the standard universal markup language.
  • xml is the standard universal markup language.
  • the terminal collects the relevant version information of the client, where the terminal includes the mobile terminal and the PC terminal; when the version information is collected, the terminal sends the upgrade query information to the front-end server, where the query information includes the collected client version information, To confirm if the client is upgraded.
  • the front-end server compares the client version information in the upgrade query information with the upgrade policy in the memory, and determines whether the current version of the client in the terminal meets the requirements. The client needs to be upgraded.
  • the information returning module 20 is configured to return the upgrade information to the terminal according to the preset upgrade policy if the client needs to be upgraded.
  • the front-end server determines that the client in the terminal needs to perform the upgrade update according to the upgrade query information and the upgrade policy, the front-end server returns the corresponding upgrade information to the terminal according to the upgrade path included in the upgrade policy.
  • the front-end server may return an upgrade link to the terminal, and open the link to enter the client upgrade interface, and download a new version client in the upgrade interface to perform client replacement to complete the upgrade update, or perform online update on the upgrade interface;
  • the front-end server can also directly return the data required for the upgrade to the terminal, so that the client of the terminal completes the upgrade and update.
  • the front-end server determines that the client in the terminal does not need to perform an upgrade update according to the upgrade query information and the upgrade policy, the corresponding unavailable upgrade information is returned to the terminal.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the terminal sends the upgrade query information to the front-end server to determine whether the client needs to perform the upgrade update operation, which may be performed when the user opens the client; or the terminal may automatically send the upgrade query information to the front-end server. To ensure that the client is in the latest version.
  • the upgrade query information sent by the terminal is received, and the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy, where the preset upgrade policy is configured in the
  • the front-end server returns the upgrade information to the terminal according to the preset upgrade policy if the client needs to be upgraded.
  • the software upgrade method in this embodiment configures the version upgrade policy of the client on the front-end server, and the client does not need to access the database when performing the version upgrade query, and directly performs the upgrade query on the front end; Returning the relevant upgrade information and completing the upgrade operation on the pure front end is simple and convenient.
  • the software upgrade process is simplified by the above manner, and at the same time, the upgrade is completed at the front end, which is convenient for personnel maintenance.
  • FIG. 6 is a schematic diagram of a refinement function module of the upgrade judging module in FIG. 5.
  • the upgrade determining module 10 includes:
  • the first parsing unit 11 is configured to receive the upgrade query information sent by the terminal, and parse the upgrade query information according to the first preset parsing rule to obtain version number information of the client in the terminal.
  • the terminal collects the version information of the client, where the client version information includes the version number information of the client; when the version information is collected, the terminal encrypts the version information according to the preset encryption rule to prevent the version information from being encrypted.
  • the version information is falsified and cannot be correctly upgraded, and the data leakage of the terminal is also prevented.
  • the terminal sends the upgrade inquiry information including the encrypted version information to the front-end server.
  • the front-end server parses the upgrade query information according to the first preset parsing rule, and obtains the original version number information collected by the terminal.
  • the policy search unit 12 is configured to search for a preset upgrade policy of the corresponding version according to the version number information of the client.
  • the front-end server when the front-end server obtains the original version number information, it searches the memory for the upgrade policy corresponding to the version according to the version number information.
  • the first determining unit 13 is configured to determine, according to the version number information of the client and the preset upgrade policy of the corresponding version, whether the client needs to be upgraded.
  • the front-end server when the front-end server finds the upgrade policy corresponding to the client version, it determines whether the client needs to be upgraded according to the upgrade path and the version number according to the upgrade policy. For example, if the client version number is V2, if the upgrade path in the corresponding upgrade policy is V2 to V3 according to the version number V2, it is determined that the client needs to be upgraded; if the upgrade in the corresponding upgrade policy is found according to the version number V2 If the path is V2 to V2, or there is no upgrade path in the upgrade policy, it is determined that the client does not need to be upgraded.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the V1 version of the client's corresponding upgrade policy was originally upgraded from V1 to V2.
  • V3 was released, the V1 version of the client's corresponding upgrade policy was changed to V1 to V3, and the V2 version of the client upgrade strategy (V2 liter) was added. To V3).
  • the terminal before sending the upgrade query information, the terminal encrypts the version information in the upgrade query information to prevent the version information from being falsified and cannot be correctly upgraded, and also prevents data leakage of the terminal; the terminal will version number of the client. Send to the front-end server to determine whether the client needs to be upgraded, without having to access the database, simplifying the software upgrade process.
  • FIG. 7 is a schematic diagram of a refinement function module of the upgrade judging module in FIG. 5.
  • the upgrade judging module 10 further includes:
  • the second parsing unit 14 is configured to receive the upgrade query information sent by the terminal, and parse the upgrade query information according to the second preset parsing rule to obtain data directory information of the client in the terminal.
  • the terminal collects the version information of the client, where the client version information includes the data directory information of the client; when the version information is collected, the terminal encrypts the version information according to the preset encryption rule to prevent the version information from being encrypted.
  • the version information is falsified and cannot be correctly upgraded, and the data leakage of the terminal is also prevented.
  • the terminal sends the upgrade inquiry information including the encrypted version information to the front-end server.
  • the front-end server parses the upgrade query information according to the second preset parsing rule, and obtains the original data directory information collected by the terminal.
  • the second determining unit 15 is configured to determine, according to the data directory information of the client and the preset upgrade policy, whether the client needs to be upgraded.
  • the front-end server when the front-end server obtains the original data directory information, it compares the original data directory information with the data directory information included in the upgrade policy to determine whether the relevant data is missing in the client; if yes, determine The client needs to perform an upgrade and update, and generates differential data directory information, and returns corresponding upgrade information to the terminal according to the differential data directory information.
  • the front-end server updates the upgrade policy in real time according to the release status of the new version of the client.
  • the data directory in the original upgrade policy includes ab data.
  • the data directory in the original upgrade policy is modified to include abc data according to the new data of the V2 version.
  • the terminal before sending the upgrade query information, the terminal first encrypts the version information in the upgrade query information, prevents the version information from being tampered and causes the data to be incorrectly upgraded, and prevents the data leakage of the terminal; the terminal sets the data directory of the client.
  • the information is sent to the front-end server and compared with the data directory in the front-end server to determine whether the client needs to be upgraded, without having to access the database, and simplifying the software upgrade process.
  • FIG. 8 is a schematic diagram of a refinement function module of the information return module in FIG.
  • the upgrade determining module 20 includes:
  • the first returning unit 21 is configured to: when the client needs to be upgraded, and the upgrade type is a major upgrade, returning the first upgrade information to the terminal according to the preset upgrade policy, to complete the client Update.
  • the front-end server determines that the client in the terminal needs to be upgraded according to the upgrade query information and the upgrade policy, and the upgrade type is a major upgrade, and the client needs to be completely replaced, the first step is returned to the terminal according to the upgrade policy. Upgrade information.
  • the terminal can completely update the client through the first upgrade information.
  • the second returning unit 22 is configured to: when the client needs to be upgraded, and the upgrade type is a normal upgrade, returning the second upgrade information to the terminal according to the preset upgrade policy, to perform part of the client Update.
  • the front-end server determines that the client in the terminal needs to be upgraded according to the upgrade query information and the upgrade policy, and the type of the upgrade is a normal upgrade, and part of the content of the client needs to be modified and/or the content is increased or decreased
  • the second upgrade information is returned to the terminal according to the upgrade policy.
  • the terminal may partially update the client by using the second upgrade information.
  • the front-end server provides different upgrade methods for different versions of the client, completely replaces the client during a major upgrade, and modifies and/or increases or decreases part of the client content during the normal upgrade to simplify the client. End upgrade process, and convenient for personnel maintenance.
  • the application further provides a computer readable storage medium.
  • a software upgrade program is stored on the readable storage medium of the present application, and the software upgrade program is executed by the processor to implement the following steps:
  • the upgrade information is returned to the terminal according to the preset upgrade policy.
  • the step of receiving the upgrade query information sent by the terminal, and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy includes:
  • the step of receiving the upgrade query information sent by the terminal, and determining whether the client in the terminal needs to be upgraded according to the upgrade query information and the preset upgrade policy further includes:
  • the step of returning the upgrade information to the terminal according to the preset upgrade policy includes:
  • the upgrade type is a major upgrade, returning the first upgrade information to the terminal according to the preset upgrade policy, to completely update the client;
  • the second upgrade information is returned to the terminal according to the preset upgrade policy, so that the client is partially updated.
  • the preset upgrade policy is updated according to the release situation.

Landscapes

  • Engineering & Computer Science (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

本申请提供一种软件升级方法,所述升级方法应用于前端服务器,所述升级方法包括以下步骤:接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。本申请还提供一种前端服务器、及计算机可读存储介质。本申请将客户端的版本升级策略配置在前端服务器,客户端在进行版本升级查询时,不必访问数据库,直接在前端进行升级操作。通过以上方式,本申请简化软件升级的过程,同时由于升级在前端完成,方便人员维护。

Description

软件升级方法、前端服务器及计算机可读存储介质
本申请要求于2017年4月10日提交中国专利局、申请号为201710226910.5、发明名称为“软件升级方法及前端服务器”的中国专利申请的优先权,其全部内容通过引用结合在申请中。
技术领域
本申请涉及软件升级技术领域,尤其涉及一种软件升级方法、前端服务器及计算机可读存储介质。
背景技术
手机软件app升级是软件应用当中很常见的一个功能,基本上联网的app都具备的升级功能。通过软件升级,可修复低版本软件的bug,对软件进行优化,增加新的功能和特性,为用户提供更好的体验。
传统的app升级方法,都是由后台服务器处理软件升级。后端的数据库中配置有各版本app对应的版本升级策略,在app进行升级时,app向后台服务器发送版本号信息,后台服务器根据版本号信息搜索后端的数据库中的对应版本升级策略以确定是否需要升级。这种升级方法同时涉及到前端、后台和数据库,其升级过程较为复杂;而且由于相关升级策略是配置在数据库中,不利于工作人员进行维护。
发明内容
本申请的主要目的在于提出一种软件升级方法、前端服务器及计算机可读存储介质,旨在解决软件升级过程复杂,人员维护不便的技术问题。
为实现上述目的,本申请提供一种软件升级方法,所述软件升级方法应用于前端服务器,所述升级方法包括以下步骤:
接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
优选的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
根据所述客户端的版本号信息查找对应版本的预设升级策略;
根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
优选的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
优选的,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
优选的,所述升级方法还包括:
在发布新版本客户端时,根据发布情况更新所述预设升级策略。
此外,为实现上述目的,本申请还提供一种前端服务器,所述前端服务器配置有预设升级策略,所述前端服务器包括:
升级判断模块,用于接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级;
信息返回模块,用于若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
此外,为实现上述目的,本申请还提供一种前端服务器,所述前端服务器包括:处理器、存储器及存储在所述存储器上并可被所述处理器执行的软件升级程序,所述软件升级程序被所述处理器执行时,实现以下步骤:
接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
此外,为实现上述目的,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质上存储有软件升级程序,所述软件升级程序被处理器执行时实现如下步骤:
接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
本申请通过接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。通过以上方式,本申请软件升级方法将客户端的版本升级策略配置在前端服务器,客户端在进行版本升级查询时,不必访问数据库,直接在前端进行升级查询;在需要进行升级时,直接返回相关升级信息,在纯前端完成升级操作,简单方便。因此,本申请简化了软件升级的过程,同时由于升级在前端完成,方便人员维护。
附图说明
图1为本申请软件升级方法第一实施例的流程示意图;
图2为图1中所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的细化流程示意图;
图3为图1中所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的细化流程示意图;
图4为图1中所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的细化流程示意图;
图5为本申请前端服务器第一实施例的功能模块示意图;
图6为图5中所述升级判断模块的细化功能模块示意图;
图7为图5中所述升级判断模块的细化功能模块示意图;
图8为图5中所述信息返回模块的细化功能模块示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请实施例涉及的软件升级方法主要应用于前端服务器,前端服务器可以包括处理器1001(例如CPU),通信总线1002,用户接口1003,网络接口1004,存储器1005。其中,通信总线1002用于实现这些组件之间的连接通信;用户接口1003可以包括显示屏(Display)、输入单元比如键盘(Keyboard);网络接口1004可选的可以包括标准的有线接口、无线接口(如WI-FI接口);存储器1005可以是高速RAM存储器,也可以是稳定的存储器(non-volatile memory),例如磁盘存储器,存储器1005还可以是独立于前述处理器1001的存储装置。本领域技术人员可以理解,上述前端服务器的硬件结构并不构成对前端服务器的限定,可以包括更多或更少的部件,或者组合某些部件,或者不同的部件布置。
作为一种计算机可读存储介质的存储器1005,可以包括操作系统、网络通信模块以及软件升级程序。网络通信模块主要用于连接客户终端,与客户终端进行数据通信;而处理器1001可以调用存储器1005中存储的软件升级程序,并执行以下操作:
接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
进一步的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
根据所述客户端的版本号信息查找对应版本的预设升级策略;
根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
进一步的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
进一步的,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
进一步的,处理器1001还可以调用存储器1005中存储的软件升级程序,并执行以下操作:
在发布新版本客户端时,根据发布情况更新所述预设升级策略。
基于上述前端服务器的硬件结构,提出本申请软件升级方法的各个实施例。
参照图1,图1为本申请软件升级方法第一实施例的流程示意图。
本实施例中,所述软件升级方法应用于前端服务器,所述升级方法包括以下步骤:
步骤S10,接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器。
传统的app升级方法,都是由后台服务器处理软件升级。后端的数据库中配置有各版本app对应的版本升级策略,在app进行升级时,app向后台服务器发送版本号信息,后台服务器根据版本号信息搜索后端的数据库中的对应版本升级策略以确定是否需要升级及升级方法。这种升级方法同时涉及到前端、后台和数据库,其升级过程较为复杂,而且由于相关升级策略是配置在数据库中,不利于工作人员进行维护。在本实施例中,将客户端的升级策略配置在前端服务器中,使得在客户端进行升级更新时,直接访问前端服务器,不涉及后台服务器和数据库,在前端完成客户端的升级操作。
具体的,将客户端的升级策略配置在前端服务器的内存中,而对于升级策略文件,采用json文件的形式。json是一种轻量级的数据格式,占用空间小,传输速度快,且json支持多种语言,包括C、C#、Java、JavaScript、PHP、Python等语言,格式简单,易于读写,便于解析,具有良好的可读性和兼容性,通过使用json文件,可大大简化了代码开发量,并且易于维护;对于客户端的升级策略,可以是每一个版本的客户端单独对应一个升级策略文件,方便人员进行维护,也可以是将所有版本的升级策略配置在同一升级策略文件中,减小内存的占用。升级策略文件也可以采用xml文件的形式,xml是标准通用标记语言 (SGML) 的子集,非常适合 Web 传输,其格式统一,符合标准,便于数据共享和远程交互;当然升级策略文件还可以采用其它形式。在升级开始时,终端收集客户端的相关版本信息,其中终端包括移动终端和PC终端;在版本信息收集完毕时,终端向前端服务器发送升级询问信息,询问信息中包括收集的客户端版本信息,用以确认客户端是否需要升级。前端服务器在接收到终端发送的升级询问信息时,将升级询问信息中的客户端版本信息与内存中的升级策略进行对比,判断终端中的客户端当前版本是否符合要求,若不符合要求,则该客户端需要进行升级更新,此时进入步骤S20。
步骤S20,若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
本实施例中,若前端服务器根据升级询问信息和升级策略判断该终端中的客户端需要进行升级更新,则会根据升级策略中包括的升级途径向终端返回相应的升级信息。具体的,前端服务器可以向终端返回升级链接,通过打开该链接可进入客户端升级界面,并在该升级界面下载新版本客户端进行客户端替换完成升级更新,或在该升级界面进行在线更新;当然,前端服务器还可以直接向终端返回升级所需的数据,以使终端的客户端完成升级更新。
进一步的,若前端服务器根据升级询问信息和升级策略判断该终端中的客户端不需要进行升级更新,则会向终端返回相应的无可用升级信息。
再进一步的,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。
在具体实施中,终端向前端服务器发送升级询问信息,以确定客户端是否需要进行升级更新的操作,可以是用户打开客户端时进行的;当然也可以是终端定时自动向前端服务器发送升级询问信息,以保证客户端处于最新版本。
本实施例中,通过接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。通过以上方式,本实施例中的软件升级方法将客户端的版本升级策略配置在前端服务器,客户端在进行版本升级查询时,不必访问数据库,直接在前端进行升级查询;在需要进行升级时,直接返回相关升级信息,在纯前端完成升级操作,简单方便。本实施例通过以上方式,简化软件升级的过程,同时由于升级在前端完成,方便人员维护。
参照图2,图2为图1中所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的细化流程示意图。
基于上述图1所示实施例,步骤S10包括:
步骤S11,接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息。
本实施例中,在升级开始时,终端收集客户端的版本信息,其中客户端版本信息包括客户端的版本号信息;在版本信息收集完毕时,终端会按预设加密规则对版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;加密完成时,终端向前端服务器发送包括加密版本信息的升级询问信息。前端服务器在接收到终端发送的升级询问信息时,将根据第一预设解析规则对升级询问信息进行解析,得到终端收集到的原始版本号信息。
步骤S12,根据所述客户端的版本号信息查找对应版本的预设升级策略。
本实施例中,前端服务器在得到原始版本号信息时,将根据该版本号信息在内存中查找该版本对应的升级策略。
步骤S13,根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
本实施例中,前端服务器在查找到与客户端版本对应的升级策略时,将根据根据升级策略中的升级路径和版本号确定客户端是否需要进行升级。例如,客户端版本号为V2,若根据版本号V2查找到对应升级策略中的升级路径为V2至V3,则确定该客户端需要进行升级;若根据版本号V2查找到对应升级策略中的升级路径为V2至V2,或升级策略中无升级路径,则确定该客户端不需要进行升级。
进一步的,发布新版本客户端时,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。例如,V1版本的客户端对应升级策略原为V1升至V2,在发布V3时,V1版本的客户端对应升级策略修改为V1升至V3,同时新增V2版本的客户端升级策略(V2升至V3)。
本实施例中,终端在发送升级询问信息前,会先对升级询问信息中的版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;终端将客户端的版本号发送至前端服务器,以判断是否客户端是否需要升级,不必访问数据库,简化软件升级的过程。
参照图3,图3为图1中所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的细化流程示意图。
基于上述图1所示实施例,步骤S10还包括:
步骤S14,接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息。
本实施例中,在升级开始时,终端收集客户端的版本信息,其中客户端版本信息包括客户端的数据目录信息;在版本信息收集完毕时,终端会按预设加密规则对版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;加密完成时,终端向前端服务器发送包括加密版本信息的升级询问信息。前端服务器在接收到终端发送的升级询问信息时,将根据第二预设解析规则对升级询问信息进行解析,得到终端收集到的原始数据目录信息。
步骤S15,根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
本实施例中,前端服务器在得到原始数据目录信息时,将根据原始数据目录信息和升级策略中包括的应有数据目录信息进行对比,判断客户端中是否缺少相关应有数据;若是,则判断客户端需要进行升级更新,同时生成差别数据目录信息,并根据该差别数据目录信息向终端返回对应的升级信息。
进一步的,发布新版本客户端时,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。例如,原升级策略中的应有数据目录包括ab数据,在新发布V2版本时,根据V2版本的新增数据情况,将原升级策略中的应有数据目录修改为包括abc数据。
本实施例中,终端在发送升级询问信息前,会先对升级询问信息中的版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;终端将客户端的数据目录信息发送至前端服务器,与前端服务器中的数据目录进行对比,以判断是否客户端是否需要升级,不必访问数据库,简化软件升级的过程。
参照图4,图4为图1中所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的细化流程示意图。
基于上述图1所示实施例,步骤S20包括:
步骤S21,若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新。
本实施例中,若前端服务器根据升级询问信息和升级策略判断终端中的客户端需要升级,而且升级的类型为重大升级,需要对客户端进行完全替换,则将根据升级策略向终端返回第一升级信息。终端可通过该第一升级信息对该客户端进行完全更新。
步骤S22,若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
本实施例中,若前端服务器根据升级询问信息和升级策略判断终端中的客户端需要升级,而且升级的类型为普通升级,需要对客户端的部分内容进行修改和/或增减部分内容,则将根据升级策略向终端返回第二升级信息。终端可通过该第二升级信息对该客户端进行部分更新。
本实施例中,前端服务器为不同版本的客户端提供不同的升级方法,在重大升级时对客户端进行完全替换,在普通升级时对客户端的部分内容进行修改和/或增减操作,简化客户端升级过程,而且方便人员维护。
本申请进一步提供一种前端服务器。
参照图5,图5为本申请前端服务器第一实施例的功能模块示意图。
本实施例中,所述前端服务器配置有预设升级策略,所述前端服务器包括:
升级判断模块10,用于接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级。
传统的app升级方法,都是由后台服务器处理软件升级。后端的数据库中配置有各版本app对应的版本升级策略,在app进行升级时,app向后台服务器发送版本号信息,后台服务器根据版本号信息搜索后端的数据库中的对应版本升级策略以确定是否需要升级及升级方法。这种升级方法同时涉及到前端、后台和数据库,其升级过程较为复杂,而且由于相关升级策略是配置在数据库中,不利于工作人员进行维护。在本实施例中,将客户端的升级策略配置在前端服务器中,使得在客户端进行升级更新时,直接访问前端服务器,不涉及后台服务器和数据库,在前端完成客户端的升级操作。
具体的,将客户端的升级策略配置在前端服务器的内存中,而对于升级策略文件,采用json文件的形式。json是一种轻量级的数据格式,占用空间小,传输速度快,且json支持多种语言,包括C、C#、Java、JavaScript、PHP、Python等语言,格式简单,易于读写,便于解析,具有良好的可读性和兼容性,通过使用json文件,可大大简化了代码开发量,并且易于维护;对于客户端的升级策略,可以是每一个版本的客户端单独对应一个升级策略文件,方便人员进行维护,也可以是将所有版本的升级策略配置在同一升级策略文件中,减小内存的占用。升级策略文件也可以采用xml文件的形式,xml是标准通用标记语言 (SGML) 的子集,非常适合 Web 传输,其格式统一,符合标准,便于数据共享和远程交互;当然升级策略文件还可以采用其它形式。在升级开始时,终端收集客户端的相关版本信息,其中终端包括移动终端和PC终端;在版本信息收集完毕时,终端向前端服务器发送升级询问信息,询问信息中包括收集的客户端版本信息,用以确认客户端是否升级。前端服务器在接收到终端发送的升级询问信息时,将升级询问信息中的客户端版本信息与内存中的升级策略进行对比,判断终端中的客户端当前版本是否符合要求,若不符合要求,则该客户端需要进行升级更新。
信息返回模块20,用于若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
本实施例中,若前端服务器根据升级询问信息和升级策略判断该终端中的客户端需要进行升级更新,则会根据升级策略中包括的升级途径向终端返回相应的升级信息。具体的,前端服务器可以向终端返回升级链接,通过打开该链接可进入客户端升级界面,并在该升级界面下载新版本客户端进行客户端替换完成升级更新,或在该升级界面进行在线更新;当然,前端服务器还可以直接向终端返回升级所需的数据,以使终端的客户端完成升级更新。
进一步的,若前端服务器根据升级询问信息和升级策略判断该终端中的客户端不需要进行升级更新,则会向终端返回相应的无可用升级信息。
再进一步的,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。
在具体实施中,终端向前端服务器发送升级询问信息,以确定客户端是否需要进行升级更新的操作,可以是用户打开客户端时进行的;当然也可以是终端定时自动向前端服务器发送升级询问信息,以保证客户端处于最新版本。
本实施例中,通过接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。通过以上方式,本实施例中的软件升级方法将客户端的版本升级策略配置在前端服务器,客户端在进行版本升级查询时,不必访问数据库,直接在前端进行升级查询;在需要进行升级时,直接返回相关升级信息,在纯前端完成升级操作,简单方便。本实施例通过以上方式,简化软件升级的过程,同时由于升级在前端完成,方便人员维护。
参照图6,图6为图5中所述升级判断模块的细化功能模块示意图。
基于上述图5所示实施例,所述升级判断模块10包括:
第一解析单元11,用于接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息。
本实施例中,在升级开始时,终端收集客户端的版本信息,其中客户端版本信息包括客户端的版本号信息;在版本信息收集完毕时,终端会按预设加密规则对版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;加密完成时,终端向前端服务器发送包括加密版本信息的升级询问信息。前端服务器在接收到终端发送的升级询问信息时,将根据第一预设解析规则对升级询问信息进行解析,得到终端收集到的原始版本号信息。
策略查找单元12,用于根据所述客户端的版本号信息查找对应版本的预设升级策略。
本实施例中,前端服务器在得到原始版本号信息时,将根据该版本号信息在内存中查找该版本对应的升级策略。
第一判断单元13,用于根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
本实施例中,前端服务器在查找到与客户端版本对应的升级策略时,将根据根据升级策略中的升级路径和版本号确定客户端是否需要进行升级。例如,客户端版本号为V2,若根据版本号V2查找到对应升级策略中的升级路径为V2至V3,则确定该客户端需要进行升级;若根据版本号V2查找到对应升级策略中的升级路径为V2至V2,或升级策略中无升级路径,则确定该客户端不需要进行升级。
进一步的,发布新版本客户端时,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。例如,V1版本的客户端对应升级策略原为V1升至V2,在发布V3时,V1版本的客户端对应升级策略修改为V1升至V3,同时新增V2版本的客户端升级策略(V2升至V3)。
本实施例中,终端在发送升级询问信息前,会先对升级询问信息中的版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;终端将客户端的版本号发送至前端服务器,以判断是否客户端是否需要升级,不必访问数据库,简化软件升级的过程。
参照图7,图7为图5中所述升级判断模块的细化功能模块示意图。
基于上述图5所示实施例,所述升级判断模块10还包括:
第二解析单元14,用于接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息。
本实施例中,在升级开始时,终端收集客户端的版本信息,其中客户端版本信息包括客户端的数据目录信息;在版本信息收集完毕时,终端会按预设加密规则对版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;加密完成时,终端向前端服务器发送包括加密版本信息的升级询问信息。前端服务器在接收到终端发送的升级询问信息时,将根据第二预设解析规则对升级询问信息进行解析,得到终端收集到的原始数据目录信息。
第二判断单元15,用于根据所述客户端的数据目录信息和预设升级策略判断所述客户端是否需要进行升级。
本实施例中,前端服务器在得到原始数据目录信息时,将根据原始数据目录信息和升级策略中包括的应有数据目录信息进行对比,判断客户端中是否缺少相关应有数据;若是,则判断客户端需要进行升级更新,同时生成差别数据目录信息,并根据该差别数据目录信息向终端返回对应的升级信息。
进一步的,发布新版本客户端时,前端服务器会根据客户端的新版本发布情况对升级策略进行实时的更新。例如,原升级策略中的应有数据目录包括ab数据,在新发布V2版本时,根据V2版本的新增数据情况,将原升级策略中的应有数据目录修改为包括abc数据。
本实施例中,终端在发送升级询问信息前,会先对升级询问信息中的版本信息进行加密,防止版本信息被篡改导致不能正确升级,同时也防止终端的数据泄露;终端将客户端的数据目录信息发送至前端服务器,与前端服务器中的数据目录进行对比,以判断是否客户端是否需要升级,不必访问数据库,简化软件升级的过程。
参照图8,图8为图5中所述信息返回模块的细化功能模块示意图。
基于上述图5所示实施例,所述升级判断模块20包括:
第一返回单元21,用于若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新。
本实施例中,若前端服务器根据升级询问信息和升级策略判断终端中的客户端需要升级,而且升级的类型为重大升级,需要对客户端进行完全替换,则将根据升级策略向终端返回第一升级信息。终端可通过该第一升级信息对该客户端进行完全更新。
第二返回单元22,用于若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
本实施例中,若前端服务器根据升级询问信息和升级策略判断终端中的客户端需要升级,而且升级的类型为普通升级,需要对客户端的部分内容进行修改和/或增减部分内容,则将根据升级策略向终端返回第二升级信息。终端可通过该第二升级信息对该客户端进行部分更新。
本实施例中,前端服务器为不同版本的客户端提供不同的升级方法,在重大升级时对客户端进行完全替换,在普通升级时对客户端的部分内容进行修改和/或增减操作,简化客户端升级过程,而且方便人员维护。
本申请进一步提供一种计算机可读存储介质。
本申请可读存储介质上存储有软件升级程序,所述软件升级程序被处理器执行时实现如下步骤:
接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
进一步的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
根据所述客户端的版本号信息查找对应版本的预设升级策略;
根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
进一步的,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
进一步的,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
进一步的,所述软件升级程序被处理器执行时还实现如下步骤:
在发布新版本客户端时,根据发布情况更新所述预设升级策略。
其中,软件升级程序被执行时所实现的方法可参照本申请软件升级方法的各个实施例,此处不再赘述。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种软件升级方法,其特征在于,所述软件升级方法应用于前端服务器,所述升级方法包括以下步骤:
    接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
    若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
  2. 如权利要求1所述的升级方法,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
    接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
    根据所述客户端的版本号信息查找对应版本的预设升级策略;
    根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
  3. 权利要求1所述的升级方法,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
    接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
    根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
  4. 如权利要求1所述的升级方法,其特征在于,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
    若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
    若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
  5. 如权利要求1的升级方法,其特征在于,所述升级方法还包括:
    在发布新版本客户端时,根据发布情况更新所述预设升级策略。
  6. 一种前端服务器,其特征在于,所述前端服务器配置有预设升级策略,所述前端服务器包括:
    升级判断模块,用于接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级;
    信息返回模块,用于若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
  7. 如权利要求6所述的前端服务器,其特征在于,所述升级判断模块包括:
    第一解析单元,用于接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
    策略查找单元,用于根据所述客户端的版本号信息查找对应版本的预设升级策略;
    第一判断单元,用于根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
  8. 如权利要求6所述的前端服务器,其特征在于,所述升级判断模块还包括:
    第二解析单元,用于接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
    第二判断单元,用于根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
  9. 如权利要求6所述的前端服务器,其特征在于,所述信息返回模块模块包括:
    第一返回单元,用于若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
    第二返回单元,用于若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
  10. 如权利要求6所述的前端服务器,其特征在于,所述前端服务器还包括:
    策略更新模块,用于在发布新版本客户端时,根据发布情况更新所述预设升级策略。
  11. 一种前端服务器,其特征在于,所述前端服务器包括:处理器、存储器及存储在所述存储器上并可被所述处理器执行的软件升级程序,所述软件升级程序被所述处理器执行时,实现以下步骤:
    接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
    若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
  12. 如权利要求11所述的前端服务器,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
    接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
    根据所述客户端的版本号信息查找对应版本的预设升级策略;
    根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
  13. 如权利要求11所述的前端服务器,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
    接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
    根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
  14. 如权利要求11所述的前端服务器,其特征在于,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
    若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
    若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
  15. 如权利要求11所述的前端服务器,其特征在于,所述软件升级程序被所述处理器执行时,还实现以下步骤:
    在发布新版本客户端时,根据发布情况更新所述预设升级策略。
  16. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有软件升级程序,所述软件升级程序被处理器执行时实现如下步骤:
    接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级,其中所述预设升级策略配置在所述前端服务器;
    若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息。
  17. 如权利要求16所述的计算机可读存储介质,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤包括:
    接收终端发送的升级询问信息,并根据第一预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的版本号信息;
    根据所述客户端的版本号信息查找对应版本的预设升级策略;
    根据所述客户端的版本号信息和对应版本的预设升级策略判断所述客户端是否需要进行升级。
  18. 如权利要求16所述的计算机可读存储介质,其特征在于,所述接收终端发送的升级询问信息,并根据所述升级询问信息和预设升级策略判断所述终端中的客户端是否需要进行升级的步骤,还包括:
    接收终端发送的升级询问信息,并根据第二预设解析规则对所述升级询问信息进行解析,得到所述终端中的客户端的数据目录信息;
    根据所述客户端的数据目录信息和预设升级策略中包括的应有数据目录信息判断所述客户端是否需要进行升级。
  19. 如权利要求16所述的计算机可读存储介质,其特征在于,所述若所述客户端需要进行升级,根据所述预设升级策略向所述终端返回升级信息的步骤包括:
    若所述客户端需要进行升级,且升级类型为重大升级,则根据所述预设升级策略向所述终端返回第一升级信息,以对所述客户端进行完全更新;
    若所述客户端需要进行升级,且升级类型为普通升级,则根据所述预设升级策略向所述终端返回第二升级信息,以对所述客户端进行部分更新。
  20. 如权利要求16所述的计算机可读存储介质,其特征在于,所述软件升级程序被处理器执行时还实现如下步骤:
    在发布新版本客户端时,根据发布情况更新所述预设升级策略。
PCT/CN2017/111560 2017-04-10 2017-11-17 软件升级方法、前端服务器及计算机可读存储介质 Ceased WO2018188336A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710226910.5 2017-04-10
CN201710226910.5A CN107688462A (zh) 2017-04-10 2017-04-10 软件升级方法及前端服务器

Publications (1)

Publication Number Publication Date
WO2018188336A1 true WO2018188336A1 (zh) 2018-10-18

Family

ID=61152366

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/111560 Ceased WO2018188336A1 (zh) 2017-04-10 2017-11-17 软件升级方法、前端服务器及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN107688462A (zh)
WO (1) WO2018188336A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115904459A (zh) * 2022-11-02 2023-04-04 杭州涂鸦信息技术有限公司 一种差分升级方法、嵌入式设备和可读存储介质
CN116088926B (zh) * 2023-01-10 2023-10-20 睿智合创(北京)科技有限公司 一种决策组件版本管理方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102281160A (zh) * 2011-09-15 2011-12-14 苏州阔地网络科技有限公司 一种功能自动升级的方法、系统及服务器
CN105468414A (zh) * 2015-11-30 2016-04-06 Tcl集团股份有限公司 一种智能终端升级方法及系统
CN106502747A (zh) * 2016-11-02 2017-03-15 武汉斗鱼网络科技有限公司 一种应用升级的方法及移动终端

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8205254B2 (en) * 2004-05-20 2012-06-19 International Business Machines Corporation System for controlling write access to an LDAP directory
CN105653262A (zh) * 2015-12-21 2016-06-08 Tcl集团股份有限公司 应用程序升级方法、装置及系统
CN106095455A (zh) * 2016-06-17 2016-11-09 北京小米移动软件有限公司 一种应用更新方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102281160A (zh) * 2011-09-15 2011-12-14 苏州阔地网络科技有限公司 一种功能自动升级的方法、系统及服务器
CN105468414A (zh) * 2015-11-30 2016-04-06 Tcl集团股份有限公司 一种智能终端升级方法及系统
CN106502747A (zh) * 2016-11-02 2017-03-15 武汉斗鱼网络科技有限公司 一种应用升级的方法及移动终端

Also Published As

Publication number Publication date
CN107688462A (zh) 2018-02-13

Similar Documents

Publication Publication Date Title
WO2018120429A1 (zh) 一种资源更新的方法、终端、计算机可读存储介质及资源更新设备
WO2019019378A1 (zh) 业务处理方法、装置、适配器及计算机可读存储介质
WO2019114262A1 (zh) 加载用户界面的方法、智能电视及计算机可读存储介质
WO2015035777A1 (zh) 一种移动终端的软件升级方法和系统
WO2019019374A1 (zh) 智能语音设备控制家电的方法、装置及系统
WO2018120457A1 (zh) 数据处理方法、装置、设备及计算机可读存储介质
WO2018233367A1 (zh) 立案方法、装置、终端和计算机可读存储介质
WO2018227887A1 (zh) 视频广告投放、生成方法、装置、服务器及可读存储介质
WO2019024336A1 (zh) 数据查询方法、装置及计算机可读存储介质
WO2018058919A1 (zh) 标识信息生成方法、装置、设备和计算机可读存储介质
WO2018082482A1 (zh) 一种网络共享方法、接入网络方法及系统
WO2019061612A1 (zh) 贷款产品推广方法、装置及计算机可读存储介质
WO2019019376A1 (zh) 业务流程管理方法、装置、设备及计算机可读存储介质
WO2017107388A1 (zh) Hdmi版本切换方法及显示设备
WO2019037395A1 (zh) 密钥管理方法、装置及可读存储介质
WO2019001110A1 (zh) 权限认证方法、系统、设备及计算机可读存储介质
WO2019000801A1 (zh) 数据同步方法、装置、设备及计算机可读存储介质
WO2018188196A1 (zh) 一种数据版本控制方法、数据版本控制器、设备及计算机可读存储介质
WO2019041851A1 (zh) 家电售后咨询方法、电子设备和计算机可读存储介质
WO2018233221A1 (zh) 多窗口声音输出方法、电视机以及计算机可读存储介质
WO2017084302A1 (zh) 显示终端开机播放视频的方法及显示终端
WO2019100531A1 (zh) 数字签名生成、验证方法及其设备和存储介质
WO2015180594A1 (en) Data distribution method and system and data receiving apparatus
WO2018149190A1 (zh) 组件调试方法、装置、设备和计算机可读存储介质
WO2019051866A1 (zh) 权益信息管理方法、装置、设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17905508

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

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

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

122 Ep: pct application non-entry in european phase

Ref document number: 17905508

Country of ref document: EP

Kind code of ref document: A1