CN114780512A

CN114780512A - Gray scale publishing method, system and server

Info

Publication number: CN114780512A
Application number: CN202210284224.4A
Authority: CN
Inventors: 杨杰
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-03-22
Filing date: 2022-03-22
Publication date: 2022-07-22
Anticipated expiration: 2042-03-22
Also published as: CN114780512B

Abstract

A gray release method, a system and a server relate to the technical field of computers, ensure the consistency of data in a database and solve the problem that certain functions of the database are limited due to gray release. The method is applied to a gray scale release system, the system comprises electronic equipment, a gateway, a database server, a service server and a gray scale server, and the gray scale release method comprises the following steps: a gateway receives a first service request sent by electronic equipment, wherein the first service request carries a user identifier; the method comprises the steps that when a gateway determines that a user identifier meets a preset condition, the gateway sends a data migration request to a gray scale server, the gray scale server migrates data corresponding to the user identifier to a gray scale table from a production table according to the data migration request, the production table is a data table corresponding to a service server, and when the gateway determines that the data migration is successful, the gateway sends a first service request to the gray scale server so that the gray scale server executes corresponding response operation according to the first service request.

Description

Gray scale publishing method, system and server

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, a system, and a server for releasing a gray scale.

Background

With the rapid development of computer technology, various Applications (APPs) are widely used in people's lives, and therefore developers of various applications need to continuously update the applications according to the needs of users, so as to retain users or attract more users. In order to avoid the influence on the user service due to the application quality problem after the application is updated, developers generally upgrade the application by using a gray scale publishing method. That is, the developer issues the new version of the application to the application server in advance, and then performs functional verification using a small amount of services to verify whether the new version of the application has quality problems.

In the related art, when a developer upgrades a version of an application, it is generally necessary to upgrade both code and data of the application. It can be seen that in the process of upgrading a produced application by a developer, a scenario exists in which a table structure in a database of the application is changed (e.g., a table field is deleted, newly added, or renamed).

However, when a developer upgrades an application version in a gray release manner, the data table structure is directly upgraded in an application database, that is, the produced application is not matched with the changed data table structure, so that the application code is incompatible. Therefore, some functions in the database of the application are limited, for example, the upgraded version of the application cannot delete or modify a table field in the database of the application, so that the gray release scenario is limited.

Disclosure of Invention

The embodiment of the application provides a gray scale publishing method, a gray scale publishing system and a server, wherein after the gray scale publishing is started, under the condition that the system determines that a user identifier of electronic equipment sending a service request meets preset conditions, data corresponding to the user identifier in a production table is migrated to the gray scale table, wherein the preset conditions are that the user identifier is the user identifier of a preset user and a gray scale state corresponding to the user identifier is not started, and under the condition that the system determines that the gray scale state corresponding to the user identifier is started, the data corresponding to the user identifier in the gray scale table is migrated back to the production table. Therefore, in the gray release process, the system performs real-time migration and return on the data corresponding to the user identification, so that the consistency of the data in the production database is ensured, and the problem that certain functions in the production database are limited after gray release is solved.

In order to achieve the purpose, the following technical scheme is adopted in the application:

in a first aspect, an embodiment of the present application provides a gray scale publishing method, which is applied to a gray scale publishing system, where the system includes an electronic device, a gateway, a database server, a service server, and a gray scale server, and the gray scale method includes: a gateway receives a first service request sent by electronic equipment, wherein the first service request carries a user identifier; under the condition that the gateway determines that the user identification meets the preset condition, the gateway sends a data migration request to the gray scale server, wherein the data migration request carries the user identification; the gray server migrates data corresponding to the user identification from a production table to a gray table according to the data migration request, the production table is a data table corresponding to the service server, the gray table is a data table corresponding to the gray server, and the gray table is a data table obtained by copying a table structure of the production table or a data table obtained by upgrading the data table obtained by copying the table structure of the production table; and under the condition that the gateway determines that the data migration is successful, the gateway sends the first service request to the gray-scale server so that the gray-scale server executes corresponding response operation according to the first service request.

Therefore, corresponding data is directly written into a production database during gray scale release in the prior art, wherein the production database is an application database. In the embodiment of the application, the gray scale with the same structure as that of the production table is newly added in the production database, and the system performs real-time migration on the data corresponding to the user identification in the gray scale publishing process, so that the consistency of the data in the production database is ensured, and the problem that certain functions in the production database are limited after the gray scale is published is solved.

In some embodiments, the grey table is an empty table obtained by copying only the table structure of the production table, and when the system migrates the data corresponding to the user identifier of the electronic device of the sent first service request to the grey table, the data of other users are not affected, and during data migration, the data loss is avoided.

In other embodiments, in the gray scale publishing process, a gray scale is added to the production database of the database server, and the gray scale is a data table obtained by copying the table structure of the production table and upgrading the copied data table. For example, the gray table is a data table obtained by adding a table structure field to a data table obtained after copying the table structure of the production table.

The user identifier may be a service key value of the first service request, and is used to uniquely mark a user corresponding to the electronic device that initiated the first service request.

In a possible implementation manner, the preset condition includes that the user identifier is a user identifier of a preset user, and a gray state corresponding to the user identifier is not turned on.

It is understood that, a developer may preset some user-activated grays, for example, a user-activated grayscale for a certain age group is preset, or a user-activated grayscale for a certain region is preset.

In another possible implementation manner, before the gateway receives the first service request sent by the electronic device, the method further includes: responding to the operation of a user, and adding a grey table in a production database of the database server; in response to the operation of the user, the gateway turns on the main grayscale switch.

In another possible implementation manner, the executing, by the grayscale server, a corresponding response operation according to the first service request includes: and the gray server executes the gray service corresponding to the first service request and writes the data corresponding to the gray service into the gray table.

That is to say, after the grayscale server migrates the data corresponding to the user identifier in the production table to the grayscale table, the grayscale server may execute the grayscale service corresponding to the first service request, and write the corresponding data into the grayscale table, thereby modifying the data corresponding to the user identifier in the grayscale table. For example, the grayscale server performs operations such as adding, deleting, and modifying data corresponding to the user identifier in a grayscale table.

In another possible implementation manner, the gray scale issuing method further includes: and under the condition that the gateway determines that the user identifier is not the user identifier of the preset user, the gateway sends the first service request to the service server so that the service server executes corresponding response operation according to the first service request.

In another possible implementation manner, the performing, by the service server, a corresponding response operation according to the first service request includes: and the service server executes the production service corresponding to the first service request and writes the data corresponding to the production service into the production table.

That is to say, when the gateway determines that the user corresponding to the user identifier does not start the gray scale publishing, the service server executes the production service corresponding to the first service request and writes the corresponding data into the production table, thereby modifying the data corresponding to the user identifier in the production table. For example, the service server performs operations such as adding, deleting, and modifying on data corresponding to the user identifier in the production table.

In another possible implementation manner, the gray scale issuing method further includes: under the condition that the gateway determines that the data migration is successful, the gateway sets the gray state corresponding to the user identification as open; and under the condition that the gateway determines that the data migration is not successful, the gateway sets the gray state corresponding to the user identification as failure, and informs the gray server to perform rollback deletion operation on the data corresponding to the user identification in the gray table.

The rollback deletion operation refers to an operation of deleting the data corresponding to the user identifier in the gray table to restore the data corresponding to the user identifier in the gray table to a state before data migration.

It can be understood that, because the data migration is not successful, the production table also includes data corresponding to the user identifier, and the gray table may include a portion of data corresponding to the user identifier. In this case, the grayscale server may delete the data corresponding to the user identifier in the grayscale table, so that the grayscale table returns to the state before the data is migrated.

