Data product system management method and device, equipment, medium and product

Abstract

The invention provides a management method and device of a data product system, equipment, a medium and a product. The method belongs to the technical field of data processing, and comprises the following steps: receiving a login request which comprises internal contact information; under the condition that login information matched with the internal contact information exists in a preset login database, a data product release request is obtained, and the data product release request comprises product information and interface information; the product information comprises a product name, a product type, a business field and an application scene; judging whether a data product which is the same as the information exists in a data product directory of the data product system and under a data product subdirectory corresponding to the product type; verifying whether an interface corresponding to the interface information is normally accessed or not under the condition that the data product which is the same as the information does not exist; and under the condition that the interface access is normal, the data product is put on shelf. The technical problem that the content and authority of the data product are difficult to manage in the related technology is solved.

Description

Technical Field

[0001] The present application belongs to the field of data processing technology, and in particular, relates to a management method, device, equipment, medium and product of a data product system. Background Art

[0002] With the rapid development of information technology, data has become an important basis for corporate decision-making and product innovation. Data products are services or solutions that use data science techniques and tools to transform raw data into meaningful information and insights.

[0003] Traditionally, data products exist in the form of local or online documents, which makes it difficult to manage the content and permissions of data products, resulting in inconvenience in using data products and reducing the user experience. Summary of the invention

[0004] The embodiments of the present application provide a management method, apparatus, device, storage medium and computer program product for a data product system to solve the technical problem in related technologies that it is difficult to manage the content and permissions of data products.

[0005] In a first aspect, an embodiment of the present application provides a method for managing a data product system, wherein the data product system displays a plurality of data products, and the method comprises:

[0006] receiving a login request from a first user, the login request including internal contact information of the first user, the first user being any one of a first category of users, the first category of users being used to represent providers of data products;

[0007] If there is login information matching the internal contact information in the preset login database, obtaining a data product publishing request of the first user, the data product publishing request including product information and interface information of the first data product; the product information includes a product name, product type, business field, and application scenario of the first data product;

[0008] Determine whether, in the data product directory of the data product system, under the data product subdirectory corresponding to the product type of the first data product, there is a data product with the same product name, business field, and application scenario as the first data product;

[0009] If there is no data product with the same product name, business field and application scenario as the first data product, verify whether the interface corresponding to the interface information is normally accessible;

[0010] When the interface access corresponding to the interface information is normal, the data product is put on the shelves in the data product system in response to the putting-on-shelf operation of the first user.

[0011] In a second aspect, an embodiment of the present application provides a management device for a data product system, the device comprising:

[0012] A receiving module, configured to receive a login request from a first user, wherein the login request includes internal contact information of the first user, wherein the first user is any one of a first category of users, and the first category of users is used to represent a provider of a data product;

[0013] an acquisition module, configured to acquire a data product release request of the first user if there is login information matching the internal contact information in a preset login database, the data product release request including product information and interface information of the first data product; the product information including a product name, product type, business field, and application scenario of the first data product;

[0014] A determination module, configured to determine whether, in a data product directory of the data product system, under a data product subdirectory corresponding to a product type of the first data product, there is a data product having the same product name, business field, and application scenario as the first data product;

[0015] A verification module, used to verify whether the interface corresponding to the interface information is normally accessible when there is no data product having the same product name, business field and application scenario as the first data product;

[0016] An execution module is used to put the data product on the data product system in response to a putting-on-shelf operation by the first user when the interface access corresponding to the interface information is normal.

[0017] In a third aspect, an embodiment of the present application provides an electronic device, the device comprising:

[0018] A processor and a memory storing programs or instructions;

[0019] The above method is implemented when the processor executes the program or instruction.

[0020] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored, and the program or instruction implements the above method when executed by a processor.

[0021] In a fifth aspect, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the above method.

[0022] In the embodiment of the present application, by publishing the data product on the data product system, and before publishing, determining whether the data product is a data product that already exists in the data product system, and verifying whether the interface of the data product can be accessed normally, it is ensured that the data products in the data product system are non-duplicate and available, and compared with data products stored locally or online, the management process of the data product is optimized, the data security of the data product is enhanced, and the management efficiency of the data product is improved. The technical problem of difficult management of data product content and permissions is solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0024] Figure 1 is a flow chart of a method for managing a data product system according to an embodiment of the present invention;

