Experimental version distribution method, device, storage medium and computer equipment

By receiving access requests and updating version values ​​based on weights, and independent of the Hash algorithm and traffic sample size, smooth distribution of experimental versions is achieved, solving the problem of inaccurate allocation ratio in the prior art, and ensuring the accuracy of experimental results.

CN113268414BActive Publication Date: 2024-11-08GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110505916.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-10
Publication Date
2024-11-08
Estimated Expiration
2041-05-10

AI Technical Summary

Technical Problem

The existing experimental version allocation technology relies on the Hash algorithm and traffic sample size, and it is difficult to ensure that the allocation ratio of the experimental version is close to the preset ratio, especially when the traffic sample size is small, the allocation results are difficult to be accurate.

Method used

By receiving access requests, obtaining the current version value of the experimental version, updating the version value based on the weight, determining the target experimental version, and gradually allocating it to the user terminal to achieve smooth allocation of the experimental version, independent of the Hash algorithm and traffic sample size.

Benefits of technology

The distribution ratio of the experimental version is close to the preset ratio, ensuring the accuracy and effectiveness of the experimental results, and avoiding the influence of the uniformity of the Hash algorithm and the traffic scale.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113268414B_ABST
    Figure CN113268414B_ABST
Patent Text Reader

Abstract

The embodiment of the present application discloses a method, device, storage medium and computer equipment for allocating experimental versions, the method comprising: receiving a current access request for an experimental version of a test experiment, obtaining the current version value of each experimental version, the test experiment comprising at least two experimental versions, determining the target experimental version to be allocated in the experimental version based on the weight of each experimental version and the current version value of each experimental version, allocating the target experimental version to the user terminal that sent the current access request, then updating the version value of each experimental version, obtaining the current version value of each experimental version, then receiving the next access request for the experimental version of the test experiment, taking the next access request as the current access request, and executing the step of obtaining the current version value of each of the experimental versions. By adopting the embodiment of the present application, the experimental version is smoothly allocated to each access request, so that the final allocation ratio can be smoothly close to the ratio of the preset weight.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to a method, device, storage medium and computer equipment for distributing an experimental version. Background Art

[0002] In the Internet era, the update and iteration of various apps, websites, services, and systems inevitably require the establishment of an experimental system to measure the effect of versions. Only by controlling the direction of update and iteration based on user feedback on each version can the user experience be better improved. Among them, the ABtest experimental system is the most common tool for variable control and optimization direction selection, and data is the most effective path to support optimization. How to accurately allocate each experimental version to obtain the expected target data is the key to optimizing various versions, designs, and algorithms.

[0003] The existing allocation technology solution usually obtains the access ID information (such as device number, user account and other unique ID information) of the user access request, and then calculates the value corresponding to the access ID information according to the selected Hash algorithm, modulo 100 to get the remainder, and uses the remainder as the version number corresponding to the user access request, and then returns the page or data of the corresponding version. However, user access IDs have certain similarities. If the Hash algorithm is not properly selected, it cannot guarantee that the calculated Hash value is randomly and evenly distributed. Furthermore, even if a very uniform and random Hash algorithm is selected, if the requested traffic sample size is too small, it is also impossible to make the allocation result close to the allocation ratio of each experimental version. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, storage medium and computer device for allocating experimental versions, which can allocate experimental versions participating in the experiment to user terminals that send access requests, so that the final allocation ratio of each experimental version is smoothly close to the ratio of the preset experimental version weights.

[0005] The technical solution is as follows:

[0006] In a first aspect, an embodiment of the present application provides a method for distributing an experimental version, the method comprising:

[0007] Receiving a current access request for an experimental version of a test experiment, and obtaining a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0008] Based on the weight of each experimental version and the current version value of each experimental version, determine a target experimental version to be allocated from each experimental version, and allocate the target experimental version to the user terminal that sends the current access request;

[0009] Update the version value of each experimental version to obtain the current version value of each experimental version;

[0010] Receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and execute the step of obtaining the current version value of each experimental version.

[0011] In a second aspect, an embodiment of the present application provides an experimental version distribution device, the experimental version distribution device comprising:

[0012] A request receiving module, used to receive a current access request to an experimental version of a test experiment, and obtain a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0013] A version allocation module, configured to determine a target experimental version to be allocated from the experimental versions based on the weight of each experimental version and the current version value of each experimental version, and allocate the target experimental version to the user terminal that sends the current access request;

[0014] A version value updating module, used to update the version value of each experimental version to obtain the current version value of each experimental version;

[0015] The request receiving module is further used to receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and obtain the current version value of each experimental version.

[0016] In a third aspect, an embodiment of the present application provides a storage medium, which stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0017] In a fourth aspect, an embodiment of the present application provides a computer device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0018] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0019] In an embodiment of the present application, by receiving a current access request to an experimental version of a test experiment, the current version value of each experimental version is obtained, and based on the weight of each experimental version and the current version value of each experimental version, the target experimental version to be allocated is determined in the experimental version, and then the target experimental version is allocated to the user terminal that sends the current access request, and then the version value of each experimental version is updated to obtain the current version value of each experimental version, and then the next access request received is processed in the same manner. Using an embodiment of the present application, the weight of the experimental version participating in the experiment and the current version value of each experimental version are used to allocate the adapted target experimental version to the received access request one by one, without relying on the Hash algorithm and the traffic sample size of the access request, so that the final allocation ratio of each experimental version can be close to the ratio of the weight of each experimental version, and the smooth allocation of each experimental version is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 A flowchart of a method for distributing an experimental version is provided for an embodiment of the present application;

