Data service method and apparatus

Abstract

The embodiment of the application provides a data service method and equipment, wherein the data service method comprises the following steps: obtaining a service creation request corresponding to a data label; determining a data source of the data label and a destination address used for realizing data service based on the service creation request; and performing data service processing based on the data source and the destination address to obtain a target service corresponding to the data label. The technical scheme provided by the embodiment performs data service processing based on the determined data source and destination address to obtain a target service corresponding to the data label, effectively realizing automatic data service operation. Since collaborative operation is not required during the data service process, the delivery time of the data service is effectively shortened, the delivery efficiency of the target service is improved, and the quality and efficiency of the data service are further ensured.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a data service method and device. Background Technology

[0002] Data as a Service (DaaS) is a data management strategy that has been widely and deeply integrated into the application scenarios of various core business units (CBUs) for current online and offline data services, such as user growth (new users), marketing events (major promotions), various scenarios (group buying, flash sales), search and recommendation, factory search, private domain (member accounts), business intelligence, etc.

[0003] Currently, in the process of data service-oriented architecture, collaboration among various data parties is required. For example, the service development process requires testing and the involvement of data analysts (DAs). This involves a significant amount of offline operation time, cross-platform operations, and fragmented time, resulting in an overall operation time of several hours for the data service-oriented architecture process. Consequently, the actual delivery time is usually T+1, leading to low delivery efficiency. Summary of the Invention

[0004] This application provides a data service method and apparatus that can automatically perform data service operations, thereby improving the delivery quality and efficiency of data service delivery.

[0005] In a first aspect, embodiments of this application provide a data service method, including:

[0006] Retrieve the service creation request corresponding to the data tag;

[0007] Based on the service creation request, determine the data source of the data tag and the destination address for implementing data service;

[0008] Based on the data source and destination address, data is processed into services to obtain the target service corresponding to the data tag.

[0009] Secondly, embodiments of this application provide a data service apparatus, including:

[0010] The first acquisition module is used to acquire service creation requests corresponding to data tags;

[0011] The first determining module is used to determine the data source of the data tag and the destination address for implementing data service based on the service creation request.

[0012] The first processing module is used to perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0013] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the data service method described in the first aspect above.

[0014] Fourthly, embodiments of the present invention provide a computer storage medium for storing a computer program that, when executed by a computer, enables the data service method described in the first aspect above.

[0015] Fifthly, embodiments of the present invention provide a computer program product, comprising: a computer program that, when executed by a processor of an electronic device, causes the processor to perform the steps in the data service method described in the first aspect above.

[0016] Sixthly, embodiments of the present invention provide a data service method, including:

[0017] The operation page is displayed to realize data service. The operation page includes multiple data tags and application service controls corresponding to each data tag. The application service controls are used to realize service creation operations.

[0018] Get the action input by the user for any of the application service controls on the operation page;

[0019] Based on the executed operation, the service configuration page is displayed;

[0020] The data source for the data tag and the destination address for implementing data service can be obtained through the service configuration page.

[0021] Based on the data source and destination address, data is processed into services to obtain the target service corresponding to the data tag.

[0022] In a seventh aspect, embodiments of the present invention provide a data service apparatus, comprising:

[0023] The second display module is used to display an operation page for implementing data service. The operation page includes multiple data tags and application service controls corresponding to each data tag. The application service controls are used to implement service creation operations.

[0024] The second acquisition module is used to acquire the execution operation entered by the user for any application service control on the operation page;

[0025] The second display module is used to display a service configuration page based on the executed operation;

[0026] The second acquisition module is used to acquire the data source of the data tag and the destination address for implementing data service through the service configuration page;

[0027] The second processing module is used to perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0028] Eighthly, embodiments of this application provide an electronic device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the data service method described in the sixth aspect above.

[0029] Ninthly, embodiments of the present invention provide a computer storage medium for storing a computer program that, when executed by a computer, implements the data service method described in the sixth aspect above.

[0030] In a tenth aspect, embodiments of the present invention provide a computer program product, comprising: a computer program that, when executed by a processor of an electronic device, causes the processor to perform the steps in the data service method described in the sixth aspect above.

[0031] Eleventhly, embodiments of the present invention provide a data service method applied to a cloud server, the method comprising:

[0032] In response to a data service request to the cloud server, determine the processing resources corresponding to the data service.

[0033] The following steps are performed using the processing resources: obtaining a service creation request corresponding to the data tag; determining the data source of the data tag and the destination address for implementing data service based on the service creation request; and performing data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0034] In a twelfth aspect, embodiments of the present invention provide a data service apparatus applied to a cloud server, the apparatus comprising:

[0035] The third determining module is used to determine the processing resources corresponding to the data service in response to the data service request of the cloud server.

[0036] The third processing module is used to perform the following steps using the processing resources: obtaining a service creation request corresponding to the data tag; determining the data source of the data tag and the destination address for implementing data service based on the service creation request; and performing data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0037] In a thirteenth aspect, embodiments of this application provide an electronic device, including: a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the data service method described in the eleventh aspect above.

[0038] In a fourteenth aspect, embodiments of the present invention provide a computer storage medium for storing a computer program that, when executed by a computer, implements the data service method described in the eleventh aspect above.

[0039] In a fifteenth aspect, embodiments of the present invention provide a computer program product, comprising: a computer program that, when executed by a processor of an electronic device, causes the processor to perform the steps in the data service method described in the eleventh aspect above.

[0040] The data service method and apparatus provided in this application obtain a service creation request corresponding to a data tag, determine the data source of the data tag and the destination address for implementing data service based on the service creation request, and perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag. This effectively realizes automated data service operation. Since no collaborative operation is required from all parties during the data service process, the delivery time of data service is effectively shortened, and the delivery efficiency of the target service is improved. This further ensures the quality and efficiency of data service, and also improves the practicality of the method, which is conducive to market promotion and application. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 A schematic diagram illustrating the services provided for related technologies;

[0043] Figure 2 A diagram illustrating service access provided for related technologies;

[0044] Figure 3 This is a schematic diagram of the structure of a data service platform provided in an embodiment of this application;

[0045] Figure 4 A schematic diagram of the tag field provided in an embodiment of this application;

[0046] Figure 5 This is a schematic diagram illustrating the storage of a data table as provided in an embodiment of this application.

[0047] Figure 6 A schematic diagram illustrating the principle of the data service method provided in the embodiments of this application;

[0048] Figure 7 A schematic diagram illustrating the principle of a data service method provided in an embodiment of this application;

[0049] Figure 8 A flowchart illustrating a data service method provided in an embodiment of this application;

[0050] Figure 9 A flowchart illustrating another data service method provided in an embodiment of this application;

[0051] Figure 10 A flowchart illustrating yet another data service method provided in an embodiment of this application;

[0052] Figure 11 A flowchart illustrating another data service method provided in this application embodiment;

[0053] Figure 12 A flowchart illustrating another data service method provided in an embodiment of this application;

[0054] Figure 13 This is a schematic diagram of the structure of a data service device provided in an embodiment of this application;

[0055] Figure 14 To and Figure 13 The diagram shows the structure of the electronic device corresponding to the data service device provided in the embodiment.

[0056] Figure 15 A schematic diagram of another data service device provided in the embodiments of this application;

[0057] Figure 16 To and Figure 15 The diagram shows the structure of the electronic device corresponding to the data service device provided in the embodiment.

[0058] Figure 17A schematic diagram of the structure of another data service device provided in the embodiments of this application;

[0059] Figure 18 To and Figure 17 The illustrated embodiment provides a schematic diagram of the electronic device corresponding to the data service device. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. “Multiple” generally includes at least two, but does not exclude the inclusion of at least one.

[0062] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0063] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0064] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes that element.

[0065] Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0066] To facilitate understanding of the technical solutions provided in the embodiments of this application by those skilled in the art, the relevant technologies are briefly described below: Data as a Service (DaaS) is a data management strategy that can be used to bridge the last mile of enterprise data applications. For current online / offline data service applications, it has been widely and deeply integrated into the application scenarios of various core business units (Core Business Units / China Business Units, CBUs), such as: user growth (new users), marketing events (major promotions), various scenarios (group buying, special sales), search recommendations, factory search, private domain (member accounts), business intelligence, etc.

[0067] Currently, CBU data service delivery mainly takes three forms: services for a single department (OneService), services for an industry platform (Indicator Center), and services for other departments (data services developed by individual teams). According to incomplete statistics, CBU data is accessed over 5 billion times daily (4.2 billion for OneService, 1 billion for the Indicator Center, and over 100 million for self-developed services), and is growing at a rate of 10% annually. However, CBU's data services face the following three significant challenges:

[0068] (1) High service costs and low return on investment (ROI).

[0069] The current data service model of CBU is production-oriented, and there is a lack of effective governance methods for whether data should be taken offline. This easily leads to a large number of data services still requiring a lot of computing and storage resources even when they are not called, resulting in rising annual maintenance costs. CBU's OneService alone costs 3.57 million yuan per year (not including storage costs).

