CN116450196A - Gray level release method and system - Google Patents

Abstract

The application discloses a gray level release method and a gray level release system, which relate to the technical field of cloud computing, wherein the gray level release method comprises the following steps: receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; and providing the gray level change data to a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. The invention can support configuration of a plurality of gray scale dimensions for the same gray scale strategy, and meets the requirements of various working scenes.

Description

Gray level release method and system

Technical Field

The application relates to the field of cloud computing, in particular to a gray level publishing method and a gray level publishing system.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

Gray scale distribution refers to a distribution mode capable of smoothly transiting between black and white. On which an a/B test can be performed, i.e. letting a part of the users continue to use the product property a and a part of the users start to use the product property B, if the users do not have any objection to B, the range is gradually expanded and all users are migrated to B. The gray level release can ensure the stability of the whole system, and the problems can be found and adjusted during the initial gray level so as to ensure the influence degree. When a new function is released online, the current gray release scheme mostly carries out gray by designating the number of UIDs (User identifiers), has single dimension, and cannot meet the requirement of diversified working scenes.

Disclosure of Invention

The embodiment of the application provides a gray level release method and a gray level release system, which can support the determination of a gray level release strategy from multiple dimensions, so that the gray level release strategy is applicable to more working scenes.

According to an aspect of the present application, there is also provided a gray scale distribution method, including: receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; and providing the gray level change data to a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information.

According to another aspect of the present application, there is further provided a gray scale publishing system, including a data management module and a configuration pushing module: the data management module is used for receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; the configuration pushing module is used for providing the gray level change data for a cloud server according to the region information so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information.

According to another aspect of the present application, there is also provided an electronic apparatus including: a processor; and a memory storing a program, wherein the program comprises instructions that when executed by the processor cause the processor to perform a method according to the above.

According to another aspect of the present application, there is also provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method steps according to the above.

According to another aspect of the present application, there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the above-mentioned method steps.

The embodiment of the invention has the beneficial effects that: in the embodiment of the application, gray level change data of a target function is received; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; and providing the gray level change data to a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. According to the method, gray level change data of a target function needing gray level release are received, gray level start-stop time information, region information and user gray level information determined according to at least one dimension are obtained, and then the gray level change data are provided for a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. Because the user gray information is determined according to at least one dimension, wherein the dimension is used for classifying the users with the target functions, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be subjected to gray processing, a plurality of gray dimensions can be configured for the same gray strategy, and the requirements of various working scenes are met.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the other features, objects, and advantages of the invention.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It is evident that the drawings in the following description are only some embodiments of the invention, from which other embodiments can be obtained for a person skilled in the art without inventive effort.

FIG. 1 is a flow chart of a gray scale distribution method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an implementation flow of a gray level distribution method according to an embodiment of the present invention;

FIG. 3 is a life cycle schematic of gray scale distribution according to an embodiment of the present application;

FIG. 4 is a block diagram of an exemplary electronic device that can be used to implement embodiments of the present invention;

fig. 5 is a second schematic implementation flow chart of the gray scale distribution method in the embodiment of the present application.

Detailed Description

Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While the invention is susceptible of embodiment in the drawings, it is to be understood that the invention may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided to provide a more thorough and complete understanding of the invention. It should be understood that the drawings and embodiments of the invention are for illustration purposes only and are not intended to limit the scope of the present invention.

When a new function is released and online, the gray release is carried out by the configuration center configuration UID list mode in the existing scheme, and the method specifically comprises the following steps: creating a new configuration center configuration, configuring a gray scale effective UID list in the configuration center configuration, reading the configuration in a code, analyzing the effective UID list, checking whether the current UID is in the list, and executing gray scale logic. The scheme needs to add configuration center configuration, and when gray items are more and more, the configuration center configuration is more and more. In addition, the scheme only supports the UID dimension, and if the BID (Business Identifier, user group identifier) dimension is to be supported, the configuration center needs to be configured separately and the code implementation needs to be written separately. This scheme lacks a trace management mechanism for the gray scale flow.

