Trusted digital object packaging method, device, equipment, medium and product

Abstract

The invention provides a trusted digital object packaging method, and relates to the technical field of robot process automation. The trusted digital object packaging method comprises the steps of determining the type of to-be-packaged data according to a preset data type division rule, obtaining the to-be-packaged data according to a data obtaining rule corresponding to the type of the to-be-packaged data, and calling a packaging application programming interface of a trusted data space to carry out digital object packaging on the to-be-packaged data. The invention further provides a trusted digital object packaging device, equipment, a medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the field of robotic process automation technology, and more specifically, to a trusted digital object encapsulation method, apparatus, device, medium, and product. Background Art

[0002] With the continuous iterative development of information technology, data has become a key production factor, giving rise to a new techno-economic paradigm. The FinTech sector involves a diverse range of data producers, consumers, and interoperable entities, encompassing large institutions such as real economy enterprises, governments, and universities, as well as smaller entities such as individuals. Solutions involving data circulation should ensure efficient and secure data access. Building a trusted data space based on a digital object architecture can further improve the efficiency of data sharing and utilization, and enhance the ability to circulate data elements at scale.

[0003] When promoting the construction of data infrastructure such as trusted data spaces, a common practice is to encapsulate specific data and register it within the digital network using a digital object architecture-based digital network implementation. Encapsulated data, referred to as a digital object, consists of three main components: an identifier, an entity, and metadata. The identifier facilitates rapid routing and parsing of the data within the digital network; the metadata facilitates registry retrieval; and the entity stores the data's physical information. This standardized digital object encapsulation enables rapid data discovery, efficient retrieval, and interoperability.

[0004] When analyzing digital object packaging in the financial sector, we discovered that data production scenarios are complex and diverse. For example, existing data is relatively centralized and distributed across interconnected data centers or other storage formats; incremental data is relatively discrete, with numerous existing data embedding scenarios requiring non-invasive modification; and data integrity varies, with some scenarios involving complex data collection from both internal and external systems. Therefore, it is necessary to provide a digital object packaging method applicable to diverse data production scenarios to build a trusted data space. Summary of the Invention

[0005] In view of the above problems, the present disclosure provides a trusted digital object encapsulation method, apparatus, device, medium, and program product. The encapsulation method includes determining the type of data to be encapsulated according to a preset data type classification rule, obtaining the data to be encapsulated according to a data acquisition rule corresponding to the type of data to be encapsulated, and calling the encapsulation application programming interface of the trusted data space to encapsulate the data to be encapsulated as a digital object. The present disclosure divides the data types to be encapsulated and adopts different data acquisition methods for different types of data to be encapsulated, thereby converting data from its original form in various environments into a digital object in a trusted data space, thereby realizing the construction of a trusted data space and promoting the efficient use of data. In addition, the use of robotic process automation technology to obtain the data to be encapsulated can improve automation efficiency and reduce labor costs and operational risks.

[0006] According to a first aspect of the present disclosure, a trusted digital object encapsulation method is provided, comprising:

[0007] Determining the type of the data to be encapsulated according to a preset data type classification rule, wherein the data type classification rule is obtained based on at least one of the access rights of the encapsulation application programming interface of the trusted data space to the data to be encapsulated, the source of the data to be encapsulated, and the incremental attribute of the data to be encapsulated;

[0008] Acquire the data to be encapsulated according to a data acquisition rule corresponding to the type of the data to be encapsulated;

[0009] The encapsulation application programming interface of the trusted data space is called to perform digital object encapsulation on the data to be encapsulated, wherein the encapsulated data is accessed by at least one digital network node in the trusted data space.

[0010] According to an embodiment of the present disclosure, obtaining the data to be packaged using robotic process automation technology includes:

[0011] Utilizing a robotic process automation designer to develop a robotic process, wherein the robotic process is used to obtain the data to be packaged;

[0012] Utilizing a robotic process automation controller to publish the robotic process and control the scheduling and allocation of data acquisition tasks;

[0013] The robotic process automation client receives and executes the data acquisition task.

[0014] According to an embodiment of the present disclosure, the data type classification rules include:

[0015] If the encapsulation application programming interface of the trusted data space has no access rights to the data to be encapsulated, determining that the data to be encapsulated is first type data, otherwise further determining the source of the data to be encapsulated;

[0016] If the source of the data to be encapsulated includes an external source system, determining that the data to be encapsulated is the second type of data; otherwise, further determining the incremental attribute of the data to be encapsulated, wherein the external source system is a system that is independent of the current system and provides support for the current system;

[0017] If the incremental attribute of the data to be encapsulated has a target value, the data to be encapsulated is determined to be the third type of data; otherwise, the data to be encapsulated is determined to be the fourth type of data.

