CN113315824B - Application gray scale publishing method and device and application gray scale publishing system - Google Patents

Abstract

Embodiments of the present application provide a method and device for distributing gray levels of applications, and a system for distributing gray levels of applications, which relate to the technical field of computers. The method includes receiving traffic distribution rule data released in grayscale for the current application; obtaining the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application; calling the interface of the configuration management center to convert the traffic distribution rule data Send it to the gateway, so that the gateway can implement the gray-scale release of the current application according to the traffic distribution rules, and realize the gray-scale release of the new version of the traffic that can be precisely controlled, so as to solve the problem that related technologies may have when releasing online applications. Problems where user actions have a large impact.

Description

Applied grayscale release method, device and applied grayscale release system

technical field

The present application relates to the field of computer technology, and in particular, relates to an applied gray scale release method, device and applied gray scale release system.

Background technique

There are two existing application release methods. One is full rolling release, which can only release all online application instances at one time. After the release is completed, regression verification is performed on the new version. It has a great impact on user operations, and may also generate more dirty data; the other is batch release, which can complete the verification of the new version of the application by publishing a specified number of new version instances, but only through the new version container The ratio of the number of instances to the number of container instances of the old version is used to control the traffic of the new version of the application, which may also affect more users.

Contents of the invention

The purpose of the embodiments of the present application is to provide a grayscale release method and device for an application, and a grayscale release system for an application, so as to realize the grayscale release of new version traffic that can be precisely controlled, so as to solve the problems that may occur when the existing method publishes an online application. Problems where user actions have a large impact.

An embodiment of the present application provides a method for grayscale release of an application, which includes:

Receive grayscale published traffic distribution rule data for the current application;

Acquiring the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application;

Calling the interface of the configuration management center to send the traffic distribution rule data to the gateway, so that the gateway implements the gray release of the current application according to the traffic distribution rule.

In the above implementation process, the number of new version container instances is controlled through traffic distribution rule data, and the gray scale release of the new version traffic can be precisely controlled, so as to solve the problem that the existing method may have a great impact on user operations when publishing online applications The problem.

Further, the traffic distribution rule data includes grayscale container quantity and grayscale traffic ratio, and receiving grayscale published traffic distribution rule data for the current application includes:

Receive the number of grayscale containers sent by the user through the grayscale data configuration interface;

Modify the copy number attribute value that controls the number of application copies to control the number of grayscale application instances;

Adding a grayscale tag to the startup script of the grayscale application instance, so that the gateway can find the grayscale application instance through the grayscale tag;

Receive the grayscale traffic ratio sent by the user through the grayscale data configuration interface, so that the gateway sends the traffic corresponding to the grayscale traffic ratio to the corresponding grayscale application instance.

In the above implementation process, the number of grayscale application instances is controlled by the number of grayscale containers, and by adding grayscale tags, preparations are made for traffic allocation to grayscale application instances in subsequent gateways.

Further, before the step of obtaining the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application, the method further includes:

Receive the mapping relationship data between the gateway and the application sent by the gateway management interface through the gateway management service;

storing the mapping relationship data in a database.

In the above implementation process, the mapping relationship between the gateway and the application is stored in the MySQL database, and the traffic entry gateway corresponding to the application can be obtained later when the application is released.

Further, the calling configuration management center interface, and sending the traffic distribution rule data to the gateway include:

Generate a gray-scale traffic configuration data structure according to the traffic distribution rule data, the gray-scale traffic configuration data structure includes a gateway ID and a traffic ratio;

Call the interface of the configuration management center, and deliver the gateway ID and the corresponding traffic ratio to the corresponding gateway.

In the above implementation process, the gateway ID and the corresponding traffic ratio are sent to the corresponding gateway, so that the gateway can allocate traffic to the new version instance according to the traffic ratio.

Further, the gateway realizes the gray release of the current application according to the traffic distribution rule, including:

The gateway publishes and runs the application on a cloud host or a k8s container platform.

In the above implementation process, the application is run on a common cloud host, not in a container, so this method does not limit the publishing and running objects.

Further, the gateway controls routing for the proportion of gray traffic, including Spring Cloud Zuul gateway and/or Kong gateway.

In the above implementation process, as long as there is a gray-scale traffic ratio control route, it can be applied to this method.

The embodiment of the present application also provides an application gray scale release device, the device includes:

The receiving module is used to receive traffic distribution rule data published in gray scale for the current application;

A gateway obtaining module, configured to obtain the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application;