In another possible implementation manner, the gray scale issuing method further includes: responding to the operation of a user, and closing a gray release main switch by the gateway; the gateway receives a second service request sent by the electronic equipment, wherein the second service request carries a user identifier; under the condition that the gateway determines that the gray state corresponding to the user identification is open, the gateway sends a data migration request to a gray server; the gray server returns the data corresponding to the user identification from the gray table to the production table according to the data return request; and under the condition that the gateway determines that the data is successfully migrated back, the gateway sends the second service request to the service server so that the service server executes corresponding response operation according to the second service request.

It can be understood that, when the gray decision engine determines that the user has completed the verification of the gray release, the gray data engine performs real-time migration of the user's data in the gray table, which not only ensures the consistency of the user's data in the production table, but also avoids the data loss when the gray data engine migrates the user's data from the gray table to the production table.

In another possible implementation manner, before migrating the data corresponding to the user identifier from the gray table back to the production table, the method further includes: and the gray server deletes the data corresponding to the user identification in the production table.

That is to say, when the grayscale server migrates the data corresponding to the user identifier from the grayscale table to the production table, the grayscale server firstly deletes the data corresponding to the user identifier in the production table, and then copies the data corresponding to the user identifier in the grayscale table to the production table, thereby avoiding the repeated storage of the user data in the production table and avoiding the data loss during the data migration.

In another possible implementation manner, the gray scale issuing method further includes: and under the condition that the gateway determines that the data is not successfully migrated back, the gateway prompts operation and maintenance personnel to carry out manual processing.

In a second aspect, the present application provides another gray scale publishing method, applied to a gateway, including: receiving a first service request, wherein the first service request carries a user identifier; sending a data migration request to a gray scale server under the condition that the user identifier is determined to meet a preset condition, wherein the data migration request carries the user identifier, the gray scale server is used for migrating data corresponding to the user identifier from a production table to a gray scale according to the data migration request, the production table is a data table corresponding to a service server, the gray scale is a data table corresponding to the gray scale server, and the gray scale is a data table obtained by copying a table structure of the production table or a data table obtained by upgrading the data table after copying the table structure of the production table; and under the condition that the data migration is determined to be successful, sending the first service request to the gray scale server.

In another possible implementation manner, before receiving the first service request, the gray scale publishing method further includes: and opening a gray scale release main switch.

In another possible implementation manner, the gray scale issuing method further includes: and under the condition that the user identification is determined not to be the user identification of the preset user, sending the first service request to a service server.

In another possible implementation manner, the gray scale issuing method further includes: setting the gray state corresponding to the user identification as open under the condition of determining that the data migration is successful; and under the condition that the data migration is not successful, setting the gray state corresponding to the user identification as failure, and informing a gray server to perform rollback deletion operation on the data corresponding to the user identification in the gray table.

In another possible implementation manner, the gray scale issuing method further includes: receiving a second service request, wherein the second service request carries a user identifier; under the condition that the gray state corresponding to the user identification is determined to be open, sending a data migration request to a gray server; and under the condition that the data migration is determined to be successful, sending the second service request to the service server.

In another possible implementation manner, the gray scale issuing method further includes: and prompting operation and maintenance personnel to perform manual processing under the condition that the data is determined to be unsuccessfully migrated back.

In a third aspect, the present application provides another gray scale publishing method, applied to a gray scale server, including:

receiving a data migration request sent by a gateway, wherein the data migration request carries a user identifier, and the data migration request is sent to a gray scale server when the user identifier is determined to meet a preset condition after the gateway receives a first service request sent by electronic equipment, and the first service request carries the user identifier; according to the data migration request, migrating data corresponding to the user identification from a production table to a gray table, wherein the production table is a data table corresponding to the service server, the gray table is a data table obtained by copying a table structure of the production table by the gray server and upgrading the copied data table; and after receiving a first service request sent by the gateway, executing corresponding response operation according to the first service request, wherein the first service request is sent to the gray scale server under the condition that the gateway determines that the data migration is successful.

In another possible implementation manner, the executing, according to the first service request, a corresponding response operation includes: and executing the gray level service corresponding to the first service request, and writing the data corresponding to the gray level service into the gray level table.

In another possible implementation manner, the gray scale issuing method further includes: and after the rollback deletion operation sent by the gateway is received, performing the rollback deletion operation on the data corresponding to the user identification in the grey scale.

In another possible implementation manner, the gray scale issuing method further includes: receiving a data migration request sent by a gateway, wherein the data migration request is sent under the condition that the gray state corresponding to the user identifier is determined to be open after the gateway receives a second service request sent by the electronic equipment, and the second service request carries the user identifier; and according to the data migration request, migrating the data corresponding to the user identification from the grey table to the production table.

In another possible implementation manner, before migrating data corresponding to the user identifier from the grey table back to the production table, the method further includes: and deleting the data corresponding to the user identification in the production table.

In a fourth aspect, the present application provides a gray scale distribution system, comprising:

a gateway for executing the gray scale issuing method of the second aspect;

a gradation server for executing the gradation issuing method of the third aspect;

and the service server is used for executing corresponding response operation according to the first service request after receiving the first service request sent by the gateway under the condition that the gateway determines that the user identifier is not the user identifier of the preset user.

In a possible implementation manner, the service server is further configured to, when the gateway determines that the data migration is successful, execute a corresponding response operation according to a second service request sent by the gateway after receiving the second service request.

In a fifth aspect, the present application provides an electronic device, comprising: one or more processors; a memory; wherein the memory has stored therein one or more computer programs comprising instructions which, when executed by the electronic device, cause the electronic device to perform the grey scale publishing method as defined in any one of the above first aspects.

In a sixth aspect, the present application provides a gateway, comprising: one or more processors; a memory; wherein the memory has stored therein one or more computer programs, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the gray scale publishing method as claimed in any of the above second aspects.

In a seventh aspect, the present application provides a server, including: one or more processors; a memory; wherein the memory has stored therein one or more computer programs comprising instructions which, when executed by the electronic device, cause the electronic device to perform the grey scale publishing method as defined in any one of the above third aspects.

In an eighth aspect, the present application provides a computer readable storage medium having stored therein instructions that, when executed on a processor, perform the gray scale issuing method according to any one of the first aspect, perform the gray scale issuing method according to any one of the second aspect, and perform the gray scale issuing method according to any one of the third aspect.

In a ninth aspect, the present application provides a computer program product comprising computer instructions for performing the method of grey scale distribution according to any one of the first aspect, the method of grey scale distribution according to any one of the second aspect, and the method of grey scale distribution according to any one of the third aspect when the computer instructions are run on a processor.

For the beneficial effects of the other aspects, reference may be made to the description of the beneficial effects of the method aspect, which is not described herein again.

Drawings

Fig. 1 is an architecture diagram of a gray scale publishing system provided in an embodiment of the present application;

fig. 2 is a schematic structural diagram of a gray scale publishing system according to an embodiment of the present application;

fig. 3 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application;

fig. 4 is a schematic view of an application scenario of a gray scale publishing method provided in an embodiment of the present application;

fig. 5 is a schematic flowchart of a gray scale publishing method according to an embodiment of the present application;

fig. 6 is an exemplary diagram for prompting application upgrade according to an embodiment of the present application;

fig. 7 is a schematic flowchart of another gray scale publishing method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

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. Wherein in the description of the embodiments of the present application, "/" indicates an inclusive meaning, for example, a/B may indicate a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, the meaning of "a plurality" is two or more unless otherwise specified.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "such as" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present relevant concepts in a concrete fashion.