The second existing scheme performs gray level release by configuring a label mode in a label system, and specifically includes: a tag (including keys, values) is created in the tag system and then the gray-scale validated UID is marked. And calling the CRM system in the code to acquire a label key value list of the UID, checking whether the label key value list contains a designated key value, and executing gray logic. The scheme only supports the label dimension of the label system, and lacks a tracking management mechanism for the gray scale flow. The tag of the tag system may be a tag of UID dimension maintained by a tag maintenance team, and may support a custom tag key value.

In summary, in the existing scheme, the gray level policy mostly designates the UID number to perform gray level, the dimension is single, the gray level progress has no tracking mechanism, the gray level may not be forgotten after one time of gray level is completed, or the code and configuration of the gray level after gray level is completed still exist in the code. Gray release is performed by using the existing scheme, a light person may cause code to be bloated and poor in readability, and a heavy person may cause on-line faults and even cost loss.

Based on the background, the application provides a gray level release method and a gray level release system, wherein the method can support a multi-dimensional gray level strategy, and besides UID, gray level according to BID, labels, credit scores, credit levels, dynamic conditions and the like. The method can realize high-efficiency multi-region gray scale configuration, does not need to point to open each region to configure corresponding gray scale strategies, can configure the gray scale strategies of all regions on the same page, and improves the convenience of configuration. The scheme also comprises a complete gray scale flow tracking mechanism, and can support configuration of gray scale rhythm, customization of gray scale reminding and gray scale code offline reminding. The method can control the complete life cycle of gray scale, ensure the integrity and reliability of functional online and improve the quality of program codes.

In this embodiment, a gray scale distribution method is provided, fig. 1 is a flowchart of a gray scale distribution method according to an embodiment of the present application, and method steps involved in fig. 1 are described below.

Step S102, receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed.

In this step, the user can implement the target function by running code for implementing the target function. The same target function may be implemented by multiple users. The code of a target function may be composed of a plurality of sub-codes, and each sub-code is used as an application, and may implement a sub-function. For example, an application may be used to implement a pay-per-view function, and an application may be used to implement a pay-per-view sub-function that combines to obtain a target function for shopping.

The gradation change data may be used to control code that runs the target function to achieve gradation release for the target function. For example, based on the gradation change data, a certain user can be allowed to realize the product characteristic B in a certain application when realizing the target function. When a user performs gradation processing with respect to a target function, a certain application of the user may be allowed to realize the product characteristic B. The unused users can perform gray scale processing for different applications to achieve different product characteristics.

The gradation change data includes gradation start-stop time information, area information, and user gradation information determined in accordance with at least one dimension. The gray start and stop time information is used for determining the gray start and gray end time. And the area information is used for determining the geographic position of equipment resources used by the user to be subjected to gray scale processing. User gray information for determining a user to be gray-processed and a target application of the user to be gray-processed. The target application to be gray-scale processed is determined from a plurality of applications, one or more applications to be gray-scale processed can be identified by application names.

The user gray information may be determined according to at least one dimension, where the dimension is used to classify the user of the target function, i.e. the user of the target function may be classified from multiple dimensions. For example, users are classified based on dimension a to obtain users with category parameters of "1", "2" and "3", respectively, and classified based on dimension B to obtain users with category parameters of "1", "2" and "3", respectively. And then, determining the gray information of the user according to the classification result, and determining a gray release strategy. It should be noted that, the user gray information of the same gray distribution strategy is determined, multiple dimensions can be used simultaneously, and multiple dimensions support and or logic. For example, the user may be allowed to meet the requirements: "dimension a=taxonomy 1 and dimension b=taxonomy 2", or "dimension a=taxonomy 1 or dimension b=taxonomy 2" is satisfied, resulting in a user taxonomy result. Based on this, the user to be subjected to gradation processing and the target application corresponding to the user can be screened out. The target application may be any application that needs to be implemented by the user in implementing the target function, and the method for specifically determining the application may be selected according to actual requirements, which is not specifically limited in the embodiment of the present invention.

In the step, the user is an account number which can be logged in a cloud server, and the data processing authorities of different account numbers are different. When the gray level distribution is performed on the target function, different users can perform gray level processing on the cloud server according to the gray level change information.

In the step, gray release can be performed based on user gray information determined according to at least one dimension, and related parameters do not need to be configured for each dimension respectively, so that the scheme does not increase related configuration parameters due to the increase of gray items, and when multiple dimensions are needed, codes do not need to be independently written for each dimension, so that the processing difficulty of gray release is reduced. As multiple dimensions can be supported, the defect of single gray scale dimension is overcome, and the scheme can be suitable for more working scenes.