A delivery module, configured to call the interface of the configuration management center, and send the data of the traffic distribution rules to the gateway, so that the gateway can implement gray-scale release of the current application according to the traffic distribution rules.

In the above implementation process, through the grayscale release of the new version traffic with precise control, developers or testers can release the application online at any time during the day, because precise traffic control can be used to avoid the occurrence of problems when releasing the online application. Risks and losses caused by problems, and instead of the existing method, new applications can only be released online during low-peak traffic hours in the middle of the night to improve convenience.

The embodiment of the present application also provides an application gray scale release system, the system includes:

Gray scale data configuration interface, used to receive the traffic distribution rule data sent by the user, and send the traffic distribution rule data to the gateway management service;

The gateway management service is used to store the traffic distribution rule data in a database, and when the application is published, call the interface of the configuration management center to send the traffic distribution rule data based on the pre-stored mapping relationship data between the gateway and the application to the gateway corresponding to the current application;

The configuration management center is connected to a plurality of gateways, and is configured to issue traffic distribution rule data to the gateways, so that the gateways can realize the gray release of the current application according to the traffic distribution rules.

In the above implementation process, through the cooperation of grayscale data configuration interface, gateway management service, configuration management center and gateway, precise control of the traffic of the new version is realized when grayscale releases.

Further, the gateway is also used for sending the http test request to the new version instance after adding an application instance start tag in the request header of the http test request when performing a regression test on the new version instance.

In the above implementation process, the traffic is routed by percentage through the application instance startup tag in the gateway, and at the same time, specific routing is performed for the http test request with a specific header tag, and it is directly routed to the new version instance for effective regression testing.

The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to perform any of the above The grayscale publishing method of the application described in the item.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings that need to be used in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application, so It should not be regarded as a limitation on the scope, and those skilled in the art can also obtain other related drawings according to these drawings without creative work.

FIG. 1 is a flow chart of an applied gray scale publishing method provided by an embodiment of the present application;

FIG. 2 is a flow chart for modifying the traffic distribution ratio for gray release provided by the embodiment of the present application;

Fig. 3 is a structural block diagram of the grayscale release system provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of an interface for adjusting the number of grayscale containers provided by the embodiment of the present application;

Fig. 5 is a schematic diagram of the interface for adjusting the gray flow ratio provided by the embodiment of the present application;

FIG. 6 is a schematic diagram of flow ratio distribution provided by the embodiment of the present application;

FIG. 7 is a structural block diagram of a grayscale release device provided by an embodiment of the present application;

FIG. 8 is a specific structural block diagram of a grayscale distribution device provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a regression test provided in the embodiment of the present application.

icon:

100-receiving module; 101-container quantity receiving module; 102-modification module; 103-marking module; 104-flow ratio receiving module; 200-gateway acquisition module; 210-storage module; Generation module; 302-calling module; 11-gateway management service; 12-grayscale data configuration interface; 13-MySQL database; 14-configuration management center; 15-gateway; 16-gateway management interface.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that like numerals and letters denote similar items in the following figures, therefore, once an item is defined in one figure, it does not require further definition and explanation in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second" and the like are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

Please refer to FIG. 1 . FIG. 1 is a flow chart of an application grayscale publishing method provided by an embodiment of the present application. This method precisely controls the traffic of the new version to achieve the purpose of precise and controlled gray scale release.

This method can be based on the k8s (container orchestration management tool) container platform and combined with the Spring Cloud Gateway gateway to achieve precise controllability of the number of new version container instances. Among them, the Spring Cloud Gateway gateway is a gateway component in the springcloud microservice governance framework. Traffic requests are distributed and routed to each microservice. Of course, you can also use other types of grayscale traffic ratio control routing implementations, such as through Spring Cloud Zuul gateway or Kong gateway, and there is no limitation on the type of gateway.

The method specifically includes the following steps:

Step S100: receiving traffic distribution rule data released in grayscale for the current application;

Among them, the traffic allocation rule data includes the number of grayscale containers and the grayscale traffic ratio. As shown in Figure 2, the flow chart is modified for the traffic distribution ratio published by grayscale. This step can specifically include:

Step S101: receiving the number of grayscale containers sent by the user through the grayscale data configuration interface 12;

Step S102: Modify the copy number attribute value controlling the number of application copies to control the number of gray scale application instances;

Step S103: adding a grayscale mark in the startup script of the grayscale application instance, so that the gateway 15 can find the grayscale application instance through the grayscale mark;

