Data gray scale amplification method and device, equipment and storage medium

Abstract

The invention discloses a data gray scale amplification method, device and equipment and a storage medium, and relates to the technical field of computers.The method comprises the steps that a tile data request sent by a client side is received, and the tile data request comprises an equipment ID and a tile ID; judging whether the tile ID is associated with new version data or not; if the equipment ID is associated with the new version data, judging whether the equipment ID is in a preset quantity amplification group or not; and if the device ID is not in the preset amplification group, determining response data according to the device ID, the dynamically configured gray scale amplification progress and the dynamically configured gray scale amplification offset, and returning the response data to the client. According to the method, each tile is associated with own version number data, so that the user request does not need to be distributed to different machines or service clusters. Besides, by dynamically setting the gray scale amplification offset, each gray scale process can be started from different users, and the same batch of users cannot be influenced each time even if new edition data have problems.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a data grayscale volume expansion method, device, equipment and storage medium. Background Art

[0002] Grayscale release is a method of gradually promoting new version data or functions. By gradually pushing new version data to some users, the performance and user feedback of the new version can be monitored, and problems can be discovered and solved in a timely manner, thereby reducing the impact on all users. This method is widely used in software development, geographic information systems (GIS) and other fields.

[0003] At present, a common grayscale release technology is to perform grayscale release based on user ID or device ID. Specifically, users are diverted to different machines or service clusters according to user ID or device ID, and each cluster runs different versions of data. However, since machines and service clusters need to be independently configured for different versions of data, this will significantly increase resource consumption. In addition, each cluster requires independent computing resources, storage resources, and network resources, which not only increases hardware costs, but may also lead to low resource utilization. Managing multiple independent machines and service clusters requires maintaining multiple configuration files, monitoring the operating status of multiple systems, and handling synchronization issues of multiple versions of data. This not only increases the workload of operation and maintenance personnel, but may also introduce more management errors.

[0004] In addition, each grayscale release process usually starts with the same group of users. This means that if there are problems with the new version data, this group of users will be repeatedly affected, which will have a greater negative impact on the product. Users may lose confidence in the product due to frequent problems and even choose other competing products. Summary of the invention

[0005] Based on this, it is necessary to provide a data grayscale expansion method, device, equipment and storage medium to solve at least one of the above technical problems.

[0006] The present invention provides a data grayscale enlargement method, comprising:

[0007] Receive a data request sent by a client, wherein the data request includes a device ID and a tile ID;

[0008] Determine whether the tile ID is associated with new version data;

[0009] If new version data is associated, determine whether the device ID is in a preset volume group;

[0010] If it is not in the preset volume-enhancing group, the response data is determined according to the device ID, the dynamically configured grayscale volume-enhancing progress and the grayscale volume-enhancing offset and returned to the client.

[0011] Optionally, according to a data grayscale expansion method provided by the present invention, the step of determining response data and returning it to the client according to the device ID, the dynamically configured grayscale expansion progress and the grayscale expansion offset includes:

[0012] Determine whether the grayscale volume expansion progress is a first preset value or a second preset value, wherein the first preset value is less than the second preset value;

[0013] If the grayscale volume release progress is neither the first preset value nor the second preset value, a preset hash algorithm is used to calculate a hash value corresponding to the device ID, and the hash value is converted into a target integer;

[0014] Determine a grayscale enlargement value based on the target integer and the grayscale enlargement offset;

[0015] The grayscale volume-enhancing value is compared with the grayscale volume-enhancing progress, and response data is determined according to the comparison result and returned to the client.

[0016] Optionally, according to a data grayscale volume release method provided by the present invention, the grayscale volume release value is compared with the grayscale volume release progress to determine response data according to the comparison result and return it to the client, including:

[0017] When the grayscale volume increase value is greater than the grayscale volume increase progress, or the grayscale volume increase progress is a second preset value:

[0018] Determining whether the version identifier of the new version data matches the version identifier in the tile data request;

[0019] If the version identifiers do not match, the new version data is returned to the client as the response data.

[0020] Optionally, according to a data grayscale volume release method provided by the present invention, the grayscale volume release value is compared with the grayscale volume release progress to determine response data according to the comparison result and return it to the client, including:

[0021] When the grayscale volume increase value is less than or equal to the grayscale volume increase progress, or the grayscale volume increase progress is a first preset value:

[0022] Determine whether the version identifier of the stable version data associated with the tile ID matches the version identifier in the tile data request, wherein the stable version data refers to data that has been tested and verified and has been officially launched;