[0025] Figure 2 is a structural schematic diagram of a data product system according to an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of the overall process of a data product system management method according to an embodiment of the present invention;

[0027] Figure 4 is a flow chart of a data product trial method according to an embodiment of the present invention;

[0028] Figure 5 is a structural block diagram of a management device of a data product system according to an embodiment of the present invention;

[0029] Figure 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0030] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0031] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0032] In addition, it should be noted that the acquisition, storage, use, and processing of data in the embodiments of the present application comply with the relevant provisions of national laws and regulations.

[0033] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0034] In order to solve the technical problem in the prior art that it is difficult to manage the content and permissions of data products, an embodiment of the present application provides a management method for a data product system, which can be applied in a data product system to manage data products in the data product system. Figure 1 FIG. 1 is a flow chart of a method for managing a data product system according to an embodiment of the present invention. Figure 1 As shown, the management method of the data product system may include the following steps:

[0035] S110, receiving a login request from a first user, where the login request includes internal contact information of the first user, where the first user is any one of a first category of users, and the first category of users is used to represent a provider of a data product.

[0036] In S110, Figure 2 is a schematic diagram of the structure of a data product system according to an embodiment of the present invention. Figure 2 As shown, the data product system can be a management system that includes multiple data products and can visually display multiple data products; the data product system includes three roles, namely, the provider of data products, the manager of the data product system, and the user of data products.

[0037] The providers of the data product system are mainly responsible for creating, providing and managing data products. The managers of the data product system are mainly responsible for managing and reviewing the relevant requests of users and providers, and are responsible for the overall operation and management of the data product system to ensure the stability and security of the system. The users of the data product system are mainly responsible for viewing and using data products.

[0038] Internal contact information may refer to relevant information used to contact or identify specific users (such as providers, users, and managers of data products) within the data product system.

[0039] Internal contact information can be provided by the user when registering the data product system; internal contact information may include the user's name, company internal phone number, email address, etc.

[0040] S120, when there is login information matching the internal contact information in the preset login database, obtain a data product release request of the first user, the data product release request including product information and interface information of the first data product; the product information includes the product name, product type, business field and application scenario of the first data product.

[0041] In S120, the preset login database may be a database storing login information of all users, and the login information may be composed of part of the internal contact information and a password. For example, the login information may be an email address + a password.

[0042] When the first user attempts to log in to the system, the system checks whether the internal contact information provided by the user matches the login information of the first user in the preset login database, thereby determining whether the user has the right to access the system.

[0043] The data product release request is a request to release a new data product on the data product system, wherein the data product release request may include product information and interface information of the first data product.

[0044] Among them, product information may include product name, product type, business field, application scenario, product description, permission requirements and other additional information;

[0045] For example, product types may include rule types, algorithm types, report types, etc., which are used to describe the functions of data products; business areas may include inclusive services, green services, elderly care services and other fields; application scenarios may include marketing and customer acquisition, product innovation, risk control, operations and other scenarios; other additional information may include product version information, release time, maintainer information, etc.

[0046] For example, the product information of the first data product may be: product name - user behavior analysis model; product type - rule class; business field - digital service; application scenario - risk control; description - this data product builds a risk control model by analyzing user behavior data to identify potentially risky transactions.

[0047] The interface information may include the service address, port number, request protocol, request method, request path, request header, request body, return header and return body.

[0048] For example, the request protocol may be HyperText Transfer Protocol (HTTP), Hypertext Transfer Protocol over Secure Socket Layer (HTTPS), etc.; the request method may be GET, POST, etc.; the request header may include authentication information, etc.

[0049] For example, the interface information of the first data product can be: service IP address - 192.168.1.100; port - 8080; request protocol - HTTP; request method - POST; request path - / api / user-behavior-analysis; request header field - Content-Type: application / json; request body information - preset JSON format code; return header field - Content-Type: application / json; return body information - preset JSON format code.

[0050] In this way, by verifying the user's login information and receiving their data product release requests, including detailed product information and interface information, the system can efficiently manage and release data products and improve the availability and security of data products.

