Data element cross-domain sharing method, system and device

Abstract

The invention relates to the technical field of data processing, in particular to a data element cross-domain sharing method, which comprises the following steps: starting a task scheduling engine to timed tasks, and circularly sending monitoring tasks to a robot factory; determining an element monitoring task template corresponding to the first data element transaction platform in a task template library, creating a first robot instance based on the element monitoring task template, and executing an element monitoring task on the first data element transaction platform based on the first robot instance; after the robot factory monitors the newly-added component product, sending a component newly-added notification to the task scheduling engine through the metadata information base; the task scheduling engine sends a component putaway task to the robot factory; and determining a component putaway task template corresponding to the second data component transaction platform in the task template library, creating a second robot instance based on the component putaway task template, and executing a component putaway task for the second data transaction platform based on the component field data and the second robot instance.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, system and device for cross-domain sharing of data elements. Background Art

[0002] Currently, the data component trading and circulation platforms in various parts of the market are all self-built, without unified standards, unable to interconnect and interoperate, and still lack liquidity.

[0003] If data component products need to be shared between two platforms, the development departments of each platform need to negotiate the specific docking protocols, data formats and other information, and then conduct secondary development of the platforms and conduct docking and joint debugging tests between them. This is a cost-increasing and inefficient way. If products are shared between multiple platforms, more development and joint debugging are required, and the docking cost increases exponentially.

[0004] In view of this, how to provide a universal automated cross-domain sharing method for data components and achieve interconnection and interoperability on multiple platforms has become a technical problem that urgently needs to be solved. Summary of the invention

[0005] The embodiments of the present application provide a data element cross-domain sharing method, a data element cross-domain sharing method, a data element cross-domain sharing device, an electronic device and a computer storage medium, which are used to solve the problem that multiple platforms cannot be interconnected.

[0006] In a first aspect of an embodiment of the present application, a data element cross-domain sharing method is provided, which is applied to a sharing center, and includes:

[0007] Start the scheduled task of the task scheduling engine of the sharing center, and cyclically send the component monitoring task of the first data component trading platform to the robot factory;

[0008] Determining a component monitoring task template corresponding to the first data component trading platform in the task template library of the robot factory, creating a first robot instance based on the component monitoring task template, and executing a component monitoring task for the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process;

[0009] After the robot factory monitors the newly added component product of the first component trading platform, it extracts the component field data corresponding to the newly added component product, adds the component field data to the metadata information library, and sends a component addition notification to the task scheduling engine through the metadata information library;

[0010] The task scheduling engine sends a component listing task to the second data component trading platform to the robot factory based on the component addition notification;

[0011] A component listing task template corresponding to the second data component trading platform is determined in the task template library of the robot factory, a second robot instance is created based on the component listing task template, and the component field data corresponding to the newly added component product is obtained from the metadata information library. Based on the component field data and the second robot instance, the component listing task for the second data trading platform is executed.

[0012] In a second aspect of an embodiment of the present application, a data element cross-domain sharing system is provided, the data element cross-domain sharing system comprising a sharing center and a data element trading platform, the sharing center comprising a task designer, a task template library, a robot factory, a metadata information library and a task scheduling engine, wherein:

[0013] The task designer is used to record the product operation steps monitored on the data component trading platform into a script, upload and convert it into designer canvas data, and design corresponding task templates for each component trading platform, wherein a metadata mapping table is generated by establishing a mapping relationship between the component information field on the trading platform and the standard field of the metadata information library;

[0014] The task template library stores all the task templates generated by the task designer. The task templates and the data component trading platforms are in a one-to-one binding relationship. Each of the data component trading platforms is provided with a component monitoring task template and a component listing task template. The task templates carry the order of the operation nodes, the target positions corresponding to the operation nodes, and the metadata fields mapped by the operation nodes.

[0015] The robot factory is used to generate a corresponding RPA task robot instance according to the task template, generate a robot pool, and after the robot receives the task instruction assigned by the task scheduling engine, it executes step by step according to the task template corresponding to the task instruction, and enters a waiting state after the execution is completed, wherein the robots in the robot pool are in a waiting state;

[0016] The task scheduling engine is responsible for sending task instructions to the robot factory and executing the task of monitoring the component list of the data component trading platform and the task of putting components on the shelves.

[0017] In a third aspect of an embodiment of the present application, a data element cross-domain sharing device is provided, which is applied to a sharing center end, including:

[0018] A monitoring and sending module is configured to start a scheduled task of a task scheduling engine of the sharing center, and cyclically send a component monitoring task for the first data component trading platform to the robot factory;

[0019] a monitoring module, configured to determine a component monitoring task template corresponding to the first data component trading platform in a task template library of the robot factory, create a first robot instance based on the component monitoring task template, and perform a component monitoring task on the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process;

[0020] an extraction module, configured to extract component field data corresponding to a newly added component product on the first component trading platform after the robot factory monitors the newly added component product, add the component field data to a metadata information library, and send a component addition notification to the task scheduling engine through the metadata information library;

[0021] A shelf sending module is configured so that the task scheduling engine sends a component shelf task to the second data component trading platform to the robot factory based on the component new addition notification;

[0022] The shelving module is configured to determine a component shelving task template corresponding to the second data component trading platform in the task template library of the robot factory, create a second robot instance based on the component shelving task template, and obtain the component field data corresponding to the newly added component product from the metadata information library, and execute the component shelving task for the second data trading platform based on the component field data and the second robot instance.

[0023] In a fourth aspect of an embodiment of the present application, a computing device is provided, including:

[0024] Memory and processor;

[0025] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above-mentioned data element cross-domain sharing method are implemented.

[0026] According to a fifth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the above-mentioned data element cross-domain sharing method are implemented.

[0027] The present application provides a method for cross-domain sharing of data components, comprising: first, starting a scheduled task of a task scheduling engine of a sharing center, and cyclically sending a component monitoring task for a first data component trading platform to a robot factory; then, determining a component monitoring task template corresponding to the first data component trading platform in a task template library of the robot factory, and creating a first robot instance based on the component monitoring task template, and executing the component monitoring task for the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in an interactive process; secondly, after the robot factory monitors a newly added component product of the first component trading platform, the newly added component product is extracted The corresponding component field data is obtained, and the component field data is added to the metadata information library, and a component addition notification is sent to the task scheduling engine through the metadata information library; secondly, the task scheduling engine sends a component listing task for the second data component trading platform to the robot factory based on the component addition notification; finally, a component listing task template corresponding to the second data component trading platform is determined in the task template library of the robot factory, a second robot instance is created based on the component listing task template, and the component field data corresponding to the newly added component product is obtained from the metadata information library, and the component listing task for the second data trading platform is executed based on the component field data and the second robot instance.

[0028] The cross-domain sharing method of data components provided in the embodiment of the present application is applied, and a series of fixed standard component fields are extracted based on the unchanged business attributes of data components as the data format specification of the metadata information library. When designing tasks, the business attributes that change on different platforms are mapped one by one to the standard component fields of the metadata information library to form a field mapping table, which is fixed as a task template. In this way, on a trading platform, if there are multiple data components that need to be put on the shelves, it is only necessary to render the corresponding task template first, and convert the variables into the specific attributes of each component. Then, multiple Rpa robots with unified templates but different data can be generated to perform the shelving tasks of multiple data components respectively, thereby realizing the interconnection and interoperability of multiple platforms.

[0029] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, which can be implemented in accordance with the contents of the specification, and in order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0031] Figure 1 A block diagram of a data element cross-domain sharing system provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of a flow chart of a data element cross-domain sharing method provided in an embodiment of the present application;

[0033] Figure 3 A schematic diagram of the structure of a data element cross-domain sharing device provided in an embodiment of the present application;

[0034] Figure 4 A structural block diagram of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0036] See also Figure 1 , Figure 1 A block diagram of a data element cross-domain sharing system provided in an embodiment of the present application. Figure 1 As shown, an embodiment of the present application provides a general automated data element cross-domain sharing technology based on RPA, wherein the data element cross-domain sharing system includes a sharing center and data element trading platform A and data element trading platform B. The sharing center includes a task designer, a task template library, a robot factory, a metadata information library and a task scheduling engine, covering each node of the entire life cycle of data element sharing tasks, including design, task instance creation, and task operation.

[0037] Specifically, the task designer is used to record the product operation steps monitored on the data component trading platform into scripts, and upload them to be converted into designer canvas data, so as to design corresponding task templates for each component trading platform. The metadata mapping table is generated by establishing a mapping relationship between the component information fields on the trading platform and the standard fields of the metadata information library.

[0038] The task designer is also used to design and arrange the product operation steps monitored on the data component trading platform, and design corresponding task templates for each component trading platform. The operation nodes on the task designer correspond to the specific field meanings of the component products on the shelves, including opening the website, entering the account number, entering the password, clicking the button, selecting multiple options, and entering the content.

[0039] In actual applications, the task designer designs and arranges the manual operation steps for querying and listing products on the data component trading platform, provides a drag-and-drop DAG canvas design method, and also supports directly recording manual operation steps into scripts and uploading them into designer canvas data. The designer provides many basic operation nodes, such as opening a website, entering an account / password, clicking a button, selecting multiple options, entering content, etc. By setting the specific field meanings of these nodes corresponding to the listing of component products, a mapping relationship can be established between the component information fields on the trading platform and the standard fields of the metadata information library to form a metadata mapping table.

[0040] The task template library stores all the task templates generated by the task designer. The task templates and the data component trading platforms are bound one to one. Each of the data component trading platforms is provided with a component monitoring task template and a component listing task template. The task templates carry the order of the operation nodes, the target positions corresponding to the operation nodes, and the metadata fields mapped by the operation nodes.

[0041] The task template library includes monitoring tasks and listing tasks, wherein the monitoring task is used to simulate manual operation, query the list of listed component products on the first data component trading platform, and after monitoring and acquiring the newly added component products, extract the component field data corresponding to the newly added component products, and add the component field data to the metadata information library; the listing task is used to simulate manual operation, and list the newly added component products in the metadata information library on the second data component trading platform.

[0042] In actual applications, the designer generates a task template after designing and saving it. The task template is divided into two categories: monitoring tasks and listing tasks. The monitoring task simulates manual operation to query the list of component products that have been listed on the source trading platform. After monitoring and obtaining the newly added component products, the component information is extracted and added to the metadata information library; the listing task simulates manual operation to list the newly added components in the metadata library on the target trading platform. The task template contains the following information: the order of the operation nodes, the target location corresponding to the operation nodes (generally the target location on the web page), and the metadata field mapped by the operation nodes. The task template and the trading platform are one-to-one binding. Generally, each trading platform requires two task templates for component query and component listing.

[0043] The robot factory is used to generate corresponding RPA task robot instances according to task templates and generate a robot pool. After the robot receives the task instruction assigned by the task scheduling engine, it executes step by step according to the task template corresponding to the task instruction, and enters a waiting state after the execution is completed, wherein the robots in the robot pool are in a waiting state.

[0044] In actual applications, the robot factory generates corresponding RPA task robot instances based on the task template. The robot factory will maintain a certain number of robot instances in a waiting state, namely the robot pool. After the task scheduling engine assigns the task instruction, the robot that receives the instruction will execute it step by step according to the corresponding task template, and enter the waiting state again after the execution is completed.

[0045] The task scheduling engine is responsible for sending task instructions to the robot factory and executing the task of monitoring the component list of the data component trading platform and the task of putting components on the shelves.

[0046] In actual applications, the task scheduling engine is the task scheduling module, which is responsible for sending task instructions to the robot factory and executing established strategies such as monitoring the component list of the trading platform and putting components on the shelves. When the task engine executes the monitoring strategy, it will be triggered at a fixed interval to send the component query task instruction of the target platform to the robot factory. The task factory matches the corresponding task template, creates or wakes up the task instance, executes the task, and feedbacks the task result (if there are new component products, they will be added to the metadata information library at the same time).

[0047] When the task engine executes the listing strategy, it will be triggered when there is new data in the metadata information library, and send the component listing task instructions of the target platform to the robot factory. The task factory matches the corresponding task template, creates or wakes up the task instance, executes the task, and feedbacks the task results.

[0048] See also Figure 2 , Figure 2 A flow chart of a method for cross-domain sharing of data elements provided in an embodiment of the present application. Figure 2 As shown, the specific steps include the following steps.

[0049] Step S202: starting the scheduled task of the task scheduling engine of the sharing center, and cyclically sending the component monitoring task of the first data component trading platform to the robot factory;

[0050] Step S204: determining a component monitoring task template corresponding to the first data component trading platform in the task template library of the robot factory, creating a first robot instance based on the component monitoring task template, and executing the component monitoring task for the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process;

[0051] Step S206: After the robot factory monitors the newly added component product on the first component trading platform, the component field data corresponding to the newly added component product is extracted, and the component field data is added to the metadata information library, and a component addition notification is sent to the task scheduling engine through the metadata information library;

[0052] Step S208: the task scheduling engine sends a component listing task to the second data component trading platform to the robot factory based on the component addition notification;

[0053] Step S210: Determine the component listing task template corresponding to the second data component trading platform in the task template library of the robot factory, create a second robot instance based on the component listing task template, and obtain the component field data corresponding to the newly added component product from the metadata information library, and execute the component listing task for the second data trading platform based on the component field data and the second robot instance.

[0054] In actual applications, first, the user designs the component listening task template for platform A and the component putting on the shelves task template for platform B through the Web-side task designer; then, the task scheduling engine starts the scheduled task and cyclically initiates the component listening task for platform A to the robot factory; secondly, the robot factory creates a robot instance according to the corresponding task template and executes the component listening task for platform A; thirdly, for the component listening task of platform A, after obtaining the newly added component products of platform A, the standard component field data is extracted and added to the metadata information library; thirdly, after the metadata information library adds data, it notifies the component scheduling engine; thirdly, the task scheduling engine receives the component addition notification and initiates the component putting on the shelves task for platform B to the robot factory; thirdly, the robot factory creates a robot instance according to the corresponding task template and obtains the corresponding standard component field data from the metadata information library; finally, after the robot instance obtains the newly added metadata information, it executes the component putting on the shelves task for platform B.

[0055] The above steps complete the cross-domain sharing of components between heterogeneous platforms A and B.

[0056] In an embodiment of the present application, before starting the scheduled task of the task scheduling engine of the shared center, it includes: generating a task template corresponding to the data component trading platform through a task designer, and storing it in a task template library, wherein the task template includes a component monitoring task template and a component shelving task template, the component monitoring task template is a task template corresponding to the first data component trading platform corresponding to the component monitoring task executed by the robot factory generated by the task designer; the component shelving task template is a task template corresponding to the second data component trading platform corresponding to the component shelving task executed by the robot factory generated by the task designer.

[0057] Specifically, the task template corresponding to the data component trading platform is generated by the task designer, including: obtaining the operation steps corresponding to the query operation and / or listing operation performed by the user on the data component trading platform; designing the corresponding operation node for each operation step by a drawing design method, and generating the task template corresponding to each data component trading platform, wherein each data component trading platform corresponds to at least one component monitoring task template and one component listing task template; the task template carries the order of the operation nodes, the template position corresponding to the operation stage and the metadata field mapped by the operation node; the operation nodes include: opening a website, entering an account number, entering a password, clicking a button, selecting multiple options, and entering content.

[0058] Specifically, the generating of the task template corresponding to the data component trading platform by the task designer also includes: establishing a mapping relationship between the component field data on the data component trading platform and the standard field of the metadata information library, and generating a metadata mapping table; based on the metadata mapping table, determining the correspondence between the first data component trading platform and the second data component trading platform.

[0059] In an embodiment of the present application, the component monitoring task on the first data component trading platform is performed based on the first robot instance, including: based on the first robot instance, simulating manual query of the list of component products that have been put on the shelves on the first data component trading platform, and monitoring whether the component product list involves new component products.

[0060] In an embodiment of the present application, the first robot instance and the second robot instance constitute a robot pool, wherein the robot pool includes a preset number of robot instances, and the robot instance enters a waiting state after completing a task.

[0061] By applying this method, we can extract a series of fixed standard component fields based on the unchanged business attributes of data components as the data format specification of the metadata information library. When designing tasks, we can map the changing business attributes on different platforms to the standard component fields of the metadata information library one by one to form a field mapping table, which is fixed as a task template. In this way, if there are multiple data components that need to be put on the shelves on a trading platform, we only need to render the corresponding task template first and convert the variables into the specific attributes of each component. Then, we can generate multiple RPA robots with unified templates but different data carriers to perform the tasks of putting multiple data components on the shelves respectively.

[0062] Corresponding to the above method embodiment, this specification also provides a data element cross-domain sharing device embodiment, Figure 3 A schematic diagram of the structure of a data element cross-domain sharing device provided in an embodiment of the present application. Figure 3 As shown, the device comprises:

[0063] The monitoring and sending module 302 is configured to start the scheduled task of the task scheduling engine of the sharing center, and cyclically send the component monitoring task of the first data component trading platform to the robot factory;

[0064] The monitoring module 304 is configured to determine a component monitoring task template corresponding to the first data component trading platform in the task template library of the robot factory, create a first robot instance based on the component monitoring task template, and perform a component monitoring task on the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process;

[0065] The extraction module 306 is configured to extract the component field data corresponding to the newly added component product after the robot factory monitors the newly added component product of the first component trading platform, add the component field data to the metadata information library, and send a component addition notification to the task scheduling engine through the metadata information library;

[0066] The shelf sending module 308 is configured so that the task scheduling engine sends a component shelf sending task to the second data component trading platform to the robot factory based on the component new addition notification;

[0067] The shelving module 310 is configured to determine a component shelving task template corresponding to the second data component trading platform in the task template library of the robot factory, create a second robot instance based on the component shelving task template, and obtain the component field data corresponding to the newly added component product from the metadata information library, and execute the component shelving task for the second data trading platform based on the component field data and the second robot instance.

[0068] In an optional embodiment, before the monitoring and sending module 302, the following steps are included:

[0069] The generation module 312 is configured to generate a task template corresponding to the data component trading platform through a task designer and store it in a task template library, wherein the task template includes a component monitoring task template and a component shelving task template. The component monitoring task template is a task template corresponding to the first data component trading platform generated by the task designer for the component monitoring task performed by the robot factory; the component shelving task template is a task template corresponding to the second data component trading platform generated by the task designer for the component shelving task performed by the robot factory.

[0070] In an optional embodiment, the generating module 312 is further configured to:

[0071] Obtaining the operation steps corresponding to the query operation and / or listing operation performed by the user on the data component trading platform;

[0072] Corresponding operation nodes are designed for each of the operation steps through a drawing design method, and task templates corresponding to each data component trading platform are generated, wherein each of the data component trading platforms corresponds to at least one component monitoring task template and a component shelving task template; the task template carries the order of the operation nodes, the template position corresponding to the operation stage, and the metadata field mapped by the operation nodes; the operation nodes include: opening a website, entering an account, entering a password, clicking a button, selecting multiple options, and entering content.

[0073] In an optional embodiment, the generating module 312 is further configured to:

[0074] Establishing a mapping relationship between component field data on the data component trading platform and standard fields in the metadata information library to generate a metadata mapping table;

[0075] Based on the metadata mapping table, a corresponding relationship between the first data element trading platform and the second data element trading platform is determined.

[0076] In an optional embodiment, the monitoring module 304 is further configured to:

[0077] Based on the first robot instance, a manual search is performed on the first data component trading platform to find out the list of component products that have been put on the shelves, and the list of component products is monitored to see whether there are new component products involved.

[0078] In an optional embodiment, the monitoring module 304 is further configured to:

[0079] The first robot instance and the second robot instance constitute a robot pool, wherein the robot pool includes a preset number of robot instances, and the robot instance enters a waiting state after completing a task.

[0080] By applying this device, a series of fixed standard component fields are extracted based on the unchanged business attributes of data components as the data format specifications of the metadata information library. When designing tasks, the business attributes that change on different platforms are mapped one by one to the standard component fields of the metadata information library to form a field mapping table, which is fixed as a task template. In this way, on a trading platform, if there are multiple data components that need to be put on the shelves, it is only necessary to render the corresponding task template first, and convert the variables into the specific attributes of each component. Then, multiple Rpa robots with unified templates but different data can be generated to perform the tasks of putting multiple data components on the shelves respectively.

[0081] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the data element cross-domain sharing device, since it is basically similar to the data element cross-domain sharing method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the data element cross-domain sharing method embodiment.

[0082] Figure 4 This is a block diagram of a computing device provided in an embodiment of the present application. The components of the computing device 400 include but are not limited to a memory 410 and a processor 420. The processor 420 is connected to the memory 410 via a bus 430, and the database 450 is used to store data.

[0083] The computing device 400 also includes an access device 440, which enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world-wide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, and a near field communication (NFC).

[0084] In one embodiment of the present specification, the above components of the computing device 400 and Figure 4 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 4 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0085] The computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 400 may also be a mobile or stationary server.

[0086] The processor 420 is used to execute the following computer executable instructions, which, when executed by the processor, implement the steps of the above-mentioned data element cross-domain sharing method.

[0087] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the computing device embodiment, since it is basically similar to the data element cross-domain sharing method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the data element cross-domain sharing method embodiment.

[0088] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the above-mentioned data element cross-domain sharing method.

[0089] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the computer-readable storage medium embodiment, since it is basically similar to the data element cross-domain sharing method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the data element cross-domain sharing method embodiment.

[0090] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned data element cross-domain sharing method.

[0091] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the computer program embodiment, since it is basically similar to the data element cross-domain sharing method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the data element cross-domain sharing method embodiment.

[0092] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0093] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0094] It should be noted that the above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present specification.

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

[0096] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A data element cross-domain sharing method, applied to a sharing center, characterized in that: include: Start the scheduled task of the task scheduling engine of the sharing center, and cyclically send the component monitoring task of the first data component trading platform to the robot factory; Determining a component monitoring task template corresponding to the first data component trading platform in the task template library of the robot factory, creating a first robot instance based on the component monitoring task template, and executing a component monitoring task for the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process; After the robot factory monitors the newly added component product of the first component trading platform, it extracts the component field data corresponding to the newly added component product, adds the component field data to the metadata information library, and sends a component addition notification to the task scheduling engine through the metadata information library; The task scheduling engine sends a component listing task to the second data component trading platform to the robot factory based on the component addition notification; A component listing task template corresponding to the second data component trading platform is determined in the task template library of the robot factory, a second robot instance is created based on the component listing task template, and the component field data corresponding to the newly added component product is obtained from the metadata information library. Based on the component field data and the second robot instance, the component listing task for the second data trading platform is executed.

2. The method according to claim 1, characterized in that Before starting the scheduled task of the task scheduling engine of the sharing center, include: A task template corresponding to a data component trading platform is generated through a task designer and stored in a task template library, wherein the task template includes a component monitoring task template and a component shelving task template. The component monitoring task template is a task template corresponding to a first data component trading platform corresponding to a component monitoring task executed by a robot factory generated through a task designer; the component shelving task template is a task template corresponding to a second data component trading platform corresponding to a component shelving task executed by a robot factory generated through a task designer.

3. The method according to claim 2, characterized in that The step of generating a task template corresponding to the data component trading platform through a task designer includes: Obtaining the operation steps corresponding to the query operation and / or listing operation performed by the user on the data component trading platform; Corresponding operation nodes are designed for each of the operation steps through a drawing design method, and task templates corresponding to each data component trading platform are generated, wherein each of the data component trading platforms corresponds to at least one component monitoring task template and a component shelving task template; the task template carries the order of the operation nodes, the template position corresponding to the operation stage, and the metadata field mapped by the operation nodes; the operation nodes include: opening a website, entering an account, entering a password, clicking a button, selecting multiple options, and entering content.

4. The method according to claim 2, characterized in that: The step of generating a task template corresponding to the data component trading platform through the task designer also includes: Establishing a mapping relationship between component field data on the data component trading platform and standard fields in the metadata information library to generate a metadata mapping table; Based on the metadata mapping table, a corresponding relationship between the first data element trading platform and the second data element trading platform is determined.

5. The method according to claim 1, characterized in that The performing of the component monitoring task on the first data component trading platform based on the first robot instance includes: Based on the first robot instance, a manual search is performed on the first data component trading platform to find out the list of component products that have been put on the shelves, and the list of component products is monitored to see whether there are new component products involved.

6. The method according to claim 1, characterized in that The first robot instance and the second robot instance constitute a robot pool, wherein the robot pool includes a preset number of robot instances, and the robot instance enters a waiting state after completing a task.

7. A data element cross-domain sharing system, characterized in that: The data element cross-domain sharing system includes a sharing center and a data element trading platform. The sharing center includes a task designer, a task template library, a robot factory, a metadata information library and a task scheduling engine. The task designer is used to record the product operation steps monitored on the data component trading platform into a script, upload and convert it into designer canvas data, and design corresponding task templates for each component trading platform, wherein a metadata mapping table is generated by establishing a mapping relationship between the component information field on the trading platform and the standard field of the metadata information library; The task template library stores all the task templates generated by the task designer. The task templates and the data component trading platforms are in a one-to-one binding relationship. Each of the data component trading platforms is provided with a component monitoring task template and a component listing task template. The task templates carry the order of the operation nodes, the target positions corresponding to the operation nodes, and the metadata fields mapped by the operation nodes. The robot factory is used to generate a corresponding RPA task robot instance according to the task template, generate a robot pool, and after the robot receives the task instruction assigned by the task scheduling engine, it executes step by step according to the task template corresponding to the task instruction, and enters a waiting state after the execution is completed, wherein the robots in the robot pool are in a waiting state; The task scheduling engine is responsible for sending task instructions to the robot factory and executing the task of monitoring the component list of the data component trading platform and the task of putting components on the shelves.

8. The system according to claim 1, characterized in that The task designer is also used to design and arrange the product operation steps monitored on the data component trading platform, and design corresponding task templates for each component trading platform. The operation nodes on the task designer correspond to the specific field meanings of the component products on the shelves, including opening the website, entering the account number, entering the password, clicking the button, selecting multiple options, and entering the content.

9. The system according to claim 1, characterized in that The task template library includes monitoring tasks and listing tasks, where: The monitoring task is used to simulate manual operation, query the list of component products that have been put on the shelf on the first data component trading platform, and after monitoring and obtaining the newly added component products, extract the component field data corresponding to the newly added component products, and add the component field data to the metadata information library; The listing task is used to simulate manual operation to list the newly added component product in the metadata information library on the second data component trading platform.

10. A data element cross-domain sharing device, applied to a sharing center, characterized in that: include: A monitoring and sending module is configured to start a scheduled task of a task scheduling engine of the sharing center, and cyclically send a component monitoring task for the first data component trading platform to the robot factory; a monitoring module, configured to determine a component monitoring task template corresponding to the first data component trading platform in a task template library of the robot factory, create a first robot instance based on the component monitoring task template, and perform a component monitoring task on the first data component trading platform based on the first robot instance, wherein the task template library stores task templates corresponding to all trading platforms involved in the interactive process; an extraction module, configured to extract component field data corresponding to a newly added component product on the first component trading platform after the robot factory monitors the newly added component product, add the component field data to a metadata information library, and send a component addition notification to the task scheduling engine through the metadata information library; A shelf sending module is configured so that the task scheduling engine sends a component shelf task to the second data component trading platform to the robot factory based on the component new addition notification; The shelving module is configured to determine a component shelving task template corresponding to the second data component trading platform in the task template library of the robot factory, create a second robot instance based on the component shelving task template, and obtain the component field data corresponding to the newly added component product from the metadata information library, and execute the component shelving task for the second data trading platform based on the component field data and the second robot instance.

Images