CN114780512B

CN114780512B - Gray release method, system and server

Info

Publication number: CN114780512B
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: 2023-05-12
Anticipated expiration: 2042-03-22
Also published as: CN114780512A

Abstract

A gray level 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 gray level release causes some limited functions of the database. The method is applied to a gray level release system, the system comprises electronic equipment, a gateway, a database server, a service server and a gray level server, and the gray level release 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; when the gateway determines that the user identifier meets the preset condition, the gateway sends a data migration request to the gray server, the gray server migrates data corresponding to the user identifier from a production table to the gray table according to the data migration request, the production table is a data table corresponding to the service server, and when the gateway determines that the data migration is successful, the gateway sends a first service request to the gray server, so that the gray server executes corresponding response operation according to the first service request.

Description

Gray release method, system and server

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a gray level publishing method, system, and server.

Background

With the rapid development of computer technology, various Applications (APP) are widely used in people's life, so developers of various applications need to update applications according to the needs of users continuously, so as to keep users or attract more users. In order to avoid the influence of user service caused by the problem of application quality after the update of the application, developers generally upgrade the application by adopting a gray level release method. I.e. the developer issues the new version of application to the application server in advance, and then uses a small part of service to perform functional verification to verify whether the new version of application has quality problems.

In the related art, when a developer upgrades a version of an application, it is generally required 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, there is a scenario in which a table structure in a database of the application is changed (e.g., a table field is deleted, added, renamed, etc.).

However, when the developer upgrades the version of the application in a gray level release manner, the upgrade operation is directly performed on the data table structure in the database of the application, that is, the produced application is not matched with the changed data table structure, so that the code of the application is incompatible. Thus, some functions in the database of the application are limited, for example, the updated version of the application cannot delete the table field in the database of the application, modify the name, etc., thereby resulting in a limited gray level release scenario.

Disclosure of Invention

The embodiment of the application provides a gray level release method, a gray level release system and a gray level release server, wherein when the gray level release is started, the system determines that user identification of an electronic device sending a service request meets the preset condition, data corresponding to the user identification in a production table are migrated to the gray level table, wherein the preset condition is that the user identification is the user identification of a preset user and the gray level state corresponding to the user identification is unopened, and when the system determines that the gray level state corresponding to the user identification is opened, the data corresponding to the user identification in the gray level table are migrated back to the production table. Therefore, in the gray level release process, the system carries out real-time migration and back migration 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 level release is solved.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, an embodiment of the present application provides a gray scale publishing method, 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 publishing method includes: 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 identifier meets the preset condition, the gateway sends a data migration request to the gray server, wherein the data migration request carries the user identifier; the gray server transfers data corresponding to the user identifier from a production table to a gray table according to the data transfer request, wherein 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 the table structure of the production table or a data table obtained by upgrading the copied data table of 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 server so that the gray server executes corresponding response operation according to the first service request.

It can be seen that the corresponding data is directly written into the production database when the gray level is released compared with the prior art, wherein the production database is the database of the application. In the embodiment of the application, the gray scale table with the same table structure as the production table is newly added in the production database, so that the system carries out real-time migration on the data corresponding to the user identifier in the gray scale release process, thereby ensuring the consistency of the data in the production database and solving the problem that certain functions in the production database are limited after gray scale release.

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

In other embodiments, in the gray level distribution process, a gray level table is added to a production database of the database server, where the gray level table is a data table obtained by copying a table structure of the production table and upgrading the copied data table. For example, the gray scale 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 for uniquely marking a user corresponding to the electronic device that initiates the first service request.

In one possible implementation, the preset condition includes a user identifier of the user being preset, and a gray state corresponding to the user identifier is unopened.

It will be appreciated that the developer may preset the user-openable gray level of some users, for example, the user-openable gray level of a certain age group, or the user-openable gray level of a certain region.

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

In another possible implementation manner, the gray 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.

That is, after the gray server migrates the data corresponding to the user identifier in the production table to the gray table, the gray server may execute the gray service corresponding to the first service request and write the corresponding data into the gray table, so as to modify the data corresponding to the user identifier in the gray table. For example, the gray server performs operations such as adding, deleting, modifying, etc. on the data corresponding to the user identifier in the gray table.

In another possible implementation manner, the gray scale publishing 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 service server performs a corresponding response operation according to the first service request, including: 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, when the gateway determines that the user corresponding to the user identifier does not start gray level publishing, the service server executes the production service corresponding to the first service request and writes the corresponding data into the production table, thereby realizing modification of the data corresponding to the user identifier in the production table. For example, the service server performs operations such as adding, deleting, modifying and the like on the data corresponding to the user identifier in the production table.

In another possible implementation manner, the gray scale publishing 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 identifier as on; and under the condition that the gateway determines that the data migration is unsuccessful, the gateway sets the gray state corresponding to the user identifier as failure and informs the gray server to perform rollback deletion operation on the data corresponding to the user identifier in the gray table.

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

It can be understood that, because the data migration is unsuccessful, the production table further includes data corresponding to the user identifier, and the gray scale table may include part of the data corresponding to the user identifier. In this case, the gray server may delete the data corresponding to the user identifier in the gray table, so that the gray table is restored to the state before the data is migrated.