And step S104, providing the gray change data to a cloud server according to the area information, so that the cloud server executes gray release on the target application according to the gray start-stop time information and the user gray information.

In this step, since the area information of the gray scale policy is specified in the received gray scale change data, the corresponding gray scale change data may be provided to the cloud server according to the area information, so that the cloud server obtains the gray scale change data of each area, controls the time of starting and ending the gray scale according to the gray scale start and stop time information in the gray scale change data, determines the user to perform the gray scale processing in each area according to the user gray scale information, and the target application to perform the gray scale by the user, thereby realizing the gray scale distribution of the target function.

The cloud server may run applications of a plurality of areas, and the gray scale policies adopted by the applications of each area are different, that is, the gray scale change data is different, so that the gray scale change data needs to be provided to the cloud server according to the area information, so that the cloud server executes gray scale distribution on the target application according to the gray scale start-stop time information and the user gray scale information.

It should be noted that, the cloud server is a virtual server based on cloud computing technology, and may be created and managed on a cloud computing platform. Different from the traditional physical server, the cloud server can be elastically expanded and contracted according to the demands of users, and the users only need to purchase the required computing resources according to the demands and do not need to purchase the hardware equipment of the entity server, so that the cost and the maintenance difficulty are reduced. The cloud server also has the advantages of high availability, flexibility, safety and the like, and can meet the requirements of enterprises and individual users with different scales and requirements.

In the embodiment of the application, gray level change data of a target function is received; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; and providing the gray level change data to a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. According to the method, gray level change data of a target function needing gray level release are received, gray level start-stop time information, region information and user gray level information determined according to at least one dimension are obtained, and then the gray level change data are provided for a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. Because the user gray information is determined according to at least one dimension, wherein the dimension is used for classifying the users with the target functions, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be subjected to gray processing, a plurality of gray dimensions can be configured for the same gray strategy, and the requirements of various working scenes are met.

In one possible implementation, the user gray information is determined according to one or several of the following dimensions: user identification dimensions, user group identification dimensions, tag dimensions, credit score dimensions, credit rating dimensions, location dimensions, and real-time specified dimensions.

In this possible embodiment, the user identification dimension includes identification information of each user, and the user gray information is determined according to the user identification dimension, so that it is possible to precisely select the user to be gray according to the identification information of each user. The user group identification dimension includes identification information of a plurality of groups of users, i.e., BID information. The identification information of each group of users can comprise information of a plurality of users, the gray information of the users is determined according to the identification dimension of the user group, a plurality of groups of users with the same characteristics can be selected for gray processing, and the gray processing efficiency is improved. When determining the users included in each group of users, the users may be selected according to actual requirements, which is not particularly limited in the embodiment of the present invention.

The label dimension comprises label information of each user, and the user information is determined according to the label dimension, so that the users can be classified according to the labels, and the users conforming to the designated labels are selected as the users to be subjected to gray scale processing. The tag information may be set according to actual requirements, for example, may be used to characterize a certain feature of the user, which is not specifically limited in the embodiment of the present invention.

The credit dimension comprises credit information of each user, the user dimension information is determined according to the credit dimension, and users with the credit meeting the designated credit range can be accurately selected for gray processing.

The credit rating dimension comprises rated data of each user, and user information is determined according to the credit rating dimension, so that users with higher or lower credit ratings can be selected, and gray scale processing is carried out on the users with higher or lower credit ratings.

The position dimension comprises the relevant information of the specific geographic position of the user in each area, the user information is determined according to the position dimension, and the user at different positions in each area can be selected to carry out gray processing, so that more accurate gray processing on the more subdivided positions is realized.

In the case that the above dimensions cannot meet the requirements, the real-time specified dimensions may be used to classify the users. The real-time specified dimension comprises screening condition information determined in real time, and the user gray information is determined according to the real-time specified dimension, so that the user can be selected according to dynamic conditions, and the requirements of more added working scenes can be met.

It should be noted that when the gray information of the user is determined according to the user identification dimension, the user is generally selected according to the complete number of the UID.