[0051] S130, determining whether there is a data product having the same product name, business field, and application scenario as the first data product in a data product subdirectory corresponding to the product type of the first data product in the data product directory of the data product system.

[0052] In S130, the data product catalog is used to organize and display all data products in the data product system. It is similar to a book catalog and can help users quickly find data products they are interested in or need.

[0053] The data product catalog can organize data products according to product type, business field, application scenario or other classification standards. Correspondingly, the data product catalog can also be classified more specifically according to any one of the product type, business field, application scenario or other classification standards to form a data product sub-catalog.

[0054] For example, they can be divided according to product types, such as rule-based data products, algorithm-based data products, report-based data products, etc. Each subdirectory can contain multiple specific data products, which have the same or similar product types but may differ in product names, business areas, application scenarios, etc.

[0055] By comparing the data product subdirectories corresponding to the product type of the first data product one by one to see whether there are data products with the same product name, business field and application scenario as the first data product.

[0056] In the case that there is a data product with the same product name, business field and application scenario as the first data product, the detailed information of the two data products, including but not limited to the product name, business field, application scenario, interface information, etc., can be further checked to confirm whether they are exactly the same or have slight differences. If it is confirmed that it is a duplicate data product, the two data products can be merged or the duplicate data product can be deleted to ensure the accuracy and consistency of the data product catalog.

[0057] In this way, by comparing the data product catalog, the duplicate release of data products can be effectively avoided, the accuracy and consistency of the data product catalog can be ensured, and the efficiency and quality of data product management can be improved.

[0058] S140: If there is no data product having the same product name, business domain, and application scenario as the first data product, verify whether the interface corresponding to the interface information is normally accessible.

[0059] In S140, in the data product system, checking whether the interface corresponding to the interface information is normally accessed can be implemented in a variety of ways, for example, using an interface testing tool to perform interface testing, log analysis, performance monitoring, etc.

[0060] In this embodiment, this can be achieved through the one-click test function of the data product. The data product includes the usage of the data product, which includes the field name, remarks, format, default value and other information of the request message and the return message. When verifying the interface information, you can edit the request message according to the above usage, and then click the one-click test button to send the edited message to the corresponding interface. If the interface can return data normally, and the returned data matches the return message sample provided by the provider, it means that the interface access is normal.

[0061] For example, the request message pseudocode can be expressed as: API version number-1.0; request type-get user activity; user name-123456; specify the starting point of the analysis time range-********; access token-********.

[0062] For example, the pseudo code of the return message can be expressed as: status code - 200; request processing result - success; data - *****.

[0063] In addition, users can view the returned sample data to understand the functions and output format of the data product and perform corresponding integration and debugging in their own projects.

[0064] In this way, by verifying the normality of access to interface information, we can ensure that the interface of the data product is reliable and effective, provide technical support for the subsequent use of the data product, and help users understand the functions and output formats of the data product.

[0065] S150: When the interface access corresponding to the interface information is normal, in response to a putting-on-shelf operation by the first user, putting the data product on the data product system.

[0066] In S150, after the data product system puts the data product on the shelves in response to the first user's putting operation, the management operation of the first user may also be obtained; the management operation is an instruction issued by the user to make necessary adjustments or maintenance to the data product. After receiving the management operation, the system will immediately respond and execute the processing tasks corresponding to these operations. These processing tasks cover multiple aspects, including but not limited to: removing, activating, updating or deactivating the corresponding data product.

[0067] In this way, by listing data products and responding to subsequent management operations, flexible management and efficient maintenance of data products are achieved, which improves the availability of data products and user satisfaction.

[0068] In an overall example, Figure 3 FIG. 1 is a schematic diagram of the overall process of a method for managing a data product system according to an embodiment of the present invention. Figure 3 As shown, the following steps may be included:

[0069] S301, the provider completes the information.

[0070] In S301, the provider completes the login information and sends a login request to the administrator. The login information may include internal contact information.

[0071] S302, the administrator approves the provider's application information.

[0072] In S302, the application information corresponds to the login information of this application.

[0073] S303, determine whether the application information is approved, if so, execute S304, otherwise execute S301.

[0074] In S303, if there is login information matching the internal contact information in the preset login database, the application information is approved, otherwise it is not approved.

[0075] S304, the provider registers product services.

[0076] In S304, the product service corresponds to the data product of the present application; the provider uploads the data product to the data product system and sends a data product publishing request to the administrator, the data product publishing request including product information and interface information of the data product.

[0077] S305, determine whether the product and service are repeated, if so, execute S306, otherwise execute S304.

[0078] In S305 , the administrator determines whether the data product uploaded by the provider is duplicated with an existing data product in the data product system based on the product information of the data product.

[0079] S306, the provider registers the data product.

[0080] S307, the provider puts the data product on the shelves.

[0081] S308, the manager reviews the data product.

[0082] In S308 , before the provider puts the data product on the shelves, the administrator reviews whether the interface corresponding to the interface information of the data product is accessible normally.

[0083] S309, determine whether the audit is passed, if yes, execute S310, otherwise execute S307.

[0084] S310, the provider publishes the data product.

[0085] In the embodiment of the present application, by publishing the data product on the data product system, and before publishing, determining whether the data product is a data product that already exists in the data product system, and verifying whether the interface of the data product can be accessed normally, it is ensured that the data products in the data product system are non-duplicate and available, and compared with data products stored locally or online, the management process of the data product is optimized, the data security of the data product is enhanced, and the management efficiency of the data product is improved. The technical problem of difficult management of data product content and permissions is solved.

[0086] In some embodiments, the method further comprises:

[0087] Obtaining management operations of the first user;

[0088] In response to the management operation, a process corresponding to the management operation is performed, where the process includes at least one of delisting, activating, updating, or deactivating the corresponding data product.

[0089] In this embodiment, the management operation is an instruction issued by a user to make necessary adjustments or maintenance on a data product.

[0090] After receiving management operations, the system will immediately respond and perform processing tasks corresponding to these operations. These processing tasks cover multiple aspects, including but not limited to:

[0091] Delist a data product: remove a data product listed by the first user from the data product system, so that it is no longer visible to external users; Enable a data product: put a data product that was previously disabled or delisted by the first user back on the shelves to restore it to the state of providing services to the outside world; Update a data product: modify or improve the information of the data product listed by the first user; Deactivate a data product: temporarily stop the service of a data product, but do not delete it from the system, and it is still visible to external users.

[0092] For example, updating a data product may include updating a product description, optimizing interface performance, or fixing known issues.

[0093] It is understandable that performing the above management operations may affect the normal use of data products. Therefore, when it is necessary to enable or update a data product, it is necessary to recheck the interface information of the enabled or updated data product to ensure that it can still be accessed normally, and the product information duplication needs to be checked again.

[0094] In this way, through these management operations, the first user can flexibly manage its own data products to ensure that they are always in the best state and can meet the needs of external users.

[0095] In some embodiments, the method further comprises:

[0096] receiving a trial request from a second user, the trial request being used to indicate a request for trial of a second data product in the data product system, the trial request including identity information, credit rating and trial reason of the second user; the second user being any one of the second category of users; the second category of users being used to indicate a user of the data product;

[0097] Determining whether the credit rating of the second user is greater than a first preset threshold and whether the identity information of the second user is recorded in a trial database;

[0098] If the credit rating of the second user is greater than the first preset threshold and the identity information of the second user is recorded in the trial database, forwarding the trial reason to the provider corresponding to the second data product;

[0099] A trial key returned by the provider corresponding to the second data product based on the trial reason is received, and the trial key is forwarded to the second user, so that the second user can try the second data product based on the trial key.

[0100] In this embodiment, the user's credit rating can be dynamically adjusted according to the user's relevant information. For example, the relevant information may include the user's rank, position, number of data products used, length of time the data products are used, historical violation records, etc., without limitation. The user's credit rating can be set by score. For example, the user's credit rating can be 1 to 10 points. The higher the score, the higher the user's credit rating.

[0101] Each data product can be set by its provider with a credit level required for trial use, which is the first preset threshold.

[0102] The trial database records the identity information of multiple users who have applied for and been approved to try data products. Only those who have applied and passed the identity information review of the management end can apply for the data products of the trial data product system. The identity information review of the management end can be comprehensively judged based on the relevant information of the user, and there is no limitation on this.

[0103] It is understandable that only for users who are recorded in the trial database and whose credit level is greater than the credit level set for the data product, the system will forward the trial reason filled in by the user to the provider corresponding to the data product, and then the provider will review the trial reason.

[0104] If the provider considers the trial reason to be reasonable, the trial key returned by the provider corresponding to the second data product based on the trial reason may be received and forwarded to the second user, so that the second user can try the second data product based on the trial key. If the provider considers the trial reason to be unreasonable, the trial request may be ignored or an unreasonable reason may be returned.

[0105] The trial key is a special credential generated and assigned by the data product provider after the user's trial application is approved in order to control the access rights of the data product. This key is required for users to try the data product, and it ensures that only authorized users can access and use the data product.

[0106] The trial key is usually a string of characters, which can be randomly generated or generated according to a specific algorithm. The length, complexity and format of the key may vary depending on the type of data product, the provider's security policy, etc. For example, a trial key can be "XXX".

[0107] For example, after users receive a trial key, they can try out the data product by following these steps:

[0108] Get the data product's description or access address.

[0109] The data product is accessed according to the access address. When accessing the data product, the user needs to enter the trial key in the specified location. The input process can be in a web form, an API request, or a data product system interface.

[0110] The data product system will verify the trial key entered by the user.

[0111] If the key is valid, the user will be allowed to access and try the data product. If the key is invalid, the user will not be allowed to access the data product.

[0112] Trying out data products can include operations such as viewing data, running analysis, and testing data interfaces.

[0113] In one example, Figure 4 FIG. 1 is a flow chart of a data product trial method according to an embodiment of the present invention. Figure 4 As shown, S401, the user views the data mart of the data product system (the data mart displays several data products for users to browse or try out). S402, after the user determines the target trial product, he submits a trial application for the target data product to the system (corresponding to the trial request of this application). S403, the provider of the target data product approves the trial reason in the trial request. S404, if the provider considers the trial reason reasonable, the trial request is approved. S405, the user receives the trial key returned by the provider corresponding to the target data product based on the trial reason, and tries out the target data product with one click.

[0114] In this way, by setting up credit rating thresholds and trial reason review mechanisms, not only the security of data products is improved, but data product providers can also receive trial requests that have been screened and reviewed, which helps them understand the needs and expectations of potential users more accurately. As a result, providers can optimize products more specifically, improve user experience and satisfaction, and reduce the chance of data product providers being disturbed by invalid information.

[0115] In some embodiments, when the trial key is associated with a trial duration, the method further includes:

[0116] Control the trial key to become invalid after the trial period.

[0117] In this embodiment, the trial duration may be set by the provider of the data product, and may be set based on factors such as the complexity of the core functions of the data product and the needs of the user.

[0118] For example, if a data product is used for marketing analysis, the provider may want users to have enough time to familiarize themselves with the product and evaluate its effectiveness, so a trial period of one week or one month may be set.

[0119] For example, if the data product is relatively simple, or the provider just wants users to quickly experience the core functions of the product, the trial period may be shorter, such as one or three days.

[0120] After the trial period ends, the user will no longer be able to use the key to access the data product.

[0121] In this way, the trial period provides users with a limited time window to test the functionality and performance of the data product, which helps the provider collect feedback and make necessary optimizations. At the same time, it ensures that after the trial period ends, even if the trial key is leaked, the data product cannot be accessed anymore, thus ensuring the security of the data.

[0122] In some embodiments, the method further comprises:

[0123] receiving a query request from the second user, the query request being used to represent a request to query a provider corresponding to the second data product, the query request including a credit rating of the second user and a usage time of the second data product by the second user;

[0124] When the credit rating of the second user is greater than a second preset threshold and the usage time is greater than a preset time threshold, the internal contact information of the provider corresponding to the second data product is returned to the second user.

[0125] In this embodiment, the setting of the credit level can refer to the method provided in the above embodiment, which is not described in detail; each data product can be set by its provider with the credit level required for internal contact, that is, the second preset threshold. The second preset threshold is higher than the first preset threshold.

[0126] It is understandable that the internal contact information of the provider of the data product will be returned to the user only when the user uses the data product for a time greater than a preset time threshold.

[0127] The preset time threshold may be set by its provider and is not limited thereto.

[0128] For example, after obtaining the trial key for the data product "Customer Credit Risk Score", user B began to use the data product and verified the data product's interface and return data through the one-click test function. During the trial period, B frequently used the data product and found it very helpful for his business decisions. As the trial was coming to an end, B hoped to establish a deeper cooperative relationship with provider A so that he could continue to use the data product in the future.

[0129] Therefore, B submits a query request in the system, requesting to query the internal contact information of provider A corresponding to the "Customer Credit Risk Score" data product. In this query request, B's credit rating (given by the enterprise's internal credit evaluation system) is "8" (greater than the second preset threshold), and B has used the data product for more than a preset time threshold (for example, 20 days). Based on B's credit rating and usage time, the system determines that B meets the conditions for querying the provider's contact information.

[0130] Therefore, the system returns to B the internal contact information of provider A, including A's name, employee number, department, and contact information of the internal communication software.

[0131] In this way, by setting a usage time threshold, users who really have a demand for data products and use them for a long time can be screened out, avoiding unnecessary waste of resources; at the same time, while allowing users to query the provider's contact information, dual restrictions on credit level and usage time can ensure that only qualified users can obtain sensitive information, reducing the risk of information leakage.

[0132] In some embodiments, the method further comprises:

[0133] receiving a subscription request from a third user; the subscription request includes identity information of the third user and an identifier of the subscribed data product; the third user is any one of the second category of users; the second category of users is used to represent users of data products;

[0134] When any data product that meets the subscription request is updated or any new data product is put on the shelves in the data product system, notification information is generated according to the identity information and the data product identifier, and the notification information is sent to the third user through a preset notification method.

[0135] In this embodiment, the subscription request allows the user of the data product (i.e., the third user) to actively subscribe to the data product of interest so as to be notified in a timely manner when the data product is updated or a new data product is launched. This helps ensure that the user can obtain the latest data product information and improve work efficiency.

[0136] The subscription request includes the identity information of the third user, the identifier of the subscribed data product, the contact information of the third user, preference settings (such as notification frequency, notification content preference), and subscription conditions of the data product (such as data product scope, update frequency, etc.);

[0137] When any data product that meets the subscription request is updated or any new data product is launched in the data product system, the system can generate notification content containing update or launch information according to the subscription request.

[0138] For example, the system can extract the identity information of the third user (such as name, department, etc.), and combine it with the relevant information of the data product (such as product name, update content, listing time, etc.) to generate complete notification information.

[0139] The preset notification methods may include email notification, SMS notification, system message notification, and application push notification, etc. These methods allow the system to select the most appropriate notification method to send notification information to the third user according to the third user's preferences and actual situation, and there is no limitation on this.

[0140] For example, the complete notification information can be

[0141] “Data product update / new listing notification.

[0142] Hello! The [data product name] you subscribed to has been updated / newly listed.

[0143] Status: Published.

[0144] Interface: IP = [IP address], Port = [port number], URI = [URI path].

[0145] Operation guide: Log in to the data product system; search and apply for the product; wait for the provider’s approval.

[0146] In this way, by allowing data product users to actively subscribe and receive update notifications, it ensures that users can obtain the latest data product information in a timely manner, thereby improving work efficiency and user experience.

[0147] Figure 6 A schematic diagram of the structure of a management device for a data product system provided in another embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0148] Reference Figure 5 , the management device 500 of the data product system may include:

[0149] A receiving module 501 is configured to receive a login request from a first user, wherein the login request includes internal contact information of the first user, wherein the first user is any one of a first category of users, and the first category of users is used to represent a provider of a data product;

[0150] The acquisition module 502 is used to acquire a data product release request of the first user when there is login information matching the internal contact information in a preset login database, wherein the data product release request includes product information and interface information of the first data product; the product information includes a product name, product type, business field, and application scenario of the first data product;

[0151] A judgment module 503 is used to judge whether there is a data product with the same product name, business field and application scenario as the first data product in a data product subdirectory corresponding to the product type of the first data product in the data product directory of the data product system;

[0152] Verification module 504, used to verify whether the interface corresponding to the interface information is normally accessible when there is no data product having the same product name, business field and application scenario as the first data product;

[0153] The execution module 505 is used to put the data product on the data product system in response to the putting-on-shelf operation of the first user when the interface access corresponding to the interface information is normal.

[0154] In some embodiments, the management device 500 of the data product system may further include:

[0155] The acquisition module 502 is further used to acquire the management operation of the first user;

[0156] The execution module 505 is further used to execute a process corresponding to the management operation in response to the management operation, wherein the process includes at least one of removing, enabling, updating or deactivating the corresponding data product.

[0157] In some embodiments, the management device 500 of the data product system may further include:

[0158] The receiving module 501 is further used to receive a trial request from a second user, the trial request is used to indicate a request to try out a second data product in the data product system, and the trial request includes the identity information, credit rating and trial reason of the second user; the second user is any one of the second category of users; the second category of users is used to indicate a user of the data product;

[0159] The judgment module 503 is further used to judge whether the credit rating of the second user is greater than a first preset threshold, and whether the identity information of the second user is recorded in the trial database;

[0160] a forwarding module, configured to forward the trial reason to a provider corresponding to the second data product when the credit rating of the second user is greater than the first preset threshold and the identity information of the second user is recorded in the trial database;

[0161] The receiving module 501 is further configured to receive a trial key returned by the provider corresponding to the second data product based on the trial reason;

[0162] The forwarding module is further used to forward the data to the second user, so that the second user can try the second data product based on the trial key.

[0163] In some embodiments, the management device 500 of the data product system may further include:

[0164] The control module is used to control the trial key to become invalid after the trial time period when the trial key is associated with the trial time period.

[0165] In some embodiments, the management device 500 of the data product system may further include:

[0166] The receiving module 501 is further configured to receive a query request from the second user, wherein the query request is used to indicate a request to query a provider corresponding to the second data product, and the query request includes a credit rating of the second user and a usage time of the second user using the second data product;

[0167] The sending module is used to return the internal contact information of the provider corresponding to the second data product to the second user when the credit level of the second user is greater than a second preset threshold and the usage time is greater than a preset time threshold.

[0168] In some embodiments, the management device 500 of the data product system may further include:

[0169] The receiving module 501 is further used to receive a subscription request from a third user; the subscription request includes the identity information of the third user and the identifier of the subscribed data product; the third user is any one of the second category of users; the second category of users is used to represent the user of the data product;

[0170] A generation module is used to generate notification information based on the identity information and the data product identifier when any data product that meets the subscription request is updated or any new data product is put on the shelf in the data product system, and send the notification information to the third user through a preset notification method.

[0171] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application, and are devices corresponding to the management method of the above-mentioned data product system. All implementation methods in the above-mentioned method embodiment are applicable to the embodiment of the device. Its specific functions and technical effects brought about can be found in the method embodiment part, which will not be repeated here.

[0172] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0173] Figure 6 is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 6 As shown:

[0174] The device may include a processor 601 and a memory 602 storing programs or instructions.

[0175] When the processor 601 executes the program, the steps in any of the above method embodiments are implemented.

[0176] Exemplarily, the program may be divided into one or more modules / units, one or more modules / units are stored in the memory 602 and executed by the processor 601 to complete the present application. One or more modules / units may be a series of program instruction segments capable of completing a specific function, and the instruction segments are used to describe the execution process of the program in the device.

[0177] Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0178] The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 602 is a non-volatile solid-state memory.

[0179] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.

[0180] The processor 601 implements any one of the methods in the above embodiments by reading and executing the program or instruction stored in the memory 602 .

[0181] In one example, the electronic device may further include a communication interface 603 and a bus 604. The processor 601, the memory 602, and the communication interface 603 are connected via the bus 604 and communicate with each other.

[0182] The communication interface 603 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0183] Bus 604 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-end bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 604 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.

[0184] In addition, in combination with the method in the above embodiment, the embodiment of the present application may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores a program or instruction; when the program or instruction is executed by a processor, any one of the methods in the above embodiment is implemented. The computer-readable storage medium can be read by a machine such as a computer.

[0185] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0186] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0187] An embodiment of the present application provides a computer program product, which is stored in a computer-readable storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0188] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0189] The functional modules shown in the above block diagram can be implemented as hardware, software, firmware or their combination. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. Programs or code segments can be stored in machine-readable media, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable media" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. Code segments can be downloaded via computer grids such as the Internet, intranets, etc.

[0190] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0191] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by a computer program or instruction. These programs or instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0192] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A method for managing a data product system, characterized in that: The data product system displays a number of data products, and the method includes: receiving a login request from a first user, the login request including internal contact information of the first user, the first user being any one of a first category of users, the first category of users being used to represent a provider of a data product; If there is login information matching the internal contact information in the preset login database, obtaining a data product publishing request of the first user, wherein the data product publishing request includes product information and interface information of the first data product; the product information includes a product name, product type, business field, and application scenario of the first data product; Determine whether, in the data product directory of the data product system, under the data product subdirectory corresponding to the product type of the first data product, there is a data product having the same product name, business field, and application scenario as the first data product; If there is no data product with the same product name, business field and application scenario as the first data product, verify whether the interface corresponding to the interface information is normally accessible; When the interface access corresponding to the interface information is normal, the data product is put on the shelves in the data product system in response to the putting-on-shelf operation of the first user.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining management operations of the first user; In response to the management operation, a process corresponding to the management operation is performed, where the process includes at least one of delisting, activating, updating, or deactivating the corresponding data product.

3. The method according to claim 1, characterized in that The method further comprises: receiving a trial request from a second user, the trial request being used to indicate a request for trial of a second data product in the data product system, the trial request including identity information, credit rating and trial reason of the second user; the second user being any one of the second category of users; the second category of users being used to indicate a user of the data product; Determining whether the credit rating of the second user is greater than a first preset threshold and whether the identity information of the second user is recorded in a trial database; If the credit rating of the second user is greater than the first preset threshold and the identity information of the second user is recorded in the trial database, forwarding the trial reason to the provider corresponding to the second data product; A trial key returned by the provider corresponding to the second data product based on the trial reason is received, and the trial key is forwarded to the second user, so that the second user can try the second data product based on the trial key.

4. The method according to claim 3, characterized in that In the case where the trial key is associated with a trial duration, the method further includes: Control the trial key to become invalid after the trial period.

5. The method according to claim 3, characterized in that: The method further comprises: receiving a query request from the second user, the query request being used to represent a request to query a provider corresponding to the second data product, the query request including a credit rating of the second user and a usage time of the second data product by the second user; When the credit rating of the second user is greater than a second preset threshold and the usage time is greater than a preset time threshold, the internal contact information of the provider corresponding to the second data product is returned to the second user.

6. The method according to claim 1, characterized in that The method further comprises: receiving a subscription request from a third user; the subscription request includes identity information of the third user and an identifier of the subscribed data product; the third user is any one of the second category of users; the second category of users is used to represent users of data products; When any data product that meets the subscription request is updated or any new data product is put on the shelves in the data product system, notification information is generated according to the identity information and the data product identifier, and the notification information is sent to the third user through a preset notification method.

7. A management device for a data product system, characterized in that: The device comprises: A receiving module, configured to receive a login request from a first user, wherein the login request includes internal contact information of the first user, wherein the first user is any one of a first category of users, and the first category of users is used to represent a provider of a data product; an acquisition module, configured to acquire a data product release request of the first user if there is login information matching the internal contact information in a preset login database, the data product release request including product information and interface information of the first data product; the product information including a product name, product type, business field, and application scenario of the first data product; A determination module, configured to determine whether, in a data product directory of the data product system, under a data product subdirectory corresponding to a product type of the first data product, there is a data product having the same product name, business field, and application scenario as the first data product; A verification module, used to verify whether the interface corresponding to the interface information is normally accessible when there is no data product having the same product name, business field and application scenario as the first data product; An execution module is used to put the data product on the data product system in response to a putting-on-shelf operation by the first user when the interface access corresponding to the interface information is normal.

8. An electronic device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 6.

10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the method according to any one of claims 1 to 6.

Images