In another possible implementation manner, the gray scale publishing method further includes: responding to the operation of a user, and closing a gray level release master switch by a gateway; the gateway receives a second service request sent by the electronic equipment, wherein the second service request carries a user identifier; when the gateway determines that the gray state corresponding to the user identifier is on, the gateway sends a data migration request to the gray server; the gray server reverts the data corresponding to the user identification from the gray table to the production table according to the data reverting request; and under the condition that the gateway determines that the data returning 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.

It can be understood that when the gray level decision engine determines that the user has completed gray level release verification, the gray level data engine carries out real-time migration on the data of the user 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 returns the data of the user from the gray level table to the production table is avoided.

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

That is, when the gray server transfers the data corresponding to the user identifier from the gray table to the production table, the gray server firstly deletes the data corresponding to the user identifier in the production table, and copies the data corresponding to the user identifier in the gray table to the production table, thereby avoiding the repeated storage of the data of the user in the production table and avoiding the situation of data loss in the process of data transfer.

In another possible implementation manner, the gray scale publishing method further includes: and under the condition that the gateway determines that the data migration is unsuccessful, the gateway prompts operation and maintenance personnel to perform manual processing.

In a second aspect, the present application provides another gray scale publishing method, applied to a gateway, the method including: receiving a first service request, wherein the first service request carries a user identifier; under the condition that the user identification meets the preset condition, a data migration request is sent to a gray server, wherein the data migration request carries the user identification, the gray server is used for migrating 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 a 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 a data table obtained by copying a table structure of the production table; in determining data migration in the event of a success of this type, and sending the first service request to the gray server.

In another possible implementation manner, before receiving the first service request, the gray level publishing method further includes: and starting the gray level release master switch.

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

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

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

In another possible implementation manner, the gray scale publishing method further includes: and prompting operation and maintenance personnel to perform manual processing under the condition that the data returning is not successful.

In a third aspect, the present application provides a 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 server under the condition that the user identifier meets 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 identifier 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 a table structure of the production table by the gray server and upgrading the copied data table; 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 server under the condition that the gateway determines that data migration is successful.

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

In another possible implementation manner, the gray scale publishing method further includes: and after receiving the rollback deletion operation sent by the gateway, performing rollback deletion operation on the data corresponding to the user identifier in the gray scale table.

In another possible implementation manner, the gray scale publishing method further includes: receiving a data migration request sent by the gateway, wherein 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 equipment, and the second service request carries the user identifier; and returning the data corresponding to the user identification from the gray scale table to the production table according to the data returning request.

In another possible implementation manner, before the data corresponding to the user identifier is migrated from the gray scale table 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, including:

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

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

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 one possible implementation manner, the service server is further configured to execute a corresponding response operation according to the second service request after receiving the second service request sent by the gateway if the gateway determines that the data migration is successful.

In a fifth aspect, the present application provides an electronic device, comprising: one or more processors; a memory; wherein the memory stores one or more computer programs, the one or more computer programs comprising instructions that, when executed by the electronic device, cause the electronic device to perform the grayscale distribution method of any of the first aspects described above.

In a sixth aspect, the present application provides a gateway, comprising: one or more processors; a memory; wherein the memory stores one or more computer programs, the one or more computer programs comprising instructions that, when executed by the electronic device, cause the electronic device to perform the grayscale distribution method of any of the second aspects described above.

In a seventh aspect, the present application provides a server, comprising: one or more processors; a memory; wherein the memory stores one or more computer programs, the one or more computer programs comprising instructions that, when executed by the electronic device, cause the electronic device to perform the grayscale distribution method of any of the third aspects described above.

In an eighth aspect, the present application provides a computer-readable storage medium having instructions stored therein, which when run on a processor, perform the grayscale distribution method according to any one of the first aspects, perform the grayscale distribution method according to any one of the second aspects, and perform the grayscale distribution method according to any one of the third aspects.

In a ninth aspect, the present application provides a computer program product comprising computer instructions which, when run on a processor, perform the greyscale publishing method according to any one of the first aspects, perform the greyscale publishing method according to any one of the second aspects, and perform the greyscale publishing method according to any one of the third aspects.

The corresponding advantages of the other aspects mentioned above may be found in the description of the advantages of the method aspects, and are not repeated here.

Drawings

Fig. 1 is a schematic diagram of a gray scale publishing system according to 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 of an electronic device according to an embodiment of the present application;

Fig. 4 is an application scenario schematic diagram of a gray level publishing method provided in an embodiment of the present application;

fig. 5 is a schematic flow chart of a gray level publishing method according to an embodiment of the present application;

FIG. 6 is an exemplary diagram of a hint application upgrade provided by embodiments of the present application;

fig. 7 is a flow chart of another gray level 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, "/" means or is meant unless otherwise indicated, for example, a/B may represent a or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.

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

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the related art, when a developer performs version upgrade on an application, it is generally required to upgrade both code and data of the application. The application data comprises application content data, cache data, configuration data, user data and the like. It can be seen that in the process of upgrading an application by a developer, there is a scenario in which a table structure in a database of the application is changed (e.g., a table field is deleted, added, renamed, etc.). Currently, a developer can update a version of an application through a gray level distribution mode, wherein gray level distribution refers to a distribution mode capable of smoothly transiting between black and white. That is, the developer first makes a part of users continue to use the product characteristic A, and a part of users start to use the product characteristic B, and if the users do not have objection to the product characteristic B, the developer gradually expands the range and all users are migrated to the product characteristic B.

