Federal-based transaction management control method and device, equipment and medium

Abstract

The invention provides a federation-based transaction management control method and device, equipment and a medium. The method comprises the following steps: calling a federated protocol manager, and generating a protocol template according to transaction information which is sent by a service provider and negotiates with a service demander offline; calling a federated protocol manager, and generating an access control protocol corresponding to the service provider and an access use protocol corresponding to the service demander according to the protocol template after the protocol template completes auditing confirmation; calling a federated protocol manager, sending the access control protocol to a first transaction controller corresponding to the service provider, and sending the access use protocol to a second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol; and calling the first transaction controller, performing protocol verification on the access use protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification is passed.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, equipment and medium for managing and controlling a transaction based on a federation. Background Art

[0002] With the improvement of the overall digitalization of society and the development of the digital economy, data has become one of the production factors alongside land, labor, capital, technology, etc. The factorization, marketization, and resourceization of data have gradually become a trend. The demand for data sharing and cross-border cooperation within enterprises and between different enterprises is also increasing. Traditionally, there are two common ways to share data:

[0003] 1. Point-to-point data interface access between systems where both parties discuss each matter one by one: Although this model is relatively simple and intuitive, the implementation mechanism is personalized and varies among individuals. It lacks unified support from the underlying management mechanism in terms of security, language standards, and flow supervision. The overall management structure is relatively disordered, and the accumulated investment is difficult to precipitate into the infrastructure to support the development of data elements. It is difficult to adapt to the development requirements of large-scale marketization and resourceization of data elements.

[0004] 2. Data Sharing Center Method: Extract the data that needs to be shared with all parties to the data sharing center and provide access services to all parties. This method is usually suitable for data sharing between different departments within a tightly coupled management unit. For scenarios where data flows and accesses between enterprises and between enterprises and the government are restricted by management authority, responsibility boundaries, trust and confidentiality, it is difficult to adopt this method. In addition, even if it is used within the enterprise, although from a management perspective it can simplify the topology of data flow and supervision to a certain extent and achieve certain data control goals, in some cases it will also produce some disadvantages: (1) The thick centralized model has a long construction period and high investment, and there are problems such as centralized load (data capacity, system performance) bottlenecks and single point risks; (2) The data sharing center has a heavy operational burden, which can easily lead to a contradiction between the supply capacity of the sharing center and the growing application needs of the production system, and cause disputes in terms of security boundaries and operational responsibilities; (3) When storing multiple copies of data, some scenarios require high real-time synchronization, require large resource investment, and require technical and management means to maintain data consistency between the source system, sharing center, and application system, resulting in relatively high management and operation costs; (4) For data transaction scenarios, its versatility, flexibility, and scalability are relatively poor. Summary of the invention

[0005] The technical problem to be solved by the embodiments of the present application is to provide a transaction management and control method, device, equipment and medium based on federation, so as to achieve the lightweight of the data transaction system architecture between data members from a production perspective, and to achieve effective supervision and safe control of data flow and access from a management perspective, and to facilitate the purpose of precipitating an infrastructure that supports the marketization and resource development of data elements.

[0006] In a first aspect, an embodiment of the present application provides a transaction management control method based on a federation, which is applied to a federation management system, including:

[0007] Calling a federation protocol manager to generate a protocol template according to transaction information sent by a service provider and negotiated offline with a service demander, wherein the service provider is a federation member under the federation protocol manager;

[0008] Calling the federal protocol manager, after the protocol template is reviewed and confirmed, generating an access control protocol corresponding to the service provider and an access and use protocol corresponding to the service demander according to the protocol template;

[0009] Calling the federated protocol manager to send the access control protocol to a first transaction controller corresponding to the service provider, and to send the access use protocol to a second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol;

[0010] The first transaction controller is called to perform protocol verification on the access usage protocol in the access request sent by the second transaction controller, and data transaction is performed after the protocol verification passes.

[0011] Optionally, generating an agreement template according to the transaction information sent by the service provider and negotiated offline with the service demander includes:

[0012] Acquire the transaction information filled in by the service provider, the transaction information including: at least one of demander information, accessed object, access method, authority, scope, access trigger condition, validity period, provider address, and settlement rule information;

[0013] The agreement template is generated according to the transaction information.

[0014] Optionally, generating the access control agreement corresponding to the service provider and the access use agreement corresponding to the service demander according to the agreement template includes:

[0015] A semi-automatic generation method is adopted to automatically fill in a framework corresponding to the access control protocol according to the information in the protocol template, and generate an access control protocol corresponding to the service provider;

[0016] Sending the access control protocol to a first transaction controller of the service provider, so that the first transaction controller performs a confirmation operation on the access control protocol;

[0017] After the access control protocol is completed and confirmed, an access use protocol corresponding to the service demander is generated according to the access control protocol.

[0018] Optionally, the step of sending the access and use agreement to a second transaction controller corresponding to the service demander includes:

[0019] In the case where the service demander is not a federation member under the federation protocol manager, the blockchain technology is used to deploy the federation protocol manager corresponding to the service demander and the federation protocol manager corresponding to the service provider in the same blockchain;

[0020] The access and use agreement is sent to a second transaction controller corresponding to the service demander.