In the related art, when a developer updates the version of an application, the code and data of the application are generally required to be updated. The application data includes application content data, cache data, configuration data, user data, and the like. It can be seen that, in the process of upgrading the application by the developer, there is a scenario in which a table structure in the database of the application is changed (for example, a table field is deleted, newly added or renamed). At present, developers can update the version of the application by means of gray release, wherein the gray release is a release manner capable of smoothly transitioning between black and white. That is, the developer first lets some users continue to use the product characteristics a and some users start to use the product characteristics B, and if the users do not have any objection to the product characteristics B, the scope is gradually enlarged and all the users are migrated to the product characteristics B.

At present, in the related art, when the gray scale of the application is released, the following situations are included in the methods and problems that are adopted when the data of the application is upgraded.

In one scheme, when a developer issues the gray scale of an application to be upgraded, a business server and a gray scale server share the same database, the database of the application is not split, and the data table structure of the application is directly upgraded in a production database. In this case, there may be a problem that the application whose version is not upgraded does not match the upgraded data table structure, which causes incompatibility of the application code, and the like, and thus causes some functions of the production database to be limited. For example, the code after the release of the gray scale cannot delete or modify the table fields in the production database. Wherein the production database is used to store data applied in the production environment.

For example, assuming that a field name of an order table in the production database is "commodity name", the database server modifies the field name of the order table in the production database into "commodity name list" in response to the operation of the user during gray release, so that the modified field name meets the requirement of the application after version upgrade. However, when an application with an un-upgraded version initiates a service, an order table with a field name of "commodity name" cannot be searched in the production database. The application with the non-upgraded version is not matched with the upgraded data table structure, so that the code of the application is incompatible.

The environment of the service server is a production environment, and comprises a plurality of mature services or applications which do not need to be tested. I.e. the services or applications configured in the service server do not need to be grey distributed. The gray scale environment and the production environment are distributed to configure services or applications corresponding to the respective environments.

In another scheme, when a developer performs gray scale release on an application to be upgraded, all data in a production database of the application is copied to be used as a gray scale database. When the application to be upgraded is produced and released in the gray scale, the production database and the gray scale database are independent, and when the gray scale releasing system releases the gray scale of the application, only the data in the gray scale database is updated. However, in the process of issuing the gradation to the application by the gradation issuing system, there is a case where data is written in both the production database and the gradation database.

For example, assuming that the application to be upgraded is a shopping application, the version of the shopping application before being upgraded is a V1 version, and the version after being upgraded is a V2 version, in the process of performing gray-scale distribution on the shopping application by the gray-scale distribution system, data when a part of users (for example, ten million users) use the V1 version is added to the production database, and data when a part of users (for example, one hundred thousand users) use the V2 version is added to the gray-scale database, that is, a table (for example, an order table, a user table, etc.) in which data frequently changes occurs in both the production database and the gray-scale database. After the gray level is published, when a developer upgrades the application to a certain version, data in the production database and data in the gray level database need to be unified. Because the same data table in the production database and the gray database may have data written therein by a large number of users, and the users cannot stop writing data into the production database and the gray database, there may be problems of data loss and data asynchronization in the production database and the gray database when unifying the production database and the gray database. In addition, there is a problem that maintenance of correctness of data in the database is costly.

In another scheme, when the developer performs gray release on the application to be upgraded, data of a part of users is stored in the production database, and data of a part of users is stored in the gray database. When the gray scale release system releases the gray scale of the application, when the version to be upgraded of the application has a problem, the gray scale release system cannot close the gray scale environment in real time, so that the business of a user for storing data in the gray scale database is influenced.

In view of the above problems, an embodiment of the present application provides a gray scale publishing method, which is applied to a gray scale publishing system, and migrates data corresponding to a user identifier in a production table to a gray scale table when the system determines that a user identifier of an electronic device sending a service request satisfies a preset condition after the gray scale publishing is started, where the preset condition is that the user identifier is a user identifier of a preset user and a gray scale state corresponding to the user identifier is not started, and the system determines that the data migration is successful and then sends the service request to a gray scale server for corresponding processing. And under the condition that the system determines that the gray state corresponding to the user identification is open, migrating the data corresponding to the user identification in the gray table back to the production table.

According to the method, in the gray level releasing process, the gray level table with the same table structure as that of the production table is added in the production database, the data corresponding to the user identification in the gray level releasing process is written into the gray level table, and the data corresponding to the user identification in the gray level table is migrated and migrated in real time, so that the problems that when the data produced and the data released in the related technology are written into the same database, the table structure of the database is upgraded in the gray level releasing process, the produced application is not matched with the upgraded data table structure, the applied codes are not compatible and the like are solved. In addition, compared with the related art, in the process of gray scale release, different users respectively write data into the production database and the gray scale database to cause upgrading of the application version, and when data unification is performed on the production database and the gray scale database, the problem of data loss exists.

In addition, in the embodiment of the application, the system controls the gray state of the user identifier of the electronic device sending the service request in real time, that is, the system presets the user capable of opening the gray, or the system closes the user with the gray opened in real time, so that the purpose of ensuring that the service of the user can normally run by closing the user with the gray opened in real time when the version to be upgraded of the application has a problem in the gray release process is achieved.

Fig. 1 is an architecture diagram of a gray scale distribution system according to an embodiment of the present application.

As shown in fig. 1, the system may include: a client 110 and a server 120. The server includes a service server 121, a grayscale server 122, and a database server 123. The gray scale release system is used for releasing the gray scale of the application to be upgraded. The application to be upgraded may be a shopping application, a reading application, or a game application, and the application to be upgraded is not limited herein. The gray scale distribution system may include a software program installed at the server. The server 120 may be an application server supporting gray scale distribution. The client 110 is used to interact with a user.

In some embodiments, communication between the client 110 and the server 120 may be implemented through an Application Programming Interface (API) gateway, so as to transmit information such as pictures, videos, texts, audio or other data. The client 110 may be various terminal devices (such as the terminal devices 111, 112, and 113) shown in fig. 1, for example, the client 110 may be an electronic device such as a mobile phone, a tablet computer, a Personal Computer (PC), a Personal Digital Assistant (PDA), a smart watch, a netbook, a wearable electronic device, an Augmented Reality (AR) device, a Virtual Reality (VR) device, an in-vehicle device, a smart car, and a smart audio device, which is not limited in this embodiment.

The API gateway serves as a back-end main entrance of the gray scale publishing system, and is configured to provide different APIs for each client 110. When a user interacts with the client 110, for example, the user needs to use a certain service provided by the client 110 (for example, the user sends information through the client), the client 110 responds to the user operation to generate a corresponding service request, the client sends the service request to the API gateway, and the API gateway determines whether the client 110 can access the grayscale server 122. If the API gateway determines that the client 110 can access the grayscale server 122, the service request is sent to the grayscale server 122, so that the grayscale server 122 performs corresponding processing. If the API gateway determines that the client 110 cannot access the grayscale server 122, the service request is sent to the service server 121 for corresponding processing.

Exemplarily, as shown in fig. 2, fig. 2 is a schematic structural diagram of a gray scale distribution system provided in an embodiment of the present application.

As shown in fig. 2, the gray scale distribution system may include an API gateway, a database server, a service server, and a gray scale server.

The API gateway comprises a gray level decision engine, wherein the gray level decision engine is used for judging whether a user initiating a service request meets a gray level strategy or not, or is also used for judging whether the gray level state of the user is an open state or not.

The database server includes a production database.

