Data processing method and device, equipment, storage medium and program product

Abstract

The invention relates to a data processing method and device, equipment, a storage medium and a program product. The method comprises the steps of defining application version information and uploading an updated installation package to a specified downloading address under the condition that at least a part of instances are upgraded at a system end; according to user classification requirements of different scenes, an application version upgrading rule is configured; determining a target user group according to the application version upgrading rule; under the condition that the target user group logs in the system, acquiring a pre-defined configuration record of an application version upgrading rule from a data storage system; and determining an upgrading strategy of the client according to the configuration record of the application version upgrading rule. Therefore, the upgrading strategy of the client can be determined according to the configuration record of the application version upgrading rule, so that when a system upgrading problem occurs, the service can be quickly rolled back and recovered, the normal use of the application is ensured, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] Software application systems require continuous iteration and updating. Every system upgrade will more or less affect the use of the system, especially when it comes to upgrading the client used by users. If there are defects or vulnerabilities, it will not only affect the normal operation of the company's business, but may even cause user complaints.

[0003] Traditionally, two approaches are used to perform system upgrades. First, after the system upgrade, R&D personnel monitor the system's operation in the background for a period of time. If any system errors occur, the system is immediately rolled back to the previous version. Second, multiple instances are deployed in the system, and traffic diversion rules are set to allow a small portion of user traffic to enter the upgraded system to verify the correctness of the new system. If any system errors occur, all user traffic is immediately cut back to the original system.

[0004] However, the first method mentioned above has a wide impact range. If a problem occurs, all users will be affected. Although the second method mentioned above reduces the scope of impact to a certain extent, it can only be controlled by traffic ratio, and it is still impossible to clearly identify the affected user groups. Summary of the Invention

[0005] Based on this, it is necessary to provide a data processing method, device, computer equipment, computer-readable storage medium and computer program product that can make the impact scope of batch upgrades clear and controllable, and when system upgrade problems occur, can quickly roll back and restore services, ensure the normal use of applications, and improve user experience.

[0006] In a first aspect, the present application provides a data processing method, the method comprising:

[0007] When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address;

[0008] Configure application version upgrade rules based on user classification requirements in different scenarios;

[0009] Determine the target user group based on the application version upgrade rules;

[0010] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system;

[0011] Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0012] In one embodiment, the user classification requirement includes at least one of: organization, merchant, channel number, region, user level, registration time, login time, and user account;

[0013] The information in the version upgrade rule includes at least one of: application ID, application version number, organization, merchant, channel number, region, user level, registration time, login time, user account, whether client upgrade is involved, and update identifier.

[0014] In one embodiment, when the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system includes:

[0015] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from the data storage system according to the application ID;

[0016] If no configuration record exists, no upgrade is required.

[0017] In one embodiment, determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes:

[0018] If the configuration record of the application version upgrade rule does not belong to a full update, determining whether user information of the target user group matches the application version upgrade rule;

[0019] If the application version upgrade rule is matched, then if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded;

[0020] If the application version upgrade rule is matched and there is no need to upgrade the client, the client calls the upgraded backend service by converting the built-in uniform resource locator URL;

[0021] If the application version upgrade rules are not matched, no upgrade is required.

[0022] In one embodiment, determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes:

[0023] In the case where the configuration record of the application version upgrade rule belongs to a full update, if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded.

[0024] In one embodiment, the method further comprises:

[0025] If there are no errors in the system upgrade, the remaining embodiments of the system will be upgraded, and the update flag will be set to full update;

[0026] If there is an error in the system upgrade, the version number of the latest configuration record of the application version upgrade rule is changed to the previous version number for the client that needs to be upgraded;

[0027] If there is an error in the system upgrade, for the client that does not need to be upgraded, the other rules except the application ID and application version number in the latest configuration record of the application version upgrade rule are cleared.

[0028] In a second aspect, the present application further provides a data processing device, comprising:

[0029] A definition module is used to define application version information and upload the updated installation package to a designated download address when at least part of the instance upgrade is completed on the system side;

[0030] The rule configuration module is used to configure application version upgrade rules based on user classification requirements in different scenarios;

[0031] A determination module, configured to determine a target user group based on the application version upgrade rule;

[0032] An acquisition module, configured to acquire a configuration record of a predefined application version upgrade rule from a data storage system when the target user group logs into the system;

[0033] The upgrade module is used to determine the client upgrade strategy according to the configuration record of the application version upgrade rule.

[0034] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0035] When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address;

[0036] Configure application version upgrade rules based on user classification requirements in different scenarios;

[0037] Determine the target user group based on the application version upgrade rules;

[0038] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system;

[0039] Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0040] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0041] When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address;

[0042] Configure application version upgrade rules based on user classification requirements in different scenarios;

[0043] Determine the target user group based on the application version upgrade rules;

[0044] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system;

[0045] Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0046] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0047] When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address;

[0048] Configure application version upgrade rules based on user classification requirements in different scenarios;

[0049] Determine the target user group based on the application version upgrade rules;

[0050] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system;

[0051] Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0052] The above-mentioned data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product define application version information and upload the updated installation package to a designated download address when at least a portion of the instance upgrade is completed on the system side; configure application version upgrade rules based on user classification requirements in different scenarios; and determine the target user group based on the application version upgrade rules. This allows for batch upgrades of application software, making the impact of the batch upgrades clear and controllable. When the target user group logs into the system, the configuration record of the pre-defined application version upgrade rules is obtained from the data storage system; and the client upgrade policy is determined based on the configuration record of the application version upgrade rules. Therefore, the client upgrade policy can be determined based on the configuration record of the application version upgrade rules, so that when a system upgrade problem occurs, the service can be quickly rolled back and restored to ensure normal use of the application and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0054] Figure 1 A diagram of an application environment of a data processing method in one embodiment;

[0055] Figure 2 1 is a flow chart of a data processing method in one embodiment;

[0056] Figure 3 is a flow chart of a data processing method in another embodiment;

[0057] Figure 4 is a structural block diagram of a data processing device in one embodiment;

[0058] Figure 5 is a structural block diagram of a data processing device in another embodiment;

[0059] Figure 6 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0061] The data processing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store data that server 104 needs to process. The data storage system can be integrated with server 104, or located in the cloud or on another network server. After completing at least a portion of the instance upgrade on the system side, server 104 defines application version information and uploads the updated installation package to a designated download address. Application version upgrade rules are configured based on user classification requirements in different scenarios. Target user groups are determined based on these application version upgrade rules. When these target user groups log in to the system through a client, the configuration record of the predefined application version upgrade rules is retrieved from the data storage system. Based on the configuration record of the application version upgrade rules, an upgrade policy for the client (which can be installed on terminal 102) is determined. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart car devices, projectors, etc. Portable wearable devices can include smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device may be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0062] In an exemplary embodiment, Figure 2 As shown, a data processing method is provided, which is applied to Figure 1 The server in FIG. 1 is taken as an example to illustrate the method, including the following steps 201 to 205. Among them:

[0063] Step 201 : When the system completes the upgrade of at least a portion of the instances, the application version information is defined, and the updated installation package is uploaded to a designated download address.

[0064] In this embodiment, the application version definition includes the application ID, application version number, update content, update address, and status. The application ID is the unique identifier of the software application within the company and is determined based on the system number in the company's software asset information. The application version number is the serial number of the application after the upgrade, which is consistent with the client installation package version number and increases with each release. The update content is a brief description of the application upgrade information. The update address is the download address of the client installation package. The status (valid / invalid) is used to determine whether the record is valid.

[0065] Optionally, when it comes to client upgrades, you first need to define the application version information after the system upgrade is completed, and upload the update package to the designated download address.

[0066] Step 202: Configure application version upgrade rules based on user classification requirements in different scenarios.

[0067] Optionally, the user classification requirement includes at least one of: organization, merchant, channel number, region, user level, registration time, login time, and user account.

[0068] Optionally, the information in the version upgrade rule includes at least one of: application ID, application version number, organization, merchant, channel number, region, user level, registration time, login time, user account, whether client upgrade is involved, and update identifier. Among them, the application ID is the unique identifier of the software application within the company, determined based on the system number in the company's software asset information. The application version number is the serial number after the application upgrade, which is consistent with the client installation package version number and increases with each release. The organization is the internal organization number assigned to the user. The merchant is the merchant number corresponding to the user. The channel number refers to APP, H5, WeChat public account, etc. The region refers to the province, city, and district where the user's IP is located. The user level refers to the level obtained by the user in the company's business. The registration time refers to the time range when the user registered the application software. The login time refers to the time range when the user most recently logged into the software. The user account refers to the user's login account in the system. Whether client upgrade is involved (yes / no) is used to determine whether the client needs to be upgraded. Update flags are divided into partial update and full update. When configuring a full update, conditions such as the organization, merchant, channel number, region, user level, registration time, login time, and user account are not considered.

[0069] For example, eight dimensional system upgrade processing rules can be provided on the system's public configuration platform based on the software system's application user scenarios. These include: organization, merchant, channel number, region, user level, registration time, login time, and user account. These eight rules cover user classification needs in various scenarios, and thus the target user group (i.e., users of the application) after the system upgrade can be determined based on these rules.

[0070] It should be understood that in this embodiment, system operation and maintenance personnel can fill in the rule content and combination at any time according to actual needs, without the need for system modification, and the rule will take effect in real time.

[0071] Step 203: Determine the target user group according to the application version upgrade rule.

[0072] In this embodiment, the target user group is determined by the information in the version upgrade rule. For example, the user ID that may need to upgrade the client is locked based on the organization, merchant, channel number, region, user level, registration time, login time, and user account.

[0073] Step 204 : When the target user group logs into the system, a configuration record of a predefined application version upgrade rule is obtained from the data storage system.

[0074] In this embodiment, each time the system is upgraded, the operation and maintenance personnel will collect and register the data into the data storage system through the server management interface. Therefore, the configuration record of the predefined application version upgrade rule can be obtained from the data storage system.

[0075] Exemplarily, when the target user group logs into the system, a configuration record of a predefined application version upgrade rule is obtained from the data storage system according to the application ID; if no configuration record exists, no upgrade is required.

[0076] Step 205: Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0077] For example, when there is a configuration record of an application version upgrade rule, it can be divided into the following two cases according to the type of the configuration record of the application version upgrade rule:

[0078] Case 1: When the configuration record of the application version upgrade rule does not belong to a full update, determine whether the user information of the target user group matches the application version upgrade rule; if it matches the application version upgrade rule, then if the client needs to be upgraded and the user version number is inconsistent with the configured version number, upgrade the client; if it matches the application version upgrade rule and there is no need to upgrade the client, the client calls the upgraded backend service by converting the built-in uniform resource locator URL; if it does not match the application version upgrade rule, no upgrade is required.

[0079] Case 2: When the configuration record of the application version upgrade rule belongs to a full update, if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded.

[0080] For example, the system's backend service first upgrades some instances, retaining others at the original version. Traffic diversion is controlled via a designated URL. For client upgrades, the update package is uploaded to a designated download address. (For example, Url_v1 corresponds to accessing the backend service before the upgrade, while Url_v2 corresponds to accessing the backend service after the upgrade. The client's built-in default URL is Url_v1 before the upgrade and Url_v2 after the upgrade.) Next, after the user logs in to the system, they obtain the application ID, application version number, and information about the user's organization, merchant, channel number, region, user level, registration time, login time, and user account (which may not be present). Based on the application ID, the pre-defined version upgrade rule configuration in the data storage system is retrieved, along with the latest configuration record for the application. If no record exists, no update is required, and the original system continues (client Url_v1 --> server Url_v1).

[0081] Optionally, if a configuration record for the application upgrade rule exists, the system first determines whether a full update is required. If not, the system matches the login user's application version number, organization, merchant, channel ID, region, user level, registration time, login time, and user account, obtained in the previous step, against the application upgrade rule. If a match is found, the system then determines whether a client upgrade is required. If a client upgrade is required, the system checks whether the user version number matches the configured version number. If not, the system forces the download of the corresponding installation package for the upgrade, and uses the upgraded backend service (client Url_v2 --> server Url_v2). If no match is found, the system continues to use the original version system (client Url_v1 --> server Url_v1).

[0082] Optionally, if there is an application upgrade rule configuration record and the rule is matched based on the logged-in user information, but the client does not need to be upgraded, the user client needs to convert the built-in URL when calling the backend service and instead call the upgraded backend service (client Url_v1-->Url_v2-->server Url_v2).

[0083] In the above data processing method, by completing the upgrade of at least part of the instances on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address; the application version upgrade rules are configured according to the user classification requirements of different scenarios; the target user group is determined according to the application version upgrade rules; thereby, the application software can be upgraded in batches, making the impact range of the batch upgrade clear and controllable. By obtaining the configuration record of the pre-defined application version upgrade rules from the data storage system when the target user group logs into the system; the client upgrade policy is determined according to the configuration record of the application version upgrade rules. Therefore, the client upgrade policy can be determined according to the configuration record of the application version upgrade rules, so that when a system upgrade problem occurs, the service can be quickly rolled back and restored to ensure the normal use of the application and improve the user experience.

[0084] In another exemplary embodiment, Figure 3 As shown, a data processing method is provided, which is applied to Figure 1 The server in FIG. 1 is taken as an example to illustrate the method, including the following steps 301 to 308. Among them:

[0085] Step 301 : When the system completes the upgrade of at least a portion of the instances, the application version information is defined, and the updated installation package is uploaded to a designated download address.

[0086] Step 302: Configure application version upgrade rules based on user classification requirements in different scenarios.

[0087] Step 303: Determine the target user group according to the application version upgrade rule.

[0088] Step 304 : When the target user group logs into the system, a configuration record of a predefined application version upgrade rule is obtained from the data storage system.

[0089] Step 305: Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0090] For the specific implementation process and technical effects of steps 301 to 305 in this embodiment, please refer to Figure 2 The descriptions of steps 201 to 205 in the illustrated method embodiment are not repeated here.

[0091] Step 306: If there is no error in the system upgrade, the remaining embodiments of the system are upgraded, and the update flag is set to full update.

[0092] In this embodiment, after all system upgrades are successful, all remaining instances of the system backend service are upgraded, and the update flag is set to full update, and all users are upgraded (client Url_v2-->server Url_v2).

[0093] Step 307: If there is an error in the system upgrade, the version number of the latest configuration record of the application version upgrade rule is changed to the previous version number for the client that needs to be upgraded.

[0094] In this embodiment, when an error occurs during the upgrade and involves a client update, the version number of the latest record in the application upgrade rule configuration is changed back to the previous version.

[0095] Step 308: If there is an error in the system upgrade, for the client that does not need to be upgraded, the other rules except the application ID and application version number in the latest configuration record of the application version upgrade rule are cleared.

[0096] In this embodiment, when an error occurs during the upgrade and does not involve client updates, the system can be restored by clearing all rules except the application ID and application version number in the latest record in the configuration.

[0097] This embodiment can perform adaptive processing according to whether there are errors in the system upgrade. If there are no errors in the system upgrade, the remaining system embodiments will be upgraded. If there are errors in the system upgrade, separate processing can be performed based on whether the client needs to be upgraded. This solves the problem of batch upgrades of C / S architecture application software, clarifies the scope of impact when errors occur on the system side, and enables rapid rollback and recovery of services when upgrade errors occur, ensuring normal use by users.

[0098] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0099] Based on the same inventive concept, the present application also provides a data processing device for implementing the aforementioned data processing method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations in one or more data processing device embodiments provided below can be found in the above-mentioned limitations on the data processing method and will not be repeated here.

[0100] In an exemplary embodiment, Figure 4 As shown, a data processing device is provided, including: a definition module 401, a rule configuration module 402, a determination module 403, an acquisition module 404 and an upgrade module 405, wherein:

[0101] A definition module 401 is used to define application version information and upload the updated installation package to a designated download address when at least a portion of the instance upgrade is completed on the system side;

[0102] A rule configuration module 402 is used to configure application version upgrade rules based on user classification requirements in different scenarios;

[0103] Determination module 403, for determining a target user group according to the application version upgrade rule;

[0104] An acquisition module 404 is configured to acquire a configuration record of a predefined application version upgrade rule from a data storage system when the target user group logs into the system;

[0105] The upgrade module 405 is configured to determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0106] Exemplarily, the user classification requirement includes at least one of: organization, merchant, channel number, region, user level, registration time, login time, and user account;

[0107] The information in the version upgrade rule includes at least one of: application ID, application version number, organization, merchant, channel number, region, user level, registration time, login time, user account, whether client upgrade is involved, and update identifier.

[0108] Exemplarily, the acquisition module 404 is specifically configured to acquire a configuration record of a predefined application version upgrade rule from the data storage system according to the application ID when the target user group logs into the system; if no configuration record exists, no upgrade is required.

[0109] Exemplarily, the upgrade module 405 is specifically used to determine whether the user information of the target user group matches the application version upgrade rule when the configuration record of the application version upgrade rule does not belong to a full update; if it matches the application version upgrade rule, then if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded; if it matches the application version upgrade rule and there is no need to upgrade the client, the client calls the upgraded backend service by converting the built-in uniform resource locator URL; if it does not match the application version upgrade rule, no upgrade is required.

[0110] Exemplarily, the upgrade module 405 is specifically configured to upgrade the client when the configuration record of the application version upgrade rule belongs to a full update and the client needs to be upgraded and the user version number is inconsistent with the configured version number.

[0111] In this embodiment, the application version information is defined and the updated installation package is uploaded to the designated download address after at least a portion of the instance upgrade is completed on the system side; application version upgrade rules are configured according to user classification requirements in different scenarios; and the target user group is determined based on the application version upgrade rules; thereby, batch upgrades of the application software can be implemented, making the impact of the batch upgrades clear and controllable. When the target user group logs into the system, the configuration record of the pre-defined application version upgrade rules is obtained from the data storage system; and the client upgrade policy is determined based on the configuration record of the application version upgrade rules. Thus, the client upgrade policy can be determined based on the configuration record of the application version upgrade rules, so that when a system upgrade problem occurs, the service can be quickly rolled back and restored to ensure the normal use of the application and improve the user experience.

[0112] In another exemplary embodiment, Figure 5 As shown, a data processing device is provided. Figure 4 Based on the device shown in FIG. 4 , the device may further include: an update module 406

[0113] The flag update module 406 is configured to upgrade the remaining embodiments of the system side and set the update flag to a full update if there are no errors in the system side upgrade;

[0114] The version change module 407 is configured to change the version number of the latest configuration record of the application version upgrade rule to the previous version number for the client that needs to be upgraded if there is an error in the system upgrade;

[0115] The rule clearing module 408 is used to clear the rules other than the application ID and application version number in the latest configuration record of the application version upgrade rule for the client that does not need to be upgraded if there is an error in the system upgrade.

[0116] This embodiment can perform adaptive processing according to whether there are errors in the system upgrade. If there are no errors in the system upgrade, the remaining system embodiments will be upgraded. If there are errors in the system upgrade, separate processing can be performed based on whether the client needs to be upgraded. This solves the problem of batch upgrades of C / S architecture application software, clarifies the scope of impact when errors occur on the system side, and enables rapid rollback and recovery of services when upgrade errors occur, ensuring normal use by users.

[0117] Each module in the above-mentioned data processing device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0118] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 6 As shown. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via wired or wireless means, and the wireless means can be implemented via Wi-Fi, a mobile cellular network, near-field communication (NFC), or other technologies. When executed by the processor, the computer program implements a data processing method. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0119] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0120] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0121] When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address;

[0122] Configure application version upgrade rules based on user classification requirements in different scenarios;

[0123] Determine the target user group based on the application version upgrade rules;

[0124] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system;

[0125] Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

[0126] In one embodiment, the user classification requirement includes at least one of: organization, merchant, channel number, region, user level, registration time, login time, and user account;

[0127] The information in the version upgrade rule includes at least one of: application ID, application version number, organization, merchant, channel number, region, user level, registration time, login time, user account, whether client upgrade is involved, and update identifier.

[0128] In one embodiment, when the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system includes:

[0129] When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from the data storage system according to the application ID;

[0130] If no configuration record exists, no upgrade is required.

[0131] In one embodiment, determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes:

[0132] If the configuration record of the application version upgrade rule does not belong to a full update, determining whether user information of the target user group matches the application version upgrade rule;

[0133] If the application version upgrade rule is matched, then if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded;

[0134] If the application version upgrade rule is matched and there is no need to upgrade the client, the client calls the upgraded backend service by converting the built-in uniform resource locator URL;

[0135] If the application version upgrade rules are not matched, no upgrade is required.

[0136] In one embodiment, determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes:

[0137] In the case where the configuration record of the application version upgrade rule belongs to a full update, if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded.

[0138] In one embodiment, the method further comprises:

[0139] If there are no errors in the system upgrade, the remaining embodiments of the system will be upgraded, and the update flag will be set to full update;

[0140] If there is an error in the system upgrade, the version number of the latest configuration record of the application version upgrade rule is changed to the previous version number for the client that needs to be upgraded;

[0141] If there is an error in the system upgrade, for the client that does not need to be upgraded, the other rules except the application ID and application version number in the latest configuration record of the application version upgrade rule are cleared.

[0142] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0143] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0144] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0145] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0146] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0147] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A data processing method, characterized in that: The method comprises: When at least some instances have been upgraded on the system side, the application version information is defined and the updated installation package is uploaded to the designated download address; Configure application version upgrade rules based on user classification requirements in different scenarios; Determine the target user group based on the application version upgrade rules; When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from a data storage system; Determine the client upgrade strategy based on the configuration record of the application version upgrade rule.

2. The method according to claim 1, characterized in that The user classification requirements include: at least one of: organization, merchant, channel number, region, user level, registration time, login time, and user account; The information in the version upgrade rule includes at least one of: application ID, application version number, organization, merchant, channel number, region, user level, registration time, login time, user account, whether client upgrade is involved, and update identifier.

3. The method according to claim 1, characterized in that When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from the data storage system includes: When the target user group logs into the system, obtaining a configuration record of a predefined application version upgrade rule from the data storage system according to the application ID; If no configuration record exists, no upgrade is required.

4. The method according to claim 1, wherein The step of determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes: If the configuration record of the application version upgrade rule does not belong to a full update, determining whether user information of the target user group matches the application version upgrade rule; If the application version upgrade rule is matched, then if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded; If the application version upgrade rule is matched and there is no need to upgrade the client, the client calls the upgraded backend service by converting the built-in uniform resource locator URL; If the application version upgrade rules are not matched, no upgrade is required.

5. The method according to claim 1, wherein The step of determining the client upgrade strategy based on the configuration record of the application version upgrade rule includes: In the case where the configuration record of the application version upgrade rule belongs to a full update, if the client needs to be upgraded and the user version number is inconsistent with the configured version number, the client is upgraded.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: If there are no errors in the system upgrade, the remaining embodiments of the system will be upgraded, and the update flag will be set to full update; If there is an error in the system upgrade, the version number of the latest configuration record of the application version upgrade rule is changed to the previous version number for the client that needs to be upgraded; If there is an error in the system upgrade, for the client that does not need to be upgraded, the other rules except the application ID and application version number in the latest configuration record of the application version upgrade rule are cleared.

7. A data processing device, characterized in that: The device comprises: A definition module is used to define application version information and upload the updated installation package to a designated download address when at least part of the instance upgrade is completed on the system side; The rule configuration module is used to configure application version upgrade rules based on user classification requirements in different scenarios; A determination module, configured to determine a target user group based on the application version upgrade rule; An acquisition module, configured to acquire a configuration record of a predefined application version upgrade rule from a data storage system when the target user group logs into the system; The upgrade module is used to determine the client upgrade strategy according to the configuration record of the application version upgrade rule.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images