In one possible implementation manner, the providing of the gray scale change data to the cloud server according to the area information may be performed as follows: and sending the gray change data to a forwarding component, so that the forwarding component sends the gray change data to a cloud server according to the region information.

In this possible implementation, the forwarding component may be configured to receive the grayscale change data and may also be configured to send the grayscale change data to the cloud server. The forwarding component may be set according to actual requirements, which is not specifically limited in the embodiment of the present invention. For example, the forwarding component may also provide persistence management and dynamic configuration push services. Based on the forwarding component, the configuration released by the application side can be stored through persistent storage, and is irrelevant to the life cycle of the publisher, and the dynamic configuration pushing function of the forwarding component can be applied to a plurality of application scenes such as dynamic switching and capacity expansion of a database, change of the switch configuration of a working system during running and the like.

In this step, referring to the first implementation flow diagram of the gray level distribution method shown in fig. 2, after setting the gray level policy, an operator issues the gray level policy to the gray level application of each area through the forwarding component, that is, sends the gray level change data to the cloud server, so that stability and reliability of data processing can be higher.

In one possible implementation manner, the providing of the gray scale change data to the cloud server according to the area information may be performed as follows: and generating a calling interface according to the gray level change data, so that the cloud server calls the calling interface according to the region information to obtain the gray level change data.

In this possible implementation manner, the method for generating the call interface may be selected according to actual requirements, which is not specifically limited in the embodiment of the present invention. For example, manually writing a code call interface: and according to the interface document, manually writing a code call interface, transmitting request parameters to the interface, and receiving data returned by the interface. Calling an interface using a third party library or framework: many programming languages have corresponding third party libraries or frameworks that can conveniently invoke interfaces. Using API (Application Programming Interface), application programming interface) tools call interfaces: many API tools can be used to quickly generate code for calling interfaces. Using the SDK call interface: many cloud service providers offer corresponding SDKs (Software Development Kit, software development kits) that can conveniently invoke the interfaces they offer. Whichever method is used, information such as request parameters, request mode, return data format, etc. of the interface needs to be known first in order to call the interface correctly.

In this step, referring to the second implementation flow chart of the gray level distribution method shown in fig. 5, after setting a gray level policy, an operator stores the gray level policy in a data management module in the form of gray level change data, and then generates a calling interface according to the gray level change data, where each generated interface has corresponding area information, so that a cloud server calls the calling interface according to the area information to obtain the gray level change data. The application of each area is directly called to the system adopting the scheme to obtain the gray change data, and a forwarding component is not needed.

Considering that some cloud servers may perform multi-area management and control by using a unitization manner, a conventional multi-area gray scale manner is adopted, configuration needs to be performed on a plurality of configuration centers, which is time-consuming and labor-consuming and easy to miss-match, in order to alleviate such a situation, and to improve convenience of multi-area gray scale policy management, in one possible implementation, before providing the gray scale change data to the cloud servers according to the area information, the following steps may be further performed:

and displaying and/or modifying multiple groups of region information of the target function by using the same page, and displaying and/or modifying user gray information corresponding to the multiple groups of region information.

In this possible implementation, a page refers to a user interface displayed on a computer screen, typically including elements of text, images, buttons, links, etc., for presenting information to a user, receiving user input, performing operations, etc. The pages may be web pages, application interfaces, operating system interfaces, and the like. And displaying multiple groups of region information and user gray information corresponding to the multiple groups of region information on the same page, so that gray strategies of all regions can be browsed on the same page, the configuration efficiency is greatly improved, and the error probability is reduced.

In order to be able to manage the lifecycle of the gray scale distribution, in a possible implementation, the solution may further perform the following steps: the gray level release state of the cloud server is monitored, gray level progress reminding information is generated according to the gray level release state, and the gray level progress reminding information is sent to a management end; the management end is used for displaying the gray level progress reminding information or controlling the gray level release progress of the cloud server according to the gray level progress reminding information.

In this possible implementation manner, the gray level release state of the cloud server is monitored, so as to grasp the state of the complete life cycle of gray level release, when the state is abnormal, corresponding gray level progress reminding information can be generated according to various abnormal states, and then the gray level progress reminding information is sent to the management end, so that the management end can manage the abnormal situation in time.