[0022] Figure 2 An example schematic diagram of an experimental version distribution method is provided for the embodiment of the present application;

[0023] Figure 3 A flowchart of a method for distributing an experimental version is provided for an embodiment of the present application;

[0024] Figure 4 An example schematic diagram of updating the current version value is proposed for the embodiment of the present application;

[0025] Figure 5 An example schematic diagram of determining a target experimental version is proposed for the embodiment of the present application;

[0026] Figure 6 A schematic diagram of the structure of a dispensing device of an experimental version is provided for the embodiment of the present application;

[0027] Figure 7 A schematic diagram of the structure of a version allocation module is provided for an embodiment of the present application;

[0028] Figure 8A schematic diagram of the structure of a version value update module is provided for an embodiment of the present application;

[0029] Fig. 9 A schematic diagram of the structure of a computer device is provided for an embodiment of the present application;

[0030] Fig.10 A schematic diagram of the structure of an operating system and a user space is provided for an embodiment of the present application;

[0031] Fig.11 yes Fig. 9 The architecture diagram of the Android operating system;

[0032] Fig.12 yes Fig. 9 Architecture diagram of the IOS operating system. DETAILED DESCRIPTION

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

[0034] In the description of the present application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In the description of the present application, it should be noted that, unless otherwise clearly specified and limited, "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood in specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are an "or" relationship.

[0035] In today's Internet-advanced world, various apps, websites, services, and systems need to continuously update and iterate their products in order to improve user experience and attract more users. However, it is very risky to arbitrarily change and update existing product solutions, so many companies or organizations use AB testing to determine the update and optimization direction for their own products. It is common to design two or more versions of AB for a single element while ensuring that other conditions are consistent, and then conduct tests and data collection, and finally select the version with better data results. In the process of AB testing, each experimental version will be allocated according to version characteristics and needs. Correctly allocating traffic to each experimental version according to the ratio set by the version developer is a prerequisite for ensuring the accuracy of the experimental test data.

[0036] In the related art, it is usually achieved by obtaining unique characteristic information of a user access request, for example, unique ID information such as a device number and an account number, and then using a selected hash algorithm to calculate a hash value corresponding to the unique characteristic information, and taking the remainder of the hash value as the return data of the corresponding experimental version of the user access request. The return data falls within a certain interval, and the certain interval is divided according to a preset ratio of each experimental version to obtain multiple small intervals corresponding to each experimental version. The experimental version is allocated to the user who sent the user access request according to the position of the return interval in the small interval. For example, for each user who sends a user access request, the Hash value of its unique feature information is calculated, and the Hash value is modulo 100 to obtain a remainder, the remainder is in the range of 0 to 99, and the preset distribution ratio of the four experimental versions ABCD is 1:7:1:1, then, if the remainder is in the range of 0 to 9, the corresponding user is allocated with the A experimental version, if the remainder is in the range of 10 to 79, the corresponding user is allocated with the B experimental version, if the remainder is in the range of 80 to 89, the corresponding user is allocated with the C experimental version, and if the remainder is in the range of 90 to 99, the corresponding user is allocated with the D experimental version. First, this distribution method relies on the randomness of the Hash algorithm. If the Hash value calculated by the Hash algorithm cannot be randomly and evenly distributed in the range of 0 to 99, it is impossible to achieve the distribution result that reaches the preset distribution ratio; further, even if the Hash value calculated by the Hash algorithm is sufficiently evenly distributed, it is difficult to make the final distribution result close to the preset distribution ratio when the scale of the experimental sample participating in the distribution is small.

[0037] The AB test traffic allocation scheme proposed in this application is not limited by the random uniformity of the Hash algorithm and the size of the experimental sample, and can smoothly allocate traffic according to the allocation ratio of the preset experimental version.

[0038] See also Figure 1, which is a flowchart of a method for distributing an experimental version provided in the present application embodiment. Figure 1 As shown, the experimental version distribution method may include the following steps S101 to S104.

[0039] S101, receiving a current access request for an experimental version of a test experiment, and obtaining a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0040] The test experiment refers to the AB test experiment. In the Internet era, the release of new products requires testing experiments on new and old versions of products. Different experimental users are allocated to the new and old versions of products. According to the feedback from the experimental users on the use of each version, it is determined which version of the product better meets the needs of the market and is more popular with users. This type of test experiment is generally called AB testing, and the AB test experiment includes at least two experimental versions. Generally, AB testing requires the construction of an AB test cloud platform, which can include various experimental versions, experimental users, experimental data, etc.

[0041] The current access request can be understood as an experimental user's access request to the experimental version of the test experiment. For example, four color design schemes are designed for a page button of a web page. An AB test experiment is conducted to test which color button design scheme is more attractive to users. For this experiment, the user's request to enter the web page is the current access request. The AB test cloud platform will assign one of the four color design schemes to the user based on this request.

[0042] The current version value refers to the version identification value used for each experimental version allocation, which can be used as the basis for users to allocate experimental versions. The current version value can be set to 0 before the experiment starts. The current version value can be input into the AB test cloud platform in advance by the experiment initiator before the experiment starts and saved in the database.

[0043] Specifically, an experimental version access request for the test experiment from an experimental user is received, and the current version value of each preset experimental version is obtained from the database.

[0044] S102, determining a target experimental version to be allocated from the experimental versions based on the weights of the experimental versions and the current version values ​​of the experimental versions, and allocating the target experimental version to the user terminal that sends the current access request;

[0045] The weight refers to the preset allocation ratio for each experimental version. For example, the preset allocation ratio of experimental version 1, experimental version 2 and experimental version 3 is 3:2:1. Then it can be considered that the weight of experimental version 1 is 3, the weight of experimental version 2 is 2, and the weight of experimental version 1 is 1.

[0046] The target experimental version refers to the experimental version assigned to the user terminal. For example, user terminal 1 participates in the AB test experiment of three experimental versions: experimental version 1, experimental version 2, and experimental version 3. The AB test cloud platform receives the current access request sent by user terminal 1, and calculates the final allocation result as experimental version 1 through the set allocation algorithm. Then experimental version 1 is the target experimental version, and user terminal 1 will participate in the test experiment of experimental version 1.

[0047] Specifically, the weight of each experimental version and the current version value of each experimental version are calculated according to the set allocation algorithm, and the target experimental version to be allocated is determined among the experimental versions based on the calculated results, and then the target experimental version is allocated to the corresponding user terminal, where the user terminal refers to the user terminal that sends the corresponding current access request.

[0048] Allocating the target experimental version to the corresponding user terminal is to allocate traffic to the target experimental version. The number of user terminals using the target experimental version is the traffic of the target experimental version. Finally, the traffic ratio obtained by each experimental version should be close to the preset allocation ratio. The allocation algorithm is used to achieve an allocation effect that is infinitely close to the preset allocation ratio.

[0049] S103, updating the version value of each experimental version to obtain the current version value of each experimental version;

[0050] The version value of each of the experimental versions refers to the version value calculated from the current version value of each of the experimental versions in step S102.

[0051] Specifically, the version value calculated based on the current version value of each experimental version in step S102 is updated, and the updated version value is used as the current version value of each experimental version.

[0052] It is not difficult to understand that the updated version value is used as the current version value of each experimental version for calculation when receiving the experimental version access request of the next experimental user.

[0053] S104, receiving a next access request for the experimental version of the test experiment, and using the next access request as the current access request.

[0054] The next access request refers to an experimental version access request from another user terminal to enter the test experiment. The difference between the next access request and the access request allocated for this version may be that the device ID, user ID or terminal identifier of the user terminal sending the access request is different.

[0055] Specifically, after executing the experimental version allocation for one user terminal, continue to receive an experimental version access request from another user terminal to enter the test experiment, use the experimental version access request as the current access request, and repeat the operation of step S101 to allocate the experimental version to the other user terminal.

[0056] It is not difficult to understand that step S104 is used to loop all operations of the embodiment of the present application, and is used to implement the allocation of experimental versions to all user terminals entering the test experiment. Usually, there is a round cycle effect for allocating experimental versions to all user terminals entering the test experiment. The round refers to the process of allocating experimental versions to a user terminal. Each specific number of rounds is a round. After allocating experimental versions to user terminals in a round, the allocation ratio reaches the preset allocation ratio, and then the next round is entered to allocate experimental versions to user terminals. As long as the number of user terminals is an integer multiple of the specific number, the final allocation ratio will fully comply with the set allocation ratio. In general, the number of user terminals will not be very small, and is much larger than the specific number. Even if the number of user terminals is not an integer multiple of the specific number, the final allocation ratio will be extremely close to the set allocation ratio. The specific number is usually the sum of the weights of each experimental version.

[0057] See also Figure 2 , which provides an example schematic diagram of an experimental version distribution method for an embodiment of the present application.

[0058] like Figure 2 As shown in , the AB test cloud platform receives access requests from user terminals and allocates corresponding experimental versions to each user terminal after calculation. Figure 2 As shown, there are three experimental versions in the test experiment, among which the weight A of experimental version A is 2, the weight B of experimental version B is 1, and the weight C of experimental version C is 2. User terminal 1 sends the current access request to the AB test cloud platform. After calculation, the AB test cloud platform allocates experimental version A to user terminal 1, and receives the next access request from user terminal 2 in turn, allocates experimental version C to user terminal 2, and repeats the operation of receiving access requests and allocating experimental versions, allocating experimental version C to user terminal 2, experimental version B to user terminal 3, experimental version A to user terminal 4, and experimental version C to user terminal 5. At this time, a total of 5 user terminals have been allocated experimental versions, and the allocation ratio just reaches the preset weight ratio of 2:1:2, that is, user terminal 1 to user terminal 5 are one round, and user terminal 6 to user terminal 10 are another round. The allocation ratio within each round is 2:1:2. Continue to repeat the operation of receiving access requests and allocating experimental versions to allocate corresponding experimental versions to all user terminals participating in the AB test experiment.

[0059] In an embodiment of the present application, by receiving a current access request to an experimental version of a test experiment, the current version value of each experimental version is obtained, and based on the weight of each experimental version and the current version value of each experimental version, the target experimental version to be allocated is determined in the experimental version, and then the target experimental version is allocated to the user terminal that sends the current access request, and then the version value of each experimental version is updated to obtain the current version value of each experimental version, and then the next access request to the experimental version of the test experiment is received and allocated in the same manner. By adopting an embodiment of the present application, the weight of the experimental version participating in the experiment and the current version value of each experimental version are used to allocate the adapted target experimental version to the received access request one by one, without relying on the Hash algorithm and the traffic sample size of the sending access request, so that the final allocation ratio of each experimental version can be close to the ratio of the weight of each experimental version, and the smooth allocation of each experimental version is achieved.

[0060] See also Figure 3 , which is a flowchart of a method for distributing an experimental version provided in the present application embodiment. Figure 3 As shown, the experimental version distribution method may include the following steps S201 to S206.

[0061] S201, receiving a current access request for an experimental version of a test experiment, and obtaining a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0062] For step S201, please refer to the description of step S101 in another embodiment, which will not be described in detail here.

[0063] S202, updating the current version value of each of the experimental versions based on the weight of each of the experimental versions to obtain an updated version value of each of the experimental versions;

[0064] The updated version value refers to the current version value after the current version value is updated, and the weight refers to the preset allocation ratio for each experimental version. The weight, the current version value and the corresponding experimental version data can be input into the AB test cloud platform by the experiment initiator in advance before the experiment begins, and saved in the database. During the experiment, the weight and the current version value data in the database are called for calculation to allocate each experimental version. The database can be Redis, which is an open source log-type, Key-Value database written in the standard C language developed by the American National Standards Institute (ANSI), supports the network, can be based on memory or can be persistent, and provides application programming interfaces (Application Programming Interface, API) in multiple languages.

[0065] Specifically, the weight of the experimental version and the current version value of the experimental version are obtained, and the current version value is updated using the weight to obtain the updated current version value, i.e., the updated version value. The update can be any operation rule in the field of mathematics, including but not limited to basic operation rules such as addition, subtraction, multiplication, and division.

[0066] In a feasible implementation manner, the weight of each experimental version and the current version value of each experimental version are summed to obtain an updated version value of each experimental version.

[0067] Generally, before the experiment begins, the experimenter will upload the weight, the current version value, and the experimental version data as initial values ​​to the AB test cloud platform, and the current version value may be 0.

[0068] Specifically, the current version value of each experimental version is added to the corresponding weight of each experimental version to generate an updated version value of each experimental version.

[0069] Please also see Figure 4 , an example schematic diagram of updating the current version value is proposed for an embodiment of the present application.

[0070] like Figure 4 As shown, a test experiment has three experimental versions, among which the weight A of experimental version A is 2, the weight B of experimental version B is 1, and the weight C of experimental version C is 2. The corresponding current version values ​​of experimental version A, experimental version B and experimental version C are all 0. Then the updated version values ​​after updating the current version values ​​correspond to the updated version value A of experimental version A is 2, the updated version value B of experimental version B is 1, and the updated version value C of experimental version C is 2.

[0071] S203, determining a target experimental version to be allocated based on the update version value of each of the experimental versions, and allocating the target experimental version to the user terminal that sends the current access request;

[0072] It is not difficult to understand that after the operation of step S202, each experimental version has a corresponding update version value, and determining the target experimental version to be assigned based on the update version value of each experimental version means determining the target experimental version in each experimental version based on each update version of each experimental version, and assigning the target experimental version to the user terminal that sends the current access request.

[0073] Furthermore, the target experimental version may be the experimental version with the largest update version value among the experimental versions, that is, the maximum update version value is determined among the update version values ​​of the experimental versions, and the experimental version corresponding to the maximum update version value is determined as the target experimental version to be allocated.

[0074] Specifically, the update version values ​​of the experimental versions are compared to determine the maximum update version value, and the experimental version corresponding to the maximum update version value is determined as the target experimental version to be allocated.

[0075] Optionally, if the maximum update version values ​​include multiple ones, an experimental version corresponding to any one of the maximum update version values ​​is determined as the target experimental version to be allocated.

[0076] Please also see Figure 5 , an example schematic diagram for determining a target experimental version is proposed for an embodiment of the present application.

[0077] like Figure 5 As shown, the update version value A of experimental version A is 2, the update version value B of experimental version B is 1, and the update version value C of experimental version C is 2, then update version value A = update version value C > update version value B, and the experimental version A corresponding to the update version value A is selected from update version value A and update version value C as the target experimental version to be assigned.

[0078] S204, obtaining the sum of the weights of the experimental versions;

[0079] The sum value may be generated by adding the weights of the experimental versions.

[0080] S205, updating the updated version value of the target experimental version based on the sum value, and retaining the updated version values ​​of the remaining experimental versions except the target experimental version, to obtain the current version value of each of the experimental versions;

[0081] Specifically, the updated version value of the target experimental version is updated using the sum value, and the updated version values ​​of the remaining experimental versions except the target experimental version obtained in step S202 are retained, and the updated version values ​​of the remaining experimental versions except the target experimental version and the updated version value of the target experimental version after being updated with the sum value are used as the current version values ​​of each experimental version when the next experimental user's experimental version access request is received.

[0082] The updating of the updated version value of the target experimental version based on the sum value includes calculating the difference between the updated version value of the target experimental version and the sum value, and updating the updated version value of the target experimental version based on the difference, that is, using the difference as the current version value of the target experimental version when receiving an experimental version access request from the next experimental user.

[0083] Retaining the updated version values ​​of the remaining experimental versions except the target experimental version means using the updated version values ​​of the remaining experimental versions except the target experimental version as the current version values ​​corresponding to the remaining experimental versions when receiving an experimental version access request from the next experimental user.