Step S104: Receive the grayscale traffic ratio sent by the user through the grayscale data configuration interface 12, so that the gateway 15 sends the traffic corresponding to the grayscale traffic ratio to the corresponding grayscale application instance.

As shown in Figure 3, it is a structural block diagram of the grayscale distribution system, wherein the grayscale data configuration interface 12 can be the configuration interface of the multimedia distribution system (such as the Qingzhou CD distribution system), and when the application is released on it, the publishing process In , you can control the number of new version container instances, as well as the percentage of traffic reaching the new version container instances.

As shown in Figure 4, it is a schematic diagram of the interface for adjusting the number of gray scale containers. You can modify the number of grayscale containers on the operation interface. After modifying the number of grayscale containers on the operation interface, the bottom layer uses the k8s container management platform to modify the copy number attribute value of the deployment that controls the number of application copies, so as to control the number of grayscale application instances. Purpose.

For grayscale application instances, by adding startup parameters (marked as grayscale) in the startup script of grayscale application instances, such as: eureka.instance.metadataMap.version=grayTest, traffic distribution for subsequent gateway 15 to grayscale application instances Get ready, you can accurately find grayscale application instances that need to allocate traffic through grayscale tags.

As shown in Figure 5, it is a schematic diagram of the interface for adjusting the grayscale flow ratio, and the grayscale flow ratio can be modified on the operation interface. After modifying the grayscale traffic ratio on the operation interface, you can find the corresponding gateway 15 through the mapping relationship between the gateway 15 and the application, update the grayscale traffic distribution rules of the gateway 15 for the current application, and complete the precise allocation of traffic to grayscale container instances .

Step S200: Obtain the gateway 15 corresponding to the current application according to the preset mapping relationship data between the gateway 15 and the application;

Before this step, you also need:

Step S210: receiving the mapping relationship data between the gateway 15 and the application sent by the gateway management interface 16 through the gateway management service 11;

Step S211: storing the mapping relationship data in a database.

Since different applications may correspond to different gateways 15, it is necessary to maintain the mapping relationship between the gateway 15 and the application through the gateway management interface 16, such as the Qingzhou gateway management interface 16. Through the gateway management service 11 such as the Gateway AdminService service, the mapping relationship between the gateway 15 and the application is stored in the MySQL database 13, so that when the application is released later, the traffic entry gateway 15 corresponding to the application can be obtained.

Step S300: call the interface of the configuration management center 14, and send the data of the traffic distribution rule to the gateway 15, so that the gateway 15 realizes gray-scale publishing of the current application according to the traffic distribution rule.

This step can specifically include:

Step S301: Generate a grayscale traffic configuration data structure according to the traffic distribution rule data, and the grayscale traffic configuration data structure includes a gateway ID and a traffic ratio;

The grayscale traffic configuration data structure sent to the gateway 15 is as follows:

Step S302: call the interface of the configuration management center 14, and deliver the gateway ID and the corresponding traffic ratio to the corresponding gateway 15.

During the application publishing process, you can control the number of container instances of the new version and the percentage of traffic reaching the container instances of the new version.

Find the gateway 15 corresponding to the application by maintaining the updated relationship between the application and the gateway 15 above, and then call the new interface in the apollo configuration to update the grayscale traffic allocation rules for the application in the gateway 15, and complete the traffic targeting the grayscale container instance precise distribution.

As shown in Figure 6, it is a schematic diagram of traffic ratio distribution. When a user initiates an http request, the gateway 15 utilizes the mark (gray mark) of the gray scale application instance such as eureka. The three instances of the stable version are allocated to the new version instance, and the remaining 90% of the user traffic is evenly allocated to the three instances of the stable version, so as to achieve the purpose of precise control of the new version traffic, and solve the problem that the existing method may have a relatively large impact on user operations when releasing online applications. big impact issues.

In addition, in addition to the application running on the k8s container platform, as another implementation method, the application also runs on a common cloud host instead of running in a container. There is no restriction on the running subject of various microservice applications, so as to expand the The scope of use of the method.

The embodiment of the present application also provides an applied grayscale distribution device, which is applied to the above-mentioned applied grayscale distribution method, as shown in FIG. 7 , which is a structural block diagram of the grayscale distribution device. The device includes:

The receiving module 100 is configured to receive traffic distribution rule data released in gray scale for the current application;