[0070] Furthermore, there is a lack of a unified computing and storage model for data. Since each technology line operates and develops independently, the reusability is extremely low, and most of them are built with private storage, resulting in extremely high storage redundancy. According to incomplete statistics, the duplication rate of most common logic is 60%. Typically, a data analyst (DA) does it once, a business intelligence (BI) team does it once, and then the R&D team does it again. This means that the calculation is repeated at least twice on the Open Data Processing Service (ODPS), and different scenarios or needs may even reuse the same data.

[0071] (2) Low efficiency in service production and access.

[0072] Currently, the data service process typically takes several hours to complete. (See attached document for reference.) Figure 1 As shown, it takes about 5.5 hours for a skilled colleague to perform data service operations. This is because it requires collaboration among various data parties, including a large amount of offline operation time and cross-platform operations. For example, the service development process requires testing and the intervention of data analytics. A lot of time is fragmented, and the actual delivery time is usually more than 10 hours. The delivery efficiency does not meet the preset expectations, resulting in a low ROI of R&D output.

[0073] After the service-based product is delivered, the service integration process can be carried out, such as... Figure 2 As shown, the service access process can include: permission application process, entity class development process, interface encapsulation process, joint debugging and testing process, etc. According to the technical team's evaluation, it takes 2 days for a service-oriented product to go from access to launch. As can be seen from the above, the service access process takes a long time and has low access efficiency.

[0074] (3) Asset services are isolated, quality is difficult to guarantee, there is a lack of unified asset management methods, and data application is difficult.

[0075] There remains a "last mile" hurdle between valuable data and the value generated from that data. Bridging this "last mile" is notoriously difficult, often requiring close collaboration across multiple departments. Otherwise, self-built solutions are prohibitively expensive, leading to the creation of isolated applications. However, in real-world scenarios, single-database systems are often insufficient. To resolve these silos, users from various departments frequently spend significant time and resources modifying, developing new systems, or integrating existing ones. Returning to the data itself, users should focus on: What are the core assets? Where are these assets located? What assets does the scenario require? How can they be provided?

[0076] To address the aforementioned technical issues, this embodiment provides a data service approach and apparatus. The implementing entity of this data service approach can be a high-efficiency, low-cost, and highly available one-stop data service platform. This platform, based on a data asset center, provides unified asset definition and management operations, unified data service production / access operations (production automation), unified data service management and governance operations, and a unified scheduling and resource optimization model. For details, please refer to the appendix. Figure 3As shown, unified asset definition and management operations, as well as unified data service management and governance operations, can be achieved through the indicator definition and management module. This module can include indicator configuration, configuration verification, lineage tracing, caliber verification, access approval, configuration approval, lifecycle management, scenario domain management, and tag domain management modules.

[0077] The aforementioned indicator configuration module is used to implement indicator configuration operations, specifically including indicator generation, addition, modification, and deletion operations; the configuration verification module is used to perform configuration verification operations on the configured indicators to ensure that the configured indicators meet preset requirements; the caliber verification module is used to perform configuration verification operations on the data caliber (used to limit the data caliber, original definition, format, etc.) to ensure that the configured data caliber meets preset requirements; the lineage tracing module is used to determine the data services, indicator call volumes, and application scenarios that are related to the configured indicators, and establish lineage relationships between the indicators, related data services, indicator call volumes, and application scenarios to perform data tracking and management operations based on the established lineage relationships; the access review module is used to perform identity verification operations on users of the data service platform to achieve legitimate data processing operations; the configuration review module is used to review the configured data services to ensure that the configured data services meet preset requirements.

[0078] Unified data service management and governance can be achieved through the lifecycle management module, tag domain management module, and scenario domain management module. The lifecycle management module is used to obtain the lifecycle corresponding to each indicator (also known as a data tag) and manage each indicator and its associated data services based on that lifecycle. The tag domain management module is used to obtain the tag domain corresponding to each indicator and manage the established data services based on that tag domain. The scenario domain management module is used to obtain the scenario domain corresponding to each data service and manage the established data services based on that scenario domain.

[0079] In addition, unified data service production / access operations can be implemented through the service construction and management module, which includes a service production module and a service access module. The service production module includes: service creation module, unit creation module, cache acceleration module, seamless deployment module, automated testing module, version management module, lifecycle module, and public / private domain management module. The service access module includes: tag configuration module (for unified Chinese naming of data tags or metrics), permission management module, service routing, unified gateway, etc.

[0080] Specifically, the service creation module is used to obtain service creation requirements and create corresponding data services based on these requirements, thus transforming data into services; the unit creation module is used to configure the service management directory and manage services based on this directory; the caching acceleration module is used to perform caching operations on service-related data (historical data); the seamless deployment module is used to achieve seamless deployment of the created services; the automated testing module is used to perform automated testing operations on the created data services after their creation to ensure the quality and effectiveness of service processing; the version management module is used to upgrade or update the created data services; the lifecycle module is used to manage data services based on the lifecycle of data tags; and the public / private domain management module is used to manage data services based on pre-configured public and private domain directories.

[0081] The tag configuration module, service routing, and unified gateway in the service access module can complete the relevant configuration operations and enable other platforms to establish communication connections with the data service platform. The permission management module is used to manage data service operations according to preset permissions. For example, different users can have different data service permissions.

[0082] Unified scheduling and resource optimization can be achieved through a detection and scheduling module, which can include a unified detection module for unified detection operations and a unified scheduling module for unified scheduling operations. The unified detection module is used to perform unified degradation, circuit breaking, rate limiting, and isolation operations on the data services that the platform can provide; the unified scheduling module is used to perform data synchronization operations, signal communication operations, detection operations, and baseline protection operations on the provided data services.

[0083] It is important to note that a data service platform can also include a service application module to provide scenario-based applications and platform-based applications. Scenario-based applications can provide services to different users through a single interface or lightweight application, while platform-based applications can provide services to various platforms through open interfaces such as data circulation interfaces, capability integration interfaces, and Application Programming Interfaces (APIs). Furthermore, a data service platform can also include a storage and application management module for storing and managing data sources. Specifically, the storage and application management module can include a data source management module for managing data sources, a storage model management module for storing data, and an application management module for managing the created service applications.

[0084] Specifically, based on the aforementioned data service platform, a unified and fully automated method for producing / accessing data services can be implemented. This method may include: obtaining a service creation request corresponding to a data tag; determining the data source of the data tag and the destination address for implementing data service based on the service creation request; and performing data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0085] In the process of accessing data-driven services, two service modes are established: centralized (the data source corresponding to data service is a pre-configured central database) and decentralized (the data source corresponding to data service is a personalized data source corresponding to the user) to meet the access requirements of different scenarios. A unified Software Development Kit (SDK) is provided for access, and a unified service format is adopted to reduce access costs. Specifically, after receiving a service creation request, it can be determined whether the data source is already stored in the asset database. If the data source is already stored in the asset database, a target service corresponding to the data tag can be generated with one click, thus realizing centralized data service operation. If the data source is not stored in the asset database, data service operation can be performed through a user-configured data source (e.g., a local database), thus realizing decentralized data service operation.

[0086] In terms of the production process, the method in this embodiment can support the service-orientation of various asset forms: tables, tags, and Structured Query Language (SQL) databases, ensuring consistency by adhering to preset indicator definitions. Compared to related technologies, it effectively simplifies the production process. Specifically, it can fully standardize and configure data synchronization, service development, and test development. For example, data synchronization does not require task configuration, field mapping, service mapping, or other information; the system automatically completes the synchronization and field mapping.

[0087] Furthermore, the data service platform in this embodiment can also realize a unified data tag service management and governance system. The data service platform relies on the full-domain data asset system, fits the application scenario, and establishes unified data service management for multiple sources and multiple data types. Specifically, the method in this embodiment may include: obtaining the tag domain corresponding to the data tag, and managing the data tag based on the tag domain.

[0088] Users can create unified data sharing and service areas according to their needs, and build a tag domain system based on these needs. Data tags are generally managed based on this established tag domain system. In some examples, the tag domain system can include entity domains (buyers, merchants, products, etc.), scenario domains (business recruitment, Alipay, search, etc.), and private domains (personalized tag domains created by users according to their individual needs, which are not publicly displayed on the platform). Figure 4 As shown, the entity domain is used to establish a data management directory based on the tag entity; the scenario domain is used to establish an application attribute data directory based on the scenario; and the private domain is used to establish a temporary indicator area. In some instances, for data tags in the tag domain system, a limited number of data tags can be displayed on a single display page. Generally, no more than 20 data tags are displayed on a single page. For data tags in the tag domain system, data tags can be automatically managed according to their lifecycle. For example, if the lifecycle of a data tag is 30 days, then the data tag can be automatically silenced after 30 days. Furthermore, data tags can be renewed as needed.

[0089] In some other instances, not only can data tags be managed based on tag domains, but also full-chain lineage data corresponding to data tags can be established, and a data indicator governance system can be built based on the full-chain lineage data. In this case, the method in this embodiment may include: obtaining data sources, data services, and application scenarios corresponding to data tags; establishing relationships between data sources, data tags, data services, and application scenarios; and managing data services or data tags based on the relationships.

[0090] In other instances, since many data metrics on the platform are for one-time use, to improve the quality and efficiency of data tag management, strict replacement logic can be set according to requirements, and then data tags can be managed based on this logic; specifically:

[0091] Implementation method (1): The replacement logic can manage data tags based on the call volume corresponding to the data tag. In order to realize the management of data tags based on the call volume corresponding to the data tag, the user can establish an indicator service detection system, and then perform replacement management operation on the data tag based on the indicator service detection system. For example, when detecting the call volume of downstream in the past 33 days, 93 days or when there is no downstream, if the call volume is less than the set threshold call, the user will first go offline and then remain silent (notify through the preset application).

[0092] Implementation method (2): The replacement logic can not only manage data tags based on the call volume corresponding to the data tag, but also manage data tags based on the life cycle of the data tag. At this time, users can set the indicator type and indicator life cycle according to the application requirements. For example, the indicator type is divided into two types: one is production indicator, which usually has a long life cycle, and the other is temporary indicator, which has a maximum life cycle of no more than 30 days (automatically offline after 30 days).

[0093] In implementation method (3), the replacement logic can not only manage data tags based on the call volume and life cycle of the data tags, but also establish an indicator value assessment system to determine the tag cost and tag value of the data tags. Specifically, the computational volume, storage volume and call count of the data tags can be determined based on the indicator value assessment system. If the computational volume and storage volume of the data tags are large, it means that the tag cost of the data tags is large; if the computational volume and storage volume of the data tags are small, it means that the tag cost of the data tags is small. For data tags with large computational volume and storage volume but low call count, the tag push information corresponding to the data tags can be generated to send the tag push information to the tag producer for data tag governance.

[0094] After creating target services corresponding to data tags through the data service platform, the method in this embodiment can also achieve unified resource scheduling and resource optimization operations through the data service platform. At this time, in order to achieve unified resource scheduling for each data tag and target service, the data service platform can be configured with a unified scheduling strategy, and based on the unified scheduling strategy, and using the indicator center as the whole data management and scheduling framework, so that users can call the created target services or data tags.

[0095] Furthermore, the data service platform in this embodiment can also implement a unified storage model. Users can perform service query operations or information query operations through the following query types. Specific query methods can include any one of the following: simple query method, KV query method (primary key query), complex query method, and Structured Query Language (SQL). SQL (Sql) type single-table queries, etc., include simple queries, which can include NoSQL queries, accounting for approximately 80%+ of all query service operations; key-value (KV) queries, which can use two attributes as the primary key or a primary key plus any number of attributes. Specifically, the first key is the primary key, such as user_id, item_id, member_id, etc., and the second key is the table name, identifying the service data source name; the value is the metric name, following OneData naming conventions; complex queries account for 20%+ of all query service operations; SQL single-table queries can include SQL multi-table queries, such as collaborative multi-table queries, search engine queries, and graph queries, etc.

[0096] Furthermore, after generating target services for data tags (data metrics), you can select the storage database corresponding to the data tags (data labels). Taking HBase as an example, you can perform adaptive adjustments to the stored data based on the database's storage characteristics. Specifically, for example... Figure 5 As shown, in a database, data storage operations can be performed on tables based on keys. The relationship between the data and the data tables is not a one-to-one mapping, but a many-to-one mapping. For example, if the tables stored in a data warehouse include TableA, TableB, TableC, TableD, and TableE, TableA and TableB correspond to the keyword UserId. Since TableA and TableB both correspond to the same UserId, when storing the tables in the data warehouse, TableA and TableB can be stored using the same keyword User_Id as the key, thus effectively achieving a two-to-one mapping relationship for storing the data tables. Similarly, TableC can be stored using member_Id as the key, and TableD can be stored using Item_Id as the key.

[0097] For details, please refer to the appendix. Figure 6 As shown, the data service method in this embodiment may include the following steps:

[0098] Tag configuration personnel can create or edit tags as needed and obtain tag drafts. Tag drafts can be approved by tag approvers. After the tag drafts are approved, data tags can be obtained from the data service platform.

[0099] System administrators can perform system maintenance operations as needed. These operations can manage data tags, which can correspond to service resources, application domains, data source types, value types, dimensions, metrics, and engine mappings. Data tags can also correspond to application management.

[0100] When users have service-oriented needs for data tags on a data service platform, the following steps may be included:

[0101] Users can input service creation requests into the data service platform. After receiving the service creation request, the data source for the data tag and the destination address for implementing data service can be determined based on the service creation request. The aforementioned data source can include preset public data sources and user-created personalized data sources. When the data source is a preset public data source, the data service can be determined to be a centralized data service operation. When the data source is a user-created personalized data source, the data service can be determined to be a decentralized data service operation.

[0102] After obtaining the data source and destination address, data service processing can be performed based on these addresses to obtain the target service corresponding to the data tag. Specifically, since different data source types can correspond to different service generation methods, the data source type can be identified first after obtaining the data source. When the data source type is a first preset type (preset standard type), the data tags in the system can be standardized based on the first preset type to generate standardized tags corresponding to the data tags. This allows different data tags that can express the same meaning to be processed uniformly, thereby reducing the duplication rate of data tags. When the data source type is a second preset type (preset personalized type, user-configured private type, etc.), the data source of the second preset type can be obtained through the preset interface (dump interface).

[0103] After obtaining the data source corresponding to the data tag, a data synchronization task can be generated based on the data source and destination address. Then, the data source can be synchronized to the destination address based on the data synchronization task to obtain the target service corresponding to the data tag. The target service can realize at least one of the following: information aggregation service, service to identify whether the user is a new user, entity tag addition service, merchant transaction amount query service, merchant payment number query service, merchant payment amount query service, etc.

[0104] After generating the target service, to enable users of the data service platform to invoke the created target service, the triggering method for the created target service can be either manual or system-triggered. Specifically, the data service platform can provide manual and system triggering entry points. The manual triggering entry point is used for users to provide an interface so that users can actively invoke the created target service. The system triggering entry point is used to obtain the task results of upstream tasks. When the task results meet preset conditions, the target service can be automatically triggered based on the task results to perform corresponding data processing operations based on the target service. When the task results do not meet the preset conditions, the target service will not be triggered to perform corresponding data processing operations.

[0105] In addition, the data service platform can include multiple target services. After obtaining multiple target services, a scheduling strategy can be configured, and then scheduling operations can be performed on one or more target services based on the scheduling strategy. Similarly, the data service platform can include a version switching module, which can be used to update the versions of the created target services to achieve service upgrades or service updates.

[0106] After creating the target service, in order for users to call the target service provided in the data service platform, after establishing the corresponding target service based on the data tag, the indicator metadata of the data tag can be determined, and then the indicator metadata can be stored in the intermediate. This allows users of the data service platform to view the target services that the platform can provide, and to call and view any target service according to their needs. For example, users can schedule and update the target service through the data update scheduling interface, update the data corresponding to the target service through the real-time data update interface, and perform data query operations through the data query interface, etc.

[0107] Furthermore, after obtaining the data tags and their corresponding target services, these tags and services can be stored in a pre-defined database. Specifically, if the target service is a public service, it can be publicly stored; if it is a private service, it can be privately stored. Similarly, users can manage and maintain the stored target services as needed, such as performing service rate limiting, service detection, service authentication, multi-level storage, and service adaptation. During management and maintenance, service management and maintenance logs can be obtained and stored on a cloud server, allowing users to view the management and maintenance operations performed on the target service. If an anomaly occurs in the target service, service alarm information can be generated and displayed.

[0108] The data service platform provided in this embodiment enables data service provision in a self-service manner, effectively automating data service operations. Since no collaborative operation is required during the data service provision process, the delivery time is effectively shortened, and the delivery efficiency of the target service is improved. On the one hand, this data service platform allows for greater data openness, effectively reducing data dependence on technology, fully leveraging application innovation potential, and building enterprise-level data asset operation capabilities. On the other hand, this data service platform can complete a unified data service production / access process, achieving full automation. Furthermore, it can achieve a unified data tag service management and governance system, as well as unified scheduling and resource optimization. Specifically, data synchronization tasks ensure data service stability and allow for periodic cleanup of data tags and related data, further enhancing the practicality of the data service platform and facilitating market promotion and application.

[0109] The following detailed description of some embodiments of the present invention is provided in conjunction with the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0110] Figure 7 A schematic diagram illustrating the principle of a data service method provided in an embodiment of this application; Figure 8 A flowchart illustrating a data service method provided in this application embodiment; see attached document. Figures 7-8As shown, this embodiment provides a data service approach that enables fully automated service production operations. The execution entity of this method is a data service device, which can be implemented as software or a combination of software and hardware. When the data service device is implemented as hardware, it can specifically be various electronic devices with data service capabilities. When the data service device is implemented as software, it can be installed in the aforementioned electronic devices.

[0111] This data service device can be implemented as a local server or a cloud server. In this case, the data service method can be executed in the cloud, where several computing nodes (cloud servers) can be deployed. Each computing node has processing resources such as computing and storage. In the cloud, multiple computing nodes can be organized to provide a certain service; of course, a single computing node can also provide one or more services. The cloud provides this service by providing an external service interface, which users call to use the corresponding service. Service interfaces include Software Development Kits (SDKs), Application Programming Interfaces (APIs), etc. In terms of physical implementation, the data service device can be any device capable of providing computing services, responding to service creation requests, and performing data service operations based on those requests. Examples include cluster servers, regular servers, cloud servers, cloud hosts, virtual data centers, etc. The data service device mainly consists of a processor, hard drive, memory, system bus, etc., similar to a general computer architecture.

[0112] The data service device communicates with a client, which can be any computing device with a certain data transmission capability. Specifically, the client can be a mobile phone, a personal computer (PC), a tablet computer, a configuration application, etc. Furthermore, the basic structure of the client can include at least one processor. The number of processors depends on the client's configuration and type. The client can also include memory, which can be volatile, such as Random Access Memory (RAM), or non-volatile, such as Read-Only Memory (ROM), flash memory, etc., or both types. The memory typically stores the operating system (OS), one or more applications, and may also store program data. In addition to the processing unit and memory, the client also includes some basic configurations, such as a network interface card (NIC) chip, an I / O bus, a display component, and some peripheral devices. Optionally, some peripheral devices may include, for example, a keyboard, a mouse, a stylus, a printer, etc. Other peripheral devices are well known in the art and will not be described in detail here.

[0113] In the above embodiment, the data service device establishes a network connection with the client, which can be a wireless or wired network connection. If the data service device can establish a communication connection with the client, the mobile network standard can be any one of 2G (GSM), 2.5G (GPRS), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4G+ (LTE+), WiMax, 5G, 6G, etc. Specifically, the data service method may include:

[0114] Step S801: Obtain the service creation request corresponding to the data tag.

[0115] Step S802: Based on the service creation request, determine the data source of the data tag and the destination address used to implement data service.

[0116] Step S803: Perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0117] The specific implementation process and effects of each of the above steps are explained in detail below:

[0118] Step S801: Obtain the service creation request corresponding to the data tag.

[0119] The data service device can be configured with one or more data tags. These tags can include default tags provided by the data service device or personalized tags configured by the user. For example, data tags can include at least one of the following: "Number of paying buyers in the last 90 days," "Payment amount in the last 90 days," "Number of paying buyers in the last 7 days," etc. It is important to note that data tags can include not only tag identifiers, Chinese names, creation times, value types, indicator logic, and timeliness, but also corresponding service resources, scenario domains, data source types, value types, tag dimensions, and indicator & engine mappings, etc.

[0120] Specifically, when users create or edit data tags according to their needs, the process can include the following steps: obtaining a tag configuration page; the tag configuration personnel inputting tag creation or tag editing operations on the tag configuration page; creating tags based on the tag creation operation; and editing tags based on the tag editing operation, thereby effectively realizing the tag creation or tag editing operation and obtaining a tag draft. To ensure that the data tags provided by the data service device meet preset legal and reasonable requirements, after obtaining the tag draft, tag approvers can approve the tag draft. If the tag draft passes the approval process, it can be published; if the tag draft fails the approval process, publishing the tag is prohibited. This effectively ensures the legality and reasonableness of data tag publication.

[0121] In addition, for the data tags configured in the data service device, they are divided into data tags with created services and data tags without created services, depending on whether the data tag corresponds to a corresponding tag service. For data tags with created services, users can directly call the created service corresponding to the data tag; for data tags without created services, users can perform service creation operations on the data tag.

[0122] When a user has a service creation requirement for a data tag, the data service device can obtain the service creation request corresponding to the data tag. In some instances, the service creation request can be obtained through human-computer interaction. In this case, obtaining the service creation request corresponding to the data tag may include: displaying an interactive interface corresponding to the data tag, the interactive interface including a service application control for implementing data service; obtaining the execution operation input by the user on the service application control; and determining the service creation request corresponding to the data tag based on the execution operation, the service creation request may include the tag identifier of the data tag.

[0123] In other instances, service creation requests can be obtained not only through human-computer interaction but also through a third device. In this case, the third device, which is connected to the data service device, can store the service creation request. The data service device can then actively or passively obtain the service creation request corresponding to the data tag through the third device.

[0124] Step S802: Based on the service creation request, determine the data source of the data tag and the destination address used to implement data service.

[0125] Because data service operations are related to the data source of data tags, and different data sources correspond to different service generation methods, the data source of the data tag can be determined based on the service creation request. The data source of the data tag can include a preset public data source or a user-created personalized data source. When the data source of the data tag is a preset public data source, the public data source can be stored in a preset cloud or on a preset server, thus determining that the data service operation provided by the data service device is a centralized service operation. When the data source of the data tag is a user-created personalized data source, the personalized data source can be stored locally on the user's device, thus determining that the data service operation provided by the data service device is a decentralized service operation.

[0126] Specifically, the data source for data tags can be obtained through human-computer interaction. In this case, determining the data source for data tags based on the service creation request may include: displaying the data source configuration page based on the service creation request; obtaining the data source configuration operations entered by the user on the data source configuration page; and obtaining the data source for data tags based on the data source configuration operations. In other instances, the data source for data tags can be a default data source. In this case, determining the data source for data tags based on the service creation request may include: determining the default data source for data tags based on the service creation request; and setting the default data source as the data source for data tags.

[0127] Furthermore, since data service-oriented operations are used to transform data into corresponding target services, data synchronization is required during the data service-oriented process. Specifically, data can be synchronized to a preset address to achieve stable data service-oriented operations. After receiving a service creation request, not only can the data source of the data tag be determined based on the service creation request, but also the destination address used to implement data service-oriented operations can be determined. This destination address can be obtained based on user input. It should be noted that the data source of the data tag and the destination address used to implement data service-oriented operations can be obtained synchronously or asynchronously. Those skilled in the art can configure the method of determining the data source and destination address according to the specific application scenario.

[0128] Step S803: Perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0129] After obtaining the data source and destination address, data service processing operations can be performed based on the data source and destination address to obtain the target service corresponding to the data tag. One data tag can correspond to one target service, and different data tags correspond to different target services. For example, the data tag "Number of paying buyers in the last 90 days" can correspond to the "Calculation service for the number of paying buyers in the last 90 days," the data tag "Payment amount in the last 90 days" can correspond to the "Calculation service for the payment amount in the last 90 days," and the data tag "Number of paying buyers in the last 7 days" can correspond to the "Calculation service for the number of paying buyers in the last 7 days."

[0130] Furthermore, this embodiment does not limit the specific method of obtaining the target service. In some instances, the target service can be obtained by processing the data source and destination address through a pre-trained machine learning model or neural network model. In this case, data service processing based on the data source and destination address to obtain the target service corresponding to the data label may include: obtaining a pre-trained machine learning model or neural network model; inputting the data source and destination address into the machine learning model or neural network model to obtain the target service corresponding to the data label output by the machine learning model or neural network model.

[0131] In other instances, the target service can be obtained not only by processing the data source and destination address through a pre-trained machine learning model or neural network model, but also by establishing a corresponding target service based on data synchronization operations. In this case, data service processing based on the data source and destination address to obtain the target service corresponding to the data label can include: generating a data synchronization task based on the data source and destination address; synchronizing the data source to the destination address based on the data synchronization task to obtain the target service corresponding to the data label.

[0132] After obtaining the data source and destination address, a data synchronization task can be generated based on these two parameters. This task then synchronizes the data source to the destination address to obtain the target service corresponding to the data tag. Since different data sources may have different data synchronization processes, when the data source is a preset standard data source, the data source and its corresponding data tag can be obtained first. Then, the data source and data tag are standardized to obtain standard data. A data synchronization task can then be generated based on this standardized data. After generating the task, the data source can be synchronized to the destination address, allowing the target service corresponding to the data tag to be obtained during the data service processing. Alternatively, if the data source is not a preset standard data source, the data source with the data tag can be obtained through a preset interface. A data synchronization task can then be generated based on this data source, synchronizing the data source to the destination address. This allows the target service corresponding to the data tag to be obtained during the data service processing.

[0133] In some other instances, to improve the practicality of the method, after obtaining the target service corresponding to the data tag, the method in this embodiment can also implement a unified data service access process to achieve full service automation. In this case, the method in this embodiment may include: obtaining a service call request; determining the associated application and application purpose corresponding to the target service based on the service call request; and providing the target service to the user through the associated application, wherein the target service corresponds to the application purpose.