At present, when the gray level of the application is released in the related art, the method adopted when the data of the application is upgraded and the problems exist include the following cases.

In one scheme, when a developer performs gray level release on an application to be upgraded, a service server and a gray level server share the same database, and the database of the application is not split, but the data table structure of the application is directly upgraded in a production database. In this case, there may be a problem that the version of the application that is not upgraded does not match the updated data table structure, resulting in incompatibility of the code of the application, and thus, some functions of the production database are limited. For example, the code after gray release cannot delete, modify names, etc. the table fields in the production database. Wherein the production database is used for storing data applied in the production environment.

For example, assuming that a field name of an order table in a production database is "commodity name", the database server responds to the operation of a user in gray level release, and modifies the field name of the order table in the production database into "commodity name list", 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 queried in the production database. The version of the application which is not upgraded is not matched with the data table structure after upgrading, so that the code of the application is incompatible.

The service server environment is a production environment, and includes mature services or applications without testing. I.e. the service or application configured in the traffic server does not need to be greyscale distributed. The gray scale environment and the production environment are distributed and configured with the service or application corresponding to the respective environments.

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

For example, assume that an application to be upgraded is a shopping application, a version before the upgrading of the shopping application is a V1 version, a version after the upgrading is a V2 version, in the process of gray-scale publishing the shopping application by the gray-scale publishing system, data when a part of users (for example, ten million users) use the V1 version is added to a production database, and data when a part of users (for example, ten thousand users) use the V2 version is added to a gray-scale database, that is, tables (for example, order tables, user tables, and the like) with frequent changes of data in both the production database and the gray-scale database. After the gray level release is finished, when a developer raises the application to a certain version, the data in the production database and the gray level database need to be unified. Since the same data table in the production database and the gray database may be written with data by a large number of users, and the writing of data by the users into the production database and the gray database cannot be stopped, there is a possibility that data is lost when the production database and the gray database are unified, and the data in the production database and the gray database are not synchronized. In addition, there is a problem in that the cost of maintaining the correctness of the data in the database is high.

In yet another scheme, when the developer issues the gray level of the application to be upgraded, a part of the user's data is stored in the production database, and a part of the user's data is stored in the gray level database. When the gray level release system releases the gray level of the application, and when the version to be upgraded of the application has a problem, the gray level release system cannot close the gray level environment in real time, so that the service of a user with data stored in the gray level database is influenced.

In view of the above problems, an embodiment of the present application provides a gray level distribution method, which is applied to a gray level distribution system, where after gray level distribution is started, the system determines that a user identifier of an electronic device sending a service request meets a preset condition, and transfers data corresponding to the user identifier in a production table to a gray level table, where the preset condition is a user identifier of a user whose user identifier is preset and a gray level state corresponding to the user identifier is unopened, and after the system determines that data transfer is successful, the system sends the service request to a gray level server to perform corresponding processing. And under the condition that the system determines that the gray state corresponding to the user identifier is on, returning the data corresponding to the user identifier in the gray table to the production table.

According to the method, in the gray level release process, the gray level table which is the same as the table structure of the production table is added in the production database, data corresponding to the user identifier in the gray level release process are written into the gray level table, and real-time migration and return are carried out on the data corresponding to the user identifier in the gray level table, so that the problems that when the data of production and gray level release in the related art are written into the same database, after the table structure of the database is updated in gray level release, the produced application is incompatible with the updated data table structure, and the like are solved. In addition, compared with the related art, in the gray level release process, different users write data into the production database and the gray level database respectively, so that the version of the application is updated, when the data of the production database and the gray level database are unified, 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, namely, the system presets the user capable of starting the gray, or the system closes the user capable of starting the gray in real time, so that the purpose that the service of the user can normally run is achieved by closing the user capable of starting the gray in real time when the version to be upgraded of the application is in a problem in the gray release process.

Fig. 1 is a schematic diagram of a gray scale publishing 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 service end includes a service server 121, a gradation server 122, and a database server 123. The gray level release system is used for releasing gray level of the application to be upgraded. The application to be upgraded may be a shopping application, a reading application, a game application, or the like, and is not limited herein. The gray scale distribution system may include a software program installed at a server side. The server 120 may be an application server supporting gray scale distribution. The client 110 is used for the user interacts.

In some embodiments, communication between the client 110 and the server 120 may be implemented through an application programming interface (application programming interface, API) gateway for transmission of information such as pictures, video, text, audio, or other data. The client 110 may be various terminal devices (such as terminal devices 111, 112 and 113) shown in fig. 1, for example, the client 110 may be a mobile phone, a tablet computer, a personal computer (personal computer, PC), a personal digital assistant (personal digital assistant, PDA), a smart watch, a netbook, a wearable electronic device, an augmented reality (augmented reality, AR) device, a Virtual Reality (VR) device, a vehicle-mounted device, a smart car, a smart sound device, and other electronic devices, which are not limited in this embodiment of the present application.