[0021] Optionally, the calling of the first transaction controller, performing protocol verification on the access usage protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification passes, includes:

[0022] Calling the first transaction controller to obtain an access request sent by the second transaction controller, wherein the access request carries an access and use agreement corresponding to the service demander;

[0023] Performing protocol verification on the access usage protocol to obtain a protocol verification result;

[0024] When the protocol verification result indicates that the access usage protocol verification is successful, data transaction is performed with the second transaction controller.

[0025] Optionally, the performing data transaction with the second transaction controller includes:

[0026] Locating the accessed object in the system of the service provider;

[0027] Returning a response message to the second transaction controller, so that the second transaction controller establishes a data service link with the first transaction controller according to the response message;

[0028] Execute a transaction operation corresponding to the accessed object with the second transaction controller based on the data service link.

[0029] Optionally, after calling the first transaction controller, performing protocol verification on the access usage protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification passes, the method further includes:

[0030] After the data transaction is completed, calling the first transaction controller to obtain transaction log information and settlement list information;

[0031] The transaction log information and the settlement list information are sent to the federation protocol manager, so that the transaction log information and the settlement list information are stored by the federation protocol manager.

[0032] In a second aspect, an embodiment of the present application provides a federal transaction management control device, which is applied to a federal management system, and the device includes:

[0033] The protocol template generation module is used to call the federation protocol manager to generate a protocol template according to the transaction information sent by the service provider and negotiated offline with the service demander, wherein the service provider is a federation member under the federation protocol manager;

[0034] An access protocol generation module is used to call the federal protocol manager, and after the protocol template is reviewed and confirmed, generate an access control protocol corresponding to the service provider and an access use protocol corresponding to the service demander according to the protocol template;

[0035] An access protocol sending module, used to call the federated protocol manager, send the access control protocol to the first transaction controller corresponding to the service provider, and send the access use protocol to the second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol;

[0036] The data transaction module is used to call the first transaction controller, perform protocol verification on the access usage protocol in the access request sent by the second transaction controller, and perform data transaction after the protocol verification passes.

[0037] Optionally, the protocol template generating module includes:

[0038] A transaction information acquisition unit, used to acquire the transaction information filled in by the service provider, wherein the transaction information includes at least one of: demander information, accessed object, access method, authority, scope, access trigger condition, validity period, provider address, and settlement rule information;

[0039] The protocol template generating unit is used to generate the protocol template according to the transaction information.

[0040] Optionally, the access protocol generation module includes:

[0041] An access control protocol generation unit, configured to automatically fill in a framework corresponding to the access control protocol according to information in the protocol template in a semi-automatic generation manner, and generate an access control protocol corresponding to the service provider;

[0042] A control protocol confirmation unit, configured to send the access control protocol to a first transaction controller of the service provider, so that the first transaction controller performs a confirmation operation on the access control protocol;

[0043] The access and use agreement generating unit is used to generate an access and use agreement corresponding to the service demander according to the access control agreement after the access control agreement is confirmed.

[0044] Optionally, the access protocol sending module includes:

[0045] A protocol manager deployment unit, configured to deploy the federation protocol manager corresponding to the service demander and the federation protocol manager corresponding to the service provider in the same blockchain using blockchain technology when the service demander is not a federation member under the federation protocol manager;

[0046] The access protocol sending unit is used to send the access use protocol to the second transaction controller corresponding to the service demander.

[0047] Optionally, the data transaction module includes:

[0048] An access request acquisition unit, configured to call the first transaction controller to acquire an access request sent by the second transaction controller, wherein the access request carries an access usage agreement corresponding to the service demander;

[0049] A verification result acquisition unit, used to perform protocol verification on the access and use protocol to obtain a protocol verification result;

[0050] The data transaction unit is used to perform data transaction with the second transaction controller when the protocol verification result indicates that the access usage protocol verification is successful.

[0051] Optionally, the data transaction unit includes:

[0052] An object locating subunit, used to locate the accessed object in the system of the service provider;

[0053] a response message returning subunit, configured to return a response message to the second transaction controller, so that the second transaction controller establishes a data service link with the first transaction controller according to the response message;

[0054] The transaction operation execution subunit is used to execute the transaction operation corresponding to the accessed object with the second transaction controller based on the data service link.

[0055] Optionally, the device further comprises:

[0056] A log list acquisition module, used to call the first transaction controller to obtain transaction log information and settlement list information after the data transaction is completed;

[0057] The log list sending module is used to send the transaction log information and the settlement list information to the federal protocol manager, so that the federal protocol manager stores the transaction log information and the settlement list information.

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

[0059] A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the federation-based transaction management control method described above is implemented.

[0060] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any of the above-mentioned federal-based transaction management control methods.

[0061] Compared with the prior art, the embodiments of the present application have the following advantages:

[0062] In an embodiment of the present application, by calling the federal protocol manager, a protocol template is generated according to the transaction information sent by the service provider and the service demander for offline negotiation, wherein the service provider is a federal member under the federal protocol manager. The federal protocol manager is called, and after the protocol template is reviewed and confirmed, the access control protocol corresponding to the service provider and the access and use protocol corresponding to the service demander are generated according to the protocol template. The federal protocol manager is called to send the access control protocol to the first transaction controller corresponding to the service provider, and the access and use protocol is sent to the second transaction controller corresponding to the service demander, so that the access control protocol is loaded by the first transaction controller and the access and use protocol is loaded by the second transaction controller. The first transaction controller is called to perform protocol verification on the access and use protocol in the access request sent by the second transaction controller, and data transactions are performed after the protocol verification is passed. In an embodiment of the present application, a federal protocol management system based on the underlying management mechanism of the protocol is designed, and the access control protocol and the access and use protocol are generated by the federal protocol manager, and the data transaction is completed by the transaction controllers of the provider and the demander. It can not only achieve the lightweight of the data transaction architecture between data members from a production perspective, but also realize the effective supervision and safe control of data flow and access from a management perspective, and is conducive to the precipitation of infrastructure to support the marketization and resource development of data elements.

[0063] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 A flowchart of a transaction management control method based on a federation provided in an embodiment of the present application;

[0065] Figure 2 A schematic diagram of a logical relationship architecture provided in an embodiment of the present application;

[0066] Figure 3 A schematic diagram of a data transaction protocol generation and loading process provided in an embodiment of the present application;

[0067] Figure 4 A schematic diagram of a data transaction execution process provided in an embodiment of the present application;

[0068] Figure 5 A schematic diagram of a blockchain deployment mode provided for an embodiment of the present application;

[0069] Figure 6 A schematic diagram of a hybrid deployment mode provided in an embodiment of the present application;

[0070] Figure 7 A schematic diagram of the structure of a federal transaction management control device provided in an embodiment of the present application;

[0071] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0073] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0074] Reference Figure 1 , shows a flowchart of a transaction management control method based on a federation provided by an embodiment of the present application, which method can apply a federal protocol management system. Figure 1 As shown, the federal transaction management control method may include: step 101, step 102, step 103 and step 104.

[0075] Step 101: calling a federation protocol manager to generate a protocol template according to transaction information sent by a service provider and negotiated offline with a service demander, wherein the service provider is a federation member under the federation protocol manager.

[0076] The embodiments of the present application can be applied to scenarios where data transactions are performed in a federated data management framework based on the underlying management mechanism of the protocol.

[0077] Data transaction: a transaction in a broad sense, including but not limited to data acquisition or access under a certain payment agreement, data acquisition or access in the form of non-paid data collaboration, etc.

[0078] The embodiments of the present application can be applied to a federated protocol management system, that is, the execution subject is a federated management system. Federated data management: each data group is managed as an independent federation, and group members are federation members. Several federations can form a larger federation. Federated data management is to provide overall control and collaborative operation management for federation members. The architecture of the federated management system can be as follows: Figure 2 As shown, it may include: a federation protocol manager, federation members, and a transaction controller corresponding to each federation member.

[0079] The federation protocol manager is responsible for managing and maintaining the protocol specifications for communication and interaction between federation members. It ensures that all federation members follow unified communication standards and data exchange formats, thereby achieving seamless transmission and sharing of information. In addition, the federation protocol manager may also include functions such as protocol version control, protocol update, and compatibility check to ensure the stability and scalability of the system.

[0080] In this example, the federation protocol manager has the following roles:

[0081] 1. Responsible for registering federation members. The protocol manager is the portal for federation members to join the system and is responsible for receiving and reviewing registration applications from new members. Through the registration process, the protocol manager ensures that each member meets the basic requirements of the system and assigns it a unique identity.

[0082] 2. Register the data subjects and details that the federation members can provide for transactions. During the member registration process, the protocol manager will also collect and record the data subjects and details that each member is willing to provide or request. This information is crucial for subsequent data exchange and service matching.

[0083] 3. Provide members with the ability to browse and retrieve data topics and details. The protocol manager maintains a data directory that contains data topics and details provided by all members. Members can browse and retrieve this data through the interface or API provided by the protocol manager to discover potential trading partners and data sources.

[0084] 4. Provide fillable and configurable (service) agreement templates for data suppliers. The content of the supplier (service) agreement template instance may include but is not limited to: demander information, accessed objects, access methods, permissions, scope, access trigger conditions, validity period, service provider address, settlement rules, etc.). In order to standardize the process of data exchange and service provision, the protocol manager provides a series of customizable agreement templates. Suppliers can fill in and configure these templates according to their own needs.

[0085] 5. Based on the (service) agreement template approved by the supply and demand parties or a third party, generate an operating agreement corresponding to the agreement template instance for the supply and demand parties: that is, the (demand party) access and use agreement, and the (supplier party) access control agreement. Among them, the (supplier party) access control agreement is semi-automatically generated (the supplier participates in the configuration of some technical related links), and the (demand party) access and use agreement (corresponding to the access control agreement) is automatically generated. Once the supply and demand parties or a third party have approved the service agreement template, the agreement manager will automatically generate the corresponding operating agreement. These operating agreements include the demand party access and use agreement and the supplier access control agreement.

[0086] 6. Distribute the corresponding operating agreements to both parties. The protocol manager is responsible for distributing the generated operating agreements to both parties. In this way, both parties can clearly understand their rights and obligations in the transaction, as well as the access control and usage rules that should be followed.

[0087] 7. Receive transaction logs and settlement lists after the execution of the running protocol (initiated by the demander) from the data supplier (through the transaction controller). During the transaction, the data supplier will record the transaction logs and settlement lists through its transaction controller. Once the transaction is completed, this information will be fed back to the protocol manager. The protocol manager is responsible for receiving and processing this information for subsequent auditing, settlement, and dispute resolution.

[0088] Federation members are entities or organizations that participate in the federation management system. They can be different systems, applications, services or devices. As long as they can communicate and interact in accordance with the protocol specifications established by the federation protocol manager, they can become federation members. Data supply and demand parties, a member can play both supply and demand roles.

[0089] The transaction controller corresponding to each federation member is responsible for managing and controlling the member's transaction behavior in the federation management system. It may include functions such as processing transaction requests, verifying transaction data, feedback on transaction results, and recording transaction logs. The transaction controller ensures the fairness, security, and efficiency of the transaction process.

[0090] In this example, the transaction controller has the following functions:

[0091] 1. Load the corresponding operating protocols distributed from the protocol manager for both data supply and demand parties. The primary task of the transaction controller is to receive the operating protocols distributed by the protocol manager and load these protocols into the local system. These operating protocols define the interaction rules, access rights, data formats and other key information between data supply and demand parties, and are the basis for data interaction.

[0092] 2. There can be multiple protocols in a transaction controller, and the protocols and the supply and demand parties appear in pairs. The transaction controller supports the management of multiple running protocols at the same time, and each protocol corresponds to a pair of supply and demand parties. This design allows the transaction controller to handle multiple data interaction tasks at the same time, improving the efficiency and flexibility of the system.

[0093] 3. As an agent for data interaction between data supply and demand parties, it is responsible for protocol-based control and access, and also plays the role of a security isolator. The transaction controller is not only a channel for data interaction, but also plays the role of a control and access agent. It strictly controls and manages data transmission according to the loaded operating protocol to ensure that only requests that comply with the protocol can be responded to. At the same time, the transaction controller also acts as a security isolator to prevent unauthorized data access and leakage, and ensure data security and privacy.

[0094] 4. Encapsulate and provide unified link encryption, secure access control, transaction monitoring and other common underlying capabilities. In order to ensure the security and reliability of data interaction, the transaction controller encapsulates a series of common underlying capabilities, including link encryption, secure access control and transaction monitoring. Link encryption technology can protect the confidentiality and integrity of data during transmission; the secure access control mechanism can ensure that only legitimate requesters can obtain data access rights; the transaction monitoring function can track and record the data interaction process in real time, which is convenient for subsequent auditing and troubleshooting.

[0095] In the specific implementation, the service demander can read and retrieve the data topics and details of interest, contact the supplier and communicate and negotiate offline to reach a consensus and agreement. The specific process is as follows:

[0096] 1. The service demander will first browse the data directory maintained by the protocol manager through the interface or API provided by the federation management system. This directory contains the data topics and detailed information provided by all federation members. The demander can use keyword search, category browsing and other methods to quickly locate the data topics of interest according to their interests and needs.

[0097] 2. Once the data subject and details of interest are determined, the demander will try to contact the data provider (supplier). This is usually done through the contact methods provided by the federal management system, such as email, phone or instant messaging tools.

[0098] 3. Offline communication and negotiation. Since data exchange may involve complex commercial terms, technical details and security requirements, the supply and demand parties often need to conduct in-depth offline communication and negotiation. In this process, the two parties will discuss in detail and reach a consensus on key issues such as data access rights, usage, price, settlement method, data security, etc.

[0099] Furthermore, the federation protocol manager can be called to generate an agreement template according to the transaction information sent by the service provider and negotiated offline with the service demander, wherein the service provider can be a federation member under the federation protocol manager. The specific implementation process can be: 1. Obtain the transaction information filled in by the service provider, and the transaction information can include: demander information (such as company name, contact person, etc.), accessed object (such as data set, API (Application Program Interface, application programming interface) interface, etc.), access method (such as API call, direct access, etc.), permission (such as read and write permission, query permission, etc.), scope (such as data range, time range, etc.), access trigger condition (such as event trigger, scheduled task, etc.), validity period, provider address (server address or contact information of the service provider), settlement rule information (such as fee calculation method, payment method, etc.) and other information. 2. Generate an agreement template according to the transaction information. That is, the federation protocol manager automatically generates a specific agreement template instance (that is, the agreement template in this example) according to the parameters entered by the supplier, and this instance contains all customized agreement terms and conditions.

[0100] After the federated protocol manager is called to generate a protocol template according to the transaction information sent by the service provider and negotiated offline with the service demander, step 102 is executed.

[0101] Step 102: calling the federated protocol manager, and after the protocol template is reviewed and confirmed, generating the access control protocol corresponding to the service provider and the access and use protocol corresponding to the service demander according to the protocol template.

[0102] After calling the federal protocol manager to generate an agreement template based on the transaction information sent by the service provider and the service demander for offline negotiation, the federal protocol manager can send the agreement template to the service provider for review and confirmation. Specifically, the supplier initiates the online review and confirmation process of the (service provider) agreement template instance. If there are third-party regulatory requirements other than the supply and demand parties, it will be transferred to the third-party regulator for approval, and after approval, it will be transferred to the demander for confirmation. Then, the demander (i.e. the service demander) completes the online confirmation of the (service provider) agreement template instance.

