CN110825959B

CN110825959B - Data transmission method and selection method and device of list data acquisition model

Info

Publication number: CN110825959B
Application number: CN201910943683.7A
Authority: CN
Inventors: 叶帅; 孙会业; 王志普; 问志光; 陈峤; 张凯瑞
Original assignee: Koukouxiangchuan Beijing Network Technology Co ltd
Current assignee: Koukouxiangchuan Beijing Network Technology Co ltd
Priority date: 2019-09-30
Filing date: 2019-09-30
Publication date: 2023-05-23
Anticipated expiration: 2039-09-30
Also published as: CN110825959A

Abstract

After an application program obtains a data request message sent by a client, obtaining target version engine data corresponding to a target engine data version identifier in a data engine, and obtaining target list data through a multi-value list data obtaining function capable of obtaining list data of a target version in a multi-value field. The method avoids using a plurality of data engines to store engine data of different versions, and does not need to use a plurality of fields to store engine data of different versions, so that the application program can quickly and efficiently provide list data outwards.

Description

Data transmission method and selection method and device of list data acquisition model

Technical Field

The application relates to the field of internet, in particular to a data sending method and device. The application also relates to a selection method and a selection device for the list data acquisition model.

Background

In recent years, with the development of internet technology, application programs are used throughout the life of people, and great convenience is brought to the life of people. In general, an application program obtains engine data through its corresponding server end, stores the obtained engine data in its data engine, and when the application program needs to provide data to an external object, such as a user or other application programs, the application program obtains corresponding engine data in its data engine by obtaining a corresponding data request message, and provides the engine data to the external object.

Currently, the AB experiment capability of engine data of an application program is poor, wherein the AB experiment of engine data refers to that when the application program obtains the same class of data, the application program often obtains multiple versions of the class of data, when the application program provides engine data outwards through a data engine of the application program, different versions of engine data are provided for different external objects in a targeted manner, and performance information of the different versions of engine data is judged by continuously tracking subsequent effects of the data so as to determine which version of engine data is used on line. For example, for a store network leaderboard, an application may provide A, B two versions of the leaderboard data at the same time, when the leaderboard data is provided to the outside, the application will typically provide the a version of the leaderboard data to the users 1-100, provide the B version of the leaderboard data to the users 200-300, continuously track the page click rate and the order amount brought by the different versions of the leaderboard data, and evaluate A, B the performance of the two versions of the leaderboard data according to the data to finally determine which version to use.

When the data engine of the current application program performs an AB experiment, the common practice is as follows: 1. newly creating a plurality of data engines, storing engine data of different versions in different engines, and determining which data engine's engine data to use through a data request message of an external object; 2. in the same data engine, a plurality of data item fields of different versions are correspondingly set for engine data of different versions. The above methods have certain disadvantages, wherein the first scheme can excessively waste storage resources; in the second approach, as data item fields continue to increase, performance of the data engine tends to decrease, and even render the data engine unusable. Due to the defects, the problems of untimely data provision and low efficiency exist in the AB experiment of the existing application program.

Disclosure of Invention

The application provides a data sending method for solving the problems that data provision is not timely and efficiency is low when an existing application program performs an AB experiment.

The application provides a data transmission method, which comprises the following steps:

acquiring a data request message sent by a client, wherein the data request message is used for acquiring list data corresponding to a target list category identifier;

acquiring a target engine data version identifier and acquiring target version engine data corresponding to the target engine data version identifier, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target version engine data comprises at least one version of list data corresponding to the target list category identifier;

acquiring function information according to the target engine data version identifier and the multi-value list data, and acquiring target list data from the target engine data version identifier;

and providing the target engine data version identification and the target list data to the client.

Optionally, the obtaining the target engine data version identifier includes:

acquiring a user identifier and the target list category identifier from the data request message;

And acquiring the target engine data version identification according to the user identification and the target list category identification.

Optionally, the obtaining the target engine data version identifier according to the user identifier and the target list category identifier includes:

according to the user identification, acquiring an engine data version identification corresponding to the user identification from the corresponding relation between the user identification and the engine data version identification;

and acquiring the target engine data version identifier according to the target list category identifier and the engine data version identifier corresponding to the user identifier.

Optionally, the obtaining the target version engine data corresponding to the target engine data version identifier includes:

and obtaining engine data comprising the target engine data version identifier from total engine data, and taking the engine data comprising the target engine data version identifier as the target version engine data, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

Optionally, the list data of at least one version corresponding to the target list category identifier is obtained through the following steps:

Acquiring a business object corresponding to the target list category identifier;

acquiring source data related to the business object;

performing data mining processing on the source data to acquire list data of at least one version of the business object;

and taking the list data of at least one version of the business object as the list data of at least one version corresponding to the target list category identification.

Optionally, the obtaining the service object corresponding to the target list category identifier includes:

acquiring a business category identifier corresponding to the target list category identifier;

and acquiring the business object corresponding to the target list category identifier and the business category identifier.

Optionally, the data mining processing is performed on the source data to obtain list data of at least one version of the service object, including:

and performing data mining processing on the source data by using at least one list data acquisition model corresponding to the target list category identifier and the service category identifier to acquire list data of at least one version of the service object.

Optionally, the step of using at least one list data acquisition model corresponding to the target list category identifier and the service category identifier to perform data mining processing on the source data to acquire at least one version of list data of the service object includes:

Acquiring a first list data acquisition model;

using the first list data acquisition model to perform data mining processing on the source data to acquire first list data of the business object;

acquiring a first engine data record to be stored of the business object according to the first list data; and writing the first engine data record to be stored into total engine data to acquire first version engine data aiming at the business object, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

Optionally, the obtaining, according to the first list data, a first engine data record to be stored of the service object includes:

storing the content of at least one data item in the first list data into at least one multi-value engine data item of the business object, wherein the multi-value engine data item is used for storing the content of multiple versions of the same data item of the business object;

and acquiring a first engine data record to be stored of the business object according to the at least one multi-value engine data item.

Optionally, the multi-value list data obtaining function information includes multi-value version position information obtaining function information and multi-value list data item obtaining function information;

The obtaining function information according to the target engine data version identifier and the multi-value list data, obtaining target list data from the target engine data version, includes:

acquiring a data record of the engine to be processed from the target version engine data

Acquiring function information according to the multi-value version position information, and acquiring position information of list data corresponding to the target engine data version identifier in a multi-value engine data item of the to-be-processed engine data record;

and acquiring function information and the position information according to the multi-value list data item, and acquiring the target list data from the multi-value engine data item of the to-be-processed engine data record.

Optionally, after the target list data is obtained, ranking the target list data to obtain ranked target list data;

the providing the target engine data version identifier and the target list data to the client includes:

and providing the target engine data version identification and the sorted target list data to the client.

Optionally, the engine data record to be processed includes a multi-value engine data item storing an engine data version identifier;

The obtaining function information according to the multi-value version position information, obtaining the position information of the list data corresponding to the target engine data version identifier in the multi-value engine data item of the to-be-processed engine data record, includes:

and acquiring function information according to the multi-value version position information, and acquiring the position information of the list data corresponding to the target engine data version identifier in the multi-value engine data item of the to-be-processed engine data record from the multi-value engine data item stored with the engine data version identifier.

The application also provides a data transmitting device, which comprises:

the information acquisition unit is used for acquiring a data request message sent by the client, wherein the data request message is used for acquiring list data corresponding to the target list category identification;

the engine data acquisition unit is used for acquiring a target engine data version identifier and acquiring target version engine data corresponding to the target engine data version identifier, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target version engine data comprises at least one version of list data corresponding to the target list category identifier;

The list data acquisition unit acquires function information according to the target engine data version identification and the multi-value list data, and acquires target list data from the target version engine data;

and the data sending unit is used for providing the target engine data version identifier and the target list data for the client.

The application also provides a selection method of the list data acquisition model, which comprises the following steps:

the method comprises the steps of obtaining a target engine data version identifier and target list data provided by a server, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target list data is obtained according to multi-value list data obtaining function information;

acquiring performance information of target version engine data corresponding to the target engine data version identifier according to the target engine data version identifier and buried point information corresponding to the target list data, wherein the buried point information is used for acquiring service data associated with the target list data;

and selecting a target list data acquisition model for acquiring list data according to the performance information.

The application also provides a selection device of the list data acquisition model, which comprises:

The system comprises a data acquisition unit, a target engine data version identification and a target list data acquisition unit, wherein the data acquisition unit is used for acquiring a target engine data version identification and target list data provided by a server, the target engine data version identification is used for identifying an engine data version corresponding to the list data, and the target list data is acquired according to multi-value list data acquisition function information;

the performance information acquisition unit is used for acquiring performance information of the target version engine data corresponding to the target engine data version identifier according to the target engine data version identifier and the embedded point information corresponding to the target list data, wherein the embedded point information is used for acquiring service data associated with the target list data;

and the model selection unit is used for selecting a target list data acquisition model for acquiring list data according to the performance information.

Compared with the prior art, the application has the following advantages:

the data sending method provided by the application comprises the following steps: acquiring a data request message sent by a client, wherein the data request message is used for acquiring list data corresponding to a target list category identifier; acquiring a target engine data version identifier and acquiring target version engine data corresponding to the target engine data version identifier, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target version engine data comprises at least one version of list data corresponding to the target list category identifier; acquiring function information according to the target engine data version identifier and the multi-value list data, and acquiring target list data from the target engine data version identifier; and providing the target engine data version identification and the target list data to the client.