The API gateway is used as a back-end total entry of the gray level distribution system, and is used to provide different APIs for each client 110. When a user interacts with the client 110, for example, the user needs to use a service provided by the client 110 (e.g., the user sends information through the client), the client 110 responds to the operation of the user to generate a corresponding service request, and the client sends the service request to an API gateway, which determines whether the client 110 can access the gray server 122. If the API gateway determines that the client 110 can access the gray server 122, a service request is sent to the gray server 122, so that the gray server 122 performs a corresponding process. If the API gateway determines that the client 110 cannot access the gray server 122, the service request is sent to the service server 121 for corresponding processing.

As shown in fig. 2, fig. 2 is a schematic structural diagram of a gray scale distribution system according to 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 on 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 receiving the business request sent by the gray level decision engine.

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

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

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

Fig. 3 is a schematic hardware structure of an electronic device according to an embodiment of the present application. The electronic device may be the above-described 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 (universal serial bus, USB) interface 130, a charge 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, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, a user identification module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity 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 will be appreciated that the number of components, the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic apparatus 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 101 may include one or more processing units, for example: processor 101 may include an application processor (application processor, AP), modem processor, graphics processor (graphics processing unit, GPU), image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and a command center of the electronic device 100, among others. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals 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 has just been used or recycled by the processor 101. If the processor 101 needs to reuse the instruction or data, it may be called directly from memory. Repeated accesses are avoided and the latency of the processor 101 is reduced, thus improving the efficiency of the system.

In some embodiments, the processor 101 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also use different interfacing manners, or a combination of multiple interfacing manners in the foregoing embodiments.

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

The power management module 141 is used for connecting the battery 142, and the charge 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 may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into 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 for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the processor 101. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided 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 the 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 transmits the demodulated low frequency baseband signal to the 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 sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images 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 module, independent of the processor 101.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the 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, frequency modulate it, amplify it, and convert it into electromagnetic waves to radiate through the antenna 2.

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

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

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 fourier transform the frequency bin energy, or the like.

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: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

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

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

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

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

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

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. 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 Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: 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 may be implemented in the above gray scale distribution system. The gray level distribution method provided in the embodiment of the present application will be described by taking the electronic device 100 as an example of a mobile phone.

To pair with

For example, let the un-upgraded version of the panned treasures be version 1, the upgraded version be version 2, and when the grey scale is released, the panned treasures of version 1 run on the service server, and the panned treasures of version 2 run on the grey scale server. Responsive to user operationAnd after the gray scale with empty data, which is the same as the table structure of the production table, is added in the production database, the system performs upgrading operation on the gray scale. Compared with the production table, some fields may be added to the upgraded gray-scale table, for example, assuming that the production table is an order table, the order table does not include the field corresponding to the commodity name, and the system may add the field corresponding to the commodity name to the gray-scale table.

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

In this embodiment of the present application, referring to fig. 4, when a user uses an application in a mobile phone to transact a service, the mobile phone responds to an operation of the user to generate a corresponding service request. Such as in a mobile phone

After the application is started in response to the operation of the user, when the user creates a new order to purchase goods in the panning application in the mobile phone, the mobile phone generates a service request for creating the new order in response to the operation of the user.

In the embodiment of the application, the user may instruct to open the panning in various manners, for example, the user may open the panning by clicking an icon of panning, may open the panning by voice command, or may also instruct to open the panning by a space gesture, etc.

For example, referring to (a) of fig. 4, the user's operation of opening the panning may be an operation of clicking the panning icon 401 by the user. After detecting the operation of opening the panning by the user, the mobile phone displays a display interface corresponding to the panning in the display interface of the mobile phone.

In the embodiment of the application, taking the case that the user creates a new order in the panning, after the mobile phone detects the operation of opening the panning by the user, the mobile phone responds to the operation of creating the new order in the panning by the user and sends a service request for creating the new order to the gray level decision engine.

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

After receiving the service request for creating the new order, the gray level decision engine judges whether the user meets the gray level policy and whether the gray level state corresponding to the user is started or not so as to determine whether to send the service request to the service server for processing or to send the service request to the gray level server for processing.

It can be understood that when the mobile phone responds to the operation of the user to create the service request of the new order, the service request for creating the new order may include a new order creation request, an order payment request, a shipping state viewing request, and the like, if the gray level decision engine determines that the user meets the gray level policy and determines that the gray level state corresponding to the user is opened, the gray level decision engine sends the service request to the gray level server for processing. 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 the service server for processing.

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

After receiving the service request for creating the new order, the gray service module in the gray server creates the 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 level decision engine determines that the user does not satisfy the gray level policy or the gray level state corresponding to the user is on, the gray level decision engine sends the service request to the service server for processing.

The gray scale distribution method provided in the embodiment of the present application is described in detail below with reference to fig. 5 to 7. Fig. 5 is a flow chart of a gray scale publishing method according to an embodiment of the present application. As shown in fig. 5, the gray scale publishing method provided in the embodiment of the present application may include:

in step 501, after detecting the operation of opening the panning by the user, the mobile phone responds to the operation of creating a new order by the user in panning, and sends a service request 1 for creating the new order to the gray level decision engine.

At step 502, the gray decision engine determines whether the user satisfies a gray policy.

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

In some embodiments, after the user opens the panning and logs in, the handset sends a service request 1 to create a new order to the gray decision engine in response to the user's operation to create a new order at panning. The gray level decision engine judges whether the user meets gray level strategies according to the service key value of the service request 1.

Optionally, the service key of service request 1 is used to uniquely identify the user that sent service request 1 that created the new order, e.g., the service key of service request 1 may be the user identification of that user. After the gray level decision engine obtains the user identification corresponding to the service request 1, judging whether the user meets the gray level strategy according to the user identification.

It will be appreciated that after the user has registered with the panning, the system assigns each user a unique user identification which is used to identify the identity of the user. For example, the user identification may be an identification number (identity document, ID) of the user. When the user logs in the panning, the system can acquire various information of the user registered in the panning, such as information of age, address and the like of the user according to the user identification of the user. The user identifier may be carried in the service request 1 or may be independent, which is not limited herein.

For example, assuming that the gray level policy is a user-initiated gray level of a preset age group, if the gray level decision engine obtains that the age of the user creating the new order is not in the preset age group, the gray level decision engine determines that the user does not conform to the gray level policy. If the gray level decision engine obtains that the age of the user creating the new order is in a preset age range, the gray level decision engine determines that the user accords with the gray level strategy. For example, the gray policy is that a user with an age ranging from 20 years old to 40 years old opens a gray, and if the gray decision engine obtains that the user creating a new order has an age of 30 years old, the gray decision engine determines that the user accords with the gray policy. If the gray level decision engine obtains that the age of the user creating the new order is 55 years old, the gray level decision engine determines that the user does not conform to the gray level policy.

Further exemplary, assuming that the gray level policy is a user-initiated gray level in a predetermined region, if the gray level decision engine obtains that the address of the user creating the new order is not in the predetermined region, the gray level decision engine determines that the user does not conform to the gray level policy. If the gray level decision engine obtains that the address of the user creating the new order is in the preset area, the gray level decision engine determines that the user accords with the gray level strategy. For example, if the gray level policy is that the user whose geographic position is Beijing opens a gray level, and if the gray level policy engine obtains that the geographic position of the user who creates a new order is Shanghai, the gray level policy engine determines that the user does not conform to the gray level policy. If the gray level decision engine obtains that the geographic position of the user creating the new order is Beijing, the gray level decision engine determines that the user accords with the gray level strategy. In some embodiments, if the gray level decision engine determines that the user does not satisfy the gray level policy, steps 503-505 are performed. If the gray decision engine determines that the user satisfies the gray policy, step 506 is performed.

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

It will be appreciated that the user does not belong to the user testing the new version of the panning, i.e. the greyscale decision engine determines that the user does not meet the greyscale policy, and the service server processes the mobile phone accordingly in response to the service request 1 for creating a new order for the user.

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

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

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

Step 506, if the gray level decision engine determines that the user satisfies the gray level policy, the gray level decision engine determines whether the gray level state corresponding to the user identifier is on.

In some embodiments, when the gray level decision engine determines that the user satisfies the gray level policy, the gray level decision engine may prompt the user to upgrade the panned version to version 2 if the panned version in the user's mobile phone is still version 1, and further, the mobile phone upgrades the panned version to version 2 in response to the user's operation. For example, as shown in fig. 6, a prompt message "naughty treasured new version upgrade" may be displayed in the desktop of the mobile phone. After detecting the 'yes' operation of the user on the control, the mobile phone upgrades the panning version to the version 2.

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

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

In step 508, if the gray decision engine determines that the gray state corresponding to the user identifier is not on, the gray decision engine sends a migration request to the gray 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 grayscale data engine performs data migration.

It should be explained 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 browse records 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 identifier, the gray data engine migrates the data corresponding to the user into the gray table. I.e. the greyscale data engine copies the data corresponding to the user into the greyscale table.

The gray scale table is an empty table obtained by copying the table structure of the production table, and the table structure is identical to the table structure of the first data table, but the data is empty. That is, the gray scale table is an empty table before the gray scale data engine migrates the user's data to the gray scale table. Because the gray scale table has the same table structure as the production table, when the gray scale data engine transfers the data of the user from the production table to the gray scale table, the data of the user can be directly copied from the production table to the gray scale table, and the situation of data loss caused by different table structures during data transfer is avoided.

In some embodiments, the gray scale 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 gray scale table includes table structures of the production table, and some table structures are added or modified. In the subsequent steps, the gray data engine creates a new order according to the service request 1, and writes the corresponding data into the gray table, so that the data is not lost in the scene that the new field is added to the data corresponding to the service request 1.

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 multithreading data migration method to migrate the plurality of data of the user into the gray scale table synchronously, thereby improving the efficiency of data migration.

Illustratively, 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 for the user from the production table to the grayscale table.

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

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

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

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

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

In step 513, the gray scale decision engine sends a business request 1 to create a new order to the gray scale business service module.

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

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