The management end can be a mobile terminal, such as a mobile phone, a computer and other terminals. The management end can be used for displaying the gray level progress reminding information, so that an operator is informed of the abnormal state of the gray level release process in time. The management end can also control the gray level release progress of the cloud server according to the gray level progress reminding information.

It should be noted that, the gray level progress reminding information may be sent to the management end in the forms of notification, message, mail, etc., and the specific form may be selected according to the actual requirement, which is not limited in the embodiment of the present invention.

In this step, complete lifecycle management can be achieved. And (3) carrying out state tracking from gray level creation to gray level ending code downloading, and if the system finds that the state is abnormal, notifying an operator, avoiding the situation that the operator forgets gray level, and reducing error probability.

In one possible implementation, the gray scale release state includes no gray scale, gray scale neutralization, and gray scale completion; the gray level progress reminding information is generated according to the gray level release state and can be executed according to the following steps: determining a gray starting time according to the gray starting and ending time information, and generating first state reminding information if the gray release state is non-gray after the gray starting time exceeds a first preset time; if the gray level release state is that the duration in the gray level exceeds a second preset duration, generating second state reminding information; determining a gray scale stop time according to the gray scale start-stop time information, and generating third state reminding information if codes for gray scale release are not off-line after the gray scale stop time exceeds a third preset time; and taking the first state reminding information, the second state reminding information and the third state reminding information as gray level progress reminding information.

In this possible embodiment, the first preset duration, the second preset duration, and the third preset duration may be set according to actual requirements, and the three may be set to the same or different values, which is not specifically limited in the embodiment of the present invention. The first state reminding information, the second state reminding information and the third state reminding information can remind the user with different contents, so that the user can timely know specific abnormal conditions without confirming which abnormal conditions are again, and more accurate gray level release progress reminding is achieved.

When the management end receives the first state reminding information, a first control instruction can be sent to the cloud server, so that when the cloud server does not execute gray level release according to the gray level starting moment, the cloud server is timely controlled to start gray level release. When the management end receives the second state reminding information, a second control instruction can be sent to the cloud server, so that when the cloud server influences the gray level progress for some reasons, problems are found in time, and the normal operation of gray level release is controlled. When the management end receives the third state reminding information, a third control instruction can be sent to the cloud server, so that the code is controlled to be cut off in time under the condition that the cloud server finishes gray level release but the code is not cut off in time, the code is prevented from being bloated, and the readability of the code is ensured.

In the implementation of this possible embodiment, referring to the life cycle schematic of gray scale distribution shown in fig. 3, the life cycle flow of a gray scale is shown, and when defining a new gray scale change, it is necessary to specify a planned gray scale ending time. When the following occurs, the system will notify the operator through a particular channel (including, but not limited to, mail, work notification, etc.). (1) After the gray level change is created, the gray level state is not entered for more than N days. (2) After the state in gray is N days, the gray is not in the gray completion state. (3) after the gray level is completed for N days, the code is not put down.

The method supports configuration of a plurality of gray scale dimensions for the same gray scale strategy, meets various working scenes, supports efficient management of the gray scale strategy of multiple areas, improves configuration efficiency, supports complete gray scale change life cycle management, and reduces error probability.

The application also provides a gray level release system, which comprises a data management module and a configuration pushing module: the data management module is used for receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; the configuration pushing module is used for providing the gray level change data for a cloud server according to the region information so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information.

In this scheme, the data management module is responsible for storing data such as gradation change, gradation policy, and gradation status of each region. And the configuration pushing module is responsible for pushing the gray strategy data to the application of each area. For a specific description of the data management module and the configuration pushing module performing the above steps, reference may be made to the foregoing description of the gray level distribution method, which is not repeated herein.

In the embodiment of the application, the data management module is used for receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed; and the configuration pushing module is used for providing the gray change data for a cloud server according to the region information so that the cloud server executes gray release on the target application according to the gray start-stop time information and the user gray information. According to the method, gray level change data of a target function needing gray level release are received, gray level start-stop time information, region information and user gray level information determined according to at least one dimension are obtained, and then the gray level change data are provided for a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information. Because the user gray information is determined according to at least one dimension, wherein the dimension is used for classifying the users with the target functions, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be subjected to gray processing, a plurality of gray dimensions can be configured for the same gray strategy, and the requirements of various working scenes are met.