A gateway acquisition module 200, configured to acquire the gateway 15 corresponding to the current application according to the preset mapping relationship data between the gateway 15 and the application;

The sending module 300 is configured to call the interface of the configuration management center 14, and send the data of the traffic distribution rule to the gateway 15, so that the gateway can implement the gray release of the current application according to the traffic distribution rule.

As shown in FIG. 8 , it is a specific structural block diagram of a grayscale release device, wherein the receiving module 100 includes:

The container quantity receiving module 101 is used to receive the grayscale container quantity sent by the user through the grayscale data configuration interface 12;

A modification module 102, configured to modify the copy number attribute value controlling the number of application copies, so as to control the number of grayscale application instances;

A tagging module 103, configured to add a grayscale tag to the startup script of the grayscale application instance, so that the gateway 15 can find the grayscale application instance through the grayscale tag;

The traffic ratio receiving module 104 receives the grayscale traffic ratio sent by the user through the grayscale data configuration interface 12, so that the gateway 15 sends the traffic corresponding to the grayscale traffic ratio to the corresponding grayscale application instance.

The device also includes: a storage module 210:

receiving the mapping relationship data between the gateway 15 and the application sent by the gateway management interface 16 through the gateway management service 11;

storing the mapping relationship data in a database.

The delivery module 300 includes:

A data structure generating module 301, configured to generate a grayscale traffic configuration data structure according to the traffic distribution rule data, the grayscale traffic configuration data structure including a gateway ID and a traffic ratio;

The calling module 302 is used to call the interface of the configuration management center 14, and deliver the gateway ID and the corresponding traffic ratio to the corresponding gateway 15.

The embodiment of the present application also provides an applied gray scale publishing system, the structural block diagram of which is shown in Figure 3, the system includes:

Gray scale data configuration interface 12, configured to receive traffic distribution rule data sent by users, and send the traffic distribution rule data to gateway management service 11;

The gateway management service 11 is used to store the traffic distribution rule data in a database, and when the application is released, call the interface of the configuration management center 14, and use the traffic distribution rule data based on the pre-stored mapping between the gateway 15 and the application The relationship data is sent to the gateway 15 corresponding to the current application;

The configuration management center 14 is connected to a plurality of gateways 15, and is configured to issue traffic distribution rule data to the gateways 15, so that the gateways can realize the gray release of the current application according to the traffic distribution rules.

In addition, it also includes a MySQL database 13 for storing the mapping relationship data between the gateway 15 and the application. Since different applications may correspond to different gateways 15, the relationship data of the two can be stored, which not only facilitates updating and maintaining the relationship data in time, but also facilitates locating the gateway 15 corresponding to the current application through the relationship data.

For another function of the gateway 15, after the new version instance goes online, QA personnel can use the gateway 15 to perform regression testing.

As shown in Figure 9, it is a schematic diagram of a regression test. When a new version instance is launched, if QA personnel are required to perform a regression test first, user traffic cannot be allocated to the new version instance. QA personnel can add traffic-tag: grayTest to the header of the http test request, so that only the http test request of the QA personnel will hit the new version instance.

In the gateway 15, the traffic is routed according to the percentage through the application instance start tag, and at the same time, specific routing is performed for the http request with a specific header tag (traffic-tag: grayTest), and it is directly routed to the new version instance to realize the regression test of the new version instance .

The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory is used to store a computer program, and the processor runs the computer program so that the electronic device executes the computer program described in the embodiment. The grayscale publishing method of the application.

The embodiment of the present application also provides a readable storage medium, where computer program instructions are stored in the readable storage medium, and when the computer program instructions are read and executed by a processor, the grayscale of the application described in the embodiment is executed. degree release method.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may also be implemented in other ways. The device embodiments described above are only illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functions and possible implementations of devices, methods and computer program products according to multiple embodiments of the present application. operate. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of code that includes one or more Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified function or action , or may be implemented by a combination of dedicated hardware and computer instructions.

In addition, each functional module in each embodiment of the present application may be integrated to form an independent part, each module may exist independently, or two or more modules may be integrated to form an independent part.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

The above descriptions are only examples of the present application, and are not intended to limit the scope of protection of the present application. For those skilled in the art, various modifications and changes may be made to the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included within the protection scope of this application. It should be noted that like numerals and letters denote similar items in the following figures, therefore, once an item is defined in one figure, it does not require further definition and explanation in subsequent figures.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Claims (9)