In step 506 described above, when the gray decision engine determines that the user satisfies the gray policy, the gray decision engine sends a migration request to the gray data engine and does not send service request 1 to create a new order. When the gray level decision engine determines that the gray level state of the user is an on state, the gray level decision engine sends a service request 1 for creating a new order to the gray level service module.

In 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 table.

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

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

In step 515, if the gray level decision engine determines that the migration result is a failure for data migration, the gray level state of the user is recorded as failure.

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

Rollback refers to the action of recovering a program or data to the last correct state by a program or data processing error. Rollback includes program rollback and data rollback types. The rollback deletion operation here refers to an operation of deleting 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.

If the gray level decision engine determines that the data migration fails or the data migration is overtime according to the received migration result, the gray level decision engine records that the gray level state of the user is failed in the gray level state cache, and notifies the gray level data engine to perform rollback deletion operation of gray level table data corresponding to the user identification.

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

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

In the embodiment of the application, after the gray level release system determines that the verification of the panned version 2 meets the preset condition, the gray level release system responds to the operation of a user to close a switch for panned gray level release. For example, the gray level distribution system determines that the verification of the panning version 2 reaches a preset time period (e.g., 12 hours, 24 hours, etc.), and the developer turns off the panning gray level distribution main switch. Or the gray level release system determines that a preset number of users have used the panned version 2, and the developer turns off the panned gray level release master switch.

After the gray level distribution main switch of the panning in the mobile phone is closed in response to the user operation, the user purchases goods again at the panning, i.e. the user creates a new order again at the panning. The handset, in response to a user operation to create a new order, sends a service request 2 to create the new order to the greyscale decision engine. And the gray level decision engine determines that the gray level state of each user is on according to the gray level state of each user recorded in the gray level state cache. I.e. the greyscale data engine has migrated the user's data from the production table to the greyscale table, where all the user's data is stored. In this case, the gray decision engine notifies the gray data engine to migrate the data corresponding to the user back from the gray table to the production table. And after the gray data engine returns the data of the user in the gray table to the production table, the gray data engine sends a return result to the gray decision engine. And the gray level decision engine determines that the data of the user is returned to the production table according to the returning result, and then the gray level 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 mobile phone triggers the gray data engine to migrate the data corresponding to the user from the gray table to the production table in response to the user's operation of purchasing goods in the panning, which is only described as an example. After the main gray level release switch of the panning is closed in response to user operation, the user opens the panning again, the mobile phone initiates a first service request in response to any operation of the user (such as the user logging in the panning, browsing goods, checking purchasing records, etc.), and the gray level decision engine can trigger the gray level data engine to transfer the data corresponding to the user from the gray level table to the production table under the condition that the gray level state of each user is determined to be open according to the gray level state of each user recorded in the gray level state cache.

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

in step 701, the mobile phone responds to the operation of creating a new order in the panning by the user, and sends a service request 2 for creating the new order to the gray level decision engine.

In the embodiment of the application, after the gray level 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 again at the panning, and the mobile phone sends a service request 2 for creating the new order to the gray level decision engine.

For the implementation process of step 701, reference may be made to the implementation process of step 501, which is not described herein.

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 application, after the gray level decision engine receives 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 identification 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.

In step 703, the gray decision engine sends a data migration request to the gray data engine.

The data returning request is used for the gray data engine to return the data corresponding to the user in the gray table in the production database to the production table. The data relocation request carries the user identification of the user.

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

At step 704, the grayscale data engine relocates the user's data in the grayscale table back into the production table.

Wherein the user's data in the gray scale table includes data stored when the user uses panning version 2 (e.g., data to create an order, data to pay for an order, etc.), and the gray scale data engine migrates from the production table to the data in the gray scale table before the user performs the gray scale business process.

In the embodiment of the application, after the gray data engine receives the data returning request, the gray data engine queries data corresponding to the user in the gray table according to the user identification. And after deleting the data of the user in the production table, the gray data engine copies the data of the user in the gray table into the production table. Therefore, the gray level decision engine determines that the user has completed gray level release verification, and the gray level data engine carries out real-time return on the data of the user 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 returns the data of the user from the gray level table to the production table is avoided.

Illustratively, assuming that 5 orders data for the user are included in the production table, the gray scale data engine migrates the data for the user in the production table to the gray scale table, which includes 5 orders data for the user. When the user uses the Taobao version 2, the gray service module adds 2 pieces of order data in the gray table. I.e. 7 pieces of order data for the user are included in the gray scale table. After receiving the data returning request sent by the gray level decision engine, the gray level data engine deletes 5 order data of the user in the production table and copies 7 order data of the user in the gray level table to the production table. Therefore, the repeated storage of the data of the user in the production table is avoided, and the situation of data loss is avoided in the process of data migration.

In one case, assuming that the balance data of the user is stored in the gray scale table, when the user initiates a new order request, the mobile phone changes the balance data of the user in the gray scale table after paying in response to the payment operation of the user. In this case, when the gray data engine returns the user's data in the gray table to the production table, the gray data engine copies the user's data in the gray table to the production table after deleting the user's data in the production table, so that the loss of the user's data in the data returning process can be avoided.

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