[0084] For example, if the weight A of experimental version A is 2, the weight B of experimental version B is 1, and the weight C of experimental version C is 2, the sum = weight A + weight B + weight C = 2 + 1 + 2 = 5, the updated version value A of the target experimental version A is 2, the updated version value B of experimental version B is 1, and the updated version value C of experimental version C is 2, then the current version value A = updated version value A - sum = -3, the current version value B = 1, and the current version value C = 2.

[0085] S206: Receive a next access request for the experimental version of the test experiment, and use the next access request as the current access request.

[0086] Specifically, after executing the experimental version allocation for one user terminal, continue to receive an experimental version access request from another user terminal to enter the test experiment, take the experimental version access request as the current access request, and repeat the operation of step S201 to allocate the experimental version to the other user terminal. Allocating the experimental version to one user terminal is considered as a round, and each specific number of rounds is considered as one round. The allocation ratio of each round is a preset allocation ratio. Please refer to the following table for details.

[0087]

[0088]

[0089] Among them, the corresponding meaning of each parameter in each set in the table is [experimental version, current version value, weight]. For example, A in [A,0,2] refers to experimental version A, 0 refers to the current version value of 0, and 2 refers to the weight of experimental version A of 2. As shown in the table, the test experiment has three experimental versions, where the weight A of experimental version A is 2, the weight B of experimental version B is 1, and the weight C of experimental version C is 2. The sum of the weights is 5, and after 5 rounds of experimental version allocation, the version value of each experimental version obtained after updating the updated version value of each experimental version in the fifth round is exactly the same as the current version value of the first round, which means that five rounds are one round. It is not difficult to see from the data in the table that after 5 rounds of experimental version allocation, it can be seen from the allocation results that the allocation ratio is A:B:C=2:1:2, that is, the allocation ratio within each round is the preset weight ratio, and the preset weight ratio is equal to the preset allocation ratio.

[0090] In an embodiment of the present application, by receiving a current allocation request for an experimental version of a test experiment, the current version value of each experimental version is obtained, and then the current version value of each experimental version is updated based on the weight of each experimental version to obtain the updated version value of each experimental version, and then the target experimental version to be allocated is determined based on the updated version value of each experimental version, and the target experimental version is allocated to the user terminal that sends the first allocation request, and then by obtaining the sum of the weights of each experimental version, the updated version value of the target experimental version is updated based on the sum, and the updated version values ​​of the remaining experimental versions except the target experimental version are retained to obtain the current version value of each experimental version, and then the next allocation request for the experimental version of the test experiment is received. Using the embodiment of the present application, by using the weight of the experimental version participating in the experiment to update the current version value of each experimental version, the adapted target experimental version is allocated one by one for the received access request, without relying on the Hash algorithm and the traffic sample size of the access request, the final allocation ratio of each experimental version can be close to the ratio of the weight of each experimental version, and the smooth allocation of each experimental version is achieved.

[0091] The following will be combined Figure 6 to Figure 8 , the experimental version of the distribution device provided in the embodiment of the present application is introduced in detail. It should be noted that, Figure 6 to Figure 8 The experimental version of the distribution device is used to execute this application Figure 1 to Figure 5 For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Figure 1 to Figure 5 The embodiment shown.

[0092] See also Figure 6, is a schematic diagram of the structure of a distribution device of an experimental version provided in the embodiment of the present application. Figure 6 As shown, the experimental version distribution device 1 can be implemented as all or part of the terminal device through software, hardware or a combination of both. According to some embodiments, the experimental version distribution device 1 includes a request receiving module 11, a version distribution module 12, and a version value updating module 13, specifically including:

[0093] A request receiving module 11 is used to receive a current access request for an experimental version of a test experiment, and obtain a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0094] A version allocation module 12, configured to determine a target experimental version to be allocated from the experimental versions based on the weight of each experimental version and the current version value of each experimental version, and allocate the target experimental version to the user terminal that sends the current access request;

[0095] A version value updating module 13 is used to update the version value of each experimental version to obtain the current version value of each experimental version;

[0096] The request receiving module 11 is further used to receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and obtain the current version value of each experimental version.

[0097] Optional, such as Figure 7 As shown, a schematic diagram of the structure of a version allocation module 12 is provided in an embodiment of the present application.

[0098] The version distribution module 12 includes:

[0099] An updated version value acquiring unit 121 is used to update the current version value of each experimental version based on the weight of each experimental version to obtain an updated version value of each experimental version;

[0100] The target experimental version determining unit 122 is configured to determine a target experimental version to be allocated based on the update version value of each experimental version, and allocate the target experimental version to the user terminal that sends the current access request.

[0101] Optionally, the update version value acquiring unit 121 is specifically configured to:

[0102] The weight of each experimental version and the current version value of each experimental version are summed to obtain an updated version value of each experimental version.

[0103] Optionally, the target experimental version determining unit 122 is specifically configured to:

[0104] A maximum update version value is determined among the update version values ​​of the experimental versions, and the experimental version corresponding to the maximum update version value is determined as the target experimental version to be allocated.

[0105] Optionally, the target experimental version determining unit 122 is specifically configured to:

[0106] An experimental version corresponding to any one of the maximum update version values ​​is determined as a target experimental version to be allocated.

[0107] Optional, such as Figure 8 As shown, a schematic diagram of the structure of a version value updating module 13 is provided in an embodiment of the present application.

[0108] The version value updating module 13 includes:

[0109] A weight sum acquisition unit 131 is used to acquire the sum of the weights of each of the experimental versions;

[0110] The version value updating unit 132 is used to update the updated version value of the target experimental version based on the sum value, and retain the updated version values ​​of the remaining experimental versions except the target experimental version to obtain the current version value of each of the experimental versions.

[0111] Optionally, the version value updating unit 132 is specifically configured to:

[0112] Calculate the difference between the updated version value of the target experimental version and the sum value;

[0113] The updated version value of the target experimental version is updated based on the difference value.

[0114] It should be noted that the experimental version distribution device provided in the above embodiment only uses the division of the above functional modules as an example when executing the experimental version distribution method. In actual applications, the above functional distribution can be completed by different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the experimental version distribution device provided in the above embodiment and the experimental version distribution method embodiment belong to the same concept. The implementation process is detailed in the method embodiment and will not be repeated here.

[0115] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0116] In an embodiment of the present application, by receiving a current access request to an experimental version of a test experiment, the current version value of each experimental version is obtained, and based on the weight of each experimental version and the current version value of each experimental version, the target experimental version to be allocated is determined in the experimental version, and then the target experimental version is allocated to the user terminal that sends the current access request, and then the version value of each experimental version is updated to obtain the current version value of each experimental version, and then the next access request to the experimental version of the test experiment is received and allocated in the same manner. By adopting an embodiment of the present application, the weight of the experimental version participating in the experiment and the current version value of each experimental version are used to allocate the adapted target experimental version to the received access request one by one, without relying on the Hash algorithm and the traffic sample size of the sending access request, so that the final allocation ratio of each experimental version can be close to the ratio of the weight of each experimental version, and the smooth allocation of each experimental version is achieved.

[0117] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 1 to Figure 5 The distribution method of the experimental version in the embodiment shown in the figure can be found in the specific execution process. Figure 1 to Figure 5 The specific description of the illustrated embodiment will not be repeated here.

[0118] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figure 1 to Figure 5 The distribution method of the experimental version in the embodiment shown in the figure can be found in the specific execution process. Figure 1 to Figure 5 The specific description of the illustrated embodiment will not be repeated here.

[0119] Please refer to Fig. 9 , which shows a block diagram of a computer device provided by an exemplary embodiment of the present application. The computer device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected via a bus 150.

[0120] The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts of the entire computer device, and executes various functions and processes data of the computer device 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 120, and calling data stored in the memory 120. Optionally, the processor 110 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 110 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 110, but may be implemented separately through a communication chip.

[0121] The memory 120 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer-readable storage medium. The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a storage program area and a storage data area, wherein the storage program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The operating system may be an Android system, including a system deeply developed based on the Android system, an IOS system developed by Apple, including a system deeply developed based on the IOS system or other systems. The storage data area may also store data created by the computer device during use, such as a phone book, audio and video data, chat record data, etc.

[0122] See also Fig.10As shown, the memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party applications run in the user space. In order to ensure that different third-party applications can achieve good operating results, the operating system allocates corresponding system resources to different third-party applications. However, different application scenarios in the same third-party application also have different requirements for system resources. For example, in the local resource loading scenario, the third-party application has higher requirements for disk reading speed; in the animation rendering scenario, the third-party application has higher requirements for GPU performance. The operating system and third-party applications are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in a timely manner, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application.

[0123] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to open up data communication between third-party applications and the operating system so that the operating system can obtain the current scenario information of third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0124] Taking the Android operating system as an example, the programs and data stored in the memory 120 are as follows: Fig.11As shown, the memory 120 may store a Linux kernel layer 320, a system runtime layer 340, an application framework layer 360 and an application layer 380, wherein the Linux kernel layer 320, the system runtime layer 340 and the application framework layer 360 belong to the operating system space, and the application layer 380 belongs to the user space. The Linux kernel layer 320 provides underlying drivers for various hardware of computer devices, such as display drivers, audio drivers, camera drivers, Bluetooth drivers, Wi-Fi drivers, power management, etc. The system runtime layer 340 provides the main feature support for the Android system through some C / C++ libraries. For example, the SQLite library provides database support, the OpenGL / ES library provides 3D drawing support, and the Webkit library provides browser kernel support, etc. The system runtime layer 340 also provides an Android runtime library (Android runtime), which mainly provides some core libraries, allowing developers to use Java language to write Android applications. The application framework layer 360 provides various APIs that may be used when building applications. Developers can also use these APIs to build their own applications, such as activity management, window management, view management, notification management, content provider, package management, call management, resource management, and location management. At least one application runs in the application layer 380. These applications can be native applications that come with the operating system, such as contact applications, text messaging applications, clock applications, camera applications, etc.; they can also be third-party applications developed by third-party developers, such as game applications, instant messaging applications, photo beautification applications, experimental version distribution applications, etc.