1. An applied gray scale release method, characterized in that the method comprises: Receive grayscale published traffic distribution rule data for the current application; Acquiring the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application; calling the interface of the configuration management center, and sending the data of the traffic distribution rules to the gateway, so that the gateway can realize gray release of the current application according to the traffic distribution rules; Wherein, the traffic distribution rule data includes the number of grayscale containers; the receiving grayscale published traffic distribution rule data for the current application includes: Receive the number of grayscale containers sent by the user through the grayscale data configuration interface; Modify the copy number attribute value that controls the number of application copies to control the number of grayscale application instances; Adding a grayscale tag to the startup script of the grayscale application instance, so that the gateway can find the grayscale application instance through the grayscale tag; Before the step of obtaining the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application, the method further includes: Receive the mapping relationship data between the gateway and the application sent by the gateway management interface through the gateway management service; storing the mapping relationship data in a database. 2. The application gray-scale release method according to claim 1, wherein the traffic distribution rule data further includes a gray-scale traffic ratio, and receiving the gray-scale release traffic distribution rule data for the current application, Also includes: Receive the grayscale traffic ratio sent by the user through the grayscale data configuration interface, so that the gateway sends the traffic corresponding to the grayscale traffic ratio to the corresponding grayscale application instance. 3. The application grayscale release method according to claim 1, wherein the calling the interface of the configuration management center to send the traffic distribution rule data to the gateway includes: Generate a gray-scale traffic configuration data structure according to the traffic distribution rule data, the gray-scale traffic configuration data structure includes a gateway ID and a traffic ratio; Call the interface of the configuration management center, and deliver the gateway ID and the corresponding traffic ratio to the corresponding gateway. 4. The gray-scale release method of an application according to claim 1, wherein the gateway realizes the gray-scale release of the current application according to the traffic distribution rule, comprising: The gateway publishes and runs the application on a cloud host or a k8s container platform. 5. The application grayscale publishing method according to claim 1, characterized in that: The gateway is a gray scale traffic ratio control route, including Spring Cloud Zuul gateway and/or Kong gateway. 6. An applied grayscale release device, characterized in that the device comprises: The receiving module is used to receive traffic distribution rule data published in gray scale for the current application; A gateway obtaining module, configured to obtain the gateway corresponding to the current application according to the preset mapping relationship data between the gateway and the application; A sending module, configured to call the interface of the configuration management center, and send the data of the traffic distribution rules to the gateway, so that the gateway can implement the gray release of the current application according to the traffic distribution rules; Wherein, the traffic distribution rule data includes the number of grayscale containers; the receiving module is specifically used for: Receive the number of grayscale containers sent by the user through the grayscale data configuration interface; Modify the copy number attribute value that controls the number of application copies to control the number of grayscale application instances; Adding a grayscale tag to the startup script of the grayscale application instance, so that the gateway can find the grayscale application instance through the grayscale tag; The device also includes a storage module for: Receive the mapping relationship data between the gateway and the application sent by the gateway management interface through the gateway management service; storing the mapping relationship data in a database. 7. An applied grayscale release system, characterized in that the system includes: Gray scale data configuration interface, used to receive the traffic distribution rule data sent by the user, and send the traffic distribution rule data to the gateway management service; The gateway management service is used to store the traffic distribution rule data in a database, and when the application is published, call the interface of the configuration management center to send the traffic distribution rule data based on the pre-stored mapping relationship data between the gateway and the application to the gateway corresponding to the current application; The configuration management center is connected to a plurality of gateways, and is used to deliver traffic distribution rule data to the gateways, so that the gateways can realize gray release of the current application according to the traffic distribution rules; Wherein, the traffic distribution rule data includes the number of grayscale containers; the grayscale data allocation interface is specifically used for: Receive the number of grayscale containers sent by the user; Modify the copy number attribute value that controls the number of application copies to control the number of grayscale application instances; Adding a grayscale tag to the startup script of the grayscale application instance, so that the gateway can find the grayscale application instance through the grayscale tag; The system also includes a MySQL database for storing mapping relationship data, and the mapping relationship data is the mapping relationship data between the gateway and the application sent by the gateway management interface through the gateway management service. 8. The application grayscale publishing system according to claim 7, characterized in that: The gateway is also used for sending the http test request to the new version instance after adding an application instance start tag in the request header of the http test request when performing a regression test on the new version instance. 9. An electronic device, characterized in that the electronic device comprises a memory and a processor, the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the electronic device according to claim 1. The grayscale distribution method of the application described in any one of to 5.

Images