[0018] According to an embodiment of the present disclosure, the robotic process automation technology is used to simulate the user's operation behavior after obtaining user authorization to obtain the first type of data under the user's authority.

[0019] According to an embodiment of the present disclosure, the robotic process automation technology is used to establish a connection with the external system, and a data request is sent to the external system to obtain the second type of data.

[0020] According to an embodiment of the present disclosure, in response to using the robotic process automation technology to determine that the target value of the incremental attribute of the data to be encapsulated satisfies at least one of the time condition and the characteristic condition, the third type of data is obtained, wherein the time condition includes a rule for automatically triggering data acquisition according to a preset time, and the characteristic condition includes a rule for automatically triggering data acquisition according to a preset data attribute.

[0021] According to an embodiment of the present disclosure, the robotic process automation technology is used to obtain a calling script of the encapsulated application programming interface of the trusted data space, and the calling script is used to collect the existing data stored in the current system to obtain the fourth type of data.

[0022] Another aspect of the present disclosure provides a trusted digital object encapsulation device, configured to execute any of the above-mentioned trusted digital object encapsulation methods, including:

[0023] A data type determination module, configured to determine the type of the data to be encapsulated according to a preset data type classification rule;

[0024] A data acquisition and transmission module, configured to acquire the data to be encapsulated and transmit the data to the encapsulation application programming interface of the trusted data space;

[0025] The data encapsulation module is used to encapsulate the data to be encapsulated into a digital object.

[0026] Another aspect of an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the method described above.

[0027] Another aspect of an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processor is caused to perform the method described above.

[0028] Another aspect of an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0029] One or more of the above embodiments have the following beneficial effects:

[0030] 1. By classifying the types of data to be encapsulated and adopting different data acquisition methods for different types of data to be encapsulated, data can be converted from its original form in various environments into digital objects in a trusted data space, thus realizing the construction of a trusted data space and promoting the efficient use of data;

[0031] 2. Using robotic process automation technology to obtain data to be packaged can accurately capture information, greatly improve automation efficiency, eliminate the need for manual operation, significantly reduce labor costs, and effectively reduce operational risks caused by manual operation errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0033] Figure 1 Schematically illustrates an application scenario diagram of the trusted digital object encapsulation method, apparatus, device, medium, and program product according to an embodiment of the present disclosure;

[0034] Figure 2 Schematically shows a step diagram of a trusted digital object encapsulation method according to an embodiment of the present disclosure;

[0035] Figure 3 Schematically illustrates a step diagram of data type division rules in operation S210 according to an embodiment of the present disclosure;

[0036] Figure 4 Schematically illustrates a step diagram of obtaining data to be packaged by using robotic process automation technology in operation S220 according to an embodiment of the present disclosure;

[0037] Figure 5Schematically illustrates a schematic diagram of the principle of acquiring first type data by using robotic process automation technology in operation S220 according to an embodiment of the present disclosure;

[0038] Figure 6 Schematically illustrates a schematic diagram of the principle of acquiring the second type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure;

[0039] Figures 7a-7b Schematically illustrates a schematic diagram of the principle of acquiring the third type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure;

[0040] Figure 8 Schematically illustrates a schematic diagram of the principle of acquiring the fourth type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure;

[0041] Figure 9 The following schematically shows a flow chart of a trusted digital object encapsulation method according to an embodiment of the present disclosure;

[0042] Figure 10 A structural block diagram of a trusted digital object encapsulation device according to an embodiment of the present disclosure is schematically shown; and

[0043] Figure 11 A block diagram of an electronic device suitable for implementing a trusted digital object packaging method according to an embodiment of the present disclosure is schematically shown.

[0044] It should be noted that, for the sake of clarity, in the drawings used to describe the embodiments of the present disclosure, the sizes of the overall / local structures or overall / local areas may be enlarged or reduced, that is, these drawings are not drawn according to the actual scale. DETAILED DESCRIPTION

[0045] In order to facilitate understanding of the technical solutions of the embodiments of the present disclosure, some technical terms involved in the present disclosure are first introduced.

[0046] Data elements: Data elements are data resources that exist in electronic form and participate in production and business activities through computational means, playing a significant role. In the construction of trusted data spaces, a more mature solution is to implement digital networks and data spaces based on a digital object architecture. The data elements in this solution are embodied as digital objects.

[0047] Digital Object Architecture (DOA): A data-centric, open software architecture proposed by Turing Award winner and father of the Internet, Robert Kahn. DOA consists of a basic model and two foundational protocols. Based on the Digital Object (DO) model, DOA provides a unified, abstract definition of data, masking the heterogeneity of the original data. A digital object consists of three parts: an identifier, metadata, and a data entity. The identifier is the digital object's identity, ensuring it is uniquely identifiable and locatable; metadata is descriptive information about the digital object, used for discovery and retrieval; and the data entity represents the data itself. Systems based on this architecture implement two standard protocols: the Digital Object Identifier / Resolution Protocol (DO-IRP) and the Digital Object Interface Protocol (DOIP). These protocols support access, resolution, retrieval, and use of digital objects.