[0023] If the version identifiers do not match, the stable version data is returned to the client as the response data.

[0024] Optionally, according to a data grayscale volume expansion method provided by the present invention, after determining whether the tile ID is associated with new version data, the method further includes:

[0025] If no new version data is associated, matching the version identifier of the stable version data associated with the tile ID with the version identifier in the tile data request;

[0026] According to the first matching result, response data is determined and returned to the client.

[0027] Optionally, according to a data grayscale release method provided by the present invention, the preset release group includes a stable user whitelist group and a grayscale user whitelist group, wherein the user whitelist group refers to users who request and receive stable version data; the grayscale user whitelist group refers to users who request and receive new version data.

[0028] Optionally, according to a data grayscale volume expansion method provided by the present invention, after determining whether the device ID is in a preset volume expansion group, the method further includes:

[0029] If the user is in the stable user whitelist group, the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request; and response data is determined according to the second matching result and returned to the client;

[0030] If it is in the grayscale user whitelist group, the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request to determine the response data according to the third matching result and return it to the client.

[0031] The present invention also provides a data grayscale enlargement device, comprising:

[0032] A receiving module, configured to receive a data request sent by a client, wherein the data request includes a device ID and a tile ID;

[0033] A first determination module, used to determine whether the tile ID is associated with new version data;

[0034] The second judgment module is used to judge whether the device ID is in a preset volume group if new version data is associated;

[0035] The return module is used to determine the response data and return it to the client according to the device ID, the dynamically configured grayscale volume release progress and the grayscale volume release offset if it is not in the preset volume release group.

[0036] The present invention also provides a computer device, including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the above-mentioned data grayscale expansion method when executing the computer-readable instructions.

[0037] The present invention also provides one or more readable storage media storing computer-readable instructions, and the computer-readable instructions, when executed by a processor, implement the above-mentioned data grayscale expansion method.

[0038] The above-mentioned data grayscale release method, device, equipment and storage medium include: receiving a tile data request sent by a client, wherein the tile data request includes a device ID and a tile ID; determining whether the tile ID is associated with a new version of data; if it is associated with a new version of data, determining whether the device ID is in a preset release group; if it is not in a preset release group, determining the response data and returning it to the client based on the device ID, the dynamically configured grayscale release progress and the grayscale release offset. The present invention associates each tile with its own version number data, eliminating the need to divert user requests to different machines or service clusters. In addition, by dynamically setting the grayscale release offset, each grayscale process can start from a different user, and even if there is a problem with the new version of the data, it will not affect the same group of users every time. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0040] Figure 1 It is a flow chart of a method for increasing the data grayscale in one embodiment of the present invention;

[0041] Figure 2 is a schematic diagram of dividing a geographic space into tiles provided by an embodiment of the present invention;

[0042] Figure 3 It is a complete flow chart of a data grayscale volume expansion method provided by an embodiment of the present invention;

[0043] Figure 4is a schematic diagram of calculating grayscale volume value provided by an embodiment of the present invention;

[0044] Figure 5 It is a structural schematic diagram of a data grayscale enlargement device in one embodiment of the present invention;

[0045] Figure 6 is a schematic diagram of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0047] The terms used in one or more embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present invention. The singular forms of "a", "said" and "the" used in one or more embodiments of the present invention are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present invention refers to and includes any or all possible combinations of one or more associated listed items.

[0048] In one embodiment, specifically, Figure 1 As shown, Figure 1 1 is a flow chart of a method for increasing the volume of data in grayscale according to an embodiment of the present invention. The present invention provides a method for increasing the volume of data in grayscale, comprising the following steps:

[0049] Step S11, receiving a data request sent by a client;

[0050] It should be noted that the data request includes information such as device ID and tile ID, where tile ID refers to the identity of each tile, and tile refers to the division of geographic spatial data into small blocks (usually square or rectangular). Each small block is called a tile, and each tile contains geographic information within a certain range, such as map images, vector data, elevation data, etc. Tile technology is widely used in geographic information systems (GIS), online map services, remote sensing image processing and other fields.

[0051] Step S12, determining whether the tile ID is associated with new version data;

