Grayscale publishing method and related equipment for client application function hot update files

By matching customer tags and condition tags in client applications and dynamically updating functional files, the problems of waste of traffic and confusing permissions in grayscale release are solved, and more flexible and efficient application updates are achieved, improving user experience and system stability are improved. .

CN112445510BActive Publication Date: 2024-11-12CHINA LIFE INSURANCE CO LTD
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN202011379594.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-11-30
Publication Date
2024-11-12
Estimated Expiration
2040-11-30

AI Technical Summary

Technical Problem

The existing grayscale publishing method leads to waste of traffic and confusing permission control when users update applications, and cannot conduct targeted hot updates based on user information, affecting user experience and system stability.

Method used

By obtaining and matching the client tags and conditional tags on the server, dynamically update the application functions, downloading and updating only the required feature files, avoiding full updates, and optimizing permission management.

Benefits of technology

It achieves a more flexible and smooth grayscale release effect, saves user traffic, avoids permission setting issues, and improves the flexibility and user experience of application updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112445510B_ABST
    Figure CN112445510B_ABST
Patent Text Reader

Abstract

One or more embodiments of this specification provide a method for grayscale publishing of a client application function hot update file and related equipment. The method includes: in response to an application on a client being started, the client obtains a client tag pre-stored locally, and obtains a condition tag associated with the function hot update file of the application from a server that is communicatively connected to the client; the client determines whether the client tag matches the condition tag; in response to determining that the client tag matches the condition tag, the client obtains the function hot update file from the server, and uses the function hot update file to update the application. This method and related equipment can push function hot update files that are in line with the user's own usage habits to the user, rather than downloading the update file in full, and will not affect the customer's permission control.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of application development, and more particularly to a grayscale publishing method for hot updating of client application functions and related equipment. Background Art

[0002] With the continuous development of mobile Internet, mobile application developers need to design a variety of different pages and interactive styles to put online functions to verify user preferences and choose the best implementation method. This method of verifying the degree of user acceptance of different implementation methods within a certain range is called grayscale release.

[0003] When designing the page UI and interaction process of a new function, mobile application developers may not always be able to meet the best requirements of users. In addition, before a new function is officially launched, it is necessary to find some users to try it out in advance to verify the usability of the function and the degree of user acceptance.

[0004] Existing technologies generally use permission control methods, that is, all functions of all styles are included in all users' applications. The program will display different functions to users based on their permissions to achieve the effect of grayscale release. The main problems of this implementation are:

[0005] 1. It will waste the traffic of users updating applications. On the one hand, the system cannot selectively update only the pages or functions that the grayscale users need to see according to which type of grayscale user they are, and can only update all the content; on the other hand, even if the user is not the target user of the grayscale release, he or she also needs to update the client in full.

[0006] 2. Permission control is prone to confusion. Based on this implementation, after the grayscale release is completed, all users need to be switched to the same permission. If other functions also rely on this permission, it will cause problems for other functions. Summary of the invention

[0007] In view of this, the purpose of one or more embodiments of this specification is to propose a grayscale release method and related equipment for client application function hot update files to solve the problem of being unable to perform corresponding hot updates based on user information.

[0008] Based on the above purpose, one or more embodiments of this specification provide a method for grayscale publishing of a client application function hot update file, including:

[0009] In response to the application on the client being started, the client obtains the client tag pre-stored locally, and obtains the condition tag associated with the function hot update file of the application from the server connected to the client in communication;

[0010] The client determines whether the client tag matches the condition tag;

[0011] In response to determining that the customer tag matches the condition tag, the client obtains the function hot update file from the server and updates the application with the function hot update file.

[0012] Based on the same invention purpose, one or more embodiments of this specification also provide a device for grayscale publishing of hot update files of client application functions, which can be divided into the following modules according to functions, including:

[0013] a tag acquisition module, in response to an application on a client being started, the client acquires a pre-stored local customer tag, and acquires a conditional tag associated with a function hot update file of the application from a server connected to the client in communication;

[0014] a tag matching module, wherein the client determines whether the customer tag matches the condition tag;

[0015] The hot update module, in response to determining that the customer tag matches the condition tag, the client obtains the function hot update file from the server and uses the function hot update file to update the application.

[0016] Based on the same invention purpose, one or more embodiments of the present specification also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, a grayscale publishing method for hot update files of client application functions is implemented.

[0017] Based on the same invention purpose, one or more embodiments of the present specification also provide a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute a grayscale release method for hot update files of client application functions.

[0018] From the above description, it can be seen that a grayscale publishing method and related equipment for hot update files of client application functions provided in one or more embodiments of this specification can provide a more flexible and smoother grayscale publishing effect and save user traffic. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only one or more embodiments of the present specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 A flowchart of a method for grayscale publishing of a client application function hot update file provided by one or more embodiments of this specification;