[0103] After completing the audit confirmation process, the federal protocol manager can be called to generate the access control protocol corresponding to the service provider and the access and use protocol corresponding to the service demander according to the protocol template. Specifically, a semi-automatic generation method can be used to automatically fill in the framework corresponding to the access control protocol according to the information in the protocol template to generate the access control protocol corresponding to the service provider. Then, the access control protocol can be sent to the first transaction controller of the service provider so that the first transaction controller can perform a confirmation operation on the access control protocol. After the access control protocol is confirmed, the access and use protocol corresponding to the service demander is generated according to the access control protocol.

[0104] In actual applications, the protocol manager starts to generate access control protocols for suppliers based on the confirmed protocol templates. This process is semi-automatic, which means that during the generation process, the supplier needs to participate in the configuration of some technical-related links. These configurations may include the agreement and parameters of the supplier service agent (or program) access method or interface, the setting of access rights, the formulation of security policies, and other specific technical parameters. The supplier completes the configuration of these technical-related links through the interface or tools provided by the protocol manager based on its own technical capabilities and service requirements. This design not only ensures the flexibility of the protocol, but also ensures that the supplier can effectively control and manage its services. After the supplier completes the configuration of the access control protocol, the protocol manager will automatically generate the corresponding access and use agreement for the demander based on the generated supplier access control agreement. This process is fully automated and does not require the demander to directly participate in the configuration, thereby improving efficiency. The demander's access and use agreement will specify in detail how the demander accesses and uses the services provided by the supplier, including access methods, usage restrictions, service guarantees, fault handling, etc. These contents need to match the terms in the supplier's access control agreement to ensure a balance of rights and interests between the two parties and smooth service.

[0105] After the access control agreement and the access use agreement are generated, step 103 is executed.

[0106] Step 103: Call the federal protocol manager to send the access control protocol to the first transaction controller corresponding to the service provider, and send the access use protocol to the second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol and the second transaction controller loads the access use protocol.

[0107] In this example, the first transaction controller refers to a transaction controller of a service provider, and the second controller refers to a transaction controller of a service demander.

[0108] After the access control agreement and access use agreement are generated, the federation protocol manager can be called to send the access control agreement to the first transaction controller corresponding to the service provider, and the first transaction controller loads the access control agreement to limit or allow users to access system resources. It ensures that only authorized users can access specific information or perform specific operations, protects system resources from unauthorized access, and prevents data leakage, tampering or destruction.

[0109] At the same time, the federal protocol manager can be called to send the access and use agreement to the second transaction controller corresponding to the service demander, and the second transaction controller loads the access and use agreement to stipulate the rules and agreements that the service demander should follow when using the resources of the service provider, such as transaction limits, transaction times, etc.

[0110] The first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol, which is an important part of system security management and resource use control. The two work together to ensure the security of system resources and the compliance of user behavior.

[0111] In this example, if the service demander is a federation member under the federation protocol manager, it can be sent directly. If it is not a federation member under the federation protocol manager, the blockchain technology can be used to merge the federation protocol managers of the service provider and the service demander to exchange information. Specifically, when the service demander is not a federation member under the federation protocol manager, the blockchain technology can be used to deploy the federal protocol manager corresponding to the service demander and the federal protocol manager corresponding to the service provider in the same blockchain. The access and use agreement is sent to the second transaction controller corresponding to the service demander.

[0112] In this example, the following system topology architectures can be used according to different scenarios in actual system deployment:

[0113] 1. Data transactions between non-trusted members (such as between enterprises and between countries): For federation members under the same federation, since the protocol manager cannot be deployed on a trusted independent third party, the blockchain model can be adopted, such as Figure 5 As shown, multiple federation protocol managers deployed on the blockchain are merged into a unified federation protocol manager A, so that information interaction between federation members 1 to 5 can be realized.

[0114] 2. Data transactions between trusted members (such as within an enterprise): The protocol manager can be deployed in a third-party independent centralized manner. The protocol manager can also be deployed in a certain federation member for use by the entire federation.

[0115] 3. Hybrid deployment mode: (1) Federation merger: A small federation (C) can be merged into a larger federation (A). Figure 6 As shown in the figure, the original federation (C) composed of members 5 / 6 / 7 joins the federation (A) deployed in the blockchain structure through its protocol manager, and members 5 / 6 / 7 become members of the larger federation (A). (2) Joining of non-federal structure data groups: Non-federal structure data groups can be treated as a whole and can be joined to the federation as a member node using a unified external gateway. Figure 6 The internal structure of the federation member 4 is a system group (B) that shares data around a data center. The data center can be turned into a federation member as a unified gateway for the internal systems of the system group (B) to the outside world.

[0116] The solution provided in the embodiment of the present application has an architecture with good privacy security and traffic controllability: only the protocol manager can be added to the blockchain, and the data transaction itself does not go through the blockchain, but through a protocol-based transaction controller to conduct data transactions between the two parties, which is beneficial to improving security and reducing traffic overhead.

[0117] Step 104: calling the first transaction controller, performing protocol verification on the access usage protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification passes.

[0118] After the first transaction controller and the second transaction controller complete the loading of the corresponding protocol, the first transaction controller can be called to perform protocol verification on the access use protocol in the access request sent by the second transaction controller, and data transaction can be performed after the protocol verification passes. The specific process can be: calling the first transaction controller to obtain the access request sent by the second transaction controller, and the access request carries the access use protocol corresponding to the service demander. And perform protocol verification on the access use protocol to obtain the protocol verification result. Finally, when the protocol verification result indicates that the access use protocol verification is successful, data transaction can be performed with the second transaction controller.

[0119] Specifically, the transaction implementation process may be: first locate the accessed object in the system of the service provider, and return a response message to the second transaction controller, so that the second transaction controller establishes a data service link with the first transaction controller according to the response message, and performs a transaction operation corresponding to the accessed object with the second transaction controller based on the data service link.

[0120] In a specific implementation of the present application, after the transaction is completed, the first transaction controller may be called to obtain transaction log information and settlement list information, and the transaction log information and settlement list information may be sent to the federation protocol manager so that the transaction log information and settlement list information are stored by the federation protocol manager.

[0121] The embodiments of the present application can achieve lightweight data transaction architecture between data members (i.e., federation members). When faced with scenarios where there are a large number of members demanding data sharing transactions, the solution is simple and easy to implement, and the investment, management, and operating costs are greatly reduced compared to traditional methods.

[0122] Next, combine Figure 3 The data transaction protocol generation and loading process is described in detail as follows. Figure 3 As shown, the process may include:

[0123] Step 31: Register as a federation member in the protocol manager (if any), and register the data topics and details that the federation member can trade.

[0124] Step 32: (Demander) reads and retrieves data topics and details of interest, contacts suppliers and conducts offline communication and negotiation to reach a consensus and agreement.

[0125] Step 33: The supplier generates an agreement template instance online through the agreement manager: The supplier fills in and configures the (service provider) agreement template, including but not limited to: demander information, accessed object, access method, authority, scope, access trigger conditions, validity period, service provider address, settlement rules, etc., and generates the corresponding (service provider) agreement template instance.

[0126] Step 34: The supplier initiates (service provider) the online review and confirmation process of the agreement template instance.

[0127] Step 3401: Based on step 34, if there is a third-party supervision requirement other than the supply and demand parties, it will be transferred to the third-party supervisor for approval, and after approval, it will be transferred to the demander for confirmation.

[0128] Step 35: Based on step 34 or 3401, the demander completes online confirmation of the (service provider) agreement template instance.

[0129] Step 36: The protocol manager generates an operation protocol corresponding to the protocol template instance for both the supply and demand parties based on the confirmed (service) protocol template: namely, the (demand party) access and use protocol and the (supply party) access control protocol. As follows:

[0130] The protocol manager semi-automatically generates (supplier) access control protocols (the supplier participates in the configuration of some technology-related links).

[0131] Based on the generated (supplier) access control protocol, the protocol manager automatically generates the corresponding (demander) access and usage protocol.

[0132] Step 37: The protocol manager distributes the access control protocol and the access usage protocol to the transaction controllers corresponding to the supply and demand parties respectively.

[0133] Step 38: The transaction controllers of both the supply and demand sides complete the protocol loading respectively.

[0134] Next, combine Figure 4 The data transaction execution process is described in detail. Figure 4 As shown, the data transaction execution process may include:

[0135] Step 41: Before the demander initiates access to a supplier, the demander first selects and confirms an internal adapter module (including a program and its parameters) corresponding to a supplier's protocol.

[0136] Step 42: The demander's adaptation module initiates an access request to the supplier via the transaction controller.

[0137] Step 43: After receiving the request, the transaction controller corresponding to the supplier performs protocol verification.

[0138] Step 4301: Based on step 43, if the protocol does not match (such as expired, inconsistent with the agreement, visitor address restricted, etc.), it is rejected and responded.

[0139] Step 44: Based on step 43, if the protocol verification is passed, the supplier transaction controller completes the location of the accessed object in the supplier system, starts the service ready state, and feeds back a response to the demander's transaction controller.

[0140] Step 45: The transaction controller on the demand side receives the response, completes the establishment of the data service link with the supplier, and executes related agreed operations.

[0141] Step 46: After the relevant operations are completed, the supplier's corresponding transaction controller sends the transaction log and settlement list to the protocol manager.

[0142] The transaction management and control method based on the federation provided in the embodiment of the present application generates a protocol template by calling the federation protocol manager, according to the transaction information sent by the service provider and the service demander for offline negotiation, wherein the service provider is a federation member under the federation protocol manager. The federation protocol manager is called, and after the protocol template is reviewed and confirmed, the access control protocol corresponding to the service provider and the access and use protocol corresponding to the service demander are generated according to the protocol template. The federation protocol manager is called to send the access control protocol to the first transaction controller corresponding to the service provider, and the access and use protocol is sent to the second transaction controller corresponding to the service demander, so that the access control protocol is loaded by the first transaction controller and the access and use protocol is loaded by the second transaction controller. The first transaction controller is called to perform protocol verification on the access and use protocol in the access request sent by the second transaction controller, and data transactions are performed after the protocol verification is passed. The embodiment of the present application designs a federation protocol management system based on the underlying management mechanism of the protocol, and the access control protocol and the access and use protocol are generated by the federation protocol manager, and the data transaction is completed by the transaction controllers of the provider and the demander. It can not only achieve the lightweight of the data transaction architecture between data members from a production perspective, but also realize the effective supervision and safe control of data flow and access from a management perspective, and is conducive to the precipitation of infrastructure to support the marketization and resource development of data elements.

[0143] Reference Figure 7 , shows a schematic diagram of the structure of a federal transaction management control device provided by an embodiment of the present application, which can apply a federal protocol management system. Figure 7 As shown, the federated transaction management control device 700 may include the following modules:

[0144] The protocol template generation module 710 is used to call the federation protocol manager to generate a protocol template according to the transaction information sent by the service provider and the service demander for offline negotiation, wherein the service provider is a federation member under the federation protocol manager;

[0145] The access protocol generation module 720 is used to call the federated protocol manager, and after the protocol template is reviewed and confirmed, generate the access control protocol corresponding to the service provider and the access use protocol corresponding to the service demander according to the protocol template;

[0146] The access protocol sending module 730 is used to call the federated protocol manager to send the access control protocol to the first transaction controller corresponding to the service provider, and to send the access use protocol to the second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol;

[0147] The data transaction module 740 is used to call the first transaction controller, perform protocol verification on the access usage protocol in the access request sent by the second transaction controller, and perform data transaction after the protocol verification passes.

[0148] Optionally, the protocol template generating module includes:

[0149] A transaction information acquisition unit, used to acquire the transaction information filled in by the service provider, wherein the transaction information includes at least one of: demander information, accessed object, access method, authority, scope, access trigger condition, validity period, provider address, and settlement rule information;

[0150] The protocol template generating unit is used to generate the protocol template according to the transaction information.

[0151] Optionally, the access protocol generation module includes:

[0152] An access control protocol generation unit, configured to automatically fill in a framework corresponding to the access control protocol according to information in the protocol template in a semi-automatic generation manner, and generate an access control protocol corresponding to the service provider;

[0153] A control protocol confirmation unit, configured to send the access control protocol to a first transaction controller of the service provider, so that the first transaction controller performs a confirmation operation on the access control protocol;

[0154] The access and use agreement generating unit is used to generate an access and use agreement corresponding to the service demander according to the access control agreement after the access control agreement is confirmed.

[0155] Optionally, the access protocol sending module includes:

[0156] A protocol manager deployment unit, configured to deploy the federation protocol manager corresponding to the service demander and the federation protocol manager corresponding to the service provider in the same blockchain using blockchain technology when the service demander is not a federation member under the federation protocol manager;

[0157] The access protocol sending unit is used to send the access use protocol to the second transaction controller corresponding to the service demander.

[0158] Optionally, the data transaction module includes:

[0159] An access request acquisition unit, configured to call the first transaction controller to acquire an access request sent by the second transaction controller, wherein the access request carries an access usage agreement corresponding to the service demander;

[0160] A verification result acquisition unit, used to perform protocol verification on the access and use protocol to obtain a protocol verification result;

[0161] The data transaction unit is used to perform data transaction with the second transaction controller when the protocol verification result indicates that the access usage protocol verification is successful.

[0162] Optionally, the data transaction unit includes:

[0163] An object locating subunit, used to locate the accessed object in the system of the service provider;

[0164] a response message returning subunit, configured to return a response message to the second transaction controller, so that the second transaction controller establishes a data service link with the first transaction controller according to the response message;

[0165] The transaction operation execution subunit is used to execute the transaction operation corresponding to the accessed object with the second transaction controller based on the data service link.

[0166] Optionally, the device further comprises:

[0167] A log list acquisition module, used to call the first transaction controller to obtain transaction log information and settlement list information after the data transaction is completed;

[0168] The log list sending module is used to send the transaction log information and the settlement list information to the federal protocol manager, so that the federal protocol manager stores the transaction log information and the settlement list information.

[0169] The transaction management and control device based on the federation provided in the embodiment of the present application generates a protocol template by calling the federation protocol manager, according to the transaction information sent by the service provider and the service demander for offline negotiation, wherein the service provider is a federation member under the federation protocol manager. The federation protocol manager is called, and after the protocol template is reviewed and confirmed, the access control protocol corresponding to the service provider and the access and use protocol corresponding to the service demander are generated according to the protocol template. The federation protocol manager is called to send the access control protocol to the first transaction controller corresponding to the service provider, and the access and use protocol is sent to the second transaction controller corresponding to the service demander, so that the access control protocol is loaded by the first transaction controller and the access and use protocol is loaded by the second transaction controller. The first transaction controller is called to perform protocol verification on the access and use protocol in the access request sent by the second transaction controller, and data transactions are performed after the protocol verification is passed. The embodiment of the present application designs a federal protocol management system based on the underlying management mechanism of the protocol, and the access control protocol and the access and use protocol are generated by the federal protocol manager, and the data transactions are completed by the transaction controllers of the provider and the demander. It can not only achieve the lightweight of the data transaction architecture between data members from a production perspective, but also realize the effective supervision and safe control of data flow and access from a management perspective, and is conducive to the precipitation of infrastructure to support the marketization and resource development of data elements.

[0170] An embodiment of the present application also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the above-mentioned federal-based transaction management control method when executed by the processor.

[0171] Figure 8 FIG. 8 is a schematic diagram showing the structure of an electronic device 800 according to an embodiment of the present invention. Figure 8 As shown, the electronic device 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 802 or computer program instructions loaded from a storage unit 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic device 800 can also be stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0172] Multiple components in the electronic device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, a microphone, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a disk, an optical disk, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the electronic device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0173] The various processes and processing described above may be performed by the processing unit 801. For example, the method of any of the above embodiments may be implemented as a computer software program, which is tangibly contained in a computer-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the CPU 801, one or more actions in the method described above may be performed.

[0174] In addition, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned federal-based transaction management control method is implemented.

[0175] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0176] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0177] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminals (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0178] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0179] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal so that a series of operating steps are executed on the computer or other programmable terminal to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable terminal. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0180] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

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

[0182] The above is a detailed introduction to a federal-based transaction management and control method, a federal-based transaction management and control device, an electronic device and a computer-readable storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A transaction management control method based on federation, characterized in that: Applied to a federal management system, the method includes: Calling a federation protocol manager to generate a protocol template according to transaction information sent by a service provider and negotiated offline with a service demander, wherein the service provider is a federation member under the federation protocol manager; Calling the federal protocol manager, after the protocol template is reviewed and confirmed, generating an access control protocol corresponding to the service provider and an access and use protocol corresponding to the service demander according to the protocol template; Calling the federated protocol manager to send the access control protocol to a first transaction controller corresponding to the service provider, and to send the access use protocol to a second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol; The first transaction controller is called to perform protocol verification on the access usage protocol in the access request sent by the second transaction controller, and data transaction is performed after the protocol verification passes.

2. The method according to claim 1, characterized in that The generating of the agreement template according to the transaction information sent by the service provider and the service demander for offline negotiation includes: Acquire the transaction information filled in by the service provider, the transaction information including: at least one of demander information, accessed object, access method, authority, scope, access trigger condition, validity period, provider address, and settlement rule information; The agreement template is generated according to the transaction information.

3. The method according to claim 1, characterized in that The step of generating the access control agreement corresponding to the service provider and the access use agreement corresponding to the service demander according to the agreement template includes: A semi-automatic generation method is adopted to automatically fill in a framework corresponding to the access control protocol according to the information in the protocol template, and generate an access control protocol corresponding to the service provider; Sending the access control protocol to a first transaction controller of the service provider, so that the first transaction controller performs a confirmation operation on the access control protocol; After the access control protocol is completed and confirmed, an access use protocol corresponding to the service demander is generated according to the access control protocol.

4. The method according to claim 1, characterized in that: The step of sending the access and use agreement to a second transaction controller corresponding to the service demander includes: In the case where the service demander is not a federation member under the federation protocol manager, the blockchain technology is used to deploy the federation protocol manager corresponding to the service demander and the federation protocol manager corresponding to the service provider in the same blockchain; The access and use agreement is sent to a second transaction controller corresponding to the service demander.

5. The method according to claim 1, characterized in that The calling of the first transaction controller, performing protocol verification on the access usage protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification passes, includes: Calling the first transaction controller to obtain an access request sent by the second transaction controller, wherein the access request carries an access and use agreement corresponding to the service demander; Performing protocol verification on the access usage protocol to obtain a protocol verification result; When the protocol verification result indicates that the access usage protocol verification is successful, data transaction is performed with the second transaction controller.

6. The method according to claim 5, characterized in that The performing data transaction with the second transaction controller includes: Locating the accessed object in the system of the service provider; Returning a response message to the second transaction controller, so that the second transaction controller establishes a data service link with the first transaction controller according to the response message; Execute a transaction operation corresponding to the accessed object with the second transaction controller based on the data service link.

7. The method according to claim 1, characterized in that After calling the first transaction controller, performing protocol verification on the access usage protocol in the access request sent by the second transaction controller, and performing data transaction after the protocol verification passes, the method further includes: After the data transaction is completed, calling the first transaction controller to obtain transaction log information and settlement list information; The transaction log information and the settlement list information are sent to the federation protocol manager, so that the transaction log information and the settlement list information are stored by the federation protocol manager.

8. A transaction management control device based on a federation, characterized in that: Applied to a federal management system, the device comprises: The protocol template generation module is used to call the federation protocol manager to generate a protocol template according to the transaction information sent by the service provider and negotiated offline with the service demander, wherein the service provider is a federation member under the federation protocol manager; An access protocol generation module is used to call the federal protocol manager, and after the protocol template is reviewed and confirmed, generate an access control protocol corresponding to the service provider and an access use protocol corresponding to the service demander according to the protocol template; An access protocol sending module, used to call the federated protocol manager, send the access control protocol to the first transaction controller corresponding to the service provider, and send the access use protocol to the second transaction controller corresponding to the service demander, so that the first transaction controller loads the access control protocol, and the second transaction controller loads the access use protocol; The data transaction module is used to call the first transaction controller, perform protocol verification on the access usage protocol in the access request sent by the second transaction controller, and perform data transaction after the protocol verification passes.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor implements the federated transaction management control method according to any one of claims 1 to 7 when executing the program.

10. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the federated transaction management control method described in any one of claims 1 to 7.

Images