[0052] Specifically, refer to Figure 2 , Figure 2is a schematic diagram of dividing a geographic space into tiles provided by an embodiment of the present invention, wherein each tile is associated with corresponding version data, for example, new version data and stable version data, the new version data refers to the version data that has been recently updated or is about to be launched, which may contain new functions, fixed errors or improved performance, but has not been fully tested and verified; the stable version data refers to the data that has been tested and verified and has been officially launched; wherein, Figure 2 Tile X in the example has two version data (new version data and stable version data), and tile Y has only one version data (stable version data).

[0053] Step S13, if new version data is associated, determine whether the device ID is in a preset volume group;

[0054] It should be noted that the preset release group includes a stable user whitelist group and a grayscale user whitelist group, wherein the user whitelist group refers to users who request and receive stable version data; the grayscale user whitelist group refers to users who request and receive new version data. The stable user whitelist group and the grayscale user whitelist group can be updated according to actual conditions. For example, suppose there is a map tile data service, the current stable version is 1.0, and the new version is 2.0. The new version 2.0 contains some new map data and functions, but has not been fully tested. The ID list of the stable user whitelist group: [1001, 1002, 1003, 1004]. If the ID is in the stable user whitelist group, regardless of the grayscale release progress, the user always requests the stable version 1.0 data. Grayscale user whitelist group: [2001, 2002, 2003, 2004]. If the user ID is in the grayscale user whitelist group, regardless of the grayscale release progress, the user always requests the new version 2.0 data.

[0055] Specifically, if new version data is associated, it is further determined whether the device ID is in the stable user whitelist group and the grayscale user whitelist group.

[0056] In addition, the tile data request may include a version identifier cached by the client itself. If there is no associated new version data, it proves that the tile ID is only associated with stable version data, and then the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request to obtain a first matching result. If the first matching result is a successful match, it proves that the version data cached by the client itself is the same as the version data in the server, and the server generates empty data as response data and returns it to the client, thereby effectively reducing the amount of data transmission. If there is no match, the stable version data is returned to the client as the response data. In addition, the tile data request does not include the version identifier cached by the client itself, proving that the client itself does not store relevant data, and then the stable version data is directly returned to the client as the response data.

[0057] Step S14: If it is not in the preset volume-enhancing group, the response data is determined according to the device ID, the dynamically configured gray-scale volume-enhancing progress and the gray-scale volume-enhancing offset, and returned to the client.

[0058] It should be noted that when the service program is started, it will pull configuration information such as grayscale release progress, grayscale release offset, stable user whitelist grouping and grayscale user whitelist grouping. The grayscale release progress and grayscale release offset are set once in each release process. Optionally, different values ​​can be set each time. By dynamically setting the grayscale release offset, each grayscale process can start from different users. Even if there are problems with the new version of the data, it will not affect the same group of users every time.

[0059] Specifically, if the device ID is not in the stable user whitelist group and the grayscale user whitelist group, the grayscale volume value is calculated directly according to the device ID and the grayscale volume offset. Figure 3 , Figure 3It is a complete flow chart of the data grayscale volume method provided by an embodiment of the present invention; it can be first determined whether the grayscale volume progress is the first preset value or the second preset value; if the grayscale volume progress is not the first preset value and is not the second preset value, then the grayscale volume value is calculated according to the device ID and the grayscale volume offset, and then the grayscale volume value is compared with the grayscale volume progress. In one embodiment, when the grayscale volume value is greater than the grayscale volume progress: the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request. If the match is successful, it proves that the version data cached by the client itself is the same as the version data in the server, and the server generates empty data as response data and returns it to the client, thereby effectively reducing the amount of data transmission. If it does not match, the new version data is returned to the client as the response data. In addition, when the tile data request does not include the version identifier cached by the client itself, it proves that the client itself does not store the relevant data, and then directly returns the new version data to the client as the response data. In addition, it should be noted that the release process when the device ID is in the grayscale user whitelist group and the grayscale release progress is the second preset value is similar to the processing flow when the above-mentioned grayscale release value is greater than the grayscale release progress, and will not be repeated here.

[0060] In another embodiment, when the grayscale release value is less than or equal to the grayscale release progress: the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request. If the match is successful, it proves that the version data cached by the client itself is the same as the version data in the server, and the server generates empty data as response data and returns it to the client, thereby effectively reducing the amount of data transmission. If there is no match, the stable version data is returned to the client as response data. In addition, the tile data request does not include the version identifier cached by the client itself, proving that the client itself does not store relevant data, and then directly returns the stable version data to the client as response data. In addition, it should be noted that the release process when the device ID is in the stable user whitelist group and the grayscale release progress is the first preset value is similar to the above-mentioned processing flow when the grayscale release value is less than or equal to the grayscale release progress, and will not be repeated here.

[0061] The embodiment of the present invention, through the above scheme, includes: receiving a tile data request sent by a client, wherein the tile data request includes a device ID and a tile ID; determining whether the tile ID is associated with new version data; if it is associated with new version data, determining whether the device ID is in a preset release group; if it is not in the preset release group, determining the response data and returning it to the client according to the device ID, the dynamically configured grayscale release progress and the grayscale release offset. The present invention associates each tile with its own version number data, eliminating the need to divert user requests to different machines or service clusters. In addition, by dynamically setting the grayscale release offset, each grayscale process can start from a different user, and even if there is a problem with the new version of the data, it will not affect the same group of users every time.

[0062] In one embodiment of the present invention, according to the device ID, the dynamically configured grayscale volume increase progress and grayscale volume increase offset, the response data is determined and returned to the client, including:

[0063] Determine whether the grayscale volume release progress is a first preset value or a second preset value, wherein the first preset value is less than the second preset value; if the grayscale volume release progress is neither the first preset value nor the second preset value, calculate the hash value corresponding to the device ID using a preset hash algorithm, and convert the hash value into a target integer; determine the grayscale volume release value based on the target integer and the grayscale volume release offset; compare the grayscale volume release value with the grayscale volume release progress, and determine the response data based on the comparison result and return it to the client.

[0064] Specifically, determine whether the grayscale release progress is a first preset value or a second preset value. The first preset value or the second preset value can be set according to actual conditions. Optionally, the first preset value is set to 0, and the second preset value is set to 100. If the grayscale release progress is neither the first preset value nor the second preset value, then use a preset hash algorithm to calculate the hash value corresponding to the device ID. For example, the hash algorithm is MD5, SHA-256 or other algorithms. Further, convert the hash value into a target integer, for example, take the first few digits of the hash value. Then, based on the target integer and the grayscale release offset, calculate the grayscale release value; refer to Figure 4 , Figure 4 : is a schematic diagram of calculating the grayscale volume value provided by an embodiment of the present invention. The calculation formula of the grayscale volume value is as follows:

[0065] (Device ID%100+100-off)%100+1

[0066] Among them, off represents the grayscale release offset, and the value range of off is 0 to 99. Furthermore, the grayscale release value and the grayscale release progress are compared. In one embodiment, when the comparison result is that the grayscale release value is greater than the grayscale release progress: the version identifier of the new version data and the version identifier in the tile data request are matched; if the version identifier does not match, the new version data is returned to the client as the response data. In addition, the processing flow when the grayscale release progress is the second preset value is similar to the processing flow when the grayscale release value is greater than the grayscale release progress, which will not be repeated here.

[0067] In another embodiment, when the grayscale volume increase value is less than or equal to the grayscale volume increase progress: the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request, and if the version identifiers do not match, the stable version data is directly returned to the client as the response data. In addition, it should be noted that the processing flow when the grayscale volume increase progress is the first preset value is similar to the processing flow when the grayscale volume increase value is less than or equal to the grayscale volume increase progress, and will not be repeated here.

[0068] The embodiment of the present invention realizes the calculation of the grayscale release value according to the device ID and the grayscale release offset through the above scheme; then the grayscale release value is compared with the grayscale release progress to determine the response data and return it to the client according to the comparison result. By dynamically setting the grayscale release offset, each grayscale process can start from a different user. Even if there is a problem with the new version of the data, it will not affect the same group of users every time.

[0069] In one embodiment of the present invention, after determining whether the device ID is in a preset volume-increasing group, the method further includes:

[0070] If it is in the stable user whitelist group, the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request; based on the second matching result, the response data is determined and returned to the client; if it is in the grayscale user whitelist group, the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request, based on the third matching result, the response data is determined and returned to the client.

[0071] Specifically, in one embodiment, if in a stable user whitelist group, the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request. If the match is successful, it proves that the version data cached by the client itself is the same as the version data in the server, and the server generates empty data as response data and returns it to the client, thereby effectively reducing the amount of data transmission. If there is no match, the stable version data is returned to the client as the response data. In addition, the tile data request does not include the version identifier cached by the client itself, proving that the client itself does not store relevant data, and then directly returns the stable version data to the client as the response data.

[0072] In another embodiment, if it is in the grayscale user whitelist group, the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request. If the match is successful, it proves that the version data cached by the client itself is the same as the version data in the server, and the server generates empty data as response data and returns it to the client, thereby effectively reducing the amount of data transmission. If there is no match, the new version data is returned to the client as the response data. In addition, the tile data request does not include the version identifier cached by the client itself, proving that the client itself does not store the relevant data, and then directly returns the new version data to the client as the response data.

[0073] Through the above scheme, the embodiment of the present invention realizes fixed volume expansion for specific users through stable user whitelist grouping and grayscale user whitelist grouping, thereby improving data processing efficiency.

[0074] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0075] In one embodiment, a data grayscale enlargement device is provided, and the data grayscale enlargement device corresponds to the data grayscale enlargement method in the above embodiment. Figure 5 As shown, Figure 5 1 is a schematic diagram of a data grayscale enlargement device according to an embodiment of the present invention, wherein the data grayscale enlargement device comprises:

[0076] The receiving module 21 is used to receive a data request sent by a client, wherein the data request includes a device ID and a tile ID;

[0077] A first determination module 22, used to determine whether the tile ID is associated with new version data;

[0078] The second judgment module 23 is used to judge whether the device ID is in a preset volume group if new version data is associated;

[0079] The return module 24 is used to determine the response data and return it to the client according to the device ID, the dynamically configured grayscale volume release progress and the grayscale volume release offset if it is not in the preset volume release group.

[0080] The return module 24 is also used for:

[0081] Determine whether the grayscale volume expansion progress is a first preset value or a second preset value, wherein the first preset value is less than the second preset value;

[0082] If the grayscale volume release progress is neither the first preset value nor the second preset value, a preset hash algorithm is used to calculate a hash value corresponding to the device ID, and the hash value is converted into a target integer;

[0083] Determine a grayscale enlargement value based on the target integer and the grayscale enlargement offset;

[0084] The grayscale volume-enhancing value is compared with the grayscale volume-enhancing progress, and response data is determined according to the comparison result and returned to the client.

[0085] The return module 24 is also used for:

[0086] When the grayscale volume increase value is greater than the grayscale volume increase progress, or the grayscale volume increase progress is a second preset value:

[0087] Determining whether the version identifier of the new version data matches the version identifier in the tile data request;

[0088] If the version identifiers do not match, the new version data is returned to the client as the response data.

[0089] The return module 24 is also used for:

[0090] When the grayscale volume increase value is less than or equal to the grayscale volume increase progress, or the grayscale volume increase progress is a first preset value:

[0091] Determine whether the version identifier of the stable version data associated with the tile ID matches the version identifier in the tile data request, wherein the stable version data refers to data that has been tested and verified and has been officially launched;

[0092] If the version identifiers do not match, the stable version data is returned to the client as the response data.

[0093] The data grayscale expansion device also includes:

[0094] If no new version data is associated, matching the version identifier of the stable version data associated with the tile ID with the version identifier in the tile data request;

[0095] According to the first matching result, response data is determined and returned to the client.

[0096] The data grayscale expansion device also includes:

[0097] The preset volume-release group includes a stable user whitelist group and a grayscale user whitelist group, wherein the user whitelist group refers to users who request and receive stable version data; the grayscale user whitelist group refers to users who request and receive new version data.

[0098] The data grayscale expansion device also includes:

[0099] If the user is in the stable user whitelist group, the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request; and response data is determined according to the second matching result and returned to the client;

[0100] If it is in the grayscale user whitelist group, the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request to determine the response data according to the third matching result and return it to the client.

[0101] For the specific definition of the data grayscale expansion device, please refer to the definition of the data grayscale expansion method above, which will not be repeated here. Each module in the above-mentioned data grayscale expansion device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0102] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, Figure 6: is a schematic diagram of a computer device in one embodiment of the present invention. The computer device includes a processor, a memory, a network interface and a database connected by a device bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium and an internal memory. The readable storage medium stores an operating device, a computer-readable instruction and a database. The internal memory provides an environment for the operation of the operating device and the computer-readable instructions in the readable storage medium. The database of the computer device is used to store data involved in the data grayscale expansion method. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instruction is executed by the processor, a data grayscale expansion method is implemented. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0103] In one embodiment, a computer device is provided. The computer device may be a terminal device, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, a memory, and a network interface connected by a device bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium. The readable storage medium stores computer-readable instructions. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instructions are executed by the processor, a data grayscale volume release method is implemented. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0104] In one embodiment, a computer device is provided, including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor. When the processor executes the computer-readable instructions, the steps of the above-mentioned data grayscale expansion method are implemented.

[0105] In one embodiment, a readable storage medium is provided, and the readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the data grayscale volume release method as described above are implemented. A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When the computer-readable instructions are executed, they may include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0106] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0107] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A data grayscale volume expansion method, characterized in that: The method is applied to the server, and includes: Receive a data request sent by a client, wherein the data request includes a device ID and a tile ID; Determine whether the tile ID is associated with new version data; If new version data is associated, determine whether the device ID is in a preset volume group; If it is not in the preset volume-enhancing group, the response data is determined according to the device ID, the dynamically configured grayscale volume-enhancing progress and the grayscale volume-enhancing offset and returned to the client.

2. The data grayscale volume expansion method according to claim 1, characterized in that: The determining response data according to the device ID, the dynamically configured grayscale volume release progress and the grayscale volume release offset and returning the response data to the client includes: Determine whether the grayscale volume expansion progress is a first preset value or a second preset value, wherein the first preset value is less than the second preset value; If the grayscale volume release progress is neither the first preset value nor the second preset value, a preset hash algorithm is used to calculate a hash value corresponding to the device ID, and the hash value is converted into a target integer; Determine a grayscale enlargement value based on the target integer and the grayscale enlargement offset; The grayscale volume-enhancing value is compared with the grayscale volume-enhancing progress, and response data is determined according to the comparison result and returned to the client.

3. The data grayscale volume expansion method according to claim 2, characterized in that: The step of comparing the grayscale volume-enhancing value with the grayscale volume-enhancing progress to determine response data according to the comparison result and return the response data to the client includes: When the grayscale volume increase value is greater than the grayscale volume increase progress, or the grayscale volume increase progress is a second preset value: Determining whether the version identifier of the new version data matches the version identifier in the tile data request; If the version identifiers do not match, the new version data is returned to the client as the response data.

4. The data grayscale volume expansion method according to claim 2, characterized in that: The step of comparing the grayscale volume-enhancing value with the grayscale volume-enhancing progress to determine response data according to the comparison result and return the response data to the client includes: When the grayscale volume increase value is less than or equal to the grayscale volume increase progress, or the grayscale volume increase progress is a first preset value: Determine whether the version identifier of the stable version data associated with the tile ID matches the version identifier in the tile data request, wherein the stable version data refers to data that has been tested and verified and has been officially launched; If the version identifiers do not match, the stable version data is returned to the client as the response data.

5. The data grayscale volume expansion method according to claim 1, characterized in that: After determining whether the tile ID is associated with new version data, the method further includes: If no new version data is associated, matching the version identifier of the stable version data associated with the tile ID with the version identifier in the tile data request; According to the first matching result, response data is determined and returned to the client.

6. The data grayscale volume expansion method according to claim 1, characterized in that: The preset volume-release groups include a stable user whitelist group and a grayscale user whitelist group, wherein the user whitelist group refers to users who request and receive stable version data; the grayscale user whitelist group refers to users who request and receive new version data.

7. The data grayscale volume expansion method according to claim 5, characterized in that: After determining whether the device ID is in the preset volume group, the method further includes: If the user is in the stable user whitelist group, the version identifier of the stable version data associated with the tile ID is matched with the version identifier in the tile data request; and response data is determined according to the second matching result and returned to the client; If it is in the grayscale user whitelist group, the version identifier of the new version data associated with the tile ID is matched with the version identifier in the tile data request to determine the response data according to the third matching result and return it to the client.

8. A data grayscale enlargement device, characterized in that: include: A receiving module, configured to receive a data request sent by a client, wherein the data request includes a device ID and a tile ID; A first determination module, used to determine whether the tile ID is associated with new version data; The second judgment module is used to judge whether the device ID is in a preset volume group if new version data is associated; The return module is used to determine the response data and return it to the client according to the device ID, the dynamically configured grayscale volume release progress and the grayscale volume release offset if it is not in the preset volume release group.

9. A computer device comprising a memory, a processor, and computer-readable instructions stored in the memory and executed on the processor, characterized in that: When the processor executes the computer-readable instructions, the data grayscale enlargement method as described in any one of claims 1 to 7 is implemented.

10. A readable storage medium having computer readable instructions stored thereon, characterized in that: When the computer-readable instructions are executed by a processor, the data grayscale magnification method as described in any one of claims 1 to 7 is implemented.

Images