In the embodiment of the application, after the gray data engine returns the data of the user in the gray table to the production table, the gray data engine sends a return result to the gray decision engine.

In step 706, the gray 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 return result, then steps 707 and 708 are performed. Otherwise, step 709 is performed.

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

In step 708, the production service module creates a new order according to service request 2 and writes the corresponding data into the 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 indicates that the gray level decision 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 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.

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

In step 709, the gray decision engine prompts the operator for manual processing.

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

In some embodiments, the gray level decision engine can prompt the operation and maintenance personnel of data migration failure in a mode of sending prompt information so as to prompt the operation and maintenance personnel to perform manual processing. For example, the gray level decision engine sends a message or mail to the operation and maintenance personnel to prompt the operation and maintenance personnel to perform manual processing.

In other embodiments, the gray level decision engine may trigger an alarm light of the gray level distribution system to prompt the operation and maintenance personnel for manual processing through the alarm light.

It should be noted that the manner in which the gray level decision engine prompts the operator is merely exemplary, and any other manner that can be implemented is also suitable for the present application, which is not limited herein. For example, the gray level decision engine may trigger an audible prompt to prompt the operator for manual processing, etc.

Because the gray level decision engine determines that the data migration corresponding to the user fails, after the operation and maintenance personnel receive the manual intervention prompt, the service request 2 for creating the new order can be distributed to the gray level environment for processing. That is, the operation and maintenance personnel can manually send the service request 2 for creating the new order to the gray scale service module, so that the gray scale service module creates the new order according to the service request 2 and writes the corresponding data into the gray scale table.

In the embodiment of the present application, taking the process of issuing the gray level of panning as an example, the gray level issuing method is described as an example, and in practical application, the gray level issuing method is suitable for issuing gray levels of any application, which is not limited herein.

In the embodiment of the application, the gray level decision engine determines whether the user initiating the service request meets the gray level policy or not so as to accurately determine the 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 policy and the gray level state of the user is not started, the gray level data engine transfers 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 the gray level service module for corresponding processing. If the gray data engine determines that the user has completed gray release verification, the gray data engine reverts the user's data from the gray table to the production table. In the gray level distribution process, the gray level data engine migrates and reverts the data of the user. Therefore, by adding the gray scale table with the same structure as the produced table in the production database, writing the data corresponding to the user identifier in the gray scale release process into the gray scale table, and carrying out real-time migration and back migration on the data corresponding to the user identifier in the gray scale table, the problem that the table structure of the database cannot be changed when codes after the gray scale release are incompatible with codes before the gray scale release after the data of the production and the gray scale release are written into the same database in the related art is solved, and therefore, the situation that the scene of the gray scale release is not limited is ensured.

In addition, the gray level release system can control the on and off of the gray level release master switch in real time, so that the purpose that the service of a user using the upgraded version can normally run is realized by closing the gray level release master switch in real time when the version to be upgraded of the application has a problem in the gray level release process.

It can be seen that the same database is shared with the service server and the gray server in the prior art, or the service server and the gray server are independent, in the embodiment of the present application, by adding a gray table with the same table structure as the production table in the production database, and by migrating and returning the data corresponding to the user initiating the service request, the problem that when the service server and the gray server share the same database, the version code is required to be compatible, and the scene of deleting and renaming the table field is not supported, so that the gray release scene is limited is solved, and when the databases of the service server and the gray server are independent, different users write data into the production database and the gray database respectively, so that the version of the application is updated, and when the production database and the gray database are unified, the problem of data loss is solved.