[0134] After generating the target service corresponding to the data tag, the user can perform a service call operation on the generated target service. When the user has a service call requirement, the data service device can obtain the service call request. This service call request can be obtained through human-computer interaction input by the user, or it can be obtained automatically through a preset service call cycle. The obtained service call request can include the identifier of the service to be called. After obtaining the service call request, the associated application and application purpose corresponding to the target service can be determined based on the service call request. The associated application corresponding to the target service is used to identify the calling application corresponding to the target service, and the application purpose is used to identify the application scenario of the target service.

[0135] Specifically, this embodiment does not limit the specific method for determining the associated application and the application purpose. In some instances, the associated application and the application purpose can be obtained through user-input interactive operations. In this case, after obtaining the service call request, a service configuration page can be displayed to obtain the execution operation entered by the user on the service configuration page. Based on the execution operation, the associated application and the application purpose corresponding to the target service are determined. The associated application can be the application's name information, link information, etc., and the application purpose can be textual description information. In other instances, the associated application and the application purpose can be obtained through the user's selection operation in the alternative applications and alternative selection process. In this case, determining the associated application and the application purpose corresponding to the target service based on the service call request can include: determining multiple alternative applications and alternative purposes corresponding to the target service based on the service call request; obtaining the selection operation entered by the user in the multiple alternative applications and alternative selection process to obtain the associated application and the application purpose corresponding to the target service, thereby effectively ensuring the accuracy and reliability of determining the associated application and the application purpose. After obtaining the associated application, the target service can be provided to the user through the associated application. At this time, the target service corresponds to the application purpose, thus effectively ensuring that the generated target service can meet the user's needs.

[0136] To further improve the practicality of this method, the method in this embodiment can establish a full-link lineage relationship for data tags so as to manage data tags based on the established full-link lineage relationship. In this case, the method in this embodiment may also include: obtaining the data source corresponding to the data tag; determining the application purpose of the target service; and associating and storing the data tag, target service, data source, and application purpose.

[0137] Specifically, when establishing a corresponding target service for a data tag, the data source corresponding to the data tag can be obtained. This data source can include public data sources and private data sources. In order to further realize the management and operation of data tags and target services, after establishing the target service corresponding to the data tag, the application purpose of the target service can be determined. The application purpose is used to identify the application scenario corresponding to the target service, such as e-commerce scenario, conference scenario, data statistics scenario, etc. The application purpose can be determined through human-computer interaction.

[0138] After obtaining the data tag, target service, data source, and application purpose, the data tag, target service, data source, and application purpose can be associated and stored, thereby establishing a full-link lineage corresponding to the data tag (from data source -> data tag -> target service -> application purpose). Then, it is convenient to manage and operate the data tag or target service based on the established full-link lineage, which further improves the practicality of the method.

[0139] The data service-oriented method provided in this embodiment obtains a service creation request corresponding to a data tag, determines the data source of the data tag and the destination address for implementing data service-oriented operations based on the service creation request, and performs data service-oriented processing based on the data source and destination address to obtain the target service corresponding to the data tag. This effectively realizes automated data service-oriented operations. Since no collaborative operation is required during the data service-oriented process, the delivery time of data service-oriented operations is effectively shortened, and the delivery efficiency of the target service is improved. This further ensures the quality and efficiency of data service-oriented operations, and also improves the practicality of the method, which is conducive to market promotion and application.

[0140] Figure 9 A flowchart illustrating another data service method provided in this application embodiment; based on the above embodiments, please continue to refer to the appendix. Figure 9 As shown, the method in this embodiment can not only realize data service operations, but also realize unified management operations of data tags and related target services provided by the data service device. In this case, the method in this embodiment may further include:

[0141] Step S901: Obtain the tag management request corresponding to the data tag.

[0142] In order to further improve the practicality of the data service device, users can manage the data tags in the data service device according to their needs. At this time, the data service device can obtain the tag management request corresponding to the data tag. The specific method of obtaining the tag management request is similar to the specific method of obtaining the service call request. For details, please refer to the above description, which will not be repeated here.

[0143] Furthermore, different application scenarios may correspond to different tag management requests. In some instances, tag management requests can be implemented as standardization requests. These standardization requests are used to standardize all data tags provided by the data service device to obtain processed tags, where any two processed tags represent different meanings. In other instances, tag management requests can be implemented as replacement requests. These replacement requests are used to replace, delete, or deactivate data tags, etc.

[0144] Step S902: Perform unified management of data tags based on tag management requests.

[0145] After receiving a tag management request, the data tags provided in the data service device can be uniformly managed based on the tag management request. In some instances, uniform management of data tags based on the tag management request may include: when the tag management request is a standardization request, standardizing the data tags based on the standardization request to obtain processed tags, wherein any two processed tags are different; and / or, when the tag management request is a replacement request, replacing the data tags based on the replacement request.

[0146] Specifically, the data service device can store multiple data tags in different forms. These different data tags can correspond to different data sources. Since different data sources may have different expressions and formats, the different data tags stored in the data service device may correspond to the same meaning. For example, the data tag "payment amount within the last 60 days" and the data tag "payment amount within the last two months" have different expressions but correspond to the same meaning. To avoid storing multiple different data tags with the same meaning in the data service device, which would not only increase tag space usage but also make it more difficult to statistically analyze data tag usage, the data service device in this embodiment can standardize the data tags. After standardization, any two processed tags will be different, effectively reducing the difficulty of statistically analyzing data tag usage and increasing the quality and efficiency of data service.

[0147] In addition to standardizing data tags, it can also replace data tags based on their usage. In some instances, data tags can be replaced based on their usage volume. In this case, replacing data tags based on replacement requests can include: obtaining the usage volume of the tag corresponding to the data tag; and when the usage volume is less than or equal to a preset threshold, then performing silent or offline processing on the target service corresponding to the data tag, or on both the target service and the data tag, based on the replacement request.

[0148] Specifically, when a user invokes a data tag according to their needs, the data service device can obtain the tag invocation volume (also known as service invocation volume) corresponding to the data tag. This tag invocation volume is used to identify the number of times the data tag is invoked within a preset time period. After obtaining the tag invocation volume corresponding to the data tag, the tag invocation volume can be analyzed and compared with a preset threshold. If the tag invocation volume is less than or equal to the preset threshold, it indicates that the data tag is invoked less frequently within the preset time period, which means that the user has less demand for the data tag or the target service corresponding to the data tag. Therefore, based on the replacement request, the target service corresponding to the data tag, or the target service corresponding to the data tag and the data tag, can be silently or taken offline.

[0149] Before taking a data tag offline based on a replacement request, or taking both the target service and the data tag offline, a shutdown reminder message can be generated to ensure that the tag administrator is aware of the current status of the data tag. This reminder message can then be sent to the tag administrator via a pre-defined application or email address. This allows the tag administrator to manage the data tag based on the shutdown reminder message, such as keeping the data tag online or allowing it to be taken offline.

[0150] Specifically, when the number of calls to a tag is less than or equal to a preset threshold, the target service corresponding to the data tag can be silently processed based on a replacement request. Then, the service call volume within a preset time period after the silent processing is counted. If the service call volume is less than or equal to the preset call threshold, the target service can be taken offline. If the service call volume is greater than the preset call threshold, the target service can be brought back online. Alternatively, when the number of calls to a tag is less than or equal to the preset threshold, both the target service and the data tag corresponding to the data tag can be silently processed based on a replacement request. Then, the service call volume within a preset time period after the silent processing is counted. If the service call volume is less than or equal to the preset call threshold, both the target service and the data tag can be taken offline. If the service call volume is greater than the preset call threshold, both the data tag and the target service can be brought back online based on a replacement request.

[0151] In other instances, data tags can be replaced not only based on the number of times they are called, but also based on their lifecycle. In this case, replacing data tags based on a replacement request can include: obtaining the lifecycle corresponding to the data tag; and taking the data tag offline when its lifecycle expires based on the replacement request.

[0152] When the data service device acquires a data tag, the user can configure the data tag's lifecycle according to their needs. Different lifecycles correspond to data tags with different effective durations. Therefore, when the data service device obtains a data tag, it can acquire the corresponding lifecycle, which can be pre-configured or pre-adjusted by the user based on their needs. After acquiring the lifecycle corresponding to the data tag, the data tag can be managed based on its lifecycle. Specifically, when a data tag reaches the end of its lifecycle, it can be deactivated based on a replacement request.

[0153] For example, when a user configures a tag through a data service device and obtains a data tag, the lifecycle of the data tag can be configured simultaneously. Then, when performing data service operations through data service transposition, the lifecycle corresponding to the data tag can be obtained in real time. This lifecycle can be a preset 30 days, 60 days, 90 days, or 1 year, etc. The existence time of the data tag can then be determined. Specifically, the existence time of the data tag can be determined by the tag creation time and the current time. When the existence time reaches the lifecycle, it means that the use of the data tag has reached the duration requirement, and the data tag can be taken offline based on a replacement request. For example, when the existence time of the data tag reaches the preset 30 days, the data tag can be automatically taken offline.

[0154] In some other instances, data tags can be replaced not only based on their usage volume and lifecycle, but also based on their cost and value. In this case, replacing data tags based on a replacement request can include: obtaining the tag cost and value corresponding to the data tag; if the tag cost is greater than or equal to a preset cost and the tag value is less than a preset value, then generating tag management information corresponding to the data tag based on the replacement request and sending the tag management information to the tag producer so that the tag producer can manage the data tag based on the tag management information.

[0155] In the context of data tags in data service devices, there are often tag configuration costs or tag generation costs when configuring or generating data tags. Data tags with different configuration or generation costs may correspond to different tag invocation values. To further ensure the quality and efficiency of data tag management, the tag cost and tag value corresponding to the data tag can be obtained. In some instances, the tag cost corresponding to the data tag is related to the computational or storage requirements of the data tag. In this case, obtaining the tag cost corresponding to the data tag can include: obtaining the computational or storage requirements corresponding to the data tag; and determining the tag cost corresponding to the data tag based on the computational or storage requirements. The higher the computational or storage requirements of the data tag, the higher the tag cost, and vice versa.

[0156] In some other instances, the tag cost corresponding to a data tag can be related to the computational and storage requirements of the data tag. In this case, obtaining the tag cost corresponding to a data tag may include: obtaining the computational and storage requirements corresponding to the data tag; determining the tag cost corresponding to the data tag based on the computational and storage requirements. Specifically, the greater the computational and storage requirements, the higher the tag cost of the data tag; the smaller the computational and storage requirements, the lower the tag cost of the data tag.

[0157] In order to effectively manage data tags, the tag value corresponding to the data tag can be obtained. The tag value can be related to the number of times the data tag is called. In this case, obtaining the tag value corresponding to the data tag can include: obtaining the number of times the tag is called; and determining the tag value corresponding to the data tag based on the number of times the tag is called. The higher the number of times the tag is called, the higher the tag value, and vice versa.

[0158] After obtaining the tag cost and tag value, the tag cost can be analyzed and compared with the preset cost, and the tag value can be analyzed and compared with the preset value. When the tag cost is greater than or equal to the preset cost, and the tag value is less than the preset value, it indicates that the generation cost of the data tag is high and the application value is low. At this time, tag management information corresponding to the data tag can be generated based on the replacement request. The tag management information is used to remind the tag producer whether to take the data tag offline or silent. In order to enable the tag producer to manage the data tag in a timely manner, the tag management information can be sent to the tag producer. Specifically, the tag management information can be sent to the tag producer through a preset application or a preset email address. This allows the tag producer to perform stable and effective management operations on the data tag based on the tag management information.

[0159] In this embodiment, by obtaining the tag management request corresponding to the data tag, and then managing the data tag in a unified manner based on the tag management request, the method effectively realizes the flexible and automatic strict replacement operation of the data tag based on its usage status, thereby ensuring the quality and efficiency of data tag management and further improving the practicality of the method.

[0160] Figure 10 A flowchart illustrating another data service method provided in this application embodiment; based on the above embodiments, refer to the appendix. Figure 10 As shown, after obtaining the target service corresponding to the data tag, this embodiment can also implement a scheme for storing the tag metadata corresponding to the data tag. In this case, the method in this embodiment may further include:

[0161] Step S1001: Obtain the tag metadata corresponding to the data tag.

[0162] After obtaining the target service corresponding to the data tag, in order to enable users of the data service device to quickly and directly understand the target service that the data service device can provide, the tag metadata corresponding to the data tag can be obtained. In some instances, there is a mapping relationship between the data tag and the tag metadata. After obtaining the data tag, the tag metadata corresponding to the data tag can be determined based on the mapping relationship. The tag metadata is used to identify the relevant tag features of the data tag.

[0163] Step S1002: Determine the data storage format corresponding to the tag metadata.

[0164] After obtaining the tag metadata, in order to accurately and stably store the tag data and related data, a data storage format corresponding to the tag metadata can be determined. This data storage format can be pre-selected by the user or pre-configured. The data storage format can include at least one of the following: KKV format or KV format. In the KKV format, the first K is used to identify the "KEY" as the primary key, for example, K can be user_id, item_id, member_id, etc. The second K is used to identify the "KEY" as the table name, which is used to identify the data source name of the service, and V (Value) is used to identify the "metric name". Similarly, in the KV format, the K is used to identify the "KEY" as the table name, which is used to identify the data source name of the service, and V (Value) is used to identify the "metric name". It should be noted that both the KKV and KV formats mentioned above can follow OneData's naming conventions.

[0165] Step S1003: Store the tag metadata based on the data storage format so that users can know the target service corresponding to the data tag based on the stored tag metadata.

[0166] After obtaining the data storage format, the tag metadata can be stored based on the data storage format, thereby realizing the public storage of the target service corresponding to the data tag on the data service device. This allows users to know the target service corresponding to the data tag based on the stored tag metadata, and to call or view the target service as needed.

[0167] To save on data storage costs and improve storage efficiency when storing tag metadata, data tags can be stored in conjunction with their lifecycle. In this case, storing tag metadata based on the data storage format can include: determining the lifecycle of the data tag; and storing the data tag in separate databases and tables based on the lifecycle and data storage format.

[0168] After obtaining the data tags, they can be analyzed and processed to determine their lifecycle. This lifecycle can be pre-configured or determined based on user interaction. After obtaining the data tag lifecycle, the data tags can be sharded and stored in separate databases and tables based on the lifecycle and data storage format. This can effectively improve data storage quality and efficiency.

[0169] In other instances, to further improve the practicality of the method, the method in this embodiment may also include performing table storage operations on the relevant data of the stored target service. In this case, the method in this embodiment may also include: obtaining the periodic change request of the target service; determining the updated lifecycle corresponding to the periodic change request; and generating an update data table corresponding to the target service when the updated lifecycle is longer than the pre-update lifecycle, and writing the data corresponding to the target service into the update data table.

[0170] Specifically, after obtaining the target service corresponding to the data tag and storing the data tag in sharded databases and tables based on its lifecycle and data storage format, users can update the lifecycle of the data table corresponding to the target service as needed. At this point, the periodic change request for the target service can be obtained. After obtaining the periodic change request, the updated lifecycle corresponding to the periodic change request can be determined. In some instances, the periodic change request may include the updated lifecycle; in this case, the updated lifecycle can be obtained by extracting information from the periodic change request. Alternatively, in some instances, the periodic change request may correspond to a periodic change page, and the user's input on the periodic change page can be obtained. Based on the input, the updated lifecycle corresponding to the periodic change request can be determined.

[0171] It is important to note that the lifecycle after the update is different from the lifecycle before the update. When the lifecycle after the update is longer than the lifecycle before the update, the lifecycle of a data table can be upgraded from a low lifecycle to a high lifecycle; when the lifecycle after the update is shorter than the lifecycle before the update, the lifecycle of a data table can be downgraded from a high lifecycle to a low lifecycle.

[0172] When the lifecycle after an update is longer than the lifecycle before the update, in order to achieve data synchronization, an updated data table corresponding to the target service can be generated. This updated data table corresponds to the lifecycle after the update. To achieve data synchronization, writing relevant data for the target service to the old table can be stopped, and data can be written to the updated data table instead. This effectively synchronizes and updates the relevant data for the target service to the updated data table. In some instances, not only can the relevant data for the target service be synchronized and updated to the updated data table, but the routing information corresponding to the target service can also be updated, thus effectively ensuring the stable operation of data service-oriented architecture.

[0173] In this embodiment, by acquiring the tag metadata corresponding to the data tag, determining the data storage format corresponding to the tag metadata, and then storing the tag metadata based on the data storage format, the user can learn about the target service corresponding to the data tag based on the stored tag metadata. This effectively enables the user to view and call various target services that can be provided through the data service device, thus further improving the practicality of the method.

[0174] Figure 11 A flowchart illustrating another data service method provided in this application embodiment; see attached diagram. Figure 11As shown, this embodiment provides another data service method that can realize fully automated service production operations. The execution subject of this method is a data service device, which can be implemented as software or a combination of software and hardware. When the data service device is implemented as hardware, it can specifically be various electronic devices with data service capabilities. When the data service device is implemented as software, it can be installed in the aforementioned electronic devices. Specifically, this data service method may include:

[0175] Step S1101: Display the operation page for implementing data service. The operation page includes multiple data tags and application service controls corresponding to each data tag. The application service controls are used to implement service creation operations.

[0176] For details regarding the content and format of the operation page, please refer to the appendix. Figure 4 As shown, the operation page can include not only the application service control, but also the "details" control, "share" control, etc. In this embodiment, the operation page can be displayed by the user's input of the start operation of the preset program, which is used to implement data service operation.

[0177] Step S1102: Obtain the execution operation entered by the user for any application service control on the operation page;

[0178] Step S1103: Based on the executed operation, display the service configuration page;

[0179] Step S1104: Obtain the data source for the data tags and the destination address for implementing data service through the service configuration page;

[0180] Step S1105: Perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0181] In this embodiment, the specific implementation method, effect, and principle of the above steps are the same as those described above. Figure 8 The specific implementation methods, effects, and principles of each step in the illustrated embodiments are similar. Please refer to the above description for details, which will not be repeated here.

[0182] It should be noted that the method in this embodiment may also include Figures 3-10 For the methods shown in the embodiments, parts not described in detail in this embodiment can be referred to the following: Figures 3-10 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figures 3-10 The descriptions in the illustrated embodiments will not be repeated here.

[0183] Figure 12A flowchart illustrating another data service method provided in this application embodiment; see attached diagram. Figure 12 As shown, this embodiment provides another data service approach that can achieve fully automated service production operations. The execution entity of this method is a data service device, which can be implemented as software or a combination of software and hardware. When the data service device is implemented as hardware, it can specifically be various electronic devices with data service capabilities. When the data service device is implemented as software, it can be installed in the aforementioned electronic devices. In some instances, the data service device can be implemented as a cloud server, in which case the data service approach can be applied to the cloud server. Specifically, the data service approach may include:

[0184] Step S1201: In response to the data service request to the cloud server, determine the processing resources corresponding to the data service.

[0185] Step S1202: Utilize processing resources to perform the following steps: obtain a service creation request corresponding to the data tag; based on the service creation request, determine the data source of the data tag and the destination address for implementing data service; perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0186] Specifically, the data service method provided by this invention can be executed in the cloud, where multiple computing nodes can be deployed, each with processing resources such as computing and storage. In the cloud, multiple computing nodes can be organized to provide a certain service; of course, a single computing node can also provide one or more services.

[0187] According to the solution provided by this invention, the cloud can provide a service for completing the data service-oriented method, referred to as the data service-oriented service. When a user needs to use the data service-oriented service, they invoke the data service-oriented service to trigger a request to the cloud to invoke the data service-oriented service. The cloud determines the computing node that responds to the request and uses the processing resources in the computing node to perform the following steps: obtaining a service creation request corresponding to the data tag; based on the service creation request, determining the data source of the data tag and the destination address for implementing data service-oriented processing; performing data service-oriented processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0188] Specifically, the implementation process, implementation principle, and implementation effect of the above method steps in this embodiment are the same as those described above. Figures 3-10 The implementation process, principle, and effect of the method steps in the illustrated embodiment are similar. For parts not described in detail in this embodiment, please refer to the [examples provided]. Figures 3-10 The following is a description of the illustrated embodiment.

[0189] Figure 13 A schematic diagram of a data service device provided in an embodiment of this application; see attached diagram. Figure 13 As shown, this embodiment provides a data service apparatus, which is used to perform the above-described... Figure 8 The data service method shown may include:

[0190] The first acquisition module 11 is used to acquire the service creation request corresponding to the data tag;

[0191] The first determining module 12 is used to determine the data source of the data tag and the destination address for implementing data service based on the service creation request;

[0192] The first processing module 13 is used to perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0193] In some instances, when the first processing module 13 performs data service processing based on the data source and destination address to obtain the target service corresponding to the data tag, the first processing module 13 is used to perform: generating a data synchronization task based on the data source and destination address; synchronizing the data source to the destination address based on the data synchronization task to obtain the target service corresponding to the data tag.

[0194] In some instances, after obtaining the target service corresponding to the data tag, the first acquisition module 11, the first determination module 12, and the first processing module 13 in this embodiment are used to perform the following steps:

[0195] The first acquisition module 11 is used to acquire service call requests;

[0196] The first determining module 12 is used to determine the associated application and application purpose corresponding to the target service based on the service call request;

[0197] The first processing module 13 is used to provide the target service to the user through the associated application, wherein the target service corresponds to the purpose of the application.

[0198] In some instances, the first acquisition module 11 and the first processing module 13 in this embodiment are used to perform the following steps:

[0199] The first acquisition module 11 is used to acquire a tag management request corresponding to a data tag;

[0200] The first processing module 13 is used to uniformly manage data tags based on tag management requests.

[0201] In some instances, when the first processing module 13 performs unified management of data tags based on a tag management request, the first processing module 13 is used to perform: when the tag management request is a standardization request, perform standardization processing on the data tags based on the standardization request to obtain processed tags, wherein any two processed tags are different; and / or, when the tag management request is a replacement request, perform replacement processing on the data tags based on the replacement request.

[0202] In some instances, when the first processing module 13 performs replacement processing on the data tag based on the replacement request, the first processing module 13 is used to perform: obtaining the tag call volume corresponding to the data tag; when the tag call volume is less than or equal to a preset threshold, then performing silent or offline processing on the target service corresponding to the data tag, or the target service corresponding to the data tag and the data tag, based on the replacement request.

[0203] In some instances, when the first processing module 13 performs replacement processing on the data tag based on the replacement request, the first processing module 13 is used to perform: obtaining the lifecycle corresponding to the data tag; and when the existence time of the data tag reaches the lifecycle, performing offline processing on the data tag based on the replacement request.

[0204] In some instances, when the first processing module 13 performs replacement processing on the data tag based on the replacement request, the first processing module 13 is used to perform: obtaining the tag cost and tag value corresponding to the data tag; when the tag cost is greater than or equal to the preset cost and the tag value is less than the preset value, generating tag management information corresponding to the data tag based on the replacement request, and sending the tag management information to the tag producer so that the tag producer can manage the data tag based on the tag management information.

[0205] In some instances, the first acquisition module 11, the first determination module 12, and the first processing module 13 in this embodiment are used to perform the following steps:

[0206] The first acquisition module 11 is used to acquire the data source corresponding to the data label;

[0207] The first determining module 12 is used to determine the intended use of the target service;

[0208] The first processing module 13 is used to associate and store data tags, target services, data sources, and application purposes.

[0209] In some instances, after obtaining the target service corresponding to the data tag, the first acquisition module 11, the first determination module 12, and the first processing module 13 in this embodiment are used to perform the following steps:

[0210] The first acquisition module 11 is used to acquire tag metadata corresponding to the data tag;

[0211] The first determining module 12 is used to determine the data storage format corresponding to the tag metadata;

[0212] The first processing module 13 is used to store tag metadata based on the data storage format, so that users can know the target service corresponding to the data tag based on the stored tag metadata.

[0213] In some instances, when the first processing module 13 stores tag metadata based on the data storage format, the first processing module 13 is used to perform: determining the lifecycle of the data tag; and storing the data tag in separate databases and tables based on the lifecycle and the data storage format.

[0214] In some instances, the first acquisition module 11, the first determination module 12, and the first processing module 13 in this embodiment are used to perform the following steps:

[0215] The first acquisition module 11 is used to acquire the periodic change request of the target service;

[0216] The first determining module 12 is used to determine the updated lifecycle corresponding to the periodic change request;

[0217] The first processing module 13 is used to generate an update data table corresponding to the target service and write the data corresponding to the target service into the update data table when the life cycle after the update is longer than the life cycle before the update.

[0218] Figure 13 The data service device shown can perform Figures 3-10 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figures 3-10 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figures 3-10 The descriptions in the illustrated embodiments will not be repeated here.

[0219] In one possible design, Figure 13 The structure of the data service device shown can be implemented as an electronic device. (See attached document.) Figure 14 As shown, the data service device in this embodiment can be implemented as an electronic device. In some instances, the electronic device can be implemented as a user terminal, personal computer, intelligent device, etc. Specifically, the electronic device may include a first processor 21 and a first memory 22. The first memory 22 is used to store the data executed by the corresponding electronic device. Figure 2 In the data service method program provided in the illustrated embodiment, the first processor 21 is configured to execute the program stored in the first memory 22.

[0220] The program includes one or more computer instructions, wherein when the one or more computer instructions are executed by the first processor 21, they can perform the following steps: obtain a service creation request corresponding to the data tag; determine the data source of the data tag and the destination address for implementing data service based on the service creation request; perform data service processing based on the data source and the destination address to obtain the target service corresponding to the data tag.

[0221] Furthermore, the first processor 21 is also used to perform the aforementioned Figure 8 All or part of the steps in the illustrated embodiments. The electronic device may also include a first communication interface 23 for communication between the electronic device and other devices or communication networks.

[0222] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by an electronic device, which includes instructions for executing the above-described... Figure 8 The program involved in the data service method in the illustrated embodiment.

[0223] Furthermore, embodiments of the present invention provide a computer program product, comprising: a computer program, which, when executed by a processor of an electronic device, causes the processor to perform... Figure 8 The data service method shown in the embodiment of the method.

[0224] Figure 15 This is a schematic diagram of another data service device provided in an embodiment of this application; see attached diagram. Figure 15 As shown, this embodiment provides a data service device that can perform the above-described... Figure 11 The data service method shown herein, specifically, the data service apparatus may include:

[0225] The second display module 31 is used to display an operation page for implementing data service. The operation page includes multiple data labels and application service controls corresponding to each data label. The application service controls are used to implement service creation operations.

[0226] The second acquisition module 32 is used to acquire the execution operation entered by the user for any application service control on the operation page.

[0227] The second display module 31 is used to display the service configuration page based on the executed operation.

[0228] The second acquisition module 32 is used to obtain the data source of the data tag and the destination address for implementing data service through the service configuration page.

[0229] The second processing module 33 is used to perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0230] Figure 15 The data service device shown can perform Figure 11 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 11 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 11 The descriptions in the illustrated embodiments will not be repeated here.

[0231] In one possible design, Figure 15 The structure of the data service device shown can be implemented as an electronic device. (See attached document.) Figure 16 As shown, the data service device in this embodiment can be implemented as an electronic device. In some instances, the electronic device can be implemented as a user terminal, personal computer, intelligent device, etc. Specifically, the electronic device may include: a second processor 41 and a second memory 42. The second memory 42 is used to store the data executed by the corresponding electronic device. Figure 11 In the data service method program provided in the illustrated embodiment, the second processor 41 is configured to execute the program stored in the second memory 42.

[0232] The program includes one or more computer instructions, wherein when executed by the second processor 41, the one or more computer instructions can perform the following steps: displaying an operation page for implementing data service, the operation page including multiple data tags and application service controls corresponding to each data tag, the application service controls being used to implement service creation operations; obtaining the execution operation input by the user for any application service control on the operation page; displaying a service configuration page based on the execution operation; obtaining the data source of the data tag and the destination address for implementing data service through the service configuration page; performing data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0233] Furthermore, the second processor 41 is also used to perform the aforementioned Figure 11 All or part of the steps in the illustrated embodiments. The electronic device may also include a second communication interface 43 for communication between the electronic device and other devices or communication networks.

[0234] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by an electronic device, which includes instructions for executing the above-described... Figure 11 The program involved in the data service method in the illustrated embodiment.

[0235] Furthermore, embodiments of the present invention provide a computer program product, comprising: a computer program, which, when executed by a processor of an electronic device, causes the processor to perform... Figure 11 The data service method shown in the embodiment of the method.

[0236] Figure 17 A schematic diagram of another data service device provided in this application embodiment; see attached drawing. Figure 17 As shown, this embodiment provides a data service device that can perform the above-described... Figure 12 The data service approach illustrated can be implemented in some instances using a data service device that can be applied to a cloud server; specifically, the data service device may include:

[0237] The third determining module 51 is used to determine the processing resources corresponding to the data service in response to the data service request to the cloud server.

[0238] The third processing module 52 is used to perform the following steps using processing resources: obtain a service creation request corresponding to the data tag; determine the data source of the data tag and the destination address for implementing data service based on the service creation request; perform data service processing based on the data source and destination address to obtain the target service corresponding to the data tag.

[0239] Figure 17 The data service device shown can perform Figure 12 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 12 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 12 The descriptions in the illustrated embodiments will not be repeated here.

[0240] In one possible design, Figure 17 The structure of the data service device shown can be implemented as an electronic device. (See attached document.) Figure 18 As shown, the data service device in this embodiment can be implemented as an electronic device. In some instances, the electronic device can be implemented as a user terminal, personal computer, intelligent device, etc. Specifically, the electronic device may include a third processor 61 and a third memory 62. The third memory 62 is used to store the data executed by the corresponding electronic device. Figure 12 In the data service method program provided in the illustrated embodiment, the third processor 61 is configured to execute the program stored in the third memory 62.

[0241] The program includes one or more computer instructions, wherein when executed by the third processor 61, the one or more computer instructions are capable of performing the following steps: in response to a data service request to the cloud server, determining the processing resources corresponding to the data service; using the processing resources to perform the following steps: obtaining a service creation request corresponding to the data tag; based on the service creation request, determining the data source of the data tag and the destination address for implementing the data service; performing data service processing based on the data source and the destination address to obtain the target service corresponding to the data tag.

[0242] Furthermore, the third processor 61 is also used to perform the aforementioned... Figure 12 All or part of the steps in the illustrated embodiments. The electronic device may also include a third communication interface 63 for communication between the electronic device and other devices or communication networks.

[0243] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by an electronic device, which includes instructions for executing the above-described... Figure 12 The program involved in the data service method in the illustrated embodiment.

[0244] Furthermore, embodiments of the present invention provide a computer program product, comprising: a computer program, which, when executed by a processor of an electronic device, causes the processor to perform... Figure 12 The data service method shown in the embodiment of the method.

[0245] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0246] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0247] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of a necessary general-purpose hardware platform, or by a combination of hardware and software. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a computer product. This application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0248] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will 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 program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable device, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0249] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0250] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, a network interface, and memory. Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0251] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store data using any method or technology. Data can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store data accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0252] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data service approach, characterized in that, include: Retrieve the service creation request corresponding to the data tag; Based on the service creation request, determine the data source of the data tag and the destination address for implementing data service; Based on the data source and destination address, data service processing is performed to obtain the target service corresponding to the data tag; The method further includes: Obtain the tag management request corresponding to the data tag; When the tag management request is a standardization request, the data tags are standardized based on the standardization request to obtain processed tags, wherein any two processed tags are different; and / or, When the tag management request is a replacement request, the data tag is replaced based on the replacement request.

2. The method according to claim 1, characterized in that, Based on the data source and destination address, data service processing is performed to obtain the target service corresponding to the data tag, including: A data synchronization task is generated based on the data source and the destination address; The data synchronization task synchronizes the data source to the destination address to obtain the target service corresponding to the data tag.

3. The method according to claim 1, characterized in that, After obtaining the target service corresponding to the data tag, the method further includes: Obtain the service call request; Based on the service call request, determine the associated application and the purpose of the application corresponding to the target service; The target service is provided to the user through the associated application, wherein the target service corresponds to the purpose of the application.

4. The method according to claim 1, characterized in that, The data tag is replaced based on the replacement request, including: Obtain the tag call count corresponding to the data tag; When the number of calls to the tag is less than or equal to a preset threshold, the target service corresponding to the data tag, or the target service corresponding to the data tag and the data tag, are either silenced or taken offline based on the replacement request.

5. The method according to claim 1, characterized in that, The data tag is replaced based on the replacement request, including: Obtain the lifecycle corresponding to the data tag; When the existence time of the data tag reaches the life cycle, the data tag is taken offline based on the replacement request.

6. The method according to claim 1, characterized in that, The data tag is replaced based on the replacement request, including: Obtain the tag cost and tag value corresponding to the data tag; When the cost of the tag is greater than or equal to the preset cost and the value of the tag is less than the preset value, tag management information corresponding to the data tag is generated based on the replacement request, and the tag management information is sent to the tag producer so that the tag producer can manage the data tag based on the tag management information.

7. The method according to claim 1, characterized in that, After obtaining the target service corresponding to the data tag, the method further includes: Obtain the tag metadata corresponding to the data tag; Determine the data storage format corresponding to the tag metadata; The tag metadata is stored based on the data storage format, so that users can know the target service corresponding to the data tag based on the stored tag metadata.

8. The method according to claim 7, characterized in that, The tag metadata is stored based on the data storage format, including: Determine the lifecycle of the data tag; The data tags are stored in separate databases and tables based on the lifecycle and data storage format.

9. The method according to claim 8, characterized in that, The method further includes: Obtain the periodic change request for the target service; Determine the updated lifecycle corresponding to the aforementioned periodic change request; If the lifecycle after the update is longer than the lifecycle before the update, an update data table corresponding to the target service is generated, and the data corresponding to the target service is written into the update data table.

10. A data service approach, characterized in that, include: The operation page is displayed to realize data service. The operation page includes multiple data tags and application service controls corresponding to each data tag. The application service controls are used to realize service creation operations. Get the action input by the user for any of the application service controls on the operation page; Based on the executed operation, the service configuration page is displayed; The data source for the data tag and the destination address for implementing data service can be obtained through the service configuration page. Based on the data source and destination address, data service processing is performed to obtain the target service corresponding to the data tag; The method further includes: Obtain a tag management request corresponding to the data tags included in the operation page; When the tag management request is a standardization request, the data tags are standardized based on the standardization request to obtain processed tags, wherein any two processed tags are different; and / or, When the tag management request is a replacement request, the data tag is replaced based on the replacement request.

11. A data service approach, characterized in that, Applied to cloud servers, the method includes: In response to a data service request to the cloud server, determine the processing resources corresponding to the data service. The following steps are performed using the processing resources: obtaining a service creation request corresponding to the data tag; determining the data source of the data tag and the destination address for implementing data service based on the service creation request; performing data service processing based on the data source and destination address to obtain the target service corresponding to the data tag; The processing resources also include the following steps: obtaining a tag management request corresponding to the data tag; when the tag management request is a standardization request, standardizing the data tag based on the standardization request to obtain a processed tag, wherein any two processed tags are different; and / or, when the tag management request is a replacement request, replacing the data tag based on the replacement request.

12. An electronic device, characterized in that, include: A memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the method as described in any one of claims 1-11.

Images