[0125] Taking the operating system as an IOS system as an example, the programs and data stored in the memory 120 are as follows: Fig.12As shown, the IOS system includes: a core operating system layer 420 (Core OS layer), a core service layer 440 (Core Services layer), a media layer 460 (Media layer), and a touchable layer 480 (Cocoa Touch Layer). The core operating system layer 420 includes the operating system kernel, drivers, and underlying program frameworks, which provide functions closer to the hardware for use by the program framework located in the core service layer 440. The core service layer 440 provides system services and / or program frameworks required by the application, such as the foundation framework, account framework, advertising framework, data storage framework, network connection framework, geographic location framework, motion framework, etc. The media layer 460 provides audio-visual interfaces for the application, such as graphics and image related interfaces, audio technology related interfaces, video technology related interfaces, and wireless playback (AirPlay) interfaces for audio and video transmission technologies. The touchable layer 480 provides various commonly used interface-related frameworks for application development, and the touchable layer 480 is responsible for the user's touch interaction operations on the computer device. For example, local notification service, remote push service, advertising framework, game tool framework, message user interface (UI) framework, user interface UIKit framework, map framework, etc.

[0126] exist Fig.12 Among the frameworks shown, the frameworks related to most applications include but are not limited to: the basic framework in the core service layer 440 and the UIKit framework in the touchable layer 480. The basic framework provides many basic object classes and data types, provides the most basic system services for all applications, and has nothing to do with UI. The classes provided by the UIKit framework are basic UI class libraries for creating touch-based user interfaces. iOS applications can provide UIs based on the UIKit framework, so it provides the basic architecture of applications for building user interfaces, drawing, processing and user interaction events, responding to gestures, etc.

[0127] Among them, the method and principle of implementing data communication between third-party applications and the operating system in the IOS system can be referred to the Android system, and this application will not go into details here.

[0128] Among them, the input device 130 is used to receive input instructions or data, and the input device 130 includes but is not limited to a keyboard, a mouse, a camera, a microphone or a touch device. The output device 140 is used to output instructions or data, and the output device 140 includes but is not limited to a display device and a speaker. In one example, the input device 130 and the output device 140 can be combined, and the input device 130 and the output device 140 are touch screens, which are used to receive touch operations on or near them by users using any suitable objects such as fingers and touch pens, and to display the user interfaces of various applications. The touch screen is usually set on the front panel of the computer device. The touch screen can be designed as a full screen, a curved screen or a special-shaped screen. The touch screen can also be designed as a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in the embodiments of the present application.

[0129] In addition, those skilled in the art will appreciate that the structure of the computer device shown in the above drawings does not constitute a limitation on the computer device, and the computer device may include more or fewer components than shown, or combine certain components, or arrange the components differently. For example, the computer device also includes a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (WiFi) module, a power supply, a Bluetooth module, and other components, which will not be described in detail here.

[0130] In the embodiment of the present application, the execution subject of each step may be the computer device described above. Optionally, the execution subject of each step is the operating system of the computer device. The operating system may be an Android system, an IOS system, or other operating systems, which is not limited in the embodiment of the present application.

[0131] The computer device of the embodiment of the present application may also be equipped with a display device, which may be any device capable of realizing a display function, such as a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. The user may use the display device on the computer device 101 to view displayed text, images, videos and other information. The computer device may be a smart phone, a tablet computer, a gaming device, an AR (Augmented Reality) device, a car, a data storage device, an audio playback device, a video playback device, a notebook, a desktop computing device, a wearable device such as an electronic watch, an electronic glasses, an electronic helmet, an electronic bracelet, an electronic necklace, electronic clothing and other devices.

[0132] exist Fig. 9 In the computer device shown, the processor 110 can be used to call the experimental version of the allocation program stored in the memory 120, and specifically perform the following operations:

[0133] Receiving a current access request for an experimental version of a test experiment, and obtaining a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions;

[0134] Based on the weight of each of the experimental versions and the current version value of each of the experimental versions, determine a target experimental version to be allocated from the experimental versions, and allocate the target experimental version to the user terminal that sends the current access request;

[0135] Update the version value of each experimental version to obtain the current version value of each experimental version;

[0136] Receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and execute the step of obtaining the current version value of each experimental version.

[0137] In one embodiment, the processor 110 performs the following operations when determining the target experimental version to be allocated in the experimental version based on the weight of each experimental version and the current version value of each experimental version and allocating the target experimental version to the user terminal that sends the current access request:

[0138] Based on the weight of each experimental version, the current version value of each experimental version is updated respectively to obtain an updated version value of each experimental version;

[0139] A target experimental version to be allocated is determined based on the updated version value of each experimental version, and the target experimental version is allocated to the user terminal that sends the current access request.

[0140] In one embodiment, when the processor 110 executes the updating of the current version value of each experimental version based on the weight of each experimental version to obtain the updated version value of each experimental version, the processor 110 specifically performs the following operations:

[0141] The weight of each experimental version and the current version value of each experimental version are summed to obtain an updated version value of each experimental version.

[0142] In one embodiment, when the processor 110 determines the target experimental version to be allocated based on the update version value of each experimental version and allocates the target experimental version to the user terminal that sends the current access request, the processor 110 specifically performs the following operations:

[0143] A maximum update version value is determined among the update version values ​​of the experimental versions, and the experimental version corresponding to the maximum update version value is determined as the target experimental version to be allocated.

[0144] In one embodiment, when the processor 110 determines the maximum update version value among the update version values ​​of the experimental versions and determines the experimental version corresponding to the maximum update version value as the target experimental version to be allocated, if the maximum update version value includes multiple values, the processor 110 specifically performs the following operations:

[0145] An experimental version corresponding to any one of the maximum update version values ​​is determined as a target experimental version to be allocated.