In one possible embodiment, the system further comprises: a lifecycle management module; the life cycle management module is used for monitoring the gray level release state of the cloud server, generating gray level progress reminding information according to the gray level release state, and sending the gray level progress reminding information to a management end; the management end is used for displaying the gray level progress reminding information or controlling the gray level release progress of the cloud server according to the gray level progress reminding information.

In this possible implementation, the lifecycle management module: is responsible for managing the changed state and sending a notification to an operator when the state may be abnormal. For a specific description of the implementation of the above steps by the lifecycle management module, reference may be made to the foregoing description of the gray scale distribution method, which is not repeated herein.

In one possible implementation, the user gray information is determined according to one or several of the following dimensions: user identification dimension, user group identification dimension, tag dimension, credit score dimension, credit rating dimension, location dimension, and real-time specified dimension

In a possible implementation manner, the configuration pushing module is configured to: and sending the gray change data to a forwarding component, so that the forwarding component sends the gray change data to a cloud server according to the region information.

In a possible implementation manner, the configuration pushing module is configured to: and generating a calling interface according to the gray level change data, so that the cloud server calls the calling interface according to the region information to obtain the gray level change data.

In a possible implementation manner, the configuration pushing module is further configured to: and displaying and/or modifying multiple groups of region information of the target function by using the same page, and displaying and/or modifying user gray information corresponding to the multiple groups of region information.

In one possible implementation, the lifecycle management module is specifically configured to: determining a gray starting time according to the gray starting and ending time information, and generating first state reminding information if the gray release state is non-gray after the gray starting time exceeds a first preset time; if the gray level release state is that the duration in the gray level exceeds a second preset duration, generating second state reminding information; determining a gray scale stop time according to the gray scale start-stop time information, and generating third state reminding information if codes for gray scale release are not off-line after the gray scale stop time exceeds a third preset time; and taking the first state reminding information, the second state reminding information and the third state reminding information as gray level progress reminding information.

The embodiment of the invention also provides electronic equipment, which comprises: at least one processor; and a memory communicatively coupled to the at least one processor. The memory stores a computer program executable by the at least one processor for causing the electronic device to perform a method according to an embodiment of the invention when executed by the at least one processor.

The embodiments of the present invention also provide a non-transitory computer readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is for causing the computer to perform a method according to an embodiment of the present invention.

Embodiments of the present invention also provide a computer program product comprising a computer program, wherein the computer program, when being executed by a processor of a computer, is for causing the computer to perform a method according to embodiments of the present invention.

Referring to fig. 4, a block diagram of an electronic device 400 that may be a server or user of the present invention will now be described, which is an example of a hardware device that may be applied to aspects of the present invention. Electronic devices are intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, the electronic device 400 includes a computing unit 401 that can perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM) 402 or a computer program loaded from a storage unit 408 into a Random Access Memory (RAM) 403. In RAM 403, various programs and data required for the operation of device 400 may also be stored. The computing unit 401, ROM 402, and RAM 403 are connected to each other by a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.

Various components in electronic device 400 are connected to I/O interface 405, including: an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. The input unit 406 may be any type of device capable of inputting information to the electronic device 400, and the input unit 406 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. The output unit 407 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 408 may include, but is not limited to, magnetic disks, optical disks. The communication unit 409 allows the electronic device 400 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.

The computing unit 401 may be a variety of general purpose and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 401 include, but are not limited to, a processing unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 401 performs the respective methods and processes described above. For example, in some embodiments, the foregoing methods may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 408. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 400 via the ROM 402 and/or the communication unit 409. In some embodiments, the computing unit 401 may be configured to perform the aforementioned methods by any other suitable means (e.g., by means of firmware).

Program code for carrying out methods of embodiments of the present invention may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of embodiments of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that the term "comprising" and its variants as used in the embodiments of the present invention are open-ended, i.e. "including but not limited to". The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. References to "one or more" modifications in the examples of the invention are intended to be illustrative rather than limiting, and it will be understood by those skilled in the art that "one or more" is intended to be interpreted as "one or more" unless the context clearly indicates otherwise.