As shown in fig. 8, an embodiment of the present application discloses an electronic device, which may be the mobile phone described above. The electronic device may specifically include: a touch screen 801, the touch screen 801 including a touch sensor 806 and a display screen 807; one or more processors 802; a memory 803; one or more applications (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 will be appreciated that the electronic device or the like may include hardware structures and/or software modules that perform the functions described above. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven 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.

The embodiment of the present application may divide the functional modules of the electronic device or the like according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present invention, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

In the case of dividing the respective functional modules with the respective functions, one possible composition diagram of the electronic device involved in the above-described embodiment may include: a display unit, a transmission unit, a processing unit, etc. It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

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 being configured to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the server to perform the related method steps described above to implement the gray scale distribution method of the above embodiments.

Embodiments of the present application also provide a computer-readable storage medium having stored therein computer instructions that, when executed on an electronic device, cause the electronic device to perform the above-described related method steps to implement the grayscale distribution method in the above-described embodiments.

Embodiments of the present application also provide a computer program product comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the above-described related method steps to implement the gray scale distribution method of the above-described 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 configured to store computer-executable instructions, and when the apparatus is running, the processor may execute the computer-executable instructions stored in the memory, so that the apparatus executes the gray-scale distribution 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 used to execute the corresponding method provided above, so that the advantages achieved by the method can refer to the advantages in the corresponding method provided above, and will not be described herein.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

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

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform 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 disk, read-only memory, random access memory, magnetic or optical disk, and the like.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection 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 distribution method, which is applied to a gray scale distribution system, wherein 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;

when the gateway determines that the user identifier meets a preset condition, the gateway sends a data migration request to the gray server, wherein the data migration request carries the user identifier; the preset condition comprises a user identifier of which the user identifier is a preset user, and the gray state corresponding to the user identifier is unopened;

the gray server transfers the data corresponding to the user identifier from a production table to a gray table according to the data transfer request, wherein 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 a data table obtained by copying a 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 server so that the gray server executes corresponding response operation according to the first service request.

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

adding the gray scale table in a production database of the database server in response to a user operation;

and responding to the operation of a user, and starting a gray level release master switch by the gateway.

3. The method of claim 1, wherein the gray server performs a corresponding response operation according to the first service request, comprising:

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

4. A method according to any one of claims 1-3, wherein the method further comprises:

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.

5. The method of claim 4, wherein the service server performing a corresponding response operation according to the first service request 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.

6. A method according to any one of claims 1-3, wherein the method further comprises:

setting a gray state corresponding to the user identifier to be on by the gateway under the condition that the gateway determines that data migration is successful;

and under the condition that the gateway determines that the data migration is unsuccessful, the gateway sets the gray state corresponding to the user identifier as failure, and informs the gray server to perform rollback deletion operation on the data corresponding to the user identifier in the gray table.

7. A method according to any one of claims 1-3, wherein the method further comprises:

responding to the operation of a user, and closing a gray level release master 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;

When the gateway determines that the gray state corresponding to the user identifier is on, the gateway sends a data migration request to the gray server;

the gray server returns the data corresponding to the user identifier from the gray table to the production table according to the data returning 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.

8. The method of claim 7, wherein the transferring the data corresponding to the user identification from the grayscale table back to the production table is preceded by:

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

9. The method of claim 7, wherein the method further comprises:

and under the condition that the gateway determines that the data migration is unsuccessful, the gateway prompts operation and maintenance personnel to perform manual processing.

10. A gray scale distribution method applied to a gateway, the method comprising:

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

transmitting a data migration request to a gray server under the condition that the user identifier meets a preset condition, wherein the data migration request carries the user identifier, and the gray server is used for migrating data corresponding to the user identifier from a production table to a gray table according to the data migration request, wherein the production table is a data table corresponding to a 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 a copied data table of the table structure of the production table; the preset condition comprises a user identifier of which the user identifier is a preset user, and the gray state corresponding to the user identifier is unopened;

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

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

And starting the gray level release master switch.

12. The method according to claim 10 or 11, characterized in that the method further comprises:

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

13. The method according to claim 10 or 11, characterized in that the method further comprises:

setting the gray state corresponding to the user identifier to be on under the condition that the data migration is successful;

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

14. The method according to claim 10 or 11, characterized in that the method further comprises:

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

transmitting a data migration request to the gray server under the condition that the gray state corresponding to the user identifier is determined to be on;

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

15. The method of claim 14, wherein the method further comprises:

and prompting operation and maintenance personnel to perform manual processing under the condition that the data returning is not successful.

16. A gray scale distribution method applied to a gray scale server, the method comprising:

receiving a data migration request sent by a gateway, wherein the data migration request carries a user identifier, and after the data migration request is a first service request sent by electronic equipment and received by the gateway, the data migration request is sent to the gray server under the condition that the user identifier meets a preset condition, and the first service request carries the user identifier; the preset condition comprises a user identifier of which the user identifier is a preset user, and the gray state corresponding to the user identifier is unopened;

according to the data migration request, migrating the data corresponding to the user identifier 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 a table structure of the production table by the gray server and upgrading the copied data table;

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 server under the condition that the gateway determines that data migration is successful.

17. The method of claim 16, wherein said performing a corresponding response operation in accordance with said first service request comprises:

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

18. The method of claim 16, wherein the method further comprises:

and after receiving the rollback deletion operation sent by the gateway, performing rollback deletion operation on the data corresponding to the user identifier in the gray scale table.

19. The method of claim 16, wherein the method further comprises:

receiving a data returning request sent by the gateway, wherein the data returning request is sent under the condition that the gray state corresponding to the user identifier is determined to be on after the gateway receives a second service request sent by the electronic equipment, and the second service request carries the user identifier;

And returning the data corresponding to the user identifier from the gray scale table to the production table according to the data returning request.

20. The method of claim 19, wherein before the migrating the data corresponding to the user identification from the grayscale table back to the production table, the method further comprises:

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

21. A gradation release system, comprising:

a gateway for performing the gray scale distribution method of any of the preceding claims 10-15;

a gray server for performing the gray distribution method of any of the above claims 16 to 20;

22. The system of claim 21, wherein the system further comprises a controller configured to control the controller,

and the service server is also used for executing corresponding response operation according to the 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.

23. An electronic device, 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 server, cause the server to perform the grayscale distribution method of any of claims 1-9.

24. 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 server, cause the server to perform the grayscale distribution method of any of claims 10-15.

25. A server, 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 server, cause the server to perform the grayscale distribution method of any of claims 16-20.

26. A computer readable storage medium having instructions stored therein, which when run on a processor, perform the grayscale distribution method of any one of claims 1-9, or perform the grayscale distribution method of any one of claims 10-15, or perform the grayscale distribution method of any one of claims 16-20.