[0048] The Internet of Data: Based on a software-defined network architecture, this system transforms heterogeneous data through a data-centric, open software system and standardized operating protocols, enabling a "virtual / digital" network above the "physical / machine" network. This Internet of Data architecture creates a data space characterized by "data interconnection, on-demand scheduling, and domain-wide autonomy."

[0049] Trusted Data Space: A place where multiple entities collaborate on data in cyberspace. Under common rules and constraints, participants in this data space share, exchange, and process data based on scenarios, exploring potential pragmatic relationships between data. Data spaces in the financial sector can explore scenarios such as providing inclusive and convenient data services for small and medium-sized enterprises and individual users, and enabling end-to-end data interconnection across the entire industry chain. Trusted Data Spaces ensure that data users can efficiently discover, access, and use data, empowering fintech and promoting the exploration of new financial paradigms.

[0050] Robotic Process Automation (RPA), also known as Digital Labor, is a software solution that uses intelligent software to simulate and enhance the interaction between people and computers and perform repeatable tasks based on certain rules. It can improve enterprise automation efficiency and reduce labor costs and operational risks. RPA technology mainly consists of the following three parts: (1) RPA designer, which is used to develop robotic processes and assist in development based on user UI interaction through screen recording, control capture, etc.; (2) RPA controller, which is used to publish the processes designed by the designer, actually control task scheduling, and assign tasks to each RPA client, and is responsible for supervising, managing and controlling the work process of the RPA client; (3) RPA client, which is the embodiment of the "robot" in RPA technology. It can be deployed on the physical / virtual terminal of the computer, is responsible for executing specific tasks, recording the execution process, and supporting centralized / decentralized deployment. RPA technology is mainly applicable to the following technical scenarios: (1) processes with high repetitiveness, high frequency, and low-value operations; (2) fixed rules that do not require manual complex scenario judgment; (3) the need to interact between multiple heterogeneous scenarios; (4) there are many interacting entities involved, and the probability of manual errors is high; (5) the cost of transforming existing systems is high (the transformation cycle is long and the transformation is difficult).

[0051] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the detailed description below, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0052] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise," "include," etc. used herein indicate the presence of the features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0053] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0054] When expressions such as "at least one of A, B, and C, etc." are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0055] In related technologies, data production scenarios are complex and diverse, including: existing data is relatively concentrated and distributed in interconnected data centers or other storage forms; incremental data points are relatively discrete, and there are many existing data point scenarios, requiring non-invasive transformation methods; there are differences in data integrity, and some scenarios involve data collection from internal / external systems, which is relatively complex.

[0056] The embodiments of the present disclosure provide a trusted digital object encapsulation method, apparatus, device, medium, and product. The trusted digital object encapsulation method includes: determining the type of data to be encapsulated according to a preset data type classification rule, where the data type classification rule is obtained based on at least one of the access rights to the data to be encapsulated, the source of the data to be encapsulated, and the incremental attributes of the data to be encapsulated by the encapsulation application programming interface of the trusted data space; obtaining the data to be encapsulated according to a data acquisition rule corresponding to the type of the data to be encapsulated; and calling the encapsulation application programming interface of the trusted data space to perform digital object encapsulation on the data to be encapsulated, wherein the encapsulated data is accessed by at least one digital network node in the trusted data space.

[0057] In the technical solutions disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0058] Figure 1 The following schematically illustrates an application scenario diagram applicable to the trusted digital object encapsulation method according to an embodiment of the present disclosure.

[0059] like Figure 1As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links or optical fiber cables.

[0060] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. For example, the user can send a digital object packaging instruction to the server 105 through the first terminal device 101, the second terminal device 102, and the third terminal device 103, and the server 105 can implement the digital object packaging method of the embodiment of the present disclosure.

[0061] Various business systems, such as an Enterprise Resource Planning (ERP) system and a Customer Relationship Management (CRM) system, may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103 (for example only). The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices with display screens and web browsing support, including but not limited to smartphones, tablet computers, laptop computers, and desktop computers.

[0062] Server 105 can be a server that provides various services, such as a backend management server (for example only) that supports the business systems browsed by users using first terminal device 101, second terminal device 102, and third terminal device 103. The backend management server can analyze and process received user requests and other data, and provide feedback (e.g., web pages, information, or data obtained or generated based on user requests) to the terminal devices. For example, server 105 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud computing, network services, and middleware services.

[0063] It should be noted that the trusted digital object encapsulation method provided by the embodiment of the present disclosure can generally be executed by a server. Accordingly, the trusted digital object encapsulation device provided by the embodiment of the present disclosure can generally be set in a server.

[0064] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0065] The following will be based on Figure 1 The described scenario provides a detailed description of the trusted digital object encapsulation method of the embodiment of the present disclosure.

[0066] Figure 2 The following schematically shows the steps of the trusted digital object encapsulation method according to an embodiment of the present disclosure.

[0067] like Figure 2 As shown, the trusted digital object encapsulation method of this embodiment includes operations S210 to S230.

[0068] In operation S210, the type of data to be encapsulated is determined according to a preset data type classification rule, where the data type classification rule is obtained based on at least one of the access rights to the data to be encapsulated, the source of the data to be encapsulated, and the incremental attributes of the data to be encapsulated by the encapsulation application programming interface of the trusted data space.

[0069] For example, when analyzing digital object encapsulation in the financial sector, data production scenarios are complex and diverse. For example, existing data is relatively concentrated and distributed across interconnected data centers or other storage formats; incremental data is relatively discrete, and existing data is embedded in a wide variety of scenarios, requiring non-invasive transformation methods; data integrity varies, and some scenarios involve data collection from internal and external systems, which is more complex. Therefore, it is necessary to classify the data types generated in different data production scenarios and adopt different encapsulation measures for different types of data.

[0070] In this embodiment, the data type classification rules are derived based on at least one of the following: access rights, source, and incremental attributes of the data to be encapsulated, as determined by the trusted data space's Encapsulation Application Programming Interface (Encapsulation API). The data type classification rules utilize a multi-level matching mechanism to ensure comprehensive coverage of all data types. By setting these rules, the data type classification can be used to determine at least one of the access rights, source, and incremental attributes of the data to be encapsulated, thereby enabling precise classification and effective management of different data types, providing robust support for data encapsulation and subsequent processing.

[0071] As an example, the access rights of the encapsulation API of the trusted data space to the encapsulated data refer to: whether the trusted data space encapsulation API has access isolation from the data to be encapsulated, for example, whether the data to be encapsulated can be obtained directly through system calls and other means. If the encapsulation API of the trusted data space has no access rights to the encapsulated data, it means that the trusted data space encapsulation API cannot reach the data to be encapsulated, and the trusted data space encapsulation API cannot be directly used to process the data to be encapsulated; conversely, if the encapsulation API of the trusted data space has access rights to the encapsulated data, the trusted data space encapsulation API can be directly used to process the data to be encapsulated.

[0072] As an example, the source of the data to be packaged refers to: the data to be packaged comes from the current system or an external system, wherein the external system is a system that is independent of the current system and provides support for the current system. In this embodiment, the bank system is used as the current system, and the external system can be a UnionPay system, a credit system, a data service system, or other systems that have business cooperation with the bank. That is, the external system is used to achieve cross-system data interaction and business collaboration, helping the bank to complete various business processes. It should be noted that the above system is only an example to illustrate the difference between the current system and the external system. In actual application, the specific meaning of the external system depends on the actual situation. In other optional embodiments, the current system can be other industry systems, which is not limited here.

[0073] For example, the incremental attribute of the data to be packaged refers to whether the data to be packaged is existing data or incremental data. Existing data is centrally stored data, such as data records generated by regular archiving and writing in the current system, distributed across interconnected data centers or other storage formats, such as data warehouses, data lakes, and files. Incremental data is ungenerated data, defined to be compatible with subsequent data production. The services that generate data are distributed across multiple machine environments, and there are multiple discrete data producers for point recording.

[0074] In operation S220, the data to be packaged is obtained according to a data acquisition rule corresponding to the type of the data to be packaged;

[0075] In this embodiment, Robotic Process Automation (RPA) technology is used to obtain the data to be packaged. RPA, a software solution that uses machines as task execution terminals to simulate manual user operations such as mouse clicks, keyboard input, and copy / paste, can streamline task execution based on rules and conditions, improving the automated efficiency of digital object packaging and reducing labor costs and operational risks. In other optional embodiments, artificial intelligence, machine learning, and other technologies can also be used to obtain the data to be packaged, which is not a limitation here.

[0076] In operation S230, the encapsulation application programming interface of the trusted data space is called to perform digital object encapsulation on the data to be encapsulated, wherein the encapsulated data is accessed by at least one digital network node in the trusted data space.

[0077] As an example, the encapsulation API of the trusted data space is called to encapsulate the data to be encapsulated to form a data object that complies with specific standards and formats. The encapsulation API of the trusted data space ensures that the data complies with security and privacy standards during transmission.

[0078] As an example, a trusted data space is a secure and controllable data sharing environment, which consists of multiple data networking nodes. The encapsulated data is accessed by at least one data networking node in the trusted data space. These nodes can be different enterprises, institutions or systems. These nodes share and interact with data through the trusted data space to ensure the secure and compliant transmission of data within the trusted data space.

[0079] Figure 3 The following schematically illustrates a step diagram of data type classification rules in operation S210 according to an embodiment of the present disclosure.

[0080] like Figure 3 As shown, the data type classification rules of this embodiment include operations S310 to S330.

[0081] In operation S310 , if the encapsulation application programming interface of the trusted data space has no access authority to the data to be encapsulated, the data to be encapsulated is determined to be first type data, otherwise the source of the data to be encapsulated is further determined.

[0082] As an example, to determine whether the trusted data space's encapsulation API has access to the data to be encapsulated, the first type of data is data to which the trusted data space's encapsulation API does not have access. In some embodiments, the first type of data may be personal information, such as identity verification information. During the digital object encapsulation process, the trusted data space's encapsulation API may not be able to directly access this identity verification data due to privacy protection and security regulations. In other alternative embodiments, the first type of data may be enterprise information, such as corporate financial statements or corporate planning documents. This data is accessible only to authorized personnel and systems, and the trusted data space's encapsulation API generally does not have access permissions.

[0083] In operation S320 , if the source of the data to be packaged is an external system, the data to be packaged is determined to be second type data; otherwise, an incremental attribute of the data to be packaged is further determined.

[0084] For example, for data to be packaged that has access to the packaging API of the trusted data space, further determination is made as to whether it originates from the current system or an external system. The second type of data is data from external systems. For example, using the current system as a banking system, the second type of data could be publicly available industry research data, such as industry research reports. Industry research reports are typically provided by professional market research institutions and are considered data from external systems.

[0085] In operation S330 , if the incremental attribute of the data to be packaged has the target value, the data to be packaged is determined to be the third type of data; otherwise, the data to be packaged is determined to be the fourth type of data.

[0086] As an example, for the data from the current system, it is further determined whether its incremental attribute has a target value. If it has a target value, it is incremental data and is determined to be the third type of data. Otherwise, it is stock data and is determined to be the fourth type of data.

[0087] By comprehensively considering multi-dimensional characteristics such as data access rights, sources, and incremental attributes, the data to be packaged is divided into four types, so that different data acquisition methods can be used for different types of data to be packaged in the future, and the data can be converted from its original form in diverse environments into digital objects in a trusted data space, thereby promoting the efficient use of data.

[0088] Figure 4 The diagram schematically illustrates a step diagram of obtaining data to be packaged by using robotic process automation technology in operation S220 according to an embodiment of the present disclosure.

[0089] like Figure 4 As shown, the method of obtaining the data to be packaged by using the robotic process automation technology in this embodiment includes operations S410 to S430.

[0090] In operation S410, the RPA designer is used to develop an RPA process for obtaining data to be packaged. For example, auxiliary development based on user UI interaction can be performed by relying on screen recording, control capture, etc.

[0091] In operation S420, the RPA controller publishes the RPA process and controls the scheduling and allocation of data acquisition tasks. For example, the RPA controller allocates data acquisition tasks to each RPA client and is responsible for supervising, managing, and controlling the RPA client's work process.

[0092] In operation S430 , the RPA client receives and executes the data acquisition task. For example, the RPA client, which is the embodiment of the "robot" in RPA technology, is deployed on a physical or virtual computer terminal and is responsible for executing specific tasks and recording the execution process.

[0093] Figure 5The schematic diagram schematically shows the principle of obtaining the first type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure.

[0094] like Figure 5 As shown, in the data production plane, the first type of data is generated in at least one business system, and the encapsulation API of the trusted data space has no access rights to the above-mentioned business system; in the first RPA control plane, the RPA client sends a request to the user to obtain user authorization, and if the user authorizes, simulates the user's operation behavior to obtain the first type of data under the user's authority; in the data storage plane, the obtained first type of data is stored in a database, data warehouse or file, so that it can be subsequently integrated in the second RPA control plane, and encapsulated as a digital object in the encapsulation control plane.

[0095] Through the above steps, the data to be encapsulated is non-invasively read to the encapsulation API side of the trusted data space for encapsulation without the need for data storage. The reading process carries trusted account information, complies with access control principles, and has low risk.

[0096] Figure 6 The schematic diagram schematically shows the principle of obtaining the second type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure.

[0097] like Figure 6 As shown, in one optional embodiment, the source of the data to be packaged consists of the current system and an external system. On the data production plane, RPA technology is used to establish a connection with the external system, send a data request to the external system to obtain the data to be packaged from the external system, and store the data in the external business system. At the same time, the data to be packaged from the current business system is obtained and combined with the data to be packaged stored in the external business system to form the second type of data. On the RPA control plane, the RPA client collects and integrates the second type of data separately, realizing cross-system data collection and integration, so as to facilitate the subsequent digital object packaging on the packaging control plane. In other optional embodiments, the source of the data to be packaged can be only the external system. In this case, the second type of data is the data to be packaged from the external system.

[0098] Through the above steps, foreign-related data can be effectively obtained, and the data originally scattered in the external system and the current system can be integrated to complete the incomplete data, providing a complete and accurate data basis for data encapsulation. In addition, data encapsulation is no longer limited to the current system, and it can flexibly handle scenarios involving foreign-related data, realize the encapsulation of digital objects into the network, and improve the applicability and flexibility of data encapsulation.

[0099] Figure 7a and Figure 7bThe schematic diagram schematically shows the principle of obtaining the third type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure.

[0100] like Figure 7a As shown, in an optional embodiment, on the data production plane, the third type of data is generated in at least one business system, and there are multiple discrete data producers to record the data; on the RPA control plane, the RPA client responds to determining that the data to be packaged meets at least one of the time conditions and characteristic conditions to collect and integrate the third type of data separately, so as to facilitate the subsequent digital object packaging on the packaging control plane.

[0101] As an example, time conditions include rules that automatically trigger data acquisition based on preset times. For example, at a specific time point every day, or a specific day of the week, the RPA client automatically starts the data collection program in response to the preset time point and obtains the latest information from the corresponding current business system to ensure the timeliness and accuracy of the data.

[0102] As an example, characteristic conditions include automatically triggering data acquisition rules based on preset data attributes. For example, when the data meets the preset data attributes, the RPA client automatically starts the data collection program and obtains data that meets the attributes from the corresponding current business system to ensure the accuracy of data collection.

[0103] like Figure 7b As shown, in another optional embodiment, after the RPA control plane and RPA clients separately collect and integrate the third type of data, they centrally store the third type of data in the data storage plane, facilitating subsequent digital object encapsulation in the encapsulation control plane. This centralized data storage approach facilitates unified management and maintenance and can more easily adapt to the addition of new data sources, requiring only integration and configuration on the data storage plane. This approach offers excellent scalability and adaptability.

[0104] Through the above steps, dynamic updating and complete encapsulation of data can be achieved, ensuring the timeliness and integrity of the data encapsulated into the network for digital objects, and effectively compatible with the continuous data production of business systems. In addition, non-invasive transformation methods are adopted to avoid modifying the complex logic of existing business systems, reducing the risk and cost of system transformation. At the same time, with the help of RPA technology, incremental data can be encapsulated into the network, taking into account both the value of data encapsulation and system stability. It is especially suitable for scenarios where the logic of existing systems is complex and the modification cost is high.

[0105] Figure 8 The schematic diagram schematically shows the principle of obtaining the fourth type of data by using the robotic process automation technology in operation S220 according to an embodiment of the present disclosure.

[0106] like Figure 8 As shown, Type 4 data is stored more centrally, typically as data records regularly archived and written by business systems. This represents the stock data of existing business systems and is distributed across interconnected data centers or other storage formats, such as data warehouses, databases, and files. For Type 4 data, the RPA client can be used to obtain a script that calls the trusted data space's encapsulation API. This script, compatible with multiple data storage formats, collects Type 4 data for subsequent digital object encapsulation on the encapsulation control plane.

[0107] Through the above steps, the RPA client can quickly process multi-source heterogeneous data and achieve efficient packaging through script-based API calls, saving time and labor costs and improving packaging efficiency. In addition, the RPA client strictly retrieves and packages data according to preset logic, reducing human errors, ensuring that the packaged data is consistent with the original data, and improving data reliability.

[0108] Figure 9 A flowchart of a trusted digital object encapsulation method according to an embodiment of the present disclosure is schematically shown.

[0109] like Figure 9 As shown, a packaging task is established to determine whether the packaging API of the trusted data space has access rights to the data to be packaged. If not, the data to be packaged is determined to be first-type data. The packaging API of the trusted data space is connected to the first-type data through RPA technology to perform digital object packaging. For the specific principle, please refer to Figure 5 The description is not repeated here.

[0110] If the encapsulated API of the trusted data space has access rights to the data to be encapsulated, the source of the data to be encapsulated is further determined, that is, whether it includes data from an external system. If the data to be encapsulated includes data from an external system, the data to be encapsulated is determined to be second-type data. The second-type data is obtained through RPA technology and digital object encapsulation is performed. For the specific principle, please refer to Figure 6 The description is not repeated here.

[0111] If the source of the data to be packaged does not include data from an external system, the incremental attribute of the data to be packaged is further determined, that is, whether the data to be packaged belongs to existing data or incremental data. If the data to be packaged belongs to incremental data, the data to be packaged is determined to be third-type data. The third-type data is non-invasively collected through RPA technology for digital object packaging. For the specific principle, please refer to the description of Figure 7, which will not be repeated here.

[0112] If the data to be packaged belongs to stock data, it is determined that the data to be packaged is the fourth type of data. For the specific packaging principle, refer to Figure 8 As shown, no further details are given here.

[0113] It should be noted that some steps of the above method can be executed individually or in combination, and can be executed in parallel or sequentially, and are not limited to the specific operation sequence shown in the figure.

[0114] Based on the above-mentioned trusted digital object packaging method, the present disclosure also provides a trusted digital object packaging device. Figure 10 The device is described in detail.

[0115] Figure 10 The structural block diagram of the trusted digital object encapsulation device according to an embodiment of the present disclosure is schematically shown.

[0116] like Figure 10 As shown, the trusted digital object encapsulation device 900 of this embodiment includes a data type determination module 910 , a data acquisition and transmission module 920 , and a data encapsulation module 930 .

[0117] The data type determination module 910 may, for example, perform operation S210 to determine the type of the data to be encapsulated according to a preset data type classification rule.

[0118] According to an embodiment of the present disclosure, the data type determination module 910 can be used to perform operations S310 to S330. It is used to determine the type of the data to be encapsulated according to a preset data type classification rule, wherein the data type classification rule is obtained based on at least one of the access rights of the encapsulation API of the trusted data space to the encapsulated data, the source of the data to be encapsulated, and the incremental attribute of the data to be encapsulated; determining the type of the data to be encapsulated specifically includes: if the encapsulation application programming interface of the trusted data space has no access rights to the encapsulated data, then determining that the data to be encapsulated is the first type of data, otherwise further determining the source of the data to be encapsulated; if the source of the data to be encapsulated is an external system, then determining that the data to be encapsulated is the second type of data, otherwise further determining the incremental attribute of the data to be encapsulated; if the incremental attribute of the data to be encapsulated has a target value, then determining that the data to be encapsulated is the third type of data, otherwise determining that it is the fourth type of data.

[0119] The data acquisition and transmission module 920 may, for example, perform operation S220 to acquire the data to be packaged and transmit the data to the packaging application programming interface of the trusted data space.

[0120] According to an embodiment of the present disclosure, the data acquisition and transmission module 920 can be used to perform operations S410 to S430, which utilize robotic process automation technology to acquire data to be packaged. Specifically, the steps include: using an RPA designer to develop an RPA process for acquiring data to be packaged; using an RPA controller to publish the RPA process and control the scheduling and allocation of data acquisition tasks; and an RPA client receiving and executing the data acquisition task.

[0121] The data encapsulation module 830 may, for example, perform operation S230 to encapsulate the data to be encapsulated into a digital object, specifically including: calling an encapsulation API of the trusted data space to encapsulate the data to be encapsulated into a digital object, wherein the encapsulated data is accessed by at least one network node in the trusted data space.

[0122] For the parts not mentioned in the apparatus part, they can be understood with reference to the various embodiments of the above-mentioned method. That is, the apparatus part includes modules for executing the various steps of any one of the method embodiments described above. In addition, the implementation methods, technical problems solved, functions achieved, and technical effects achieved of each module / unit / subunit, etc. in the apparatus part embodiment are respectively the same or similar to the implementation methods, technical problems solved, functions achieved, and technical effects achieved of each corresponding step in the method part embodiment, and will not be repeated here.

[0123] According to an embodiment of the present disclosure, any multiple modules among the data type determination module 910, the data acquisition and transmission module 920, and the data encapsulation module 930 can be combined into a single module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in a single module.

[0124] According to an embodiment of the present disclosure, at least one of the data type determination module 910, the data acquisition and transmission module 920, and the data encapsulation module 930 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware through any other reasonable means of integrating or encapsulating circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in an appropriate combination of any of them. Alternatively, at least one of the data type determination module 910, the data acquisition and transmission module 920, and the data encapsulation module 930 can be at least partially implemented as a computer program module, which can perform the corresponding function when executed.

[0125] Figure 11A block diagram of an electronic device suitable for implementing a trusted digital object packaging method according to an embodiment of the present disclosure is schematically shown.

[0126] like Figure 11 As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage portion 1008 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0127] Various programs and data required for the operation of the electronic device 1000 are stored in the RAM 1003. The processor 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the programs in the ROM 1002 and / or the RAM 1003. It should be noted that the programs may also be stored in one or more memories other than the ROM 1002 and the RAM 1003. The processor 1001 may also perform various operations of the method flow according to the embodiment of the present disclosure by executing the programs stored in the one or more memories.

[0128] According to an embodiment of the present disclosure, electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to bus 1004. Electronic device 1000 may also include one or more of the following components connected to I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including devices such as a cathode ray tube (CRT), liquid crystal display (LCD), and speakers; a storage section 1008 including a hard disk; and a communication section 1009 including a network interface card such as a LAN card or modem. Communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to I / O interface 1005 as needed. Removable media 1011, such as a magnetic disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed in drive 1010 as needed, so that computer programs read from the removable media can be installed into storage section 1008 as needed.

[0129] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when executed, implements the method according to the embodiments of the present disclosure.

[0130] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, and may include, for example, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above, and / or one or more memories other than ROM 1002 and RAM 1003.

[0131] The embodiments of the present disclosure also include a computer program product, which includes a computer program containing program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiments of the present disclosure.

[0132] The computer program executes the above functions defined in the system / device of the embodiment of the present disclosure when the processor 1001 executes the computer program. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0133] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal on a network medium, downloaded and installed via the communication portion 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0134] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the systems, devices, means, modules, units, etc. described above can be implemented by computer program modules.

[0135] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, languages such as Java, C++, Python, "C" or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect via the Internet).

[0136] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] Those skilled in the art will appreciate that the features described in the various embodiments of the present disclosure may be combined and / or coupled in various ways, even if such combinations or couplings are not explicitly described in the present disclosure. In particular, the features described in the various embodiments of the present disclosure may be combined and / or coupled in various ways without departing from the spirit and teachings of the present disclosure. All such combinations and / or couplings fall within the scope of the present disclosure.

[0138] The embodiments of the present disclosure are described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although each embodiment has been described separately above, this does not mean that the measures in each embodiment cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A trusted digital object encapsulation method, characterized in that: include: Determining the type of the data to be encapsulated according to a preset data type classification rule, wherein the data type classification rule is obtained based on at least one of the access rights of the encapsulation application programming interface of the trusted data space to the data to be encapsulated, the source of the data to be encapsulated, and the incremental attribute of the data to be encapsulated; Acquire the data to be encapsulated according to a data acquisition rule corresponding to the type of the data to be encapsulated; The encapsulation application programming interface of the trusted data space is called to perform digital object encapsulation on the data to be encapsulated, wherein the encapsulated data is accessed by at least one digital network node in the trusted data space.

2. The trusted digital object encapsulation method according to claim 1, characterized in that: The data to be packaged is obtained by using robotic process automation technology, including: Utilizing a robotic process automation designer to develop a robotic process, wherein the robotic process is used to obtain the data to be packaged; Utilizing a robotic process automation controller to publish the robotic process and control the scheduling and allocation of data acquisition tasks; The robotic process automation client receives and executes the data acquisition task.

3. The trusted digital object encapsulation method according to claim 2, characterized in that: The data type classification rules include: If the encapsulation application programming interface of the trusted data space has no access rights to the data to be encapsulated, determining that the data to be encapsulated is first type data, otherwise further determining the source of the data to be encapsulated; If the source of the data to be encapsulated includes an external source system, determining that the data to be encapsulated is the second type of data; otherwise, further determining the incremental attribute of the data to be encapsulated, wherein the external source system is a system that is independent of the current system and provides support for the current system; If the incremental attribute of the data to be encapsulated has a target value, the data to be encapsulated is determined to be the third type of data; otherwise, the data to be encapsulated is determined to be the fourth type of data.

4. The trusted digital object encapsulation method according to claim 3, characterized in that: The robotic process automation technology is used to simulate the user's operation behavior after obtaining the user's authorization to obtain the first type of data under the user's authority.

5. The trusted digital object encapsulation method according to claim 3, characterized in that: The robotic process automation technology is used to establish a connection with the external system, and a data request is sent to the external system to obtain the second type of data.

6. The trusted digital object encapsulation method according to claim 3, characterized in that: In response to using the robotic process automation technology to determine that the target value of the incremental attribute of the data to be encapsulated satisfies at least one of a time condition and a characteristic condition, the third type of data is obtained, wherein the time condition includes a rule for automatically triggering data acquisition according to a preset time, and the characteristic condition includes a rule for automatically triggering data acquisition according to a preset data attribute.

7. The trusted digital object encapsulation method according to claim 3, characterized in that: The robotic process automation technology is used to obtain a calling script of the encapsulated application programming interface of the trusted data space, and the calling script is used to collect the existing data stored in the current system to obtain the fourth type of data.

8. A trusted digital object packaging device, characterized in that: The method for executing the trusted digital object encapsulation method according to any one of claims 1 to 7 comprises: A data type determination module, configured to determine the type of the data to be encapsulated according to a preset data type classification rule; A data acquisition and transmission module, configured to acquire the data to be encapsulated and transmit the data to the encapsulation application programming interface of the trusted data space; The data encapsulation module is used to encapsulate the data to be encapsulated into a digital object.

9. An electronic device comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images