User information (including but not limited to user equipment information, user personal information and the like) and data (including but not limited to data for analysis, stored data, presented data and the like) according to the embodiment of the invention are information and data authorized by a user or fully authorized by all parties, and the collection, use and processing of related data are required to comply with related laws and regulations and standards of related countries and regions, and are provided with corresponding operation entrances for users to select authorization or rejection.

The steps described in the method embodiments provided in the embodiments of the present invention may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the invention is not limited in this respect.

The term "embodiment" in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the invention. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive. The various embodiments in this specification are described in a related manner, with identical and similar parts being referred to each other. In particular, for apparatus, devices, system embodiments, the description is relatively simple as it is substantially similar to method embodiments, see for relevant part of the description of method embodiments.

The above examples merely represent a few embodiments of the present invention, which are described in more detail and are not to be construed as limiting the scope of the patent claims. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the invention, which are all within the scope of the invention. Accordingly, the scope of the invention should be assessed as that of the appended claims.

Claims (12)

1. A gray scale distribution method, comprising:

receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed;

and providing the gray level change data to a cloud server according to the region information, so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information.

2. The method of claim 1, wherein the user grey scale information is determined in one or more of the following dimensions:

user identification dimensions, user group identification dimensions, tag dimensions, credit score dimensions, credit rating dimensions, location dimensions, and real-time specified dimensions.

3. The method of claim 1, wherein providing the gradation change data to a cloud server according to the area information comprises:

and sending the gray change data to a forwarding component, so that the forwarding component sends the gray change data to a cloud server according to the region information.

4. The method of claim 1, wherein providing the gradation change data to a cloud server according to the area information comprises:

and generating a calling interface according to the gray level change data, so that the cloud server calls the calling interface according to the region information to obtain the gray level change data.

5. The method of claim 1, wherein before providing the gradation change data to the cloud server according to the area information, further comprising:

and displaying and/or modifying multiple groups of region information of the target function by using the same page, and displaying and/or modifying user gray information corresponding to the multiple groups of region information.

6. The method of any of claims 1-5, further comprising:

the gray level release state of the cloud server is monitored, gray level progress reminding information is generated according to the gray level release state, and the gray level progress reminding information is sent to a management end; the management end is used for displaying the gray level progress reminding information or controlling the gray level release progress of the cloud server according to the gray level progress reminding information.

7. The method of claim 6, wherein the gray scale distribution state comprises non-gray scale, gray scale neutralization, and gray scale completion; generating gray level progress reminding information according to the gray level release state comprises the following steps:

determining a gray starting time according to the gray starting and ending time information, and generating first state reminding information if the gray release state is non-gray after the gray starting time exceeds a first preset time;

if the gray level release state is that the duration in the gray level exceeds a second preset duration, generating second state reminding information;

determining a gray scale stop time according to the gray scale start-stop time information, and generating third state reminding information if codes for gray scale release are not off-line after the gray scale stop time exceeds a third preset time;

And taking the first state reminding information, the second state reminding information and the third state reminding information as gray level progress reminding information.

8. A gray level release system comprises a data management module and a configuration pushing module:

the data management module is used for receiving gray level change data of a target function; the gray change data comprises gray start-stop time information, region information and user gray information determined according to at least one dimension; the dimension is used for classifying users of the target function, the user gray information is determined according to the classification result of the users, and the user gray information comprises target applications to be gray processed;

the configuration pushing module is used for providing the gray level change data for a cloud server according to the region information so that the cloud server executes gray level release on the target application according to the gray level start-stop time information and the user gray level information.

9. The system of claim 8, further comprising: a lifecycle management module;

the life cycle management module is used for monitoring the gray level release state of the cloud server, generating gray level progress reminding information according to the gray level release state, and sending the gray level progress reminding information to a management end; the management end is used for displaying the gray level progress reminding information or controlling the gray level release progress of the cloud server according to the gray level progress reminding information.

10. An electronic device, comprising:

a processor; and

a memory in which a program is stored,

wherein the program comprises instructions which, when executed by the processor, cause the processor to perform the method steps according to any of claims 1-7.

11. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method steps of any one of claims 1-7.

12. A computer program product, wherein the computer program product comprises a computer program which, when executed by a processor, implements the method steps of any of claims 1-7.