[0021] Figure 2 A schematic diagram of a process for generating a customer label provided for one or more embodiments of this specification;

[0022] Figure 3 A flowchart of a function hot update file upload provided in one or more embodiments of this specification;

[0023] Figure 4 A flowchart of application hot update provided for one or more embodiments of this specification;

[0024] Figure 5 A schematic diagram of the structure of a device for grayscale publishing of hot update files of client application functions provided by one or more embodiments of this specification;

[0025] Figure 6 A schematic diagram of the structure of an electronic device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0027] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in one or more embodiments of this specification should be understood by people with ordinary skills in the field to which this disclosure belongs. The words "first", "second" and similar words used in one or more embodiments of this specification do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprises" and similar words mean that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, without excluding other elements or objects.

[0028] As described in the background technology, in the existing grayscale publishing method, all functions of all styles are included in the applications of all users, and different functions will be displayed according to the user's permissions to achieve the effect of grayscale publishing. However, since the system cannot selectively update only the pages or functions that such grayscale users need to see according to which type of grayscale user the user is, all content can only be updated during the application update process; on the other hand, even if the user is not the target user of the grayscale release, the application needs to be fully updated. Moreover, the existing grayscale publishing method also faces the problem of easy confusion in permission control: based on this grayscale publishing method, after the grayscale release is completed, all users need to be switched to the same permission. If there are other functions that rely on this permission, it will cause problems with other functions.

[0029] One or more embodiments of this specification propose a grayscale release method and related equipment for client application function hot update files, which are used to solve the problems faced by existing grayscale release methods. First, the application collects user information to generate a customer tag and stores it on the client; the server configures a conditional tag that can match the customer tag for the function hot update file; when the user starts the application, the application obtains the conditional tag of the function hot update file from the server and matches it with the customer tag. If the match is successful, the corresponding function hot update file is downloaded and decompressed, and the decompressed file overwrites the original file to complete the hot update; otherwise, the application is started normally.

[0030] One or more embodiments of this specification propose a method for grayscale publishing of hot update files of client application functions, referring to Figure 1 , the steps are as follows:

[0031] Step S101: In response to an application on a client being started, the client obtains a client tag pre-stored locally, and obtains a condition tag associated with a function hot update file of the application from a server connected to the client.

[0032] In this step, the collected user information is uploaded to the server, and the user information is processed using technologies including MapReduce (parallel processing computing model), Spark (computing engine), HDFS (distributed file system), Hive (data warehouse tool), and HBase, and the generated customer tags are stored in the application client. The storage technologies used by the Android version and the iOS version are different. The Android version uses SharedPreferrences for storage, and the iOS version uses NSUserDefaults for storage.

[0033] Step S102: The client determines whether the customer tag matches the condition tag.

[0034] Step S103: In response to determining that the customer tag matches the condition tag, the client obtains the function hot update file from the server and uses the function hot update file to update the application.

[0035] In this step, Webview hot update technology is used. Web pages can be placed on a remote server or on the local mobile phone. The Web page is developed according to the H5 standard and the corresponding functions are implemented. It is placed in the local storage of the mobile phone, and then the local H5 standard Web page files are opened with Webview to realize the mobile application function page. At the same time, the mobile application can download the H5 page compression package on the server and dynamically overwrite the local H5 page file. After the overwriting is completed, the page opened by Webview again is the updated page. This is how the hot update of the function page is realized.

[0036] The technical solution provided in this specification is described below in conjunction with specific embodiments.

[0037] refer to Figure 2 One or more embodiments of this specification provide a method for generating a customer tag, the steps of which are as follows:

[0038] Step S201: User registration.

[0039] In this step, the user fills in a verifiable mobile phone number and password to register the app.

[0040] Step S202: Obtain user equipment information.

[0041] In this step, the system will collect and store the user's registration time, IP address, geographic location information, etc., and also collect the brand, model, operating system and device number of the mobile device where the application is located, and store them in the database.

[0042] Step S203: User real-name authentication.

[0043] In this step, the name, gender, ID type, ID number, date of birth, etc. used by the user for real-name authentication are stored.

[0044] Step S204: Obtain user insurance policy information.

[0045] In this step, business-related data is pulled based on real-name data. For example, in insurance applications, the customer's insurance policy information can be queried based on real-name authentication information for subsequent label calculation.

[0046] Step S205: Initialize the customer tag.

[0047] In this step, the registration ID, registration time, IP address, geographic location, brand, model, operating system, device number, name, gender, ID type, ID number, date of birth and business information such as insurance policy information of the mobile phone in the previous step are processed to generate data labels.

[0048] First, data cleaning is performed to convert the above user information into data to be processed in a standard format; then the operation staff formulates customer label generation rules and the developers write programs to implement the rules; finally, the program completed by the developers is used to process the data to be processed to obtain customer labels.

[0049] Step S206: The client stores the customer tag.

[0050] refer to Figure 3 One or more embodiments of this specification provide a method for uploading a function hot update file, and the steps are as follows:

[0051] Step S301: Generate a function hot update file.

[0052] In this step, the files including HTML (Hypertext Markup Language) files based on the H5 standard, js files, css (Cascading Style Sheets) files, images and configuration files required for the function page are organized according to the preset directory structure and packaged to generate function hot update files.

[0053] Step S302: Select a condition tag for a function hot update file.

[0054] In this step, the function hot update file is matched with the conditional tag, and a specific version number is set.

[0055] Step S303: Upload the function hot update file to the server.

[0056] In this step, the function hot update file is uploaded and stored on the server in the format of " / version number / compressed package".

[0057] refer to Figure 4 One or more embodiments of this specification provide an application hot update method, the steps of which are as follows:

[0058] Step S401: The user opens the application.

[0059] Step S402: The application obtains the customer tag of the local user.

[0060] Step S403: Request the background interface to obtain the conditional tag.

[0061] Step S404: Check whether the tags match.

[0062] In this step, if the customer tag matches the condition tag, the process goes to step S405 to continue the subsequent operation; otherwise, the process goes to step S407 to open the application normally.

[0063] An example of the tag matching process is as follows: after the user logs in to the application, the generated tags are "Gender: Female, Region: Beijing, Mobile Operating System: Android, Mobile Brand: Huawei, Whether there is a long-term insurance policy: Yes".

[0064] If the corresponding tag in the hot update file is "Gender: Female, Long-term Insurance Policy: Yes", the values ​​of "Gender" and "Long-term Insurance Policy" in the user's tags are consistent with the values ​​of "Gender" and "Long-term Insurance Policy" in the hot update version, and the tags are considered to match.

[0065] If the corresponding label in the hot update version is "Gender: Female, Long-term Insurance Policy: No", then the value of the user's "Long-term Insurance Policy" field is inconsistent with the requirement in the hot update version, and it is considered a mismatch.

[0066] If the corresponding tag in the hot update version is "Region: Beijing or Tianjin, Whether there is a long-term insurance policy: Yes", then the value of the user's "Whether there is a long-term insurance policy" field is consistent with the requirements in the hot update version, and the value of the "Region" field is within the range required by the hot update version's tag field "Region", then it is considered a match.

[0067] That is, the tags are considered matched only when the value of the tag field stored by the user on the client is exactly the same as the value of the field required by the conditional tag in the hot update version, or the field value of the user tag is within the range of the field value required by the conditional tag in the hot update version. Otherwise, they are considered mismatched.

[0068] Step S405: Request the grayscale hot update interface to obtain the function hot update file.

[0069] Step S406: decompress the function hot update file and overwrite the original file.

[0070] Step S407, enter the application.

[0071] The grayscale release method of client application function hot update files presented in one or more embodiments of the present specification can recommend function hot update files that meet user needs based on the application user's personal information and business information to update the application, thereby avoiding the problem of traditional application update methods that require customers to download the update files in full and that will affect the user's permission settings; it can make grayscale release more flexible and smooth, and save user traffic.

[0072] It should be noted that the method of one or more embodiments of this specification can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of one or more embodiments of this specification, and the multiple devices will interact with each other to complete the described method.

[0073] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0074] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, one or more embodiments of this specification also provide a grayscale publishing device for hot update files of client application functions.

[0075] refer to Figure 5 , the grayscale publishing device of the client application function hot update file includes:

[0076] The tag acquisition module 501, in response to the application on the client being started, the client acquires the client tag pre-stored locally, and acquires the conditional tag associated with the function hot update file of the application from the server connected to the client.

[0077] Tag matching module 502, the client determines whether the customer tag matches the condition tag.

[0078] The hot update module 503, in response to determining that the customer tag matches the condition tag, the client obtains the function hot update file from the server and uses the function hot update file to update the application.

[0079] For the convenience of description, the above devices are described in terms of functions divided into various modules. Of course, when implementing one or more embodiments of this specification, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0080] The device of the above embodiment is used to implement the grayscale publishing method of the corresponding client application function hot update file in the above embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0081] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, one or more embodiments of this specification also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the grayscale publishing method for the hot update file of the client application function described in any of the above embodiments is implemented.

[0082] Figure 6 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0083] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0084] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0085] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0086] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0087] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0088] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0089] The electronic device of the above embodiment is used to implement the grayscale publishing method of the corresponding client application function hot update file in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0090] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, one or more embodiments of the present specification also provide a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the grayscale release method of the client application function hot update file as described in any of the above embodiments.

[0091] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0092] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the grayscale release method of the client application function hot update file as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0093] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. In line with the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of different aspects of one or more embodiments of the present specification as described above, which are not provided in detail for the sake of simplicity.

[0094] In addition, to simplify the description and discussion, and in order not to obscure one or more embodiments of the present specification, known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device may be shown in the form of a block diagram so as to avoid obscuring one or more embodiments of the present specification, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which one or more embodiments of the present specification will be implemented (i.e., these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that one or more embodiments of the present specification may be implemented without these specific details or with variations in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0095] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0096] One or more embodiments of this specification are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of this specification should be included in the scope of protection of this disclosure.

Claims

1. A method for grayscale publishing of a client application function hot update file, comprising: In response to the application on the client being started, the client obtains a pre-stored client tag locally, and obtains a condition tag associated with a function hot update file of the application from a server connected to the client in communication, the function hot update file being generated by organizing and packaging files including HTML text, js files, css files, pictures and configuration files based on the H5 standard required for the function page according to a preset directory structure, and the function hot update file corresponds to the condition tag; The client determines whether the customer tag matches the condition tag, the condition tag is pre-configured by an administrator to the function hot update file and is associated with the function hot update file and uploaded to the server; In response to determining that the customer tag matches the condition tag, the client obtains the function hot update file from the server and updates the application with the function hot update file; The client determines whether the customer tag matches the condition tag, including: Determine whether the value of the first field in the customer tag is consistent with the preset value of the first field in the condition tag; and / or determining whether the value of the second field in the customer tag is within a range of preset values ​​of the second field in the condition tag; The customer tag is obtained by converting the user registration information, user device information, user real-name authentication information and user insurance policy information into the data to be processed in a standard format after data cleaning, formulating customer tag generation rules, and writing a program to implement the rules and process the data to be processed; Wherein, the function hot update file includes a function webpage hot update file; and the updating of the application using the function hot update file includes: updating the function webpage of the application using the function webpage hot update file through a hot update technology based on WebView; The functional webpage hot update file includes a hypertext markup language file HTML based on the H5 standard, a js file, a cascading style sheet file css, a picture and a configuration file; The client tag is generated by the server or the client based on the following information of the user of the client: User registration information, user device information, user real-name authentication information, and user insurance policy information; The step of updating the application using the functional hot update file comprises: Decompress the function hot update file; The decompressed function hot update file is used to overwrite the corresponding file for the application stored on the client.

2. A device for grayscale publishing of hot update files of client application functions, comprising: A tag acquisition module, for obtaining a pre-stored client tag locally in response to an application being started on a client, and obtaining a conditional tag associated with a function hot update file of the application from a server connected to the client in communication, wherein the function hot update file is generated by organizing and packaging files including HTML text, js files, css files, pictures and configuration files based on the H5 standard required for the function page according to a preset directory structure, and the function hot update file corresponds to the conditional tag; a tag matching module, used to determine whether the customer tag matches the condition tag, the condition tag is pre-configured by an administrator to the function hot update file, and is uploaded to the server in association with the function hot update file; a hot update module, configured to obtain the function hot update file from the server in response to the tag matching module determining that the customer tag matches the condition tag, and update the application with the function hot update file; The tag matching module is further used to determine whether the value of the first field in the customer tag is consistent with the preset value of the first field in the condition tag; and / or determine whether the value of the second field in the customer tag is within the range of the preset value of the second field in the condition tag; The customer tag is obtained by converting the user registration information, user device information, user real-name authentication information and user insurance policy information into the data to be processed in a standard format after data cleaning, formulating customer tag generation rules, and writing a program to implement the rules and process the data to be processed; Wherein, the function hot update file includes a function webpage hot update file; and the updating of the application using the function hot update file includes: updating the function webpage of the application using the function webpage hot update file through a hot update technology based on WebView; The functional webpage hot update file includes a hypertext markup language file HTML based on the H5 standard, a js file, a cascading style sheet file css, a picture and a configuration file; The client tag is generated by the server or the client based on the following information of the user of the client: User registration information, user device information, user real-name authentication information, and user insurance policy information; The step of updating the application using the functional hot update file comprises: Decompress the function hot update file; The decompressed function hot update file is used to overwrite the corresponding file for the application stored on the client.

3. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein: When the processor executes the computer program, the method according to claim 1 is implemented.

4. A non-transitory computer-readable storage medium having computer instructions stored thereon, wherein: When the computer instructions are executed by a computer, the computer is caused to implement the method according to claim 1 .

Citation Information

Patent Citations

  • Version updating method and device

    CN106648562A

  • Gray release method and gray release device

    CN106685687A

  • Application gray publishing method and device and computer readable storage medium

    CN108768875A

  • Hot updating method and device and computer storage medium

    CN109710287A

  • Gray release method and device and storage medium

    CN110597535A