The business server comprises a production business service module, and the production business service module is used for correspondingly processing the business request after the business server receives the business request sent by the gray decision engine.

The gray scale server comprises a gray scale business service module and a gray scale data engine. The gray level business service module is used for carrying out corresponding processing on a business request sent by the gray level decision engine after the gray level server receives the business request.

The gray scale data engine is used for migrating data in a production table of the production database into a gray scale, or migrating data in the gray scale back to the production table. Wherein the production table is used for storing data applied in a production environment. The grey scale is used for storing data applied in a grey scale environment.

It should be noted that the gray scale distribution system shown in fig. 1 and fig. 2 is only an example provided in the present embodiment, and should not be construed as limiting the present application.

Exemplarily, fig. 3 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure. The electronic device may be the client. As shown in fig. 3, the electronic device 100 may include a processor 101, an external memory interface 102, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 101 may include one or more processing units, such as: the processor 101 may include an Application Processor (AP), a modem processor, a Graphics Processor (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. The different processing units may be separate devices or may be integrated into one or more processors.

Wherein the controller may be a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the time sequence signal to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 101 for storing instructions and data. In some embodiments, the memory in the processor 101 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 101. If the processor 101 needs to use the instruction or data again, it can be called directly from memory. Avoiding repeated accesses reduces the latency of the processor 101, thereby increasing the efficiency of the system.

In some embodiments, processor 101 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

It should be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only an illustration, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive a charging input from a charger. The charger can be a wireless charger or a wired charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 101.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 101. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 101.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 101.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 101. The wireless communication module 160 may also receive a signal to be transmitted from the processor 101, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 101 may include one or more GPUs that execute program instructions to generate or alter display information.

The electronic device 100 may implement a photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor, etc.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor, which processes input information quickly by referring to a biological neural network structure, for example, by referring to a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 102 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100. The external memory card communicates with the processor 101 through the external memory interface 102, implementing a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headset interface 170D, and the application processor. Such as music playing, recording, etc.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects in response to touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The technical solutions involved in the following embodiments can be implemented in the above grayscale distribution system. The following takes the electronic device 100 as a mobile phone as an example, and exemplifies the gray scale distribution method provided in the embodiment of the present application.

To is in pair

Taking gray release as an example, assuming that the non-upgraded version of the panning is version 1 and the upgraded version is version 2, when gray release is performed, the panning of version 1 operates in the service server, and the panning of version 2 operates in the gray server. In response to the operation of the user, the system adds a grey table with empty data, which has the same table structure as the production table, in the production database, and then carries out upgrading operation on the grey table. For example, if the production table is an order table which does not include a field corresponding to the item name, the system may add a field corresponding to the item name to the grey table.

It can be understood that the production table and the grey table are tables in the same database, the production table is a data table corresponding to the service server, and the grey table is a corresponding data table in the grey server. In the process of gray scale release, data corresponding to the business executed by the business server is written into the production table, and data corresponding to the business executed by the gray scale server is written into the gray scale table.

In the embodiment of the present application, referring to fig. 4, when a user transacts a certain service using an application in a mobile phone, the mobile phone generates a corresponding service request in response to an operation of the user. E.g. in a mobile phone

Application response to userAfter the operation is started, when a user creates a new order to purchase goods by the Taobao application in the mobile phone, the mobile phone responds to the operation of the user to generate a service request for creating the new order.

In the embodiment of the present application, the user may instruct to open the treasure panning in various ways, for example, the user may open the treasure panning by clicking an icon of the treasure panning, may open the treasure panning by a voice instruction, or may also instruct to open the treasure panning by an interval gesture, and the like.

For example, referring to (a) in fig. 4, the operation of opening a tab by the user may be an operation of clicking a tab icon 401 by the user. After the mobile phone detects that the user opens the Taobao operation, a display interface corresponding to the Taobao is displayed in the display interface of the mobile phone.

In the embodiment of the present application, taking the case that a user creates a new order in panning, after the mobile phone detects that the user opens panning, the mobile phone sends a service request for creating a new order to the grayscale decision engine in response to the operation that the user creates a new order in panning.

For example, as shown in fig. 4 (a), when the mobile phone detects that the user clicks the tab icon on the desktop, tab may be started, and an interface as shown in fig. 4 (b) is displayed. The mobile phone may respond to an operation of creating a new order in panning by the user, such as an operation of submitting an order as shown in (c) in fig. 4, and the mobile phone generates a service request for creating a new order in response to the operation of the user.

After the gray level decision engine receives a business request for creating a new order, the gray level decision engine judges whether the user meets a gray level strategy or not and whether a gray level state corresponding to the user is started or not so as to determine whether the business request is sent to a business server for processing or sent to the gray level server for processing.

It can be understood that, when the mobile phone creates a service request of a new order in response to an operation of a user, where the service request of creating the new order may include a new order creation request, an order payment request, a request for checking a delivery status, and the like, if the gray level decision engine determines that the user satisfies a gray level policy and determines that a gray level status corresponding to the user is opened, the gray level decision engine sends the service request to the gray level server for processing. And if the gray level decision engine determines that the gray level state corresponding to the user is not started, the gray level decision engine sends the service request to a service server for processing.

In some embodiments, if the grayscale decision engine determines that the user satisfies the grayscale policy and the grayscale state corresponding to the user is not turned on, the grayscale decision engine determines to send the service request to the grayscale server for processing. The grayscale decision engine first sends a data migration request to the grayscale data engine. And after the gray data engine migrates the data of the user in the production table into the gray table, the gray data engine sends a data migration result to the gray decision engine. And if the gray level decision engine determines that the data migration is successful according to the data migration result, sending the service request for creating the new order to a gray level server for corresponding processing.

After receiving a service request for creating a new order, the grayscale service module in the grayscale server creates a new order for the user according to the service request, and returns corresponding information to the display interface of the mobile phone for display, see (d) in fig. 4.

In other embodiments, if the gray decision engine determines that the user does not satisfy the gray policy or the gray state corresponding to the user is on, the gray decision engine sends the service request to the service server for processing.

The following describes in detail the gray scale issuing method provided in the embodiment of the present application with reference to fig. 5 to 7. Fig. 5 is a schematic flowchart of a gray scale issuing method according to an embodiment of the present application. As shown in fig. 5, a gray scale issuing method provided in the embodiment of the present application may include:

step 501, after the mobile phone detects an operation of opening a panning function by a user, the mobile phone responds to the operation of creating a new order in the panning function by the user, and sends a business request 1 for creating the new order to the grayscale decision engine.

Step 502, the grayscale decision engine determines whether the user satisfies the grayscale policy.

The gray level policy is a preset condition which can be met by a user who can start gray levels. The users meeting the conditions can be users in a certain area, users in a certain age group, or users with the tail numbers of the mobile phone numbers meeting the preset numbers.

In some embodiments, after the user opens the treasure collection and logs in, the mobile phone sends a business request 1 for creating a new order to the grayscale decision engine in response to the operation of the user for creating the new order in the treasure collection. And the gray level decision engine judges whether the user meets the gray level strategy according to the business key value of the business request 1.

Optionally, the service key value of the service request 1 is used to uniquely identify the user sending the service request 1 for creating a new order, for example, the service key value of the service request 1 may be the user identification of the user. And after acquiring the user identification corresponding to the service request 1, the gray level decision engine judges whether the user meets the gray level strategy or not according to the user identification.

It can be understood that after the user registers for panning, the system assigns a unique user identifier to each user, and the user identifier is used for identifying the identity of the user. For example, the user identifier may be an Identity Document (ID) of the user. After the user logs in the treasure removal, the system can acquire various information of the user registered in the treasure removal according to the user identification of the user, such as the age, the address and other information of the user. The user identifier may be carried in the service request 1, or may be independent, and is not limited herein.

For example, assuming that the grayscale policy is the grayscale started by a user in a preset age group, if the age of the user who acquires the new order is not in the preset age group, the grayscale decision engine determines that the user does not conform to the grayscale policy. And if the age of the user who creates the new order is in the preset age range, the gray level decision engine determines that the user accords with the gray level strategy. For example, the grayscale policy is a grayscale opened by a user in an age range from 20 years old to 40 years old, and if the grayscale decision engine obtains that the age of the user creating the new order is 30 years old, the grayscale decision engine determines that the user meets the grayscale policy. If the age of the user who acquires the created new order is 55 years, the gray level decision engine determines that the user does not conform to the gray level policy.

As another example, assuming that the grayscale policy is a user opening grayscale in a preset area, if the address of the user who creates the new order is not in the preset area, the grayscale decision engine determines that the user does not conform to the grayscale policy. And if the address of the user for creating the new order is acquired by the gray level decision engine and is in the preset area, the gray level decision engine determines that the user accords with the gray level strategy. For example, the grayscale policy is that the user whose geographic position is beijing opens the grayscale, and if the geographic position where the grayscale decision engine acquires the user who creates the new order is shanghai, the grayscale decision engine determines that the user does not conform to the grayscale policy. And if the geographic position of the user for creating the new order, which is acquired by the gray level decision engine, is Beijing, the gray level decision engine determines that the user accords with the gray level strategy. In some embodiments, if the grayscale decision engine determines that the user does not satisfy the grayscale policy, then steps 503-505 are performed. If the grayscale decision engine determines that the user satisfies the grayscale policy, step 506 is performed.

Step 503, if the gray decision engine determines that the user does not satisfy the gray policy, the gray decision engine sends a business request 1 for creating a new order to the production business service module.

It can be understood that the user does not belong to the user who tests the new edition of the naught, that is, the gray decision engine determines that the user does not satisfy the gray policy, and the business server performs corresponding processing on the mobile phone in response to the business request 1 of the user for creating a new order.

Step 504, the production business service module creates a new order according to the business request 1, and writes the corresponding data into a production table in the production database.

And 505, the production business service module sends the newly created order to the mobile phone through the API gateway.

In the embodiment of the present application, the grayscale decision engine sends a business request 1 for creating a new order to the production business service module, and after the production business service module receives the business request 1 for creating a new order, the production business service module can create a new order according to the business request 1, and write corresponding data into a production table in the production database. The data corresponding to the new order comprises the data of the Taobao user name, the order quantity, the money amount, the receiving address, the order number, the transaction time and the like. And after the production business service module finishes the business of creating the new order, the newly created order is returned to the mobile phone for displaying through the API gateway. Namely, the Taobao in the mobile phone can display a new order created by the production business service module. Illustratively, as shown in fig. 4 (d), a new order created by the production business service module, that is, an order of a fairy tale purchased by the user is displayed in the interface of the mobile phone.

In step 506, if the grayscale decision engine determines that the user satisfies the grayscale policy, the grayscale decision engine determines whether the grayscale state corresponding to the user identifier is on.

In some embodiments, when the grayscale decision engine determines that the user satisfies the grayscale policy, and the panning in the user's cell phone is still version 1, the grayscale decision engine may prompt the user to upgrade the panning version to version 2, and the cell phone, in turn, upgrades the panning version to version 2 in response to the user's operation. For example, as shown in fig. 6, a prompt message "naobao new version upgrade" may be displayed on the desktop of the mobile phone. And after the mobile phone detects that the user operates the control 'yes', upgrading the Taobao version to a version 2.

Step 507, if the gray level decision engine determines that the gray level state corresponding to the user identifier is open, the gray level decision engine sends the service request 1 for creating a new order to the gray level service module.

In some embodiments, when the grayscale decision engine determines that the user satisfies the grayscale policy, the grayscale decision engine determines that the grayscale state corresponding to the user identifier is on. That is, the grayscale decision engine determines that the user's data has been completely migrated from the production table into the grayscale table. In this case, the gray level decision engine sends a business request 1 for creating a new order to the gray level business service module, and the gray level business service module creates the new order according to the business request 1 and writes corresponding data into the gray level table.

Step 508, if the gray level decision engine determines that the gray level state corresponding to the user identifier is not turned on, the gray level decision engine sends a migration request to the gray level data engine.

The migration request carries a user identifier, so that the gray data engine queries data corresponding to the user from the production table according to the user identifier.

In step 509, the gray scale data engine performs data migration.

It should be noted that the production table of the production database may include at least one data table corresponding to each user. For example, the data tables for each user may include an order table, a payment table, a browsing history table, a shopping cart table, and the like.

In the embodiment of the application, after the gray data engine acquires the data corresponding to the user from the production table according to the user identification, the gray data engine migrates the data corresponding to the user into the gray table. That is, the gray data engine copies the data corresponding to the user into the gray scale.

The grey table is an empty table obtained by copying the table structure of the production table, the table structure of the grey table is completely the same as that of the first data table, and the data is empty. That is, before the grayscale data engine migrates the user's data to the grayscale table, the grayscale table is an empty table. Because the table structure of the grey scale table is the same as that of the production table, when the grey scale data engine migrates the data of the user from the production table to the grey scale table, the data of the user can be directly copied from the production table to the grey scale table, and the condition that the data are lost due to different table structures during data migration is avoided.

In some embodiments, the grey table may be an empty table obtained by copying the table structure of the production table and upgrading the copied data table. For example, the grey table includes the table structure of the production table, and some table structures are added or modified. In the subsequent steps, when the gray data engine creates a new order according to the service request 1 and writes the corresponding data into the gray table, under the scene that a new field is added to the data corresponding to the service request 1, data loss is avoided.

In some embodiments, when the gray scale data engine migrates the data of the user from the production table to the gray scale table, if the data of the user is a plurality of data tables, the gray scale data engine may adopt a multi-thread data migration method to synchronously migrate a plurality of data of the user to the gray scale table, thereby improving the efficiency of data migration.

For example, assuming that the production table includes 5 pieces of order data corresponding to the user, the grayscale data engine copies the 5 pieces of order data of the user from the production table into the grayscale table.

It should be explained that, after the gray scale data engine receives the migration request, only the data of the user is migrated from the production table to the gray scale table, and the data of other users is not migrated, thereby avoiding the loss of data.

Step 510, after the gray data engine completes the data migration, the gray data engine sends the migration result to the gray decision engine.

In step 511, the grayscale decision engine determines whether the migration was successful.

If the gray level decision engine determines that the data table migration is successful, step 512 to step 514 are executed, otherwise step 515 and step 516 are executed.

In step 512, if the grayscale decision engine determines that the migration result is that the data migration is successful, the grayscale state of the user is recorded as on.

Step 513, the grayscale decision engine sends a business request 1 for creating a new order to the grayscale business service module.

In the embodiment of the present application, after the gray decision engine receives the response notification of data migration completion sent by the gray data engine, the gray decision engine sets the gray state of the user to be on.

In some embodiments, the grayscale decision engine may record the grayscale state of each user in a grayscale state cache. For example, the grayscale decision engine may record the grayscale state of the user as on in a grayscale state cache.

In step 506, when the grayscale decision engine determines that the user satisfies the grayscale policy, the grayscale decision engine sends a migration request to the grayscale data engine, and does not send the service request 1 for creating a new order. And when the gray level decision engine determines that the gray level state of the user is the opening state, the gray level decision engine sends a business request 1 for creating a new order to the gray level business service module.

And step 514, the gray scale service module creates a new order according to the service request 1 and writes the corresponding data into the gray scale.

In the embodiment of the application, after receiving the business request 1 for creating a new order, the gray business service module writes data when creating the new order into the gray table, so that the data corresponding to the user identifier is modified in the gray table.

For example, assuming that the gray scale data engine has migrated the 5 pieces of order data used in the production table into the gray scale table, after the gray scale business service module creates a new order according to the business request 1, the gray scale business service module adds data corresponding to the new order to the 6 th piece of order data in the gray scale table.

Step 515, if the grayscale decision engine determines that the migration result is a data migration failure, then record the grayscale status of the user as a failure.

In step 516, the grayscale decision engine notifies the grayscale data engine to perform a rollback deletion operation on the data in the grayscale table corresponding to the user identifier.

The rollback refers to a behavior of restoring the program or the data to a last correct state due to a program or data processing error. Rollback includes types of program rollback and data rollback. The rollback deletion operation herein refers to an operation of deleting data corresponding to the user identifier in the gray table, so as to restore the data corresponding to the user identifier in the gray table to a state before data migration.

And if the gray decision engine determines that the data migration fails or the data migration is overtime according to the received migration result, the gray decision engine records the gray state of the user as failure in the gray state cache and informs the gray data engine to perform rollback deletion operation of the gray table data corresponding to the user identification.

In the embodiment of the application, after the grayscale decision engine determines that data migration fails, after the grayscale decision engine receives a new service request (for example, a payment order request) sent by a mobile phone, the grayscale decision engine sends the new service request to the production service module, and the production service module writes corresponding data into a production table in the production database according to the received new service request. That is, after the gray level decision engine determines that the data migration fails, the subsequent service request does not perform data migration.

It is to be understood that the operation of creating a new order in the production business service module in the business server is an operation performed in version 1 of panning, and the operation of creating a new order in the grayscale business service module in the grayscale server is an operation performed in version 2 of panning. When the gray scale releasing system releases the gray scale, the gray scale decision engine determines that a user creating a new order meets a gray scale strategy, and the business creating the new order is executed by the gray scale business service module. That is, the Taobao running in the user's handset is version 2.

In the embodiment of the application, after the gray scale issuing system determines that the verification of the version 2 of the panning baby meets the preset condition, the gray scale issuing system turns off a switch for issuing the gray scale of the panning baby in response to the operation of a user. For example, the gray release system determines that the verification of the version 2 of the panning operation reaches a preset time period (e.g., 12 hours, 24 hours, etc.), and the developer turns off the main switch of the gray release of the panning operation. Alternatively, the gray release system determines that a preset number of users have used the panning version 2, and the developer turns off the panning gray release main switch.

After the gray release main switch of the Taobao in the mobile phone is turned off in response to the user operation, the user purchases the commodity at the Taobao again, namely, the user creates a new order at the Taobao again. And the mobile phone responds to the operation of creating a new order by the user and sends a business request 2 for creating the new order to the gray level decision engine. And the gray level decision engine determines the gray level state of each user to be open according to the gray level state of each user recorded in the gray level state cache. That is, the gray scale data engine has migrated the user's data from the production table to the gray scale where all the user's data is stored. In this case, the grayscale decision engine notifies the grayscale data engine to migrate the data corresponding to the user from the grayscale table back to the production table. And the gray data engine sends the migration result to the gray decision engine after migrating the user data in the gray table to the production table. And the gray decision engine determines that the data of the user is migrated back to the production table according to the migration result, the gray decision engine sends a service request 2 for creating a new order to the production service module, and the production service module creates the new order according to the service request 2 and writes the corresponding data into the production table.

It should be explained that, the above-mentioned mobile phone triggers the gray data engine to return the data corresponding to the user from the gray table to the production table in response to the operation of the user to purchase goods in the Taobao, which is only an exemplary description. After the main switch for releasing the gray scale of the panning responds to the user operation and is closed, the user opens the panning again, after the mobile phone responds to any operation of the user (for example, the user logs in the panning, browses commodities, checks purchase records and the like) and initiates a first service request, the gray scale decision engine can trigger the gray scale data engine to transfer the data corresponding to the user from the gray scale table to the production table under the condition that the gray scale state of the user is determined to be opened according to the gray scale state of each user recorded in the gray scale state cache.

The above process is described in detail below with reference to fig. 7. As shown in fig. 7, the gray scale publishing method provided in the embodiment of the present application may further include:

step 701, the mobile phone sends a service request 2 for creating a new order to the grayscale decision engine in response to an operation of creating the new order by the user in panning.

In the embodiment of the application, after the grayscale release of the panning in the mobile phone is closed, the user purchases the commodity at the panning again, that is, the user creates a new order at the panning again, and the mobile phone sends a service request 2 for creating the new order to the grayscale decision engine.

The implementation process of step 701 may refer to the implementation process of step 501, and is not described herein again.

In step 702, the gray level decision engine determines that the gray level state corresponding to the user is on.

In the embodiment of the present application, after receiving the service request 2, the gray level decision engine queries that the gray level state corresponding to the user is on from the gray level state cache according to the user identifier of the user. That is, the user has accessed the grayscale server, and the grayscale distribution system has performed grayscale distribution verification for the user.

Step 703, the gray level decision engine sends a data migration request to the gray level data engine.

And the data migration request is used for the gray scale data engine to migrate the data corresponding to the user in the gray scale table in the production database back to the production table. The data migration request carries the user identifier of the user.

In the embodiment of the present application, the grayscale decision engine determines that the grayscale process corresponding to the user is finished, and the grayscale decision engine sends a data migration request to the grayscale data engine, so that the grayscale data engine migrates the data corresponding to the user in the grayscale table in the production database to the production table.

In step 704, the gray data engine migrates the user's data in the gray list back to the production list.

The data of the user in the gray scale comprises data stored when the user uses the version 2 of Taobao (for example, data for creating an order, data for paying the order, and the like), and data migrated from the production table to the gray scale by the gray scale data engine before the user performs the gray scale business process.

In the embodiment of the application, after the gray data engine receives the data migration request, the gray data engine queries the data corresponding to the user in the gray scale according to the user identification. After the gray data engine deletes the user's data in the production table, the user's data in the gray table is copied to the production table. Therefore, the gray level decision engine determines that the user has finished gray level release verification, and the gray level data engine carries out real-time migration on the user data in the gray level table, so that the consistency of the user data in the production table is ensured, and the situation that the data is lost when the gray level data engine migrates the user data from the gray level table to the production table is avoided.

For example, assuming that the production table includes 5 pieces of order data of the user, after the gray scale data engine migrates the data of the user in the production table to the gray scale table, the gray scale table includes 5 pieces of order data of the user. When the user uses Taobao version 2, the gray level business service module adds 2 pieces of order data in the gray scale. I.e. 7 order data for the user are included in the grey scale. After the gray data engine receives the data migration request sent by the gray decision engine, the gray data engine deletes the 5 pieces of order data of the user in the production table, and copies the 7 pieces of order data of the user in the gray table into the production table. Therefore, the situation that the data of the user is repeatedly stored in the production table and the data is lost in the process of data migration is avoided.

In one case, assuming that the gray table stores the balance data of the user, when the user initiates a new order request, the mobile phone makes a payment in response to the payment operation of the user, and then the balance data of the user in the gray table is changed. In this case, when the gray data engine migrates the user's data in the gray table back to the production table, the gray data engine deletes the user's data in the production table and copies the user's data in the gray table to the production table, thereby avoiding the loss in the data migration process.

Step 705, the gray data engine sends the transition result to the gray decision engine.

In the embodiment of the application, after the gray data engine migrates the data of the user in the gray table back to the production table, the gray data engine sends the migration result to the gray decision engine.

In step 706, the grayscale decision engine determines whether the migration was successful.

If the gray level decision engine determines that the data migration is successful according to the received migration result, step 707 and step 708 are executed. Otherwise, step 709 is performed.

And 707, if the gray level decision engine determines that the data migration is successful, sending a service request 2 for creating a new order to the production service module.

Step 708, the production business service module creates a new order according to the business request 2, and writes the corresponding data into the production table.

And if the gray level decision engine determines that the data migration is successful according to the migration result, indicating that the gray level data engine has migrated the data of the user in the gray level table to the production table. I.e. all data of the user are included in the production table. The gray level decision engine sends a business request 2 for creating a new order to the production business service module, and the production business service module creates the new order according to the business request 2 and writes corresponding data into a production table.

If the gray level decision engine determines that the data migration is successful according to the migration result, the gray level decision engine can delete the gray level state of the user in the gray level state cache.

And 709, prompting the operation and maintenance personnel to perform manual processing by the gray decision engine.

And if the gray decision engine determines that the data migration fails according to the migration result or determines that the data migration is overtime, the gray decision engine reports an alarm to inform operation and maintenance personnel to perform manual processing.

In some embodiments, the grayscale decision engine may prompt the operation and maintenance staff that the data migration fails by sending a prompt message to prompt the operation and maintenance staff to perform manual processing. For example, the grayscale decision engine sends information such as a short message or an email to the operation and maintenance staff to prompt the operation and maintenance staff to perform manual processing.

In other embodiments, the grayscale decision engine may trigger an alarm lamp of the grayscale issuing system to prompt the operation and maintenance personnel to perform manual processing through the alarm lamp.

It should be noted that the manner in which the grayscale decision engine prompts the operation and maintenance staff is described as an example, and any other implementation manners are also applicable to the present application, and are not limited herein. For example, the grayscale decision engine may also trigger a voice prompt to prompt the operation and maintenance staff to perform manual processing, and so on.

Because the gray level decision engine determines that the data migration corresponding to the user fails, after receiving the prompt of manual intervention, the operation and maintenance personnel can distribute the service request 2 for creating a new order to the gray level environment for processing. Namely, the operation and maintenance personnel can manually send the business request 2 for creating the new order to the gray-scale business service module, so that the gray-scale business service module creates the new order according to the business request 2 and writes the corresponding data into the gray-scale table.

In the embodiment of the present application, a grayscale publishing process of panning is taken as an example, and a grayscale publishing method is exemplarily described, and in practical application, the grayscale publishing method is suitable for grayscale publishing in any application, and is not limited herein.

In the embodiment of the application, the gray level decision engine determines whether a user initiating a service request meets a gray level strategy or not so as to accurately determine a server for processing the service request, thereby improving the accuracy of gray level release. And if the gray level decision engine determines that the user initiating the service request meets the gray level strategy and the gray level state of the user is not opened, the gray level data engine migrates the data of the user from the production table to the gray level table. After the gray level decision engine determines that the data migration is successful, the gray level decision engine sends the service request initiated by the user to a gray level service module for corresponding processing. If the gray data engine determines that the user has completed the gray release verification, the gray data engine migrates the user's data from the gray table back to the production table. In the process of gray scale release, the gray scale data engine carries out migration and back migration on the data of the user. Therefore, the grey scale with the same structure as the produced table is added in the production database, the data corresponding to the user identification in the grey scale releasing process is written into the grey scale, and the data corresponding to the user identification in the grey scale are migrated and returned in real time, so that the problem that the table structure of the database cannot be changed when the code after the grey scale releasing is incompatible with the code before the grey scale releasing after the data of the production and the grey scale releasing are written into the same database in the related technology is solved, and the scene of the grey scale releasing is not limited.

In addition, the gray scale release system can control the on and off of the main switch of the gray scale release in real time, and the aim of ensuring that the business of a user using the upgraded version can normally run by closing the switch of the gray scale release in real time when the version to be upgraded of the application has a problem in the gray scale release process is fulfilled.

It can be seen that, in the embodiment of the present application, by adding a gray scale table with the same table structure as the production table in the production database and by migrating and migrating data corresponding to the user initiating the service request, the problem that when the service server and the gray scale server share the same database, version codes are required to be compatible, and a scenario of table field deletion and renaming is not supported, which results in a limited gray scale release scenario, is solved, and when the databases of the service server and the gray scale server are independent, different users write data into the production database and the gray scale database respectively, which results in upgrading the applied version, and unifying the production database and the gray scale database, there is a problem of data loss.

As shown in fig. 8, an embodiment of the present application discloses an electronic device, which may be the foregoing mobile phone. The electronic device may specifically include: a touch screen 801, the touch screen 801 including a touch sensor 806 and a display 807; one or more processors 802; a memory 803; one or more application programs (not shown); and one or more computer programs 804, which may be connected via one or more communication buses 805. Wherein the one or more computer programs 804 are stored in the memory 803 and configured to be executed by the one or more processors 802, the one or more computer programs 804 include instructions that can be used to perform the relevant steps in the embodiments described above.

It is to be understood that the electronic devices and the like described above include hardware structures and/or software modules for performing the respective functions in order to realize the functions described above. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present invention.

In the embodiment of the present application, the electronic device and the like may be divided into functional modules according to the method example, for example, each functional module may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In a case of adopting a manner that each function module is divided corresponding to each function, the electronic device according to one possible composition diagram of the above embodiment may include: display unit, transmission unit and processing unit etc. It should be noted that all relevant contents of each step related to the method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Embodiments of the present application also provide a server including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, the one or more memories are for storing computer program code comprising computer instructions which, when executed by the one or more processors, cause the server to perform the associated method steps described above to implement the gray scale publishing method in the above embodiments.

Embodiments of the present application further provide a computer-readable storage medium, in which computer instructions are stored, and when the computer instructions are run on an electronic device, the electronic device is caused to execute the above related method steps to implement the gray scale publishing method in the above embodiments.

Embodiments of the present application further provide a computer program product, which includes computer instructions, when the computer instructions are run on an electronic device, cause the electronic device to execute the above related method steps to implement the gray scale issuing method in the above embodiments.

In addition, embodiments of the present application also provide an apparatus, which may be specifically a chip, a component or a module, and may include a processor and a memory connected to each other; the memory is used for storing computer execution instructions, and when the apparatus runs, the processor can execute the computer execution instructions stored by the memory, so that the apparatus executes the gray scale issuing method executed by the electronic device in the above method embodiments.

The server, the computer-readable storage medium, the computer program product, or the apparatus provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the server can refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application, in essence or part of the technical solutions contributing to the prior art, or all or part of the technical solutions, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A gray scale issuing method is applied to a gray scale issuing system, the system comprises an electronic device, a gateway, a database server, a service server and a gray scale server, and the method comprises the following steps:

the gateway receives a first service request sent by the electronic equipment, wherein the first service request carries a user identifier;

under the condition that the gateway determines that the user identification meets the preset condition, the gateway sends a data migration request to the gray scale server, wherein the data migration request carries the user identification;

the gray scale server migrates the data corresponding to the user identification from a production table to a gray scale according to the data migration request, wherein the production table is a data table corresponding to the service server, the gray scale is a data table corresponding to the gray scale server, and the gray scale is a data table obtained by copying the table structure of the production table or a data table obtained by upgrading the data table obtained by copying the table structure of the production table;

and under the condition that the gateway determines that the data migration is successful, the gateway sends the first service request to the gray scale server so that the gray scale server executes corresponding response operation according to the first service request.

2. The method according to claim 1, wherein the preset condition includes that the user identifier is a user identifier of a preset user, and a gray state corresponding to the user identifier is not turned on.

3. The method of claim 1, wherein before the gateway receives the first service request sent by the electronic device, the method further comprises:

responding to the operation of a user, and adding the grey table in a production database of the database server;

and responding to the operation of a user, and enabling a gray scale distribution main switch by the gateway.

4. The method of claim 1, wherein the grayscale server performs a corresponding response operation according to the first service request, including:

and the gray server executes the gray service corresponding to the first service request and writes the data corresponding to the gray service into the gray table.

5. The method according to any one of claims 1-4, further comprising:

and under the condition that the gateway determines that the user identifier is not the user identifier of the preset user, the gateway sends the first service request to the service server so that the service server executes corresponding response operation according to the first service request.

6. The method of claim 5, wherein the service server performs a corresponding response operation according to the first service request, and wherein the response operation comprises:

and the service server executes the production service corresponding to the first service request and writes the data corresponding to the production service into the production table.

7. The method according to any one of claims 1-4, further comprising:

under the condition that the gateway determines that the data migration is successful, the gateway sets the gray state corresponding to the user identification to be on;

and under the condition that the gateway determines that the data migration is not successful, the gateway sets the gray state corresponding to the user identification as failure, and informs the gray server of performing rollback deletion operation on the data corresponding to the user identification in the gray table.

8. The method according to any one of claims 1-4, further comprising:

responding to the operation of a user, and closing a main gray scale release switch by the gateway;

the gateway receives a second service request sent by the electronic equipment, wherein the second service request carries the user identifier;

under the condition that the gateway determines that the gray scale state corresponding to the user identification is open, the gateway sends a data migration request to the gray scale server;

the gray scale server returns the data corresponding to the user identification from the gray scale to the production table according to the data return request;

and under the condition that the gateway determines that the data migration is successful, the gateway sends the second service request to the service server so that the service server executes corresponding response operation according to the second service request.

9. The method of claim 8, wherein before migrating the data corresponding to the user identifier from the grey table back to the production table, the method further comprises:

and the gray server deletes the data corresponding to the user identification in the production table.

10. The method of claim 8, further comprising:

and under the condition that the gateway determines that the data is not successfully migrated back, the gateway prompts operation and maintenance personnel to carry out manual processing.

11. A gray scale publishing method is applied to a gateway, and is characterized by comprising the following steps:

receiving a first service request, wherein the first service request carries a user identifier;

sending a data migration request to a gray scale server under the condition that the user identifier is determined to meet a preset condition, wherein the data migration request carries the user identifier, the gray scale server is used for migrating data corresponding to the user identifier from a production table to a gray scale according to the data migration request, the production table is a data table corresponding to the service server, the gray scale is a data table corresponding to the gray scale server, and the gray scale is a data table obtained by copying a table structure of the production table or a data table obtained by upgrading the data table obtained by copying the table structure of the production table;

and under the condition that the data migration is determined to be successful, sending the first service request to the gray scale server.

12. The method according to claim 11, wherein the preset condition includes that the user identifier is a user identifier of a preset user, and a gray state corresponding to the user identifier is not turned on.

13. The method of claim 11, wherein prior to receiving the first service request, the method further comprises:

and opening a gray scale release main switch.

14. The method according to any one of claims 11-13, further comprising:

and sending the first service request to a service server under the condition that the user identification is determined not to be the user identification of the preset user.

15. The method according to any one of claims 11-13, further comprising:

setting the gray state corresponding to the user identification as open under the condition of determining that the data migration is successful;

and under the condition that the data migration is not successful, setting the gray state corresponding to the user identification as failure, and informing the gray server to perform rollback deletion operation on the data corresponding to the user identification in the gray table.

16. The method according to any one of claims 11-13, further comprising:

receiving a second service request, wherein the second service request carries the user identifier;

under the condition that the gray state corresponding to the user identification is determined to be open, sending a data migration request to the gray server;

and under the condition that the data migration is determined to be successful, sending the second service request to a service server.

17. The method of claim 16, further comprising:

and prompting operation and maintenance personnel to perform manual processing under the condition that the data is determined to be unsuccessfully migrated back.

18. A gray scale issuing method is applied to a gray scale server, and is characterized by comprising the following steps:

receiving a data migration request sent by a gateway, wherein the data migration request carries a user identifier, the data migration request is sent to a gray scale server under the condition that the user identifier is determined to meet a preset condition after a first service request sent by electronic equipment is received by the gateway, and the first service request carries the user identifier;

according to the data migration request, migrating the data corresponding to the user identification from a production table to a gray table, wherein the production table is a data table corresponding to a service server, and the gray table is a data table obtained by copying the table structure of the production table by the gray server and upgrading the copied data table;

and after receiving the first service request sent by the gateway, executing corresponding response operation according to the first service request, wherein the first service request is sent to the gray scale server under the condition that the gateway determines that the data migration is successful.

19. The method according to claim 18, wherein the preset condition includes that the user identifier is a user identifier of a preset user, and a gray state corresponding to the user identifier is not turned on.

20. The method according to claim 18 or 19, wherein the performing the corresponding response operation according to the first service request comprises:

and executing the gray level service corresponding to the first service request, and writing the data corresponding to the gray level service into the gray level table.

21. The method of claim 18 or 19, further comprising:

and after the rollback deletion operation sent by the gateway is received, performing the rollback deletion operation on the data corresponding to the user identification in the gray table.

22. The method of claim 18 or 19, further comprising:

receiving a data migration request sent by the gateway, where the data migration request is sent when the gateway determines that the gray state corresponding to the user identifier is on after receiving a second service request sent by the electronic device, and the second service request carries the user identifier;

and according to the data migration request, migrating the data corresponding to the user identification from the grey table to the production table.

23. The method of claim 22, wherein before migrating the data corresponding to the user identifier from the grey table back to the production table, the method further comprises:

and deleting the data corresponding to the user identification in the production table.

24. A gradation issuing system characterized by comprising:

a gateway for performing the gray scale publishing method of any one of claims 11-17 above;

a gray server for executing the gray distribution method of any one of claims 18 to 23 above;

25. The system of claim 24,

and the service server is also used for executing corresponding response operation according to a second service request after receiving the second service request sent by the gateway under the condition that the gateway determines that the data migration is successful.

26. An electronic device, comprising:

one or more processors;

a memory;

wherein the memory has stored therein one or more computer programs comprising instructions which, when executed by the server, cause the server to perform the gray scale publishing method of any one of claims 1-10.

27. A gateway, comprising:

one or more processors;

a memory;

wherein the memory has stored therein one or more computer programs comprising instructions which, when executed by the server, cause the server to perform the gray scale publishing method of any one of claims 11-17.

28. A server, comprising:

one or more processors;

a memory;

wherein the memory has stored therein one or more computer programs comprising instructions which, when executed by the server, cause the server to perform the gray scale publishing method of any one of claims 18-23.

29. A computer readable storage medium having instructions stored thereon, which when executed on a processor perform the gray scale issue method of any one of claims 1 to 10, or perform the gray scale issue method of any one of claims 11 to 17, or perform the gray scale issue method of any one of claims 18 to 23.