According to the data sending method, after the application program obtains the data request message sent by the client, the target version engine data corresponding to the target engine data version identifier is obtained in the data engine, and the target list data is obtained through the multi-value list data obtaining function corresponding to the multi-value list data obtaining function information capable of obtaining the list data of the target version in the multi-value field. The method avoids using a plurality of data engines to store engine data of different versions, and does not need to use a plurality of fields to store engine data of different versions, so that an application program can quickly and efficiently provide data outwards.

The application also provides a selection method of the list data acquisition model, which comprises the following steps: the method comprises the steps of obtaining a target engine data version identifier and target list data provided by a server, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target list data is obtained according to multi-value list data obtaining function information; acquiring performance information of target version engine data corresponding to the target engine data version identifier according to the target engine data version identifier and buried point information corresponding to the target list data, wherein the buried point information is used for acquiring service data associated with the target list data; and selecting a target list data acquisition model for acquiring list data according to the performance information.

The target list data used in the selection method of the list data acquisition model is rapidly acquired by a server according to the multi-value list data acquisition function information and provided for an application program; after the application program obtains the target list data and the corresponding target engine data version identifier provided by the server, obtaining performance information of target version engine data corresponding to the target engine data version identifier through corresponding embedded point information; further, the performance information can be used for rapidly selecting a target list data acquisition model for acquiring list data.

Drawings

Fig. 1 is an application scenario schematic diagram of a data transmission method according to a first embodiment of the present application;

fig. 2 is a flowchart of a data transmission method according to a first embodiment of the present application;

FIG. 3 is a flowchart of a method for selecting a list data acquisition model according to a second embodiment of the present application;

fig. 4 is a schematic diagram of a data transmitting apparatus according to a third embodiment of the present application;

fig. 5 is a schematic diagram of a selection device of a list data acquisition model according to a fourth embodiment of the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is, however, susceptible of embodiment in many other ways than those herein described and similar generalizations can be made by those skilled in the art without departing from the spirit of the application and the application is therefore not limited to the specific embodiments disclosed below.

First, in order to enable those skilled in the art to better understand the scheme of the present application, a specific application scenario of the data transmission method provided in the present application will be described in detail below. Fig. 1 is a schematic application scenario diagram of a data transmission method according to a first embodiment of the present application.

In a specific real-time process, the data sending method is generally implemented by the application program responding to an operation request of a user 101 when the user 101 searches for the list data corresponding to the target list category identifier by using a corresponding application program on the computing device 102, sending a data request message for obtaining the list data corresponding to the target list category identifier to the computing device 103, and after the computing device 103 obtains the data request message sent by the application program, firstly obtaining a target engine data version identifier and obtaining target version engine data corresponding to the target engine data version identifier, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target version engine data comprises at least one version of list data corresponding to the target list category identifier; then, the computing device 103 obtains function information according to the target engine data version identifier and the multi-value list data, and obtains target list data from the target engine data version identifier; then, the computing device 103 provides the target engine data version identifier and the target list data to the application; after the application program obtains the target list data, the target list data is presented for viewing by the user 101 through a display device carried by or connected to the computing device 102.

It should be noted that, in the above description, the user 101 triggers the application program in the computing device 102 to send a request message for obtaining the list data corresponding to the target list category identifier, which illustrates in detail how the computing device 103 obtains the target list data of the target version, and provides the processing flow for the user 101 to view the target list data. In actual processing, other external objects, such as other application programs, may send a request message for obtaining the list data corresponding to the target list category identifier to the computing device 103 based on a certain service processing requirement, and after the computing device 103 obtains the request message, the target list data is provided to the application program.

In addition, in the present embodiment, the computing device 102 mainly refers to a mobile terminal device used by the user 101, such as a mobile phone, a tablet computer, etc., and of course, may also be a computer device used by the user 101; computing device 103 is primarily referred to as a server computing device.

The target list category identifier is an identifier for indicating a list category of list data requested by the application program, and specifically may be a string of globally unique character strings composed of english-numeral content. For example, when the application requests a network leaderboard for a store, it may be represented by a list category identification "onlcel".

The list data generally refers to ranking data of a plurality of business objects corresponding to a certain business category of the application program in a certain category list. The business category refers to business types of the application program, which are divided according to different businesses, for example, business for stores can be marked as store category; the business for the pet may be labeled as a pet category, or the like. The Business Object (Business Object) mainly refers to an abstraction of a series of entity objects with the same Business attribute in the real world in an application program, and is usually a string of character strings composed of english digits. For example, the list data of the online red list for the restaurant stores may be { "shop_id": "5", "shop_name": "xx store", "top_tags": "onlcel", "top_values": "305" }, where the shop_id represents an identifier of a specific entity object in the network red list, the shop_name represents an actual name of the specific entity object, the top_tags represent list category identifiers corresponding to the specific entity object, and the top_values are ranking data of the entity object in a list corresponding to the list category identifiers. Of course, this is merely an example of the list data, and other forms are possible in actual implementation, which is not limited herein.

And the target engine data version identifier is used for identifying the engine data version corresponding to the list data. The engine data version is a version identifier corresponding to different engine data. In this embodiment, the engine data version is mainly used to identify a version of engine data corresponding to the list data requested by the application program in total engine data, where the total engine data includes at least one version of list data corresponding to at least one list category identifier. For example, in the total engine data, for the list data of the network red list of the store, there may be three versions of engine data, such as "onlcel_a", "onlcel_b", and "onlcel_c", at the same time, and when the content of the target engine data version identifier is "onlcel_a", it indicates that the corresponding list data requested by the application program exists in the engine data including the engine data version identifier "onlcel_a".

In addition, in this embodiment, in order to solve the problems of untimely data provision and low efficiency in the AB experiment of the existing application program, the engine data of multiple versions are simultaneously stored in a multi-value engine data field, which specifically refers to a data field in which multiple values can be simultaneously stored. For example, in this embodiment, corresponding to the list data of different service classes, multiple value fields "top_tags" and "top_values" exist in one engine data record in the total engine data, and for "xx store" as well, if there are three versions of the network red list data corresponding to the multiple value fields, "top_tags" in the total engine data, the corresponding engine data record in the total engine data may be { "shop_id": "5", "shop_name": "xx store", "top_tags": "onlcel_a, onlcel_b, onlcel_c", "top_values": "305, 312, 309"}. Of course, this is merely illustrative, and in practice, other forms are possible, and will not be described herein.

The multi-value list data obtaining function information is information for representing a function capable of obtaining list data corresponding to the target engine data version identifier from a multi-value data field of an engine data record. For example, information of a multi-value version position information acquisition function for acquiring an index position of the engine data of the target version in the multi-value engine data item: get_string_index ("multi-value engine data item storing engine data version identification", "target version identification", -1), wherein the third parameter of the function represents the default return value of the function, i.e. the function returns "-1" when the engine data of the target version is not present; and multi-value list data acquisition function information for acquiring specific contents of the list data of the target version: get_attr_int64_value ("engine data item storing multiple versions of list data", "target version data position information", 0), wherein the third parameter of the function represents a default return value of the function, i.e., the function returns "0" when the target version of list data does not exist. Of course, it should be noted that, in the implementation, different functions may be correspondingly set according to different contents or types of the multi-value engine data items in the engine data record, which is not described herein.

Fig. 2 is a flowchart of a data transmission method according to the first embodiment of the present application, and the embodiment is described in detail below with reference to fig. 2.

Step 201, a data request message sent by a client is obtained, where the data request message is used to obtain list data corresponding to a target list category identifier.

In this embodiment, the client may be specifically a computing device used by a user, or may be another application program that needs to obtain the list data. For example, the user may operate an application program on the mobile phone to send the data request message, or other service side application programs may send the data request message to an application program that may provide the list data in the present application based on a certain service processing.

For example, when a user uses an application program on a mobile phone to look up the internet-leaderboard data of a store, the application program responds to the operation request of the user to acquire the user identification of the user, the list category identification of the internet-leaderboard of the store and the business category identification corresponding to the internet-leaderboard of the store, and generates a data request message for acquiring the list data of the internet-leaderboard of the store. For example, the data request message may be { "user ID": "201908080201", "traffic class identification": "SHOP", "target list category identification": "onlcel" }, of course, in implementation, the data request message may further include information such as the current area location information of the user, and information of the city in which the user is located, which is not described herein.

After step S201, step S202 is executed to obtain a target engine data version identifier, and obtain target version engine data corresponding to the target engine data version identifier, where the target engine data version identifier is used to identify an engine data version corresponding to the list data, and the target version engine data includes at least one version of list data corresponding to the target list category identifier.

In step S201, the client responds to an operation request of the user, and sends a data request message for obtaining list data corresponding to the target list category identifier to the server; and after the server acquires the data request message, the server obtains corresponding list data from total engine data according to the data request message, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier. However, when the application program performs the AB experiment, the total engine data of the server side generally includes the list data of different versions of the different list category identifiers, so in order to obtain the appropriate list data, it is necessary to obtain the target engine data version identifier corresponding to the list data requested by the data request message.

The obtaining the target engine data version identifier includes: acquiring a user identifier and the target list category identifier from the data request message; and acquiring the target engine data version identification according to the user identification and the target list category identification.

Wherein, the obtaining the target engine data version identifier according to the user identifier and the target list category identifier includes: according to the user identification, acquiring an engine data version identification corresponding to the user identification from the corresponding relation between the user identification and the engine data version identification; and acquiring the target engine data version identifier according to the target list category identifier and the engine data version identifier corresponding to the user identifier.

Specifically, after the server side obtains the data request message sent by the client side, a user identifier and a target list category identifier of a user are obtained from the data request message, and the target engine data version identifier is obtained according to the user identifier and the target list category identifier.

When an application program performs an AB experiment, when a client requests corresponding data from the server, the server allocates engine data of a corresponding version for a user with a fixed user identifier or a fixed device identifier or a fixed client according to a user identifier of the user or a device identifier of the client device, for example, a data request for obtaining list data of a network red list of a store is made for the user, and an a version, that is, engine data with a version identifier of "onlcel_a", is allocated for the user with a user identifier in the interval of "201908080000" - "201908081000".

The obtaining the target version engine data corresponding to the target engine data version identifier comprises the following steps: and obtaining engine data comprising the target engine data version identifier from total engine data, and taking the engine data comprising the target engine data version identifier as the target version engine data, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

The total engine data corresponding to the application program generally contains engine data of different versions of different service categories and different list categories. For example, in the total engine data, there may be engine data with business categories of store, pet, flower, etc. at the same time, and in particular, in some business categories, such as engine data with business category of store, there may also be engine data with different versions of different list categories of different business objects belonging to the business category, such as in the total engine data, there may be list data { "shop_id" for different versions of a network list of entity objects with entity object of "XX store": "5", "shop_name": "xx store", "top_tags": "onlcel_a, onlcel_b, onlcel_c", "top_values": "305, 312, 309" }, there may also be different versions of the top-selling-list data of the entity object { "shop_id": "5", "shop_name": "xx store", "top_tags": "bestsell_a, bestsell_b, bestsell_c", "top_values": "405, 412, 409" }, etc.

Therefore, after the data request message sent by the client is received, the target list data corresponding to the list data is obtained, and meanwhile, the number of engine data to be processed is also reduced. In this embodiment, the target engine data version identifier is obtained according to the user identifier and the list category identifier in the data request message, and according to the target engine data version identifier, the engine data including the target engine data version identifier is obtained in the total engine data, and the engine data including the target engine data version identifier is used as target version engine data for later data processing.

It should be noted that, the list data of at least one version corresponding to the target list category identifier is obtained through the following steps: acquiring a business object corresponding to the target list category identifier; acquiring source data related to the business object; performing data mining processing on the source data to acquire list data of at least one version of the business object; and taking the list data of at least one version of the business object as the list data of at least one version corresponding to the target list category identification.

Specifically, the obtaining the business object corresponding to the target list category identifier includes: acquiring a business category identifier corresponding to the target list category identifier; and then, acquiring the business object corresponding to the target list category identifier and the business category identifier.

In general, when the server side acquires the engine data, the server side acquires the engine data according to different service classifications and sub-modules. For example, engine data for store classification, typically, a server side, in a corresponding module, first obtains a business object corresponding to the store classification, such as "store 1", "store 2", and the like, and then obtains data related to the business object from different data sources.

The data mining processing is performed on the source data to obtain the list data of at least one version of the business object, including: and performing data mining processing on the source data by using at least one list data acquisition model corresponding to the target list category identifier and the service category identifier to acquire list data of at least one version of the service object.

The list data acquisition model is a model for acquiring list data of a business object by using a corresponding list data acquisition algorithm, and input data of the list data acquisition model is usually data related to the business object, such as sales data and evaluation data of the business object; the list data acquisition algorithm can be specifically set according to different requirements, and is not described herein.

In addition, the step of using at least one list data acquisition model corresponding to the target list category identifier and the service category identifier to perform data mining processing on the source data to acquire at least one version of list data of the service object includes: acquiring a first list data acquisition model; then, using the first list data acquisition model, carrying out data mining processing on the source data to acquire first list data of the business object; then, according to the first list data, a first engine data record to be stored of the business object is obtained; and writing the first to-be-stored engine data record into total engine data to acquire first version engine data aiming at the business object, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

The obtaining the first engine data record to be stored of the business object according to the first list data includes: storing the content of at least one data item in the first list data into at least one multi-value engine data item of the business object, wherein the multi-value engine data item is used for storing the content of multiple versions of the same data item of the business object; and acquiring a first engine data record to be stored of the business object according to the at least one multi-value engine data item.

Still, taking the example of obtaining the list data of the online leaderboard with the business category as the store as an example, in the server side, the business object corresponding to the store category is obtained, and the server side can obtain the list data of the online leaderboard of different versions of the entity object "xx store" through the following processes. Firstly, acquiring source data related to the entity object 'xx store', and then acquiring at least one version of list data of the entity object 'xx store' by using a list data acquisition model composed of at least one list data acquisition algorithm of the network list, namely acquiring three versions of list data of the network list of the entity object 'xx store' by using list data acquisition models of the network list, such as model_A, model_B, model_C, and model_C, respectively, wherein the three versions of list data of the network list of the entity object 'xx store' are respectively acquired by using list data acquisition models of the network list of 'onlcel_A', onlcel_B, and onlcel_C, and the three versions of data can be expressed as [ { 'label_value': "onlcel_a", "score":305} { "label_value": "onlcel_b": "score":312} { "label_value": "onlcel_c", "score":309 ], after obtaining the list data of the internet leaderboards of different versions of the entity store, storing the content in the data items in the list data of the internet leaderboards of the three versions of the entity object xx store into at least one multi-value engine data item corresponding to the entity object xx store respectively, and obtaining the engine data record to be stored of the entity object xx store according to the at least one multi-value engine data item. For example, the list data of the network red list of the three versions is correspondingly stored into a multi-value engine data item { "top_tags": "onlcel_a, onlcel_b, onlcel_c" }, and multi-value engine data item { "top_values": in "305, 312, 309" }, and according to the two multi-value engine data items, obtaining a to-be-stored engine data record { "shop_id" corresponding to the entity object "xx store": "5", "shop_name": "xx store", "top_tags": "onlcel_a, onlcel_b, onlcel_c", "top_values": "305, 312, 309" }, and writing the engine data record to be stored into the total engine data.

After step S202, step S203 is executed to obtain target list data from the target version engine data according to the target engine data version identifier and the multi-value list data obtaining function information.

In step S202, the target engine data version identifier is obtained according to the user identifier and the target list category identifier in the data request message, and after the target version engine data corresponding to the target engine data version identifier is obtained according to the target engine data version identifier, the target list data can be obtained from the target version engine data according to the target engine data version identifier and the multi-value list data to obtain function information, which is described in detail below.

In order to acquire the engine data corresponding to the target engine data version identifier from the target version engine data, in the application, the engine data of the corresponding version is acquired by setting a multi-value list data acquisition function capable of acquiring the engine data of the target version from multi-value engine data items of the engine data.

Firstly, acquiring multi-value version position information acquisition function information and multi-value list data item acquisition function information through multi-value list data acquisition function information set in a server side; then obtaining an engine data record to be processed from the target version engine data; acquiring function information according to the multi-value version position information, and acquiring position information of list data corresponding to the target engine data version identifier in a multi-value engine data item of the to-be-processed engine data record; and then, acquiring function information and the position information according to the multi-value list data item, and acquiring the target list data from the multi-value engine data item of the to-be-processed engine data record.

The engine data record to be processed comprises a multi-value engine data item stored with an engine data version identifier; the obtaining function information according to the multi-value version position information, obtaining the position information of the list data corresponding to the target engine data version identifier in the multi-value engine data item of the to-be-processed engine data record, includes: and acquiring function information according to the multi-value version position information, and acquiring the position information of the list data corresponding to the target engine data version identifier in the multi-value engine data item of the to-be-processed engine data record from the multi-value engine data item stored with the engine data version identifier.

Still taking the list data of the network red list with the service class as a store as an example, for the service object in the service class, a real object "xx store" is obtained, and a pending engine data record { "shop_id" corresponding to the real object "xx store" is obtained from the target version engine data: "5", "shop_name": "xx store", "top_tags": "onlcel_a, onlcel_b, onlcel_c", "top_values": "305, 312, 309" }, in order to obtain the list data of the "onlcel_a" version of the network red list data of the entity object "xx store" in the corresponding multivalued engine data item, then "onlcel_a" is identified according to the corresponding target engine data version, the function get_string_index corresponding to the function information is obtained by using the multivalued version position information, the index position t_idx of the "onlcel_a" version of the network red list data in the corresponding multivalued engine data item can be obtained by t_idx=get_list "," onlcel_a ", -1), and then the function get_attr_int64_value corresponding to the function information is obtained by the multivalue list data item, and the red value of the" onlcel_a "version of the network red list data can be obtained by score=get_attr_64_value (" top_value ", t_idx, 0). Thus, a record in the list data with the list category mark of 'onlcel' is obtained.

It should be noted that, only how to obtain the network-leaderboard list data of the a version of the entity object "xx store" is illustrated herein, in a specific implementation, the target version engine data may include engine data records of a plurality of service objects belonging to the same service category, and the method can correspondingly obtain the network-leaderboard list data of different service objects, and meanwhile, the network-leaderboard list data of the plurality of service objects are combined together to obtain the target list data corresponding to the target list category identifier.

For example, 1000 ten thousand engine data records may be stored in the overall engine data, and 200 engine data records including the list data of the network red list of the identifier "onlcel_a" can be screened out from the 1000 ten thousand engine data records through the target engine data version identifier "onlcel_a", namely the target version engine data described in the application; and then, obtaining target list data marked as 'onlcel_A' in the 200 engine data through the multi-value list data obtaining function.

In particular, in the implementation, the target service data corresponding to the service data may be obtained by using a multi-value service data obtaining function corresponding to the service data according to the service data to be obtained in the data request, which is not necessarily limited to the list data described in the present application.

According to the data transmission method, the engine data of different versions of the business object, such as the list data, are stored in the multi-value engine data item field, so that storage resources can be greatly saved, and performance of a data engine is not reduced due to the fact that the data item field is continuously increased; when the engine data of a specific version is required to be acquired, the target engine data of a target version, such as target list data, can be acquired through the multi-value list data acquisition function information provided by the application.

After step S203, step S204 is performed to provide the target engine data version identifier and the target list data to the client.

After obtaining the target list data corresponding to the target list category identifier in step S203, the target engine data version identifier and the target list data may be provided to the client.

In addition, after the target list data is obtained, the target list data can be subjected to ranking, the ranked target list data is obtained, and the target engine data version identification and the target list data are provided for the client.

It should be noted that, here, the target engine data version identifier is provided to the client so that the client may obtain the version of the engine data corresponding to the target list data. Thus, when an AB experiment is performed on an application program of a client, the application program can continuously acquire performance information of the target version engine data corresponding to the target engine data version identifier through the embedded point information by setting the embedded point information at a service processing position corresponding to the target list data, for example, the embedded point information can acquire exposure click data, transaction data, order data and other relevant service data information corresponding to the target list data, and further, the performance information of the target version engine data can be acquired. And selecting a target list data acquisition model for acquiring list data according to the performance information.

The embedded point information is a mark arranged at a key business process or a key event of an application program when the embedded point data acquisition method is used for analyzing engine data of the application program, and the mark can be used for acquiring performance data of the key business process or the engine data corresponding to the key event. Since methods for how to embed dots and how to perform embedded dot analysis are prior art, the description thereof is omitted herein.

In summary, in the data sending method, the data request message sent by the client is obtained, where the data request message is used to obtain the list data corresponding to the target list category identifier; acquiring a target engine data version identifier and acquiring target version engine data corresponding to the target engine data version identifier, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target version engine data comprises at least one version of list data corresponding to the target list category identifier; acquiring function information according to the target engine data version identifier and the multi-value list data, and acquiring target list data from the target engine data version identifier; and providing the target engine data version identification and the target list data to the client. The method avoids using a plurality of data engines to store engine data of different versions, and does not need to use a plurality of fields to store the engine data of different versions, so that the application program can quickly and efficiently provide the engine data outwards.

In correspondence to the above-mentioned data transmission method, the present application further provides a method for selecting a list data acquisition model, please refer to fig. 3, which is a flowchart of a method for selecting a list data acquisition model according to a second embodiment of the present application, and since detailed processing thereof is described in detail in the above-mentioned embodiments, the description herein is relatively simple, and relevant points are referred to the partial description provided in the above-mentioned embodiments.

Fig. 3 is a flowchart of a method for selecting a list data acquisition model according to the second embodiment of the present application, and the embodiment is described in detail below with reference to fig. 3.

Step S301, a target engine data version identifier and target list data provided by a server are obtained, wherein the target engine data version identifier is used for identifying an engine data version corresponding to the list data, and the target list data is obtained according to multi-value list data obtaining function information.

Step S302, according to the target engine data version identifier and the embedded point information corresponding to the target list data, obtaining performance information of the target engine data corresponding to the target engine data version identifier, wherein the embedded point information is used for obtaining service data associated with the target list data.

Step S303, selecting a target list data acquisition model for acquiring list data according to the performance information.

According to the selection method of the list data acquisition model, the performance information of the target version engine data corresponding to the target engine data version identification can be rapidly and efficiently obtained through the target engine data version identification and the target list data provided by the server side and through the embedded point information corresponding to the target list data, and then the target list data acquisition model for acquiring the list data is selected according to the performance information.

In correspondence with the above-mentioned data transmission method, the present application further provides a data transmission device, please refer to fig. 4, which is a schematic diagram of a data transmission device provided in the third embodiment of the present application, and since the device embodiments are substantially similar to the method embodiments, the description is relatively simple, and the relevant points refer to the part of the description provided in the above-mentioned embodiments, and the device embodiments described below are only illustrative. The data transmitting device comprises the following parts.

The message obtaining unit 401 is configured to obtain a data request message sent by the client, where the data request message is used to obtain list data corresponding to the target list category identifier.

The engine data obtaining unit 402 is configured to obtain a target engine data version identifier, and obtain target version engine data corresponding to the target engine data version identifier, where the target engine data version identifier is used to identify an engine data version corresponding to the list data, and the target version engine data includes at least one version of list data corresponding to the target list category identifier.

And a list data obtaining unit 403, configured to obtain target list data from the target version engine data according to the target engine data version identifier and the multi-value list data obtaining function information.

And the data sending unit 404 is configured to provide the target engine data version identifier and the target list data to the client.

Optionally, the engine data acquisition unit includes:

the identification acquisition subunit is used for acquiring a user identification and the target list category identification from the data request message;

and the target engine data version identifier acquisition subunit is used for acquiring the target engine data version identifier according to the user identifier and the target list category identifier.

Optionally, the engine data acquisition unit further includes:

and the target version engine data acquisition subunit is used for acquiring the engine data comprising the target engine data version identifier from the total engine data, and taking the engine data comprising the target engine data version identifier as the target version engine data, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

acquiring source data related to the business object;

Acquiring a first list data acquisition model;

acquiring a first engine data record to be stored of the business object according to the first list data;

and writing the first engine data record to be stored into total engine data to acquire first version engine data aiming at the business object, wherein the total engine data comprises at least one version of list data corresponding to at least one list category identifier.

In correspondence to the above-mentioned selection method of the list data obtaining model, the present application further provides a selection device of the list data obtaining model, please refer to fig. 5, which is a schematic diagram of the selection device of the list data obtaining model provided in the fifth embodiment of the present application, and since the device embodiment is substantially similar to the method embodiment, the description is relatively simple, and the relevant points refer to the part of the description provided in the above embodiment, and the device embodiment described below is merely illustrative. The selection device for the list data acquisition model comprises the following parts.

A data obtaining unit 501, configured to obtain a target engine data version identifier and target list data provided by a server, where the target engine data version identifier is used to identify an engine data version corresponding to the list data, and the target list data is obtained according to multi-value list data obtaining function information;

The performance information obtaining unit 502 obtains performance information of the target version engine data corresponding to the target engine data version identifier according to the target engine data version identifier and buried point information corresponding to the target list data, where the buried point information is used to obtain service data associated with the target list data;

the model selecting unit 503 is configured to select a target list data acquisition model for acquiring list data according to the performance information.

While the preferred embodiment has been described, it is not intended to limit the invention thereto, and any person skilled in the art may make variations and modifications without departing from the spirit and scope of the present invention, so that the scope of the present invention shall be defined by the claims of the present application.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer readable media, as defined herein, does not include non-transitory computer readable media (transmission media), such as modulated data signals and carrier waves.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims

1. A data transmission method, comprising:

providing the target engine data version identifier and the target list data to the client;

the multi-value list data acquisition function information comprises multi-value version position information acquisition function information and multi-value list data item acquisition function information;

the obtaining function information according to the target engine data version identifier and the multi-value list data, obtaining target list data from the target engine data version, includes: acquiring an engine data record to be processed from the target version engine data; acquiring function information according to the multi-value version position information, and acquiring position information of list data corresponding to the target engine data version identifier in a multi-value engine data item of the to-be-processed engine data record; acquiring function information and the position information according to the multi-value list data item, and acquiring the target list data from the multi-value engine data item of the to-be-processed engine data record;

Wherein the multi-value engine data item stores engine data of different versions of the business object.

2. The data transmission method according to claim 1, wherein the obtaining the target engine data version identifier includes:

3. The method for sending data according to claim 2, wherein the obtaining the target engine data version identifier according to the user identifier and the target list category identifier includes:

4. The data transmission method according to claim 3, wherein the acquiring the target version engine data corresponding to the target engine data version identification includes:

5. The data transmission method as recited in claim 1, wherein the target list category identification corresponds to at least one version of list data, and the method comprises the steps of:

acquiring source data related to the business object;

6. The method of claim 5, wherein the obtaining a business object corresponding to the target list category identifier comprises:

7. The method of claim 6, wherein the performing data mining on the source data to obtain the list data of at least one version of the business object includes:

8. The method of claim 7, wherein the obtaining the list data of the at least one version of the business object by performing data mining processing on the source data using at least one list data obtaining model corresponding to the target list category identifier and the business category identifier includes:

acquiring a first list data acquisition model;

9. The method for sending data as recited in claim 8, wherein the obtaining the first engine data record to be stored of the business object according to the first list data includes:

10. The data transmission method according to claim 1, wherein the engine data record to be processed includes a multi-value engine data item storing an engine data version identification;

11. The data transmission method according to claim 1, wherein after the target list data is obtained, ranking the target list data to obtain ranked target list data;

12. A data transmission apparatus, comprising:

the data sending unit is used for providing the target engine data version identifier and the target list data for the client;

13. A selection method of a list data acquisition model is characterized by comprising the following steps:

the target list data is obtained according to multi-value list data obtaining function information, and comprises the following steps: the target list data is obtained from a multi-value engine data item of an engine data record to be processed according to the multi-value list data item, wherein the position information is obtained according to the multi-value version position information obtaining function information, the position information is the position information of list data corresponding to a target engine data version identifier in the multi-value engine data item of the engine data record to be processed, and the engine data record to be processed is obtained from the target version engine data;

Wherein, the multi-value engine data item stores engine data of different versions of the business object;

14. A selection device for a list data acquisition model, comprising: