Method and apparatus for implementing unified data management

Abstract

The present disclosure relates to a method and apparatus for implementing unified data management, which includes: for a target scenario selected by an external party from at least one scenario, creating a target situation corresponding to the target scenario; wherein, there is a 1-to-N relationship between the scenario and the situation, and N is a positive integer; for each of the target situations, during the process of creating the target situation, subscribing to target data corresponding to the target situation from public data, and allocating the target data to the target situation; wherein, the public data is the original data collected and shared by the at least one scenario; and managing the target data through the target situation.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technologies, and more particularly, to a method and apparatus for implementing unified data management. Background Art

[0002] For an operation optimization system that relies on data-driven decision-making, perfect data management is crucial. On the one hand, it can significantly reduce the threshold and cost of product use, and on the other hand, it provides strong support for subsequent service quality (such as recommendation effect). Looking at the digital operation and marketing systems on the market, data management forms the foundation of the product.

[0003] Currently, the data production process is often initiated temporarily and randomly, resulting in poor data management unity. Summary of the Invention

[0004] An object of embodiments of the present disclosure is to provide a new technical solution for implementing unified data management.

[0005] According to a first aspect of the present disclosure, there is provided a method for implementing unified data management, including: for a target scenario externally selected from at least one scenario, creating a target scenario corresponding to the target scenario; wherein, the relationship between a scenario and a scenario is 1 to N, and N is a positive integer; for each of the target scenarios, during the process of creating the target scenario, subscribing to target data corresponding to the target scenario from public data, and allocating the target data to the target scenario; wherein, the public data is the collected original data shared by the at least one scenario; managing the target data through the target scenario.

[0006] According to a second aspect of the present disclosure, there is also provided an apparatus for implementing unified data management, including:

[0007] A scenario creation module, configured to create a target scenario corresponding to a target scenario externally selected from at least one scenario; wherein, the relationship between a scenario and a scenario is 1 to N, and N is a positive integer;

[0008] A data allocation module, configured to, for each of the target scenarios, during the process of creating the target scenario, subscribe to target data corresponding to the target scenario from public data, and allocate the target data to the target scenario; wherein, the public data is the collected original data shared by the at least one scenario;

[0009] A data management module, configured to manage the target data through the target scenario.

[0010] According to a third aspect of the present disclosure, there is also provided a system including at least one computing device and at least one storage device, wherein the at least one storage device is configured to store instructions for controlling the at least one computing device to execute the method according to the first aspect of the present disclosure.

[0011] According to a fourth aspect of the present disclosure, there is also provided a computer-readable storage medium having a computer program stored thereon, and the computer program, when executed by a processor, implements the method according to the first aspect of the present disclosure.

[0012] One beneficial effect of the embodiments of the present disclosure is that for any one of multiple scenarios, at least one scenario corresponding to the scenario is constructed, and during the process of creating the scenario, corresponding original data subscribed from the common data shared by multiple scenarios is subscribed, and the subscribed data is assigned to the scenario, so that the scenario can be used as the basic unit for managing data to manage the assigned data, thereby achieving unified management of data and making the unity of data management better.

[0013] Other features and advantages of the embodiments of the present disclosure will become clear through the following detailed description of the exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings incorporated in and constituting a part of this specification illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0015] Figure 1 is a schematic diagram of an implementation environment of a method for implementing unified data management according to an embodiment and a system composition structure capable of implementing the method;

[0016] Figure 2 is a flowchart of a method for implementing unified data management according to an embodiment;

[0017] Figures 3 - 20 shows a schematic diagram of the interface effect of the present invention;

[0018] Figure 21 is a flowchart of a method for implementing unified data management according to another embodiment;

[0019] Figure 22 is a block schematic diagram of a device for implementing unified data management according to an embodiment;

[0020] Figure 23 is a schematic diagram of the hardware structure of a system for implementing unified data management according to an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0021] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present invention.

[0022] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way a limitation on the present invention or its application or use.

[0023] Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods, and devices should be regarded as part of the specification.

[0024] In all the examples shown and discussed herein, any specific values should be construed as merely exemplary and not as a limitation. Thus, other examples of the exemplary embodiments may have different values.

[0025] It should be noted that: like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, further discussion thereof in subsequent drawings is not required.

[0026] One application scenario of the embodiments of the present disclosure is the unified management of data. In the process of implementation, the inventors found that when the data production process is initiated temporarily and randomly, there will be a problem of poor data management unity.

[0027] In view of the technical problems existing in the above embodiments, the inventors proposed a method for realizing unified data management. This method uses scenarios as the basic units for managing data. For any one of multiple scenarios, by constructing at least one situation corresponding to the scenario and allocating the corresponding original data subscribed from the common data to the situation to manage the data, the data management unity is better.

[0028] <Implementation Environment and Hardware Configuration>

[0029] Figure 1 It is a schematic structural diagram of the composition of a system 100 for realizing unified data management (hereinafter simply referred to as system 100). This system 100 can apply the method for realizing unified data management according to an embodiment. As Figure 1 shown, this system 100 includes a device 1000 for realizing unified data management (hereinafter simply referred to as device 1000) and a client 2000. This system 100 can be applied to the scenario of unified data management.

[0030] The device 1000 may exist in the form of a server. A server is a business point that provides processing, database, and communication facilities. The server can be an integrated server, a distributed server across multiple computers, a computer data center, a cloud server, or a server cluster deployed in the cloud, etc. The server can be of various types, such as, but not limited to, a web server, a news server, a mail server, a messaging server, an advertising server, a file server, an application server, an interactive server, a database server, or a proxy server. In some embodiments, each server may include hardware, software, or embedded logic components for performing the appropriate functions supported or implemented by the server, or a combination of two or more such components. For example, a server such as a blade server, a cloud server, etc., or a server group composed of multiple servers, may include one or more of the above types of servers, and so on.

[0031] In one embodiment, the device 1000 may be as Figure 1 shown, including a processor 1100, a memory 1200, an interface device 1300, and a communication device 1400.

[0032] The processor 1100 is used to execute a computer program, and the computer program can be written using instruction sets of architectures such as x86, Arm, RISC, MIPS, SSE, etc. The memory 1200 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), non-volatile memory such as a hard disk, etc. The interface device 1300 includes, for example, various bus interfaces, such as a serial bus interface (including a USB interface), a parallel bus interface, etc. The communication device 1400 can perform wired or wireless communication, for example.

[0033] Applied to the embodiments of the present disclosure, the memory 1200 of the device 1000 is used to store a computer program, and the computer program is used to control the processor 1100 of the device 1000 to operate to implement a method for unified data management according to any embodiment. Those skilled in the art can design a computer program according to the solution of the embodiments of the present disclosure. How the computer program controls the processor to operate is well known in the art, so it will not be described in detail here.

[0034] Although multiple devices of the device 1000 are shown in Figure 1 , the present invention may only relate to some of the devices, for example, the device 1000 only relates to the memory 1200 and the processor 1100.

[0035] In this embodiment, the client 2000 is, for example, a desktop computer, a mobile phone, a laptop computer, a tablet computer, a handheld computer, etc. As Figure 1As shown, the client 2000 may include a processor 2100, a memory 2200, an interface device 2300, a communication device 2400, a display device 2500, an input device 2600, a speaker 2700, a microphone 2800, and so on.

[0036] The processor 2100 may be a central processing unit CPU, a microcontroller unit MCU, etc., and is used to execute a computer program, which can be written in an instruction set with architectures such as x86, Arm, RISC, MIPS, SSE, etc. The memory 2200 includes, for example, ROM (read-only memory), RAM (random access memory), non-volatile memory such as a hard disk, etc. The interface device 2300 includes, for example, a USB interface, a headphone interface, etc. The communication device 2400 can perform wired or wireless communication, for example. The communication device 2400 may include at least one short-range communication module, for example, any module that performs short-range wireless communication based on short-range wireless communication protocols such as the Hilink protocol, WiFi (IEEE 802.11 protocol), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, LiFi, etc. The communication device 2400 may also include a remote communication module, for example, any module that performs WLAN, GPRS, 2G / 3G / 4G / 5G remote communication. The display device 2500 is, for example, a liquid crystal display screen, an LED display screen, a touch display screen, etc. The input device 2600 may include, for example, a touch screen, a keyboard, etc. The client 2000 can output an audio signal through the speaker 2700 and collect an audio signal through the microphone 2800.

[0037] Applied to the embodiments of the present disclosure, the memory 2200 of the client 2000 is used to store a computer program, which is used to control the processor 2100 of the client 2000 to operate and provide support for implementing the method of unified data management according to any embodiment. Those skilled in the art can design a computer program according to the solution of the embodiments of the present disclosure. How the computer program controls the processor to operate is well known in the art and will not be described in detail here.

[0038] The network 3000 can be a wireless communication network or a wired communication network, and can be a local area network or a wide area network. In Figure 1 In the system 100 shown, the client 2000 and the device 1000 can communicate through the network 3000. In addition, the networks 3000 based on different clients 2000 and devices 1000 can be the same or different.

[0039] It should be understood that although Figure 1Only one device 1000 and one client 2000 are shown, but this is not intended to limit the respective quantities. The system 100 may include multiple devices 1000 and multiple clients 2000.

[0040] Figure 1 The system 100 shown is merely illustrative and is in no way intended to limit the present invention, its applications, or uses.

[0041] Hereinafter, various embodiments and examples according to the present invention will be described with reference to the accompanying drawings.

[0042] <Method Embodiment>

[0043] Figure 2 is a flowchart showing a method for implementing unified data management according to an embodiment. The implementation entity of this embodiment is, for example, Figure 1 the device 1000 in

[0044] In a possible implementation, the device 1000 may include a business middle platform and a technology middle platform. Among them, the business middle platform can be oriented to specific businesses, encapsulate and package the technology services provided by the technology middle platform, and can be used to provide corresponding services for different scenarios. For example, there can be search business scenarios, push business scenarios, recommendation business scenarios, etc. The technology middle platform can be oriented to technology implementation and provide business services for the business middle platform. For example, the technology middle platform may specifically include a recommendation middle platform, a search middle platform, a push middle platform, a data middle platform, etc.

[0045] In this embodiment, a scenario is a concept of the business middle platform. As a unit for providing services, it can be understood as a business solution for describing a service requirement, which consists of three elements: service content, service type, and service layout. One scenario corresponds to one service location. For example, for the product recommendation scenario on the home page of a certain app client, its scenario elements include: personalized recommendation service (service type) for products (service content) at a fixed feed stream (service layout) location.

[0046] Specifically, the above-mentioned data middle platform may have functions such as data collection, data access, data management, data production, and data operation and maintenance. For example, the data middle platform can directly obtain original public data from the client side (such as Figure 1 the client 2000 shown in

[0047] Considering that the original public data collected usually cannot be directly used by the algorithm models underlying various scenario services, in this embodiment, the public data can be processed and calculated to generate data, so as to convert it into application data. This application data can be used as the direct input of the algorithm model and be used by the algorithm models underlying various scenario services.

[0048] Based on the above, in this embodiment, each scenario corresponding to the scenario is constructed, and the corresponding public data is assigned to the constructed scenario, and data is produced and managed in units of scenarios.

[0049] In this embodiment, a scenario is a concept of a data middle platform. As a unit for isolated management of application data, it can be understood as a data solution for carrying a clear optimization problem, and is composed of elements such as channel, page, position, goal, and feedback period. These five aspects are the basic elements of an optimization problem and also the measurable boundaries for evaluating the scenario effect.

[0050] For example, give an example of a scenario: Through the personalized placement of the information flow (position) on the home page (page) of the APP (channel), the purchase rate (goal) on a single day (feedback period) is increased. This scenario defines: channel: APP; page: home page; position: information flow; goal: purchase rate; feedback period: single day.

[0051] Specifically, the original public data can at least include three types: user data, material data, and behavior data. These three types are described as follows:

[0052] Based on the above user data, the unified user data in the enterprise operation process can be managed, and together with the data collection and access components, the user data content and meta-information (schema) are uniformly managed.

[0053] Based on the above material data, the unified material data in the enterprise operation process can be managed, and together with the data collection and access components, the material data content and meta-information are uniformly managed. Different from user data, material data can include different types, such as commodities, information, and short videos.

[0054] Based on the above behavior data, the behavior data generated during the online and offline user interaction process in the enterprise operation process can be managed. Similarly, together with the collection and access components, the behavior data content and meta-information are uniformly managed. Among them, behaviors can be divided into different types according to the actual channels where they occur, such as online and offline behaviors, online click, browse, play and other behaviors, and offline transaction, push, order and other behaviors.

[0055] Specifically, the application data can at least include four types: data (subscribed data), portraits, samples, and metrics, which are described as follows:

[0056] Data (subscribed data): For a specified type of business scenario, in the push, recommendation, and search scenarios, materials and behavior data will be selected from the original public data according to the scenario requirements. It also includes system data produced by business systems, such as recommendation service logs, material user update requests, etc.

[0057] Portraits: Divided into user portraits and material portraits. During the operation of scenario applications, it is often necessary to directly process the original data of users and materials or perform specified calculations based on behavior history to generate portrait attributes of users and materials. This part of the processed data will provide data support for scenario services such as recommendation and search.

[0058] Samples: Are data instances obtained by encapsulating features, including two parts: model features and sample labels, and are used to train models. During the process of model building and optimization, sample production is an essential data preparation process. According to the modeling behavior goal, the sample labels are deduced backward, and then samples are produced by splicing their associated features. The samples are supplied to the recommendation, search, and push middle platforms for model training.

[0059] Metrics: During the whole-channel operation experience and growth process, it is necessary to calculate metrics and perform dashboard diagnostics on user behavior data in various dimensions. Therefore, a unified metric template and an extended mode can be provided to facilitate scenario builders to quickly generate metrics.

[0060] Based on the above content, as Figure 2 shown, the method for implementing unified data management in this embodiment may include the following steps S201 to S203:

[0061] Step S201: For a target scenario externally selected from at least one scenario, create a target situation corresponding to the target scenario; where the relationship between the scenario and the situation is 1 to N, and N is a positive integer.

[0062] As described above, there can be multiple scenarios, such as the search business scenario, the push business scenario, and the recommendation business scenario. Users can request to create a situation for any scenario, and for the creation of a situation, any scenario can correspond to multiple situations, that is, the relationship between the scenario and the situation is one-to-many.

[0063] For example, taking the recommendation service as an example, if the scenario only considers a single optimization problem, such as only optimizing the purchase rate of goods, then it can be associated with one situation. For a scenario with multiple goals (such as simultaneously optimizing the click-through rate and viewing duration of a short video recommendation service), multiple situations can be associated, such as using the data of two situations respectively for scenario optimization.

[0064] In one embodiment of the present disclosure, to illustrate a possible implementation of creating a scenario, in step S201, for a target scenario selected by an external party from at least one scenario, a target scenario corresponding to the target scenario is created, including steps S2011 - S2012:

[0065] Step S2011: In response to a new scenario request, determine the target scenario selected by the external party from at least one scenario, and obtain target scenario configuration information.

[0066] Specifically, the new scenario request can be issued by a user, for example, by triggering a corresponding function button provided on the interaction interface. When the user creates a new scenario, the user can select the scenario corresponding to the scenario, and then obtain the corresponding target scenario configuration information.

[0067] Step S2012: Create a target scenario corresponding to the target scenario according to the target scenario configuration information.

[0068] After obtaining the scenario configuration information, a corresponding scenario can be created accordingly. The created scenario corresponds to the scenario selected by the user, so that the selected scenario can be optimized based on the created scenario.

[0069] In addition, after obtaining the scenario configuration information, corresponding public data can also be subscribed and assigned to the created scenario accordingly, so that the corresponding data can be managed based on the scenario. Based on this, in the following step S202, subscribing to target data corresponding to the target scenario from public data includes: subscribing to target data corresponding to the target scenario from public data according to the target scenario configuration information.

[0070] Specifically, for the creation of a scenario, there are at least two implementation methods. One is personalized creation, and the other is to create with an existing scenario as a template. Below, the two scenario creation methods are described separately.

[0071] For the above implementation method of personalized scenario creation:

[0072] In one embodiment of the present disclosure, to illustrate a possible implementation of personalized scenario creation, please refer to Figure 3 , step S2011, in response to a new scenario request, determine the target scenario selected by the external party from at least one scenario, and obtain target scenario configuration information, including steps S20111 - S20113:

[0073] Step S20111: In response to the new scenario request, provide personalized creation items for the at least one scenario.

[0074] Such as Figure 3As shown, in response to the new scenario request, in the type options, there are personalized creation items for three scenarios: recommended personalization, push personalization, and search personalization.

[0075] Step S20112, when the personalized creation item of the target scenario is externally triggered, provide a scenario creation configuration item corresponding to the target scenario; where the target scenario is any one of the at least one scenario.

[0076] For the personalized creation items of each provided scenario, the user can select the personalized creation item of the scenario for which they need to create a corresponding scenario. Furthermore, an interface for the scenario creation configuration item corresponding to this scenario can be provided to facilitate user configuration as needed.

[0077] Normally, the scenario creation configuration item can be provided through a display interface. For example, this display interface can be as Figure 4 shown. As Figure 4 shown, the provided scenario creation configuration items can include a placement channel configuration item, an optimization target configuration item, a feedback period configuration item, and a material library configuration item. In addition, by clicking the advanced settings button shown in Figure 4 , it can also be associated with the behavioral characteristics that the scenario needs to subscribe to. For example, as Figure 5 shown, the provided scenario creation configuration items can include a behavior type configuration item, a behavior channel configuration item, and an interaction field configuration item.

[0078] Based on the above, in an embodiment of the present disclosure, please refer to Figure 4 and Figure 5 , the scenario creation configuration item includes at least one of a placement channel configuration item, an optimization target configuration item, a feedback period configuration item, a material library configuration item, a behavior type configuration item, a behavior channel configuration item, and an interaction field configuration item.

[0079] Please refer to Figure 4 , the specific contents of the placement channel configuration item, the optimization target configuration item, the feedback period configuration item, and the material library configuration item can be as described below:

[0080] ① Placement channel, the content placement position is used to locate the scenario optimized by this scenario, including channel clients (APP, mini-program, Web, others) and placement fields.

[0081] ② Optimization target, the target placement information for the recommended, search, and push scenarios can be selected, including click-through rate, purchase rate, open rate, churn rate, etc.

[0082] ③ Feedback period, the time window for behavioral target feedback.

[0083] ④ Material library selection, select the material library associated with this scenario that needs to be used.

[0084] Please refer to Figure 5 , the specific contents of the behavior type configuration item, behavior channel configuration item, and interaction field configuration item can be described as follows:

[0085] ① Behavior type, select all behaviors on the behavior path to achieve the scenario optimization goal. For example, if the optimization goal of this scenario is purchase, there is a behavior path (exposure, click, add to cart, create order, purchase), and these behaviors need to be added to the behavior type of the scenario.

[0086] ② Behavior channel, select the generation channels of the behaviors that need to be concerned about, and multiple selections are allowed. Include ios, Android, mp, and others.

[0087] ③ Interaction field, select all positions where the behavior occurs, such as the product list page, product details page, shopping cart details page, order payment page, etc.

[0088] In this embodiment, based on the associated configuration of behavior data, corresponding behavior data can be assigned to the scenario to prevent redundant management of all behavior data and reduce the application data management cost.

[0089] Step S20113, obtain the target scenario configuration information through the scenario creation configuration item provided in the step S20112. As described above, based on the scenario creation configuration item, on-demand configuration can be performed to obtain the scenario configuration information.

[0090] For the above implementation method of creating a scenario using an existing scenario as a template:

[0091] In an embodiment of the present disclosure, in order to illustrate a possible implementation method of creating a scenario using an existing scenario as a template, so, please refer to Figure 6 , the step S2011, in response to a new scenario request, determines the target scenario selected by the external from at least one scenario, and obtaining the target scenario configuration information includes steps S20114 - step S20117:

[0092] Step S20114, in response to the new scenario request, provide a scenario template creation item.

[0093] Please refer to Figure 3 and Figure 6 , in response to the new scenario request, in the type option, in addition to providing the personalized creation items of the above three scenarios, a scenario template creation item can also be provided.

[0094] Step S20115, when the scenario template creation item is externally triggered, provide at least one constructed scenario.

[0095] Such as Figure 6As shown, when the user expects to create a scenario using an existing scenario as a template, the user can select the type of "using an existing scenario as a template". Among them, the existing scenario can be any scenario that has been created. In this way, the constructed scenarios can be provided.

[0096] Step S20116: Determine a first scenario selected from the at least one constructed scenario externally, and use the scenario corresponding to the first scenario as the target scenario.

[0097] Step S20117: Obtain the target scenario configuration information according to the scenario configuration information of the first scenario.

[0098] Specifically, for the case of creating a scenario using an existing scenario as a template, no additional configuration is required, and the behavior data is default to be executed according to the response schema and calculation logic when the user saves.

[0099] In this embodiment, the precipitation and reuse of scenario templates are supported, so as to precipitate the customer's data assets, and the efficiency of implementing related projects, such as AI (Artificial Intelligence) projects, can be improved.

[0100] After creating a scenario, the user can also view the constructed scenarios as needed. Based on this, in an embodiment of the present disclosure, please refer to Figure 7 , the method further includes step S214:

[0101] Step S214: In response to a scenario display request, provide a scenario list, where the scenario list includes scenario display items and scenario operation items of the target scenario.

[0102] As Figure 7 shown, in response to a scenario display request, a scenario list can be provided. Based on the provided scenario list, the user can view the information of the constructed scenarios, specifically including scenario display items and scenario operation items.

[0103] In an embodiment of the present disclosure, please refer to Figure 7 , the scenario display items include at least one of: a number display item, a name display item, a status display item, a type display item, an update time display item, and a creation time display item.

[0104] As Figure 7 shown, the scenario list can display display items such as the number, name, status, type, update time, and creation time of the constructed scenarios.

[0105] In an embodiment of the present disclosure, the scenario operation items include at least one of: a start / stop operation item, a publish to scenario library operation item, a settings operation item, and a delete operation item.

[0106] AsFigure 7 As shown, operation items such as start, stop, publish to the scenario library, setting, and deletion of the constructed scenarios can be displayed in the scenario list.

[0107] For example, if the user clicks the deletion operation item of a certain scenario, the application data corresponding to the scenario will be deleted. For example, the portrait corresponding to the scenario and its corresponding service can be cleared, and the metrics corresponding to the scenario and its corresponding service can be cleared. However, the public portrait derived from the scenario can be not destroyed.

[0108] Based on the above, in an embodiment of the present disclosure, the scenario operation item includes a start / stop operation item; the method further includes step S215:

[0109] Step S215, in response to an external trigger of the start / stop operation item of the target scenario, during the process of starting the target scenario, execute the step of subscribing to the target data corresponding to the target scenario from the public data according to the target scenario configuration information, and allocating the target data to the target scenario.

[0110] In this embodiment, after creating a scenario, the scenario can be automatically or manually started by the user, or the user can manually start a previously stopped scenario. After the scenario is started, the corresponding public data can be subscribed according to the corresponding scenario configuration information, and then the subscribed public data can be allocated to the scenario.

[0111] Based on the above, in an embodiment of the present disclosure, the scenario operation item includes a start / stop operation item; the method further includes step S216:

[0112] Step S216, in response to an external trigger of the start / stop operation item of the target scenario, in the case of stopping the target scenario, stop executing the step of subscribing to the target data corresponding to the target scenario from the public data according to the target scenario configuration information, and allocating the target data to the target scenario.

[0113] Corresponding to the above start scenario, in this embodiment, for a started scenario, the user can manually stop the scenario. After the scenario is stopped, the corresponding public data will no longer be subscribed according to the corresponding scenario configuration information, and then the corresponding data will no longer be allocated to the scenario.

[0114] In an embodiment of the present disclosure, the scenario operation item includes a publish to scenario library operation item; the method further includes step S216:

[0115] Step S216, in the case of an external trigger of the publish to scenario library operation item of the target scenario, publish the target scenario to the scenario library.

[0116] In this embodiment, for any constructed scenario, after the user triggers the operation item of publishing to the scenario library, for example, when the user views the scenario list and for a certain scenario displayed on the interface, by triggering its operation item of publishing to the scenario library, the scenario can be published to the scenario library. By publishing the scenario to the scenario library, it is convenient for the user to quickly view the scenarios in the scenario library, for example.

[0117] As Figure 7 shown, if a scenario has been published to the scenario library, it can be correspondingly displayed in the scenario list. Specifically, the scenario library can only be displayed after the scenario is published.

[0118] Based on the above content, after creating any scenario, the following step S202 can be executed to allocate corresponding public data to the created scenario.

[0119] Step S202: For each of the target scenarios created in the above step S201, during the process of creating the target scenario, subscribe to the target data corresponding to the target scenario from the public data, and allocate the target data to the target scenario; wherein, the public data is the original data collected for the at least one scenario and shared by them.

[0120] Specifically, during the process of creating a scenario, by subscribing to the corresponding original public data and allocating the subscribed data to the scenario, it supports the creation of the scenario. Since the subscribed data is specific to this scenario, it can be used as an application data of this scenario, and other types of application data of this scenario, such as the above-mentioned portrait, sample, index, etc. application data, can be constructed based on this type of application data.

[0121] In addition, based on the already created scenario, by setting relevant configuration items, it is also possible to subscribe to the corresponding original public data again accordingly, and allocate the data subscribed again to the scenario to support the creation of a new scenario, that is, it can be realized to create a new scenario with an existing scenario as a scenario template.

[0122] Specifically, the original public data collected from the customer side can be jointly called by multiple scenario services (such as recommendation, search, push, etc. scenarios) through the scenario subscription method. In this embodiment, by the scenario subscription mode, subscribing to the corresponding data in the original public data is beneficial to reducing data redundancy and improving the scenario construction efficiency.

[0123] As can be seen from the above, the scenario configuration information can be obtained through the scenario creation configuration item, and then the scenario can be created according to the scenario configuration information. Among them, the scenario creation configuration item can include an optimization target configuration item, based on which the optimization target of the business scenario can be configured, so that one scenario is associated with one or more scenarios.

[0124] In this embodiment, corresponding material data, behavior data, etc. can be selected from the original public data according to the optimization objectives in the scenario configuration information and assigned to the corresponding scenarios, so as to achieve data management in units of scenarios accordingly.

[0125] For example, as shown in Table 1 below, assume that for the scenarios of personalized recommendation of products with optimization objectives of click-through rate and purchase rate, they respectively correspond to Scenario 1 and Scenario 2. First, all material information in the material library 32 (which can be configured in the above material library configuration item) can be assigned to Scenario 1 and Scenario 2. Then, according to the optimization objectives, the required display and click behavior data are assigned to Scenario 1, and the required display, click, add to cart, create order, pay order and other behavior data are assigned to Scenario 2.

[0126] Table 1

[0127]

[0128]

[0129] It can be seen that some common data can be shared among different scenarios of the same scene. In addition, in the case of expanding different types of scenarios, some application data can be shared among different scenarios.

[0130] In addition, in addition to assigning the above material data and behavior data, system data output by the business system, such as recommendation service logs, material user update requests, etc., can also be assigned to the corresponding scenarios as needed.

[0131] Based on the above content, after assigning data to the scenarios, the following step S203 can be executed to achieve unified data management in units of scenarios.

[0132] Step S203, after the above step S202, manage the target data through the target scenario.

[0133] As described above, the subscribed original public data usually cannot be directly used by the algorithm models at the bottom layer of each scenario service. Therefore, in this step, the public data can be processed and calculated to generate data, so as to convert it into application data. This application data can be used as the direct input of the algorithm model and be used by the algorithm models at the bottom layer of each scenario service.

[0134] In this embodiment, scenarios are used as the basic units for managing application data, and the production process and production results of application data are uniformly managed. For example, based on the subscribed data, around the business scenario, the configuration-based construction and management of user portraits, material portraits, scenario metrics, and algorithm optimization samples can be provided, and data access interfaces can be opened to support the expansion of calculation methods.

[0135] Based on this, in an embodiment of the present disclosure, step S203 of managing the target data through the target scenario includes steps S2031 - S2032:

[0136] Step S2031, construct application data corresponding to the target scenario according to the target data.

[0137] In this step, based on the corresponding subscription data assigned to the scenario, data processing can be performed to construct application data corresponding to the scenario, such as portraits, samples, metrics, etc.

[0138] Step S2032, provide the application data to the model corresponding to the target scenario for processing.

[0139] In this step, based on the application data of the scenario, the corresponding model can be processed. For example, application data such as samples of the scenario can be used to optimize the model for the scenario corresponding to this scenario. In this way, since the application data is generated by subscribing to the corresponding public data and the generated application data further optimizes the model, when using the optimized model to provide corresponding business services to customers, the services can be provided more accurately.

[0140] As can be seen from the above, the application data can include portraits, samples, metrics, etc. Based on this, in an embodiment of the present disclosure, the application data includes any one or more types of portraits, samples, and metrics; step S2031 of constructing application data corresponding to the target scenario according to the target data includes steps S20311 - S20313:

[0141] Step S20311, in response to a new request for any type of application data for the target scenario, display a first configuration item corresponding to the any type of application data.

[0142] In this step, if the user needs to create a certain application data, a corresponding new request can be issued. In this way, to facilitate the user to set configuration information, the corresponding configuration item can be displayed.

[0143] Step S20312, determine the data configuration information set externally through the first configuration item.

[0144] In this step, after the user configures the configuration item as needed, the corresponding configuration information can be obtained.

[0145] Step S20313, process the target data according to the data configuration information to construct the any type of application data corresponding to the target scenario.

[0146] In this step, the corresponding application data can be constructed based on this configuration information.

[0147] Next, the construction of the three types of application data, namely images, samples, and metrics, will be described separately.

[0148] For the application data of images, in an embodiment of the present disclosure, please refer to Figures 8 - 11 , Figures 14 - 15 , the application data includes the image; the first configuration item includes at least one of an image name configuration item, at least one type of image type configuration item, and an image description configuration item.

[0149] Specifically, during the operation of scenario applications, it is often necessary to directly process the original data of users and materials, or perform specified calculations based on the behavior history to generate user and material images. User images and material images can be directly used as part of the sample data to provide data support for scenarios such as recommendation and search.

[0150] In an embodiment of the present disclosure, the image includes a user image and a material image. Next, the corresponding configuration items for the user image and the material image will be described separately.

[0151] In this embodiment, when the user requests to generate the application data of the user image, a page as shown in any one of Figures 8 - 11 can be displayed. Please refer to Figures 8 - 11 , when the application data is a user image, the above first configuration item can include the name, type, description, etc. of the user image. Among them, the type of the user image can be configured as basic, statistical, model, and public image as needed.

[0152] In this embodiment, when the user requests to generate the application data of the material image, a page as shown in any one of Figures 14 - 15 can be displayed. Please refer to Figures 14 - 15 , when the application data is a material image, the above first configuration item can include the name, type, description, etc. of the material image. Among them, the type of the material image can be configured as basic, session (or statistical), and public image as needed.

[0153] Based on this, in an embodiment of the present disclosure, please refer to Figures 8 - 10 , the application data includes the image; the first configuration item includes at least one type of image type configuration item; in step S20312 of determining the data configuration information set externally through the first configuration item, it includes steps S203121 - S203123:

[0154] Step S203121, determining the target image type configuration item selected externally from the at least one type of image type configuration item.

[0155] Such as Figures 8 - 11As shown, on the display page of the first configuration item corresponding to the user portrait, multiple portrait type configuration items can be displayed, such as basic features, statistical features, model tags, and public portraits respectively. Users can select any type as needed to generate a user portrait of that type.

[0156] As Figures 14 - 15 shown, on the display page of the first configuration item corresponding to the material portrait, multiple portrait type configuration items can be displayed, such as basic features, statistical features, and public portraits respectively. Users can select any type as needed to generate a material portrait of that type.

[0157] Step S203122, provide the second configuration item corresponding to the target portrait type configuration item.

[0158] In this step, based on the portrait type selected by the user, the corresponding second configuration item can be displayed. Below, the corresponding second configuration items for user portraits and material portraits will be described separately.

[0159] For the second configuration item of the above-mentioned user portrait:

[0160] As mentioned above, the portrait types of user portraits can include basic features, statistical features, model tags, and public portraits. Below, these four types will be described separately.

[0161] For the portrait type of basic features:

[0162] Basic features refer to the static attributes of users, based on facts. For example: user ID, IP, age, gender, etc. Thus, the corresponding configuration items can have the following fields and methods:

[0163] (1) Field, select the attribute of the user, such as "IP".

[0164] (2) Method, select the method acting on the attribute, such as "geographical information extraction", etc.; support custom extraction methods using UDF (User Define Function), and UDF is uniformly managed by system functions.

[0165] As Figure 8 shown, assuming that the user currently selects the basic type, the corresponding second configuration items of this type will be displayed, such as fields and methods.

[0166] For the portrait type of statistical features:

[0167] Statistical features are features obtained by statistically analyzing user behaviors. Thus, the corresponding configuration items can have the following behavior types, attributes, time windows, calculation methods, and service filters:

[0168] (1) Behavior type, behaviors accumulated in a session, such as "purchase behavior".

[0169] (2) Attribute, accumulated attributes, which can be attribute fields in user, material, or behavior data.

[0170] (3) Time window, that is, the calculation period.

[0171] (4) Calculation method, supports using UDAF (User-Defined Aggregation Function) for custom extraction methods. UDAFs are uniformly managed by system functions and include three built-in aggregation methods: "accumulation", "counting", and "segmented counting".

[0172] (5) Service filtering, in the calculation of exposure behavior data, it is necessary to determine whether to calculate services generated by paradigm services. For example, it can include three types: "only paradigm services (which can be understood as a specific service)", "non-paradigm services", and "all".

[0173] For example, a statistical feature can be: the sum (calculation method) of the purchase price (attribute) for purchases (behavior type) within 3 days (time window).

[0174] As Figure 9 shown, assuming the user currently selects the statistics type, the corresponding second-level configuration items of this type will be displayed, such as behavior type, attribute, time window, calculation method, and service filtering.

[0175] For the model label portrait type:

[0176] It is used to connect to external custom scripts / calculation processes to generate user portrait results. It provides functions for related configurations and includes a built-in script for calculating user interests (USER_INTEREST). For scripts involving offline calculations, their running times can be configured in the system background.

[0177] Example: Use the built-in USER_INTEREST script to calculate that the product type (material attribute) most likely to be purchased (behavior type) by the user is sports.

[0178] As Figure 10 shown, assuming the user currently selects the model type, the corresponding second-level configuration items of this type will be displayed, such as behavior type, material attribute, and calculation method.

[0179] For the public portrait type:

[0180] This type is used to select portrait attributes that have been exported to the public portrait. For example, a copy that can be referenced will be created for this portrait in the current scenario, and meta-information such as description and name belongs to the current scenario, and the portrait description information of the current scenario can be modified.

[0181] Please refer toFigure 11 Assume that the user currently selects the public portrait type, then the corresponding display interface can be as Figure 11 shown.

[0182] Based on the above, in an embodiment of the present disclosure, please refer to Figures 8 - 11 , the portrait includes a user portrait;

[0183] The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, a model label type configuration item, and a public portrait configuration item;

[0184] When the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction method configuration item;

[0185] When the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, a calculation attribute configuration item, a time window configuration item, a calculation method configuration item, and a service screening configuration item;

[0186] When the target portrait type configuration item is a model label type configuration item, the second configuration item includes at least one of a calculation method configuration item, a behavior type configuration item, and a material attribute configuration item.

[0187] For the second configuration item of the above material portrait:

[0188] As described above, the portrait types of the material portrait can be basic features, statistical features, and public portraits. The following will separately describe these three types.

[0189] For the portrait type of basic features:

[0190] The corresponding configuration items can have the following fields and methods:

[0191] (1) Fields, select the static attributes of the material, such as material ID, type, title, url (Uniform Resource Locator), etc.

[0192] (2) Methods, select the methods acting on the attributes, such as "keyword extraction", etc.; support the use of UDF (User-Defined Function) to customize the extraction method, and the UDF is uniformly managed by the system functions.

[0193] As Figure 14 shown, assume that the user currently selects the basic type, then the second configuration items corresponding to this type will be displayed, such as fields and methods.

[0194] For the portrait type of statistical features:

[0195] The corresponding configuration items can have the following behavior types, cumulative amounts, time windows, and service filters:

[0196] (1) Behavior type, the target behavior type accumulated in the session, only single selection is supported.

[0197] (2) Cumulative amount, the behavior field to be accumulated. For example, duration can be used to accumulate the duration of the playback behavior; amount can be used to accumulate the quantity of the purchase behavior.

[0198] (3) Time window, the statistical time interval. For example, it can have full volume, recent time range, and time range defined by behavior (such as "the last 100 exposures").

[0199] (4) Service filter: In the calculation of exposure behavior data, it is necessary to determine whether to calculate the services generated by the paradigm services. It includes three types: "only paradigm services", "non-paradigm services", and "all".

[0200] In addition, when the user, material, and behavior occurrence attributes in the public data change (such as increase) and this update is published, the corresponding optional items in the portrait configuration will increase accordingly. For example, after the reported material data adds geographical information (geolocation), the optional material attributes in the portrait will increase the geographical field.

[0201] Please refer to Figure 15 , assuming that the user currently selects the statistics type, the second configuration item corresponding to this type will be displayed, and the display interface can be as Figure 15 shown.

[0202] For the public portrait of this portrait type:

[0203] This type is used to select the portrait attributes that have been exported to the public portrait. For example, a reference copy of the portrait will be created for this portrait in this scenario, and the meta-information such as the description and name belongs to the current scenario, and the portrait description information of the current scenario can be modified.

[0204] Please refer to Figures 14 - 15 , and the user can also select the public portrait type to generate the material portrait of this type.

[0205] Based on the above content, in an embodiment of the present disclosure, please refer to Figures 14 - 15 , the portrait includes a material portrait;

[0206] The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, and a public portrait configuration item;

[0207] When the target portrait type configuration item is the basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction method configuration item;

[0208] When the target portrait type configuration item is the statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, an accumulation amount configuration item, a time window configuration item, and a service screening configuration item;

[0209] When the target portrait type configuration item is the public portrait configuration item, the second configuration item includes a user portrait attribute selection configuration item.

[0210] Step S203123, determine the data configuration information externally set through the second configuration item.

[0211] In this step, the user can set the second configuration item as needed, so as to obtain the corresponding data configuration information, and then can build the corresponding portrait based on this data configuration information.

[0212] After the portrait is built, the user can also view the built portrait as needed. Based on this, in an embodiment of the present disclosure, please refer to Figure 12 and Figure 16 , the application data includes portraits; the method further includes step S204:

[0213] Step S204, in response to a portrait viewing request for the target scenario, provide a portrait attribute list; wherein, the portrait attribute list includes: portrait attribute display items and portrait attribute operation items for each target portrait, and the target portrait is the built portrait corresponding to the target scenario.

[0214] In this embodiment, when the user needs to view the built portrait, a portrait viewing request can be issued. Among them, there are two ways to view the portrait. One is to view the attribute list, and the other is content exploration. Below, the two portrait viewing methods will be described separately.

[0215] For the portrait viewing method of viewing the attribute list:

[0216] In response to the portrait viewing request, a portrait attribute list can be provided. For example, when viewing a user portrait, the display effect of the portrait attribute list can be as shown in Figure 12 shown, when viewing a material portrait, the display effect of the portrait attribute list can be as shown in Figure 16 shown. Please refer to Figure 12 and Figure 16 , in the portrait attribute list, portrait attribute display items and portrait attribute operation items can be displayed.

[0217] Based on the above content, in an embodiment of the present disclosure, please refer toFigure 12 and Figure 16 wherein the portrait attribute display items include at least one of an attribute name display item, an attribute type display item, an update time display item, and a description display item;

[0218] The portrait attribute operation items include at least one of an update operation item, a view / setting operation item, and a save-to-public-portrait operation item.

[0219] Based on the above, in an embodiment of the present disclosure, please refer to Figure 12 and Figure 16 wherein the portrait attribute operation items include an update operation item; the method further includes steps S205 - S206:

[0220] Step S205, in response to an external trigger of the update operation item for the first target portrait, during the process of starting the first target portrait, execute the step of updating the first target portrait; wherein, the first target portrait is any one of the various target portraits.

[0221] In this step, a newly created portrait may not be started by default. After the user checks the attributes to be started and then clicks "Refresh", the corresponding periodic / real-time calculation task can be started to update the portrait.

[0222] Step S206, in response to an external trigger of the update operation item for the first target portrait, in the case of stopping the first target portrait, stop executing the step of updating the first target portrait.

[0223] In this step, for a portrait that is being updated, after clicking "Stop Update", the corresponding task will be stopped, and when the task is associated with multiple attributes, the portrait attributes that may be implicated will be prompted.

[0224] Based on the above, in an embodiment of the present disclosure, please refer to Figure 12 and Figure 16 wherein the portrait attribute operation items include a save-to-public-portrait operation item; the method further includes step S207:

[0225] Step S207, in response to an external trigger of the save-to-public-portrait operation item for the second target portrait, save the second target portrait to the public portrait, wherein the second target portrait is any one of the various target portraits.

[0226] In this embodiment, by saving the constructed portrait to the public portrait, the portrait attributes can be published to the public data, and thereafter these attributes will be used as public user portraits / material portraits and supplied to different scenarios.

[0227] Among them, considering the naming of attributes, attributes saved to the system's public portrait can have a name prefix added to the public portrait attribute set. For example, for a user portrait, assuming the scenario name for exporting the portrait is "home_recommend" and the saved attribute name is "user_recent_purchcase", it will be named "${scenario name}-${attribute name}" in the system's built-in public portrait library, and here it will be named "home_recommend-user_recent_purchase".

[0228] Another example, for a material portrait, assuming the scenario name for exporting the portrait is "home_recommend" and the saved attribute name is "item_recent_purchcase", it will be named "${scenario name}-${attribute name}" in the system's built-in public portrait library, and here it will be named "home_recommend-item_recent_purchase".

[0229] In this embodiment, it supports the precipitation and reuse of portraits, thereby precipitating the customer's data assets and improving the efficiency of related projects such as the implementation of AI projects.

[0230] Regarding the above content, explore this portrait viewing method:

[0231] In an embodiment of the present disclosure, please refer to Figure 13 , the application data includes portraits; the method further includes step S208:

[0232] Step S208, in response to a portrait search request, provide the constructed portrait corresponding to the search identifier included in the portrait search request.

[0233] In this embodiment, the portrait attributes can be searched by user / material ID or user / material name, and the content of the portrait can be viewed. The most recently updated portrait content can be provided by default. For example, for a user portrait, the display interface for viewing the portrait through the content exploration method can be as Figure 13 shown.

[0234] Specifically, a sample is a data instance, an encapsulation of features. Labeled samples can be used to train a model, and unlabeled samples can be used to test a model. A large number of well-featured labeled samples are the key to machine learning. Based on this, after generating the portrait as application data according to the data assigned to the scenario, samples as application data can also be generated based on the portrait. The generated samples can be used to train and optimize the basic model of the corresponding scenario.

[0235] Therefore, in an embodiment of the present disclosure, the application data includes portraits and samples;

[0236] In step S20313, the target data is processed according to the data configuration information to construct any type of application data corresponding to the target scenario, including: generating a sample corresponding to the target scenario according to the data configuration information and the portrait corresponding to the target scenario.

[0237] In this embodiment, a sample may be a wide table data composed of seven parts: user information, material information, behavior information, user portrait, material portrait, label (optimization target attribution), and scoring (estimated service).

[0238] Among them, the user information is the original data of the user in the public data; the material information is the original data of the material in the public data; the behavior information is the environmental information at the time of the exposure / display behavior; the user portrait is the long-term and short-term portraits configured for the user; the material portrait is the portrait attribute configured for the material.

[0239] For the label, the target behavior is attributed and deduced to obtain the sample label. If the label is positive, the sample is a positive sample; if the label is negative, the sample is a negative sample. For example, when the optimization target is the click-through rate, for the recommendation result, whether to click is the label.

[0240] For the scoring, if it is the output of the system recommendation this time, the scoring data and other request information in the system log are associated.

[0241] As mentioned above, the application data may include portraits, samples, and metrics. For the sample as an application data, in an embodiment of the present disclosure, please refer to Figure 17 The application data includes samples; the first configuration item includes at least one of a placement channel configuration item, a placement column configuration item, a target behavior configuration item, and a feedback period configuration item.

[0242] Specifically, the placement channel is the channel source for display, such as WeChat Mini Program (MP), mobile application (Android / IOS), etc.; the placement column is the content column for display, such as the home page information flow home_feed; the target behavior is the target behavior to be predicted, such as purchase (purchcase), purchase any (purchase any), purchase similar (purchase similar), click (click); the feedback period is the time window of the feedback delay.

[0243] For example, when the user requests to generate the sample as an application data, the corresponding display interface may be as Figure 17 shown.

[0244] Specifically, considering different scenarios, such as there being many similar calculation patterns between the metric data in the recommendation scenario and the push scenario, and considering that for various subsequent scenarios and supporting user operation diagnosis, etc., corresponding dashboards and metric insights are required, an efficient metric development framework can be provided at the data foundation level. By unifying the development view, the same calculation logic can be precipitated and reused. Therefore, the application data of metrics can be created.

[0245] For the application data of metrics, in an embodiment of the present disclosure, please refer to Figure 18 , the application data includes metrics; the first configuration item includes: template metric configuration items corresponding to at least one scenario, and custom metric configuration items.

[0246] In this embodiment, built-in template metrics and custom metrics are supported as supplements, where the template metrics are metrics currently defined for existing different scenarios, and the custom ones can be extended according to the scenario needs.

[0247] For example, the template metrics can include push metrics for the push business scenario, recommendation metrics for the recommendation business scenario, and search metrics for the search business scenario.

[0248] For custom metrics, after clicking to add, the metrics can be extended according to the scenario needs. For example, the extended metrics can be configured from aspects such as name, statistical method, filtering conditions, grouped statistics, description, etc. to meet the scenario requirements. Based on this, in an embodiment of the present disclosure, please refer to Figure 18 , the custom metric configuration item includes at least one of: a name configuration item, a statistical method configuration item, a filtering condition configuration item, a grouped statistics configuration item, and a description configuration item.

[0249] For the statistical method, the user can configure the number of users / total times / total amount / total duration of the occurrence of a specified behavior as needed, and can also configure a custom metric formula.

[0250] For segmented statistics, the user can specify the segmented (grouped) field as needed.

[0251] For the filtering conditions, the user can perform filtering statistics within a specified range for the target attribute. Similar to the filtering of material and user data, the filtering rules can include: rules for numerical, floating-point, text, date and time, and boolean fields.

[0252] (1) For numerical types (short integer, long integer, integer), the query input box defaults to "Please enter an integer, such as 0", and the following operators can be available:

[0253] Equal to (=)

[0254] Not equal to (≠)

[0255] Greater than (>)

[0256] Less than (<)

[0257] Greater than or equal to (≥)

[0258] Less than or equal to (≤)

[0259] Not null (is null)

[0260] Null (is not null)

[0261] (2) For floating-point (floating-point numerical) fields, the query input box defaults to "Please enter a decimal number, such as 0.0", and the following operators are available:

[0262] Equal to (=)

[0263] Not equal to (≠)

[0264] Greater than (>)

[0265] Less than (<)

[0266] Greater than or equal to (≥)

[0267] Less than or equal to (≤)

[0268] Not null (is null)

[0269] Null (is not null)

[0270] (3) For text (string) fields, the query input box defaults to "Please enter text, such as abc", and the following operators are available:

[0271] Equal to (=)

[0272] Not equal to (≠)

[0273] Contains (contains)

[0274] Does not contain (not contains)

[0275] Same as (like)

[0276] Different from (not like)

[0277] Not null (is null)

[0278] Null (is not null)

[0279] (4) For date and time fields, "Please enter a date, such as 2020-01-01" or "Please enter a time, such as 2020-01-01 00:00:00", and the following operators are available:

[0280] before

[0281] after

[0282] equal or after

[0283] equal or before

[0284] is null

[0285] is not null

[0286] (5) Boolean type, "Please enter a Boolean number, such as true", and the following operators can be used:

[0287] equal (=)

[0288] not equal (≠)

[0289] is null

[0290] is not null

[0291] For example, when the user selects to create a custom metric, the corresponding configuration interface can be as Figure 19 shown.

[0292] In an embodiment of the present disclosure, please refer to Figure 19 , the application data includes metrics; the method further includes steps S209 - step S211:

[0293] Step S209, in response to a metric display configuration request, provide metric display configuration items.

[0294] In an embodiment of the present disclosure, the metric display configuration items include at least one of: a time granularity configuration item, a start time configuration item, and an end time configuration item.

[0295] In this embodiment, the user can configure the time granularity, start time, and end time as needed, and then select the corresponding interval metrics for display. For example, the time granularity supports four modes: "by 15 minutes", "by 30 minutes", "by hour", and "by day", and the start time and end time serve as the interval boundaries of the trend chart. Based on this, the metrics are updated in real time based on the corresponding granularity.

[0296] Step S210, determine the metric display configuration information set externally through the metric display configuration items.

[0297] Step S211, in response to an index display request for the target scenario, according to the index display configuration information, display the data change trend of the indexes corresponding to the target scenario through an index display panel.

[0298] In this step, based on the index display configuration information set by the user, the corresponding data change trend is displayed to the user. Preferably, a card-style index display panel can be provided, which includes the change trend of the indexes and gives the overall situation icon of the corresponding group. Based on this, this display interface can be as Figure 19 shown. In this way, the user can intuitively view the index change situation.

[0299] In addition to creating scenarios, viewing scenario lists, configuring various application data, etc. as described above, to facilitate the user to view the data assigned to the scenarios, an embodiment of the present disclosure may also have a data viewing function.

[0300] Based on this, in an embodiment of the present disclosure, please refer to Figure 20 , the method further includes steps S212 - S213:

[0301] Step S212, in response to a request to view the target data, display a data list, where the

[0302] Specifically, the user can request to view the data assigned to a certain scenario, and based on this request, a data list listing this data can be displayed. As Figure 20 shown, the data list may include data types such as behavior data, user data, and material data. In addition, the user can search for fields according to the field name and issue a data viewing request accordingly.

[0303] Step S213, when a target data of any data type in the data list is externally triggered, display the data attributes of the target data of any data type.

[0304] In this step, please refer to Figure 20 , which supports the user to view the attributes of the data, such as field name, type, null value rate, description information, etc.

[0305] Based on this, in an embodiment of the present disclosure, please refer to Figure 20 , the at least one data type includes at least one of behavior data, user data, and material data; the behavior data includes data corresponding to at least one behavior among detail viewing, shopping cart, exposure, comment, and request; the data attributes include at least one of name, type, null value rate, and description.

[0306] In one embodiment of the present disclosure, unified data management operations can be performed based on the UI interface. In this embodiment, through the UI interface design, it supports the visual creation, publishing, and management of scenarios, so that real-time, closed-loop, and personalized intelligent operation decision-making applications can be easily configured and built in a short time.

[0307] In this embodiment, the production and management of application data can be uniformly processed, thereby solving the problems in the existing data management methods. In the existing data management methods, due to the temporary and random initiation of the production process of application data, the computing tasks and states are nowhere to be explored, resulting in problems such as production redundancy and uncontrollable production process. And it can also solve the problems in the existing data management methods. In the existing data management methods, due to the lack of precipitation and integration of the production results of application data, the application data scattered everywhere has problems such as storage redundancy and poor unity, resulting in low reusability.

[0308] As can be seen from the above, the embodiment of the present disclosure proposes a new application data management concept of scenarios, and combined with the open real-time data update method, it can realize the scenario-based data governance in the intelligent operation scenario. The embodiment of the present disclosure uniformly manages the production of application data, can efficiently precipitate data assets, and directly empower the AI model.

[0309] According to the method provided by the embodiment of the present disclosure, the scenario-based governance of application data can be realized, thereby serving the online intelligent operation of enterprises and helping enterprises quickly build a customer-specific application and service system relying on artificial intelligence.

[0310] Figure 21 A flowchart of the method according to an embodiment is given. Now, taking the Figure 1 system 100 shown as an example, the method for realizing unified data management in this embodiment is described.

[0311] As Figure 21 shown, the method of this embodiment may include the following steps S301-step S317:

[0312] Step S301, in response to a new scenario request, provide a scenario template creation item and personalized creation items for at least one scenario, and execute step S302 and step S303.

[0313] Specifically, Figure 1 the device 1000 shown can provide a UI interface for the user to operate as needed. The user can send a request by performing an operation on the UI interface.

[0314] Step S302, when the personalized creation item of the target scenario is externally triggered, provide a scenario creation configuration item corresponding to the target scenario, and obtain target scenario configuration information through the scenario creation configuration item; wherein, the target scenario is any one of the at least one scenario, and execute step S304.

[0315] Step S303: When the scenario template creation item is externally triggered, provide at least one constructed scenario, determine the first scenario externally selected from the at least one constructed scenario, obtain target scenario configuration information according to the scenario configuration information of the first scenario, and execute Step S304.

[0316] Step S304: Create a target scenario corresponding to the target scene according to the target scenario configuration information, where the relationship between the scene and the scenario is 1 to N, and N is a positive integer, and execute Step S305 and Step S309.

[0317] Step S305: For each target scenario, during the process of creating the target scenario, subscribe to target data corresponding to the target scenario from the common data according to the target scenario configuration information, and allocate the target data to the target scenario; where the common data is the original data collected for the at least one scenario and is shared, and execute Step S306 and Step S311.

[0318] Specifically, it can be Figure 1 the device 1000 shown in Figure 1 collect data from the client 2000 shown in as common data.

[0319] Step S306: In response to a new request for any type of application data for the target scenario, display a first configuration item corresponding to the any type of application data, where the application data is a portrait, a sample, or an indicator.

[0320] Step S307: Determine the data configuration information set externally through the first configuration item; process the target data according to the data configuration information to construct the any type of application data corresponding to the target scenario, and execute Step S308, Step S313, Step S315, and Step S317.

[0321] Step S308: Provide the sample corresponding to the target scenario to the model corresponding to the target scenario for processing, and end the current process.

[0322] Step S309: In response to a scenario display request, provide a scenario list, where the scenario list includes a scenario display item and a scenario operation item of the target scenario, and the scenario operation item includes a publish to scenario library operation item.

[0323] Step S310: When the publish to scenario library operation item of the target scenario is externally triggered, publish the target scenario to the scenario library, and end the current process.

[0324] Step S311: In response to a request to view the target data, display a data list, where the data list includes at least one data type.

[0325] Step S312: When a target data of any data type in the data list is externally triggered, display the data attributes of the target data of the any data type, and end the current process.

[0326] Step S313: In response to a metric display configuration request, provide metric display configuration items; determine the metric display configuration information set externally through the metric display configuration items.

[0327] Step S314: In response to a metric display request for the target scenario, according to the metric display configuration information, display the data change trend of the metrics corresponding to the target scenario through a metric display panel, and end the current process.

[0328] Step S315: In response to a portrait viewing request for the target scenario, provide a portrait attribute list; where the portrait attribute list includes: portrait attribute display items and portrait attribute operation items for each target portrait, the target portrait is a constructed portrait corresponding to the target scenario, and the portrait attribute operation items include an operation item for saving to a public portrait.

[0329] Step S316: In response to an external trigger of the operation item for saving the second target portrait to a public portrait, save the second target portrait to the public portrait, and end the current process, where the second target portrait is any one of the target portraits.

[0330] Step S317: In response to a portrait search request, according to the search identifier included in the portrait search request, provide the constructed portrait corresponding to the search identifier.

[0331] <Device Embodiment>

[0332] Figure 22 is a schematic block diagram of a device 40 for implementing unified data management according to an embodiment. As Figure 22 shown, the data management device 40 may include a scenario creation module 401, a data distribution module 402, and a data management module 403. The device 40 for implementing unified data management may be Figure 1 the device 1000 in

[0333] Among them, the scenario creation module 401 creates a target scenario corresponding to the target scenario selected by the external from at least one scenario; wherein, the relationship between the scenario and the scenario is 1 to N, and N is a positive integer. The data distribution module 402 subscribes to target data corresponding to each target scenario from the public data during the creation of the target scenario, and distributes the target data to the target scenario; wherein, the public data is the original data collected and shared by the at least one scenario. The data management module 403 manages the target data through the target scenario.

[0334] In an embodiment of the present disclosure, the data management module 403 includes: a module for constructing application data corresponding to the target scenario according to the target data; a module for providing the application data to a model corresponding to the target scenario for processing.

[0335] In an embodiment of the present disclosure, the application data includes any one or more types of portraits, samples, and metrics;

[0336] The constructing application data corresponding to the target scenario according to the target data includes: in response to a new request for any type of application data for the target scenario, displaying a first configuration item corresponding to the any type of application data; determining data configuration information set by the external through the first configuration item; processing the target data according to the data configuration information to construct the any type of application data corresponding to the target scenario.

[0337] In an embodiment of the present disclosure, the application data includes the portrait;

[0338] The first configuration item includes at least one of a portrait name configuration item, at least one portrait type configuration item, and a portrait description configuration item.

[0339] In an embodiment of the present disclosure, the application data includes the portrait;

[0340] The first configuration item includes at least one portrait type configuration item;

[0341] The determining data configuration information set by the external through the first configuration item includes: determining a target portrait type configuration item selected by the external from the at least one portrait type configuration item; providing a second configuration item corresponding to the target portrait type configuration item; determining the data configuration information set by the external through the second configuration item.

[0342] In an embodiment of the present disclosure, the application data includes the portrait;

[0343] The device 40 for implementing unified data management further includes: a module for providing a list of portrait attributes in response to a portrait viewing request for the target scenario;

[0344] Wherein, the list of portrait attributes includes: portrait attribute display items and portrait attribute operation items of each target portrait, and the target portrait is a constructed portrait corresponding to the target scenario.

[0345] In an embodiment of the present disclosure, the portrait attribute display items include at least one of an attribute name display item, an attribute type display item, an update time display item, and a description display item;

[0346] The portrait attribute operation items include at least one of an update operation item, a viewing setting operation item, and a saving-to-public-portrait operation item.

[0347] In an embodiment of the present disclosure, the portrait attribute operation items include an update operation item;

[0348] The device 40 for implementing unified data management further includes: a module for, in response to an external trigger of an update operation item for a first target portrait, performing the step of updating the first target portrait during the startup of the first target portrait; wherein, the first target portrait is any one of the target portraits;

[0349] A module for, in response to an external trigger of an update operation item for a first target portrait, stopping the execution of the step of updating the first target portrait when the first target portrait is stopped.

[0350] In an embodiment of the present disclosure, the portrait attribute operation items include a saving-to-public-portrait operation item;

[0351] The device 40 for implementing unified data management further includes: a module for, in response to an external trigger of a saving-to-public-portrait operation item for a second target portrait, saving the second target portrait to a public portrait, wherein the second target portrait is any one of the target portraits.

[0352] In an embodiment of the present disclosure, the application data includes portraits;

[0353] The device 40 for implementing unified data management further includes: a module for, in response to a portrait search request, providing a constructed portrait corresponding to the search identifier included in the portrait search request according to the search identifier.

[0354] In an embodiment of the present disclosure, the portraits include user portraits and material portraits.

[0355] In an embodiment of the present disclosure, the portraits include user portraits;

[0356] The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, a model label type configuration item, and a public portrait configuration item;

[0357] When the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction device configuration item;

[0358] When the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, a calculation attribute configuration item, a time window configuration item, a calculation device configuration item, and a service screening configuration item;

[0359] When the target portrait type configuration item is a model label type configuration item, the second configuration item includes at least one of a calculation device configuration item, a behavior type configuration item, and a material attribute configuration item.

[0360] In an embodiment of the present disclosure, the portrait includes a material portrait;

[0361] The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, and a public portrait configuration item;

[0362] When the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction device configuration item;

[0363] When the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, an accumulation amount configuration item, a time window configuration item, and a service screening configuration item;

[0364] When the target portrait type configuration item is a public portrait configuration item, the second configuration item includes a user portrait attribute selection configuration item.

[0365] In an embodiment of the present disclosure, the application data includes portraits and samples;

[0366] Processing the target data according to the data configuration information to construct any type of application data corresponding to the target scenario includes:

[0367] Generating a sample corresponding to the target scenario according to the data configuration information and the portrait corresponding to the target scenario.

[0368] In an embodiment of the present disclosure, the application data includes samples;

[0369] The first configuration item includes at least one of: a placement channel configuration item, a placement field configuration item, a target behavior configuration item, and a feedback period configuration item.

[0370] In an embodiment of the present disclosure, the application data includes metrics;

[0371] The first configuration item includes: a template metric configuration item corresponding to at least one scenario, and a custom metric configuration item.

[0372] In an embodiment of the present disclosure, the custom metric configuration item includes at least one of: a name configuration item, a statistical device configuration item, a screening condition configuration item, a grouped statistics configuration item, and a description configuration item.

[0373] In an embodiment of the present disclosure, the application data includes metrics;

[0374] The device 40 for implementing unified data management further includes: a module for providing a metric display configuration item in response to a metric display configuration request;

[0375] a module for determining metric display configuration information externally set through the metric display configuration item;

[0376] a module for, in response to a metric display request for the target scenario, displaying, according to the metric display configuration information, the data change trend of the metrics corresponding to the target scenario through a metric display panel.

[0377] In an embodiment of the present disclosure, the metric display configuration item includes at least one of: a time granularity configuration item, a start time configuration item, and an end time configuration item.

[0378] In an embodiment of the present disclosure, the device 40 for implementing unified data management further includes: a module for displaying a data list in response to a request to view the target data, where the data list includes at least one data type;

[0379] a module for, when a target data of any data type in the data list is externally triggered, displaying the data attributes of the target data of the any data type.

[0380] In an embodiment of the present disclosure, the scenario creation module 401 includes: a module for, in response to a new scenario request, determining a target scenario externally selected from at least one scenario and obtaining target scenario configuration information;

[0381] a module for creating a target scenario corresponding to the target scenario according to the target scenario configuration information;

[0382] The data distribution module 402 is configured to subscribe to target data corresponding to the target scenario from the public data according to the target scenario configuration information.

[0383] In an embodiment of the present disclosure, the determining a target scenario selected by an external party from at least one scenario in response to a new scenario request and obtaining target scenario configuration information includes: in response to the new scenario request, providing personalized creation items for the at least one scenario; in the case where the personalized creation item of the target scenario is triggered externally, providing a scenario creation configuration item corresponding to the target scenario; wherein the target scenario is any one of the at least one scenario; and obtaining the target scenario configuration information through the scenario creation configuration item.

[0384] In an embodiment of the present disclosure, the scenario creation configuration item includes at least one of a placement channel configuration item, an optimization target configuration item, a feedback period configuration item, a material library configuration item, a behavior type configuration item, a behavior channel configuration item, and an interaction field configuration item.

[0385] In an embodiment of the present disclosure, the determining a target scenario selected by an external party from at least one scenario in response to a new scenario request and obtaining target scenario configuration information includes: in response to the new scenario request, providing a scenario template creation item; in the case where the scenario template creation item is triggered externally, providing at least one constructed scenario; determining a first scenario selected by an external party from the at least one constructed scenario, and using the scenario corresponding to the first scenario as the target scenario; and obtaining the target scenario configuration information according to the scenario configuration information of the first scenario.

[0386] In an embodiment of the present disclosure, the device 40 for implementing unified data management further includes: a module for providing a scenario list in response to a scenario display request, where the scenario list includes a scenario display item and a scenario operation item of the target scenario.

[0387] In an embodiment of the present disclosure, the scenario display item includes at least one of a number display item, a name display item, a status display item, a type display item, an update time display item, and a creation time display item.

[0388] In an embodiment of the present disclosure, the scenario operation item includes at least one of a start / stop operation item, a publish to scenario library operation item, a setting operation item, and a delete operation item.

[0389] In an embodiment of the present disclosure, the scenario operation item includes a start / stop operation item;

[0390] The data distribution module 402 is configured to, in response to an external trigger of the start / stop operation item of the target scenario, during the process of starting the target scenario, execute the step of subscribing, according to the target scenario configuration information, to target data corresponding to the target scenario from public data, and distributing the target data to the target scenario.

[0391] In an embodiment of the present disclosure, the scenario operation item includes a start / stop operation item;

[0392] The data distribution module 402 is configured to, in response to an external trigger of the start / stop operation item of the target scenario, in the case of stopping the target scenario, stop executing the step of subscribing, according to the target scenario configuration information, to target data corresponding to the target scenario from public data, and distributing the target data to the target scenario.

[0393] In an embodiment of the present disclosure, the scenario operation item includes a publish-to-scenario-library operation item;

[0394] The device 40 for implementing unified data management further includes a module configured to publish the target scenario to a scenario library when an external trigger of the publish-to-scenario-library operation item of the target scenario occurs.

[0395] <System Embodiment>

[0396] Figure 23 It is a schematic hardware structure diagram of a system 50 for implementing unified data management according to another embodiment.

[0397] As Figure 23 shown, the system 50 for implementing unified data management includes at least one computing device 501 and at least one storage device 502. The at least one storage device 502 is configured to store instructions for controlling the at least one computing device 501 to execute the method in any of the above method embodiments.

[0398] The system 50 for implementing unified data management may include at least one device 1000 as Figure 1 shown, or have a hardware structure identical or similar to that of the device 1000, which is not limited herein.

[0399] In addition, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method in any of the method embodiments of the present disclosure.

[0400] The present invention may be a system, a method, and / or a computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions thereon for causing a processor to implement aspects of the present invention.

[0401] A computer-readable storage medium may be a tangible device that can retain and store instructions for use by an instruction execution device. A computer-readable storage medium may be, for example—but not limited to—an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), a memory stick, a floppy disk, a mechanically encoded device such as a punch card or raised structures in a groove having instructions stored thereon, and any suitable combination of the foregoing. The computer-readable storage medium as used herein is not to be construed as a transitory signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through an optical fiber cable), or an electrical signal transmitted through a wire.

[0402] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing / processing device, or may be downloaded to an external computer or an external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical fiber transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in each computing / processing device.

[0403] The computer program instructions for performing the operations of the present invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine - related instructions, microcode, firmware instructions, state - setting data, or source code or object code written in any combination of one or more programming languages, including object - oriented programming languages such as Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" language or similar programming languages. The computer - readable program instructions may be executed entirely on the user's computer, partially on the user's computer, executed as a stand - alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or, alternatively, may be connected to an external computer (e.g., through the Internet using an Internet service provider). In some embodiments, by using the state information of the computer - readable program instructions to customize an electronic circuit, such as a programmable logic circuit, a field - programmable gate array (FPGA), or a programmable logic array (PLA), the electronic circuit can execute the computer - readable program instructions to implement various aspects of the present invention.

[0404] Aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer - readable program instructions.

[0405] These computer - readable program instructions can be provided to a processor of a general - purpose computer, a special - purpose computer, or other programmable data - processing apparatus to produce a machine such that the instructions, when executed by the processor of the computer or other programmable data - processing apparatus, create a means for implementing the functions / acts specified in one or more blocks of the flowchart and / or block diagram. These computer - readable program instructions can also be stored in a computer - readable storage medium, which instructions cause a computer, a programmable data - processing apparatus, and / or other devices to function in a particular manner, such that the computer - readable medium storing the instructions comprises a manufacture, including instructions for implementing various aspects of the functions / acts specified in one or more blocks of the flowchart and / or block diagram.

[0406] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices, causing a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other devices to generate a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other devices to implement the functions / acts specified in one or more boxes of the flowchart and / or block diagram.

[0407] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two consecutive blocks may in fact be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or acts, or by a combination of dedicated hardware and computer instructions. It is well known to those skilled in the art that implementation through hardware, implementation through software, and implementation through a combination of software and hardware are equivalent.

[0408] The embodiments of the present invention have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art in the technical field without departing from the scope and spirit of the described embodiments. The selection of the terms used herein is intended to best explain the principles of the embodiments, the practical application, or the improvement of the technology in the market, or to enable other ordinary skilled persons in the technical field to understand the embodiments disclosed herein. The scope of the present invention is defined by the appended claims.

Claims

1. A method for implementing unified data management, comprising: For a target scenario selected by an external party from at least one scenario, creating a target scenario corresponding to the target scenario; wherein, the scenario and the scenario have a 1-to-N relationship, N is a positive integer greater than 1, and the scenario is used to carry the data solution of the optimization problem. The scenario includes the following basic elements of the optimization problem: channel, page, location, target, feedback period; For each of the target scenarios, during the process of creating the target scenario, subscribing to target data corresponding to the target scenario from the common data, and allocating the target data to the target scenario; wherein, the common data is the original data collected and shared by the at least one scenario; Managing the target data through the target scenario.

2. The method according to claim 1, wherein, The managing the target data through the target scenario includes: Constructing application data corresponding to the target scenario according to the target data; Providing the application data to the model corresponding to the target scenario for processing.

3. The method according to claim 2, wherein The application data includes any one or more of portraits, samples, and metrics; The constructing application data corresponding to the target scenario according to the target data includes: In response to a new request for any type of application data for the target scenario, displaying a first configuration item corresponding to the any type of application data; Determining the data configuration information set by an external party through the first configuration item; Processing the target data according to the data configuration information, and constructing the any type of application data corresponding to the target scenario.

4. The method according to claim 3, wherein The application data includes the portrait; The first configuration item includes: a portrait name configuration item, and / or, at least one portrait type configuration item, and / or, a portrait description configuration item.

5. The method according to claim 3, wherein, The application data includes the portrait; The first configuration item includes at least one portrait type configuration item; The determining the data configuration information set by an external party through the first configuration item includes: Determining a target portrait type configuration item selected by an external party from the at least one portrait type configuration item; Providing a second configuration item corresponding to the target portrait type configuration item; Determining the data configuration information set by an external party through the second configuration item.

6. The method according to claim 3, wherein The application data includes the portrait; The method further includes: in response to a portrait viewing request for the target scenario, providing a portrait attribute list; Wherein, the portrait attribute list includes: a portrait attribute display item and a portrait attribute operation item for each target portrait, and the target portrait is the constructed portrait corresponding to the target scenario.

7. The method according to claim 6, wherein The portrait attribute display item includes at least one of an attribute name display item, an attribute type display item, an update time display item, and a description display item; The portrait attribute operation item includes at least one of an update operation item, a view settings operation item, and a save to common portrait operation item.

8. The method according to claim 6, wherein The portrait attribute operation item includes an update operation item; The method further includes: in response to an external trigger of an update operation item for a first target portrait, during the process of starting the first target portrait, performing the step of updating the first target portrait; wherein, the first target portrait is any one of the various target portraits; In response to an external trigger of an update operation item for a first target portrait, in the case of stopping the first target portrait, stopping the execution of the step of updating the first target portrait.

9. The method according to claim 6, wherein, The portrait attribute operation item includes a save-to-public-portrait operation item; The method further includes: in response to an external trigger of the save-to-public-portrait operation item for a second target portrait, saving the second target portrait to the public portrait, wherein, the second target portrait is any one of the various target portraits.

10. The method according to claim 3, wherein The application data includes portraits; The method further includes: in response to a portrait search request, providing a constructed portrait corresponding to the search identifier included in the portrait search request according to the search identifier.

11. According to the method as claimed in any one of claims 3 to 10, wherein, The portraits include user portraits and material portraits.

12. The method according to claim 5, wherein, The portraits include user portraits; The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, a model label type configuration item, and a public portrait configuration item; In the case where the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction method configuration item; In the case where the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, a calculation attribute configuration item, a time window configuration item, a calculation method configuration item, and a service screening configuration item; In the case where the target portrait type configuration item is a model label type configuration item, the second configuration item includes at least one of a calculation method configuration item, a behavior type configuration item, and a material attribute configuration item.

13. The method according to claim 5, wherein The portraits include material portraits; The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, and a public portrait configuration item; In the case where the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction method configuration item; In the case where the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, an accumulation amount configuration item, a time window configuration item, and a service screening configuration item; In the case where the target portrait type configuration item is a public portrait configuration item, the second configuration item includes a user portrait attribute selection configuration item.

14. The method according to claim 3, wherein, The application data includes portraits and samples; The processing of the target data according to the data configuration information to construct any type of application data corresponding to the target scenario includes: Generating samples corresponding to the target scenario according to the data configuration information and the portraits corresponding to the target scenario.

15. The method according to claim 3, wherein, The application data includes samples; The first configuration item includes at least one of a delivery channel configuration item, a delivery column configuration item, a target behavior configuration item, and a feedback period configuration item.

16. The method according to claim 3, wherein, The application data includes metrics; The first configuration item includes: template metric configuration items corresponding to at least one scenario, and custom metric configuration items.

17. The method according to claim 16, wherein, The custom metric configuration items include at least one of: a name configuration item, a statistical method configuration item, a filtering condition configuration item, a grouped statistics configuration item, and a description configuration item.

18. The method according to claim 3, wherein The application data includes metrics; The method further includes: in response to a metric display configuration request, providing metric display configuration items; Determining the metric display configuration information set externally through the metric display configuration items; In response to a metric display request for the target scenario, according to the metric display configuration information, displaying the data change trend of the metrics corresponding to the target scenario through a metric display panel.

19. The method according to claim 18, wherein, The metric display configuration items include at least one of: a time granularity configuration item, a start time configuration item, and an end time configuration item.

20. The method according to claim 1, wherein The method further includes: In response to a request to view the target data, displaying a data list, where the data list includes at least one data type When the target data of any data type in the data list is externally triggered, displaying the data attributes of the target data of the any data type.

21. The method according to claim 1, for a target scenario externally selected from at least one scenario, creating a target situation corresponding to the target scenario includes: In response to a new situation request, determining a target scenario externally selected from at least one scenario, and obtaining target situation configuration information; Creating a target situation corresponding to the target scenario according to the target situation configuration information; The subscribing to target data corresponding to the target situation from public data includes: According to the target situation configuration information, subscribing to target data corresponding to the target situation from public data.

22. The method according to claim 21, the responding to a new situation request, determining a target scenario externally selected from at least one scenario, and obtaining target situation configuration information includes: In response to the new situation request, providing personalized creation items for the at least one scenario; When the personalized creation item of the target scenario is externally triggered, providing scenario creation configuration items corresponding to the target scenario; where the target scenario is any one of the at least one scenario; Obtaining the target situation configuration information through the scenario creation configuration items.

23. The method according to claim 22, wherein, The scenario creation configuration items include at least one of: a placement channel configuration item, an optimization target configuration item, a feedback period configuration item, a material library configuration item, a behavior type configuration item, a behavior channel configuration item, and an interaction field configuration item.

24. The method according to claim 21, wherein, The responding to a new situation request, determining a target scenario externally selected from at least one scenario, and obtaining target situation configuration information includes: In response to the new situation request, providing scenario template creation items; When the scenario template creation item is externally triggered, providing at least one constructed scenario; Determining a first scenario externally selected from the at least one constructed scenario, and using the scenario corresponding to the first scenario as the target scenario; According to the scenario configuration information of the first scenario, obtaining the target situation configuration information.

25. The method according to claim 21, wherein The method further includes: In response to a scenario display request, providing a scenario list, where the scenario list includes a scenario display item and a scenario operation item of the target scenario.

26. The method according to claim 25, wherein, The scenario display item includes at least one of a number display item, a name display item, a status display item, a type display item, an update time display item, and a creation time display item.

27. The method according to claim 25, wherein, The scenario operation item includes at least one of a start / stop operation item, a publish to scenario library operation item, a setting operation item, and a deletion operation item.

28. The method according to claim 27, wherein, The scenario operation item includes a start / stop operation item; The method further includes: In response to an external trigger of the start / stop operation item of the target scenario, during the process of starting the target scenario, performing the step of subscribing to target data corresponding to the target scenario from public data according to the target scenario configuration information, and allocating the target data to the target scenario; and / or The scenario operation item includes a start / stop operation item; The method further includes: In response to an external trigger of the start / stop operation item of the target scenario, in the case of stopping the target scenario, stopping the execution of the step of subscribing to target data corresponding to the target scenario from public data according to the target scenario configuration information, and allocating the target data to the target scenario.

29. The method according to claim 25, wherein, The scenario operation item includes a publish to scenario library operation item; The method further includes: In the case of an external trigger of the publish to scenario library operation item of the target scenario, publishing the target scenario to the scenario library.

30. A device for realizing unified data management, including: A scenario creation module, configured to create a target scenario corresponding to a target scenario externally selected from at least one scenario; where the relationship between the scenario and the scenario is 1 to N, N is a positive integer greater than 1, and the scenario is used to carry a data solution to an optimization problem, and the scenario includes the following basic elements of the optimization problem: channel, page, location, target, feedback period; A data allocation module, configured to, for each target scenario, during the process of creating the target scenario, subscribe to target data corresponding to the target scenario from public data, and allocate the target data to the target scenario; where the public data is the original data collected and shared by the at least one scenario; A data management module, configured to manage the target data through the target scenario.

31. The apparatus according to claim 30, wherein, The data management module includes: A module for constructing application data corresponding to the target scenario according to the target data; A module for providing the application data to a model corresponding to the target scenario for processing.

32. The apparatus according to claim 31, wherein, The application data includes any one or more types of portraits, samples, and metrics; The constructing application data corresponding to the target scenario according to the target data includes: In response to a new request for any type of application data for the target scenario, displaying a first configuration item corresponding to the any type of application data; Determining data configuration information set externally through the first configuration item; Processing the target data according to the data configuration information to construct the any type of application data corresponding to the target scenario.

33. The apparatus according to claim 32, wherein, The application data includes the portrait; The first configuration item includes at least one of: a portrait name configuration item, at least one portrait type configuration item, and a portrait description configuration item.

34. The apparatus according to claim 32, wherein, The application data includes the portrait; The first configuration item includes at least one portrait type configuration item; The determination of the data configuration information set externally through the first configuration item includes: Determining the target portrait type configuration item selected externally from the at least one portrait type configuration item; Providing a second configuration item corresponding to the target portrait type configuration item; Determining the data configuration information set externally through the second configuration item.

35. The apparatus according to claim 32, wherein, The application data includes portraits; The device further includes: a module for providing a portrait attribute list in response to a portrait viewing request for the target scenario; Wherein, the portrait attribute list includes: portrait attribute display items and portrait attribute operation items for each target portrait, and the target portrait is a constructed portrait corresponding to the target scenario.

36. The apparatus according to claim 35, wherein, The portrait attribute display items include at least one of: an attribute name display item, an attribute type display item, an update time display item, and a description display item; The portrait attribute operation items include at least one of: an update operation item, a viewing settings operation item, and a save to public portrait operation item.

37. The apparatus according to claim 35, wherein, The portrait attribute operation items include an update operation item; The device further includes: a module for, in response to an external trigger of the update operation item for a first target portrait, performing the step of updating the first target portrait during the startup of the first target portrait; wherein, the first target portrait is any one of the target portraits; A module for, in response to an external trigger of the update operation item for a first target portrait, stopping the execution of the step of updating the first target portrait when the first target portrait is stopped.

38. The device according to claim 35, wherein, The portrait attribute operation items include a save to public portrait operation item; The device further includes: a module for, in response to an external trigger of the save to public portrait operation item for a second target portrait, saving the second target portrait to a public portrait, where the second target portrait is any one of the target portraits.

39. The apparatus according to claim 32, wherein, The application data includes portraits; The device further includes: a module for, in response to a portrait search request, providing a constructed portrait corresponding to the search identifier included in the portrait search request.

40. The apparatus according to any one of claims 32 - 39, wherein, The portraits include user portraits and material portraits.

41. The apparatus according to claim 34, wherein, The portraits include user portraits; The at least one portrait type configuration item includes at least one of: a basic feature type configuration item, a statistical feature type configuration item, a model label type configuration item, and a public portrait configuration item; When the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of: a field configuration item and an extraction device configuration item; When the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of: a behavior type configuration item, a calculation attribute configuration item, a time window configuration item, a calculation device configuration item, and a service screening configuration item; When the target portrait type configuration item is a model label type configuration item, the second configuration item includes at least one of a computing device configuration item, a behavior type configuration item, and a material attribute configuration item.

42. The apparatus according to claim 34, wherein The portrait includes a material portrait; The at least one portrait type configuration item includes at least one of a basic feature type configuration item, a statistical feature type configuration item, and a public portrait configuration item; When the target portrait type configuration item is a basic feature type configuration item, the second configuration item includes at least one of a field configuration item and an extraction device configuration item; When the target portrait type configuration item is a statistical feature type configuration item, the second configuration item includes at least one of a behavior type configuration item, an accumulation amount configuration item, a time window configuration item, and a service screening configuration item; When the target portrait type configuration item is a public portrait configuration item, the second configuration item includes a user portrait attribute selection configuration item.

43. The apparatus according to claim 32, wherein, The application data includes portraits and samples; Processing the target data according to the data configuration information to construct any type of application data corresponding to the target scenario includes: Generating a sample corresponding to the target scenario according to the data configuration information and the portrait corresponding to the target scenario.

44. The apparatus according to claim 32, wherein, The application data includes samples; The first configuration item includes at least one of a delivery channel configuration item, a delivery slot configuration item, a target behavior configuration item, and a feedback period configuration item.

45. The apparatus according to claim 32, wherein, The application data includes metrics; The first configuration item includes a template metric configuration item and a custom metric configuration item corresponding to at least one scenario.

46. The apparatus according to claim 45, wherein, The custom metric configuration item includes at least one of a name configuration item, a statistical device configuration item, a screening condition configuration item, a grouped statistics configuration item, and a description configuration item.

47. The apparatus according to claim 32, wherein, The application data includes metrics; The device further includes: a module for providing a metric display configuration item in response to a metric display configuration request; A module for determining metric display configuration information set externally through the metric display configuration item; A module for, in response to a metric display request for the target scenario, displaying the data change trend of the metrics corresponding to the target scenario through a metric display panel according to the metric display configuration information.

48. The apparatus according to claim 47, wherein, The metric display configuration item includes at least one of a time granularity configuration item, a start time configuration item, and an end time configuration item.

49. The apparatus according to claim 30, wherein, The device further includes: A module for displaying a data list in response to a request to view the target data, where the data list includes at least one data type; A module for displaying the data attributes of the target data of any data type in the data list when the target data of any data type in the data list is externally triggered.

50. The device according to claim 30, wherein the scenario creation module includes: A module for, in response to a new scenario request, determining a target scenario selected externally from at least one scenario and obtaining target scenario configuration information; A module for creating a target scenario corresponding to the target scenario according to the target scenario configuration information; The data distribution module is configured to subscribe to target data corresponding to the target scenario from the public data according to the target scenario configuration information.

51. The apparatus according to claim 50, wherein the step of determining a target scenario selected by the external party from at least one scenario in response to a new scenario request and obtaining target scenario configuration information includes: In response to the new scenario request, providing personalized creation items for the at least one scenario; In the case where the external party triggers the personalized creation item of the target scenario, providing a scenario creation configuration item corresponding to the target scenario; wherein the target scenario is any one of the at least one scenario; Obtaining the target scenario configuration information through the scenario creation configuration item.

52. The device according to claim 51, wherein, The scenario creation configuration item includes at least one of a placement channel configuration item, an optimization target configuration item, a feedback period configuration item, a material library configuration item, a behavior type configuration item, a behavior channel configuration item, and an interaction field configuration item.

53. The apparatus according to claim 50, wherein, The step of determining a target scenario selected by the external party from at least one scenario in response to a new scenario request and obtaining target scenario configuration information includes: In response to the new scenario request, providing a scenario template creation item; In the case where the external party triggers the scenario template creation item, providing at least one pre-constructed scenario; Determining a first scenario selected by the external party from the at least one pre-constructed scenario, and using the scenario corresponding to the first scenario as the target scenario; Obtaining the target scenario configuration information according to the scenario configuration information of the first scenario.

54. The apparatus according to claim 50, wherein, The apparatus further includes: A module configured to provide a scenario list in response to a scenario display request, where the scenario list includes a scenario display item and a scenario operation item of the target scenario.

55. The apparatus according to claim 54, wherein, The scenario display item includes at least one of a number display item, a name display item, a status display item, a type display item, an update time display item, and a creation time display item.

56. The apparatus according to claim 54, wherein, The scenario operation item includes at least one of a start / stop operation item, a publish to scenario library operation item, a settings operation item, and a delete operation item.

57. The apparatus according to claim 56, wherein, The scenario operation item includes a start / stop operation item; The data distribution module is configured to, in response to the external party triggering the start / stop operation item of the target scenario, during the process of starting the target scenario, execute the step of subscribing to target data corresponding to the target scenario from the public data according to the target scenario configuration information and allocating the target data to the target scenario; and / or, The scenario operation item includes a start / stop operation item; The data distribution module is configured to, in response to the external party triggering the start / stop operation item of the target scenario, in the case of stopping the target scenario, stop executing the step of subscribing to target data corresponding to the target scenario from the public data according to the target scenario configuration information and allocating the target data to the target scenario.

58. The apparatus according to claim 54, wherein, The scenario operation item includes a publish to scenario library operation item; The apparatus further includes a module configured to publish the target scenario to a scenario library in the case where the external party triggers the publish to scenario library operation item of the target scenario.

59. A system including at least one computing device and at least one storage device, wherein, The at least one storage device is used to store instructions for controlling the at least one computing device to execute the method according to any one of claims 1-29.

60. A computer-readable storage medium having a computer program stored thereon, the computer program implementing the method according to any one of claims 1-29 when executed by a processor.

Images