[0146] In one embodiment, when the processor 110 executes the updating of the version value of each experimental version to obtain the current version value of each experimental version, the processor 110 specifically performs the following operations:

[0147] Obtaining the sum of the weights of the experimental versions;

[0148] The updated version value of the target experimental version is updated based on the sum value, and the updated version values ​​of the remaining experimental versions except the target experimental version are retained to obtain the current version value of each of the experimental versions.

[0149] In one embodiment, when the processor 110 executes the updating of the update version value of the target experimental version based on the sum value, the processor 110 specifically performs the following operations:

[0150] Calculate the difference between the updated version value of the target experimental version and the sum value;

[0151] The updated version value of the target experimental version is updated based on the difference value.

[0152] In an embodiment of the present application, by receiving a current allocation request for an experimental version of a test experiment, the current version value of each experimental version is obtained, and then the current version value of each experimental version is updated based on the weight of each experimental version to obtain the updated version value of each experimental version, and then the target experimental version to be allocated is determined based on the updated version value of each experimental version, and the target experimental version is allocated to the user terminal that sends the first allocation request, and then by obtaining the sum of the weights of each experimental version, the updated version value of the target experimental version is updated based on the sum, and the updated version values ​​of the remaining experimental versions except the target experimental version are retained to obtain the current version value of each experimental version, and then the next allocation request for the experimental version of the test experiment is received. Using the embodiment of the present application, by using the weight of the experimental version participating in the experiment to update the current version value of each experimental version, the adapted target experimental version is allocated one by one for the received access request, without relying on the Hash algorithm and the traffic sample size of the access request, the final allocation ratio of each experimental version can be close to the ratio of the weight of each experimental version, and the smooth allocation of each experimental version is achieved.

[0153] Those skilled in the art can clearly understand that the technical solution of the present application can be implemented with the help of software and / or hardware. The "unit" and "module" in this specification refer to software and / or hardware that can independently complete or cooperate with other components to complete specific functions, where the hardware can be, for example, a field programmable gate array (FPGA), an integrated circuit (IC), etc.

[0154] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0155] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0156] In the several embodiments provided in the present application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0157] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0158] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0159] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, disk or optical disk and other media that can store program code.

[0160] A person skilled in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by entering a program to instruct the relevant hardware. The program may be stored in a computer-readable memory, and the memory may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0161] The above is only an exemplary embodiment of the present disclosure, and the scope of the present disclosure cannot be limited thereto. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the specification and practicing the disclosure here, those skilled in the art will easily think of other embodiments of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field not recorded in the present disclosure. The description and examples are only regarded as exemplary, and the scope and spirit of the present disclosure are defined by the claims.

Claims

1. A method for distributing an experimental version, characterized in that: The method comprises: Receiving a current access request for an experimental version of a test experiment, and obtaining a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions; Based on the weight of each experimental version, the current version value of each experimental version is updated respectively to obtain an updated version value of each experimental version; Determine a target experimental version to be allocated based on the update version value of each of the experimental versions, and allocate the target experimental version to the user terminal that sends the current access request; Update the version value of each experimental version to obtain the current version value of each experimental version; Receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and execute the step of obtaining the current version value of each experimental version.

2. The method for distributing an experimental version according to claim 1, characterized in that: The updating of the current version value of each experimental version based on the weight of each experimental version to obtain the updated version value of each experimental version includes: The weight of each experimental version and the current version value of each experimental version are summed to obtain an updated version value of each experimental version.

3. The method for distributing an experimental version according to claim 1, characterized in that: The determining the target experimental version to be allocated based on the updated version value of each experimental version includes: A maximum update version value is determined among the update version values ​​of the experimental versions, and the experimental version corresponding to the maximum update version value is determined as the target experimental version to be allocated.

4. The method for distributing the experimental version according to claim 3, characterized in that: When the maximum update version value includes multiple values, determining the experimental version corresponding to the maximum update version value as the target experimental version to be allocated includes: An experimental version corresponding to any one of the maximum update version values ​​is determined as a target experimental version to be allocated.

5. The method for distributing an experimental version according to claim 1, characterized in that: The updating of the version value of each experimental version to obtain the current version value of each experimental version includes: Obtaining the sum of the weights of the experimental versions; The updated version value of the target experimental version is updated based on the sum value, and the updated version values ​​of the remaining experimental versions except the target experimental version are retained to obtain the current version value of each of the experimental versions.

6. The method for distributing the experimental version according to claim 5, characterized in that: The updating of the updated version value of the target experimental version based on the sum value includes: Calculate the difference between the updated version value of the target experimental version and the sum value; The updated version value of the target experimental version is updated based on the difference value.

7. An experimental version of the dispensing device, characterized in that: include: A request receiving module, used to receive a current access request to an experimental version of a test experiment, and obtain a current version value of each of the experimental versions, wherein the test experiment includes at least two experimental versions; A version allocation module, used to update the current version value of each experimental version based on the weight of each experimental version, obtain the updated version value of each experimental version, determine the target experimental version to be allocated based on the updated version value of each experimental version, and allocate the target experimental version to the user terminal that sent the current access request; A version value updating module, used to update the version value of each experimental version to obtain the current version value of each experimental version; The request receiving module is further used to receive a next access request for the experimental version of the test experiment, use the next access request as the current access request, and obtain the current version value of each experimental version.

8. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the method as claimed in any one of claims 1 to 6.