CN116245622A

CN116245622A - Block chain-based production and fusion service system and method and electronic equipment

Info

Publication number: CN116245622A
Application number: CN202310503403.7A
Authority: CN
Inventors: 蒋海; 王静茹; 刘文杰; 袁建勇
Original assignee: Bubi Beijing Network Technology Co ltd
Current assignee: Bubi Beijing Network Technology Co ltd
Priority date: 2023-05-06
Filing date: 2023-05-06
Publication date: 2023-06-09

Abstract

The embodiment of the application provides a block chain-based production and fusion service system, a block chain-based production and fusion service method and electronic equipment. The system comprises a block chain-based fusion service system and a system management system, wherein the block chain-based fusion service system comprises a gateway interface layer, a data processing layer and a fusion service layer; the data processing layer comprises a blockchain network and a database; the gateway interface layer is used for connecting the fusion operation end, the fusion service end and the fusion platform end into the fusion service system; the production and fusion service layer comprises a production and fusion center management module and a basic service module; the fusion center management module is used for providing account management service for the fusion service provider and the fusion platform so that the fusion service provider and the fusion platform can realize the butt joint of fusion service through the fusion service system.

Description

Block chain-based production and fusion service system and method and electronic equipment

Technical Field

The present disclosure relates to the field of blockchain technologies, and in particular, to a blockchain-based fusion service system, a blockchain-based fusion service method, and an electronic device.

Background

The current production and fusion service (industrial financial service) has become a hotspot of social economy, the production and fusion service is the fusion of industry and financial industry, and the problems of difficult financing, expensive financing and other social economy of small and micro enterprises can be solved through the production and fusion service.

In the related art, a product fusion platform serving as a supply chain financial system is respectively in butt joint with each financial institution serving as a product fusion service provider, and the business process and the wind control management of each product fusion platform are required to be matched with the personalized requirements of each financial institution. Because each time of docking between the fusion platform and different financial institutions needs to repeatedly establish a business cooperation mode and a system docking work, the problems of long fusion service docking flow, long transaction flow, high management cost and the like exist in the related technology.

Therefore, how to efficiently and safely realize the butt joint between the fusion platform and the fusion service provider is a technical problem to be solved.

Disclosure of Invention

The embodiment of the application provides a block chain-based fusion service system, a block chain-based fusion service method and electronic equipment, which are used for realizing the butt joint between a fusion platform and a fusion service provider efficiently and safely.

One embodiment of the present application provides a blockchain-based production and fusion service system, the system including: a block chain-based fusion service system, which is characterized by comprising a gateway interface layer, a data processing layer and a fusion service layer; wherein the data processing layer comprises a blockchain network and a database; the gateway interface layer is used for connecting the fusion operation end, the fusion service end and the fusion platform end into the fusion service system; the fusion service terminal is a terminal used by a fusion service provider for accessing the fusion service system, and the fusion platform terminal is a terminal used by a fusion platform for accessing the fusion service system; the production and fusion service layer comprises a production and fusion center management module and a basic service module; the fusion center management module is used for providing account management service for the fusion service provider and the fusion platform so that the fusion service provider and the fusion platform can realize the butt joint of fusion service through the fusion service system; the basic service module at least comprises a key management service unit, a uplink service unit, a file service unit and a timing task unit; the blockchain network is used for realizing transaction corresponding to the fusion service between the fusion service provider and the fusion platform through intelligent contracts.

In some embodiments, the gateway interface layer is further configured to provide the targeted service to a service platform of the non-registered user, the service platform being a converged service provider or a converged platform, by: responding to an API request of the service platform, which carries a group of APIkey and APISECret, and inquiring whether a target service corresponding to the API request exists or not to the production and fusion center management module; returning an access token generated by the fused center station management module to the service platform under the condition that the target service exists; wherein the access token is valid within a preset time period; responding to the service request carried by the service platform with the access token, and sending the service request to the fused center management module so that the fused center management module performs verification processing on the access token and provides service corresponding to the service request according to the result of the verification processing; the production and fusion center management module is further configured to provide the target service to the service platform by: responding to the received API request sent by the gateway interface layer, and inquiring whether a target service corresponding to the API request exists or not; generating the access token in the presence of the target service, and associating the access token with information of the service platform; returning the token to a gateway interface layer; and responding to the service request carrying the access token received from the gateway interface layer, performing verification processing on the access token, and providing the target service according to the result of the verification processing.

In some embodiments, the account management service includes a fusion service provisioning service; the production and fusion center management module realizes the production and fusion service opening service for the target service platform by the following steps: responding to the operation that the fusion operation terminal triggers to enable or disable the fusion service of the target service platform, and acquiring contract operation data for enabling or disabling the fusion service of the target service platform; assembling the contract operation data, generating contract operation executable by a node of a blockchain, and sending the contract operation to the target service platform for signature operation; submitting the signed contract operation to the blockchain network;

and modifying the state information of the fusion service of the target service platform in the database.

In some embodiments, the account management service further comprises an provisioning service account service; the production and fusion center management module realizes the service of the opening service account by the following steps: responding to receiving an account opening request carrying account opening information sent by a target fusion platform, and checking whether the account opening information is legal or not; under the condition that the account opening information is legal, sending the account opening request to a fusion producing service end corresponding to the account opening request, so that the fusion producing service end opens a service account for an initiator of the account opening request according to the account opening information, and generates service account information corresponding to the service account; acquiring the service account information from the fusion server; encrypting the service account information by using a key acquired from the key management service unit; and the service account information after encryption is uplink through the uplink service unit so as to establish a blockchain account corresponding to the service account in the blockchain network, and an intelligent contract is called to generate an address of the blockchain account.

In some embodiments, the account management service further includes an add bank card account service; the production and fusion center management module realizes the service of adding the bank card account by the following steps: responding to a service request for adding a bank card, which is sent by a target fusion producing platform and carries account information of the bank card, and checking whether the service request is a service request for adding the bank card for the first time; under the condition that the service request is the service request for adding the bank card for the first time, encrypting the account information of the bank card by utilizing the key acquired from the key management service unit; the bank card account information subjected to encryption processing is uplink through the uplink service unit so as to establish a corresponding block chain account of the bank card in the block chain network, and an intelligent contract is called to generate an address of the block chain account; or returning to the blockchain account address corresponding to the bank card under the condition that the service request is the service request for not adding the bank card for the first time.

In some embodiments, the account management service further includes a sub-account management service for sub-accounts; the sub-account is an account of an enterprise accessing the target production platform, and the sub-account management service at least comprises a binding card service, a card releasing service, a recharging service, a cash withdrawal service, a transfer service, a fund freezing service, a fund thawing service, a transaction receipt downloading service, an account fund information inquiry service and a transaction running water inquiry service; the production and fusion center management module realizes sub-account management service of the target sub-account by executing the following steps: responding to a sub-account management service request carrying sub-account information sent by a target fusion platform, and executing a preset operation corresponding to the sub-account management service; under the condition that the sub-account management service can be executed, sending the sub-account management service request to a fused service end corresponding to the sub-account management service request, so that the fused service end executes the sub-account management service; and updating the state information of the sub-account in a database according to the execution result of the fusion server, and returning the execution result to the target fusion platform.

In some embodiments, the fusion center management module is further configured to provide trade authenticity verification services for the fusion service provider and the fusion platform; the trade authenticity verification service at least comprises an invoice identification service and an invoice verification service; the production and fusion center management module realizes invoice identification service through the following steps of; receiving an OCR file of at least one invoice from a target fusion platform, storing the OCR file into the file service unit, and returning a file identification of the OCR file acquired from the file service unit to the target fusion platform; responding to an invoice identification service request which is triggered by the target production and fusion platform and carries a file identification of an invoice to be identified, and acquiring an OCR file of the invoice to be identified from the file service unit according to the file identification; the OCR file of the invoice to be identified is sent to a target producing and thawing service end, so that the target producing and thawing service end carries out OCR identification on the invoice to be identified; and returning the OCR recognition result to the target fusion platform.

In some embodiments, the production and fusion center management module provides invoice verification services for a target production and fusion platform by; responding to an invoice verification service request which is triggered by a target production and fusion platform and carries information of an invoice to be verified, and determining whether the invoice to be verified is verified and whether the invoice to be verified is in a revocation state or a red-flushing state according to the information of the invoice to be verified; under the condition that the invoice to be verified is not verified, and the invoice to be verified is in a non-revocation state or a red-flushing state, the invoice to be verified is sent to a target producing and thawing service end, so that the target producing and thawing service end carries out verification on the invoice to be verified; if the verification result is successful, inputting the information of the invoice to be verified into the database, and setting the blockchain state of the invoice to be verified as initialization; and returning the verification result to the target fusion platform.

In some embodiments, the timed task unit is configured to perform an invoice chaining operation; the timing task unit realizes the invoice chaining operation in a preset time interval through the following steps: acquiring information of a to-be-uplink invoice with a blockchain state being initialized from the database; inquiring whether the invoice to be uploaded exists in an invoice contract deployed in the blockchain network; submitting contract operations to update invoice information to the blockchain network under the condition that the invoice information to be uploaded is recorded in the invoice contract; or submitting contract operation for registering invoice information to the blockchain network under the condition that the invoice information to be uploaded is not recorded in the invoice contract; and changing the blockchain state of the invoice to be uploaded in the database into submitted.

In some embodiments, the timed task unit is further configured to perform a query transaction status task; the timing task unit realizes the task of inquiring the transaction state within the preset time interval through the following steps: acquiring record information of a transaction to be updated of a transaction state of an un-updated blockchain from the database; submitting a contract operation to the blockchain network for querying a transaction state of the transaction to be updated; under the condition that the blockchain network returns the transaction result of the transaction to be updated, updating the transaction state of the transaction to be updated in the database according to the transaction result; and under the condition that the blockchain network does not return the transaction result of the transaction to be updated and the submitting time of the transaction to be updated exceeds the preset duration, determining the transaction state of the transaction to be updated as transaction failure, and updating the transaction state of the transaction to be updated in the database as transaction failure.

One of the embodiments of the present application provides a blockchain-based fusion service method, which is applied to the blockchain-based fusion service system as described above, and includes:

and the target fusion platform is used for carrying out butt joint of fusion service with one or more fusion service providers through account management service provided by the fusion service system.

In some embodiments, the method further comprises: and the target fusion service provider responds to the service request of the target fusion platform and provides trade authenticity verification service for the target fusion platform through the trade authenticity verification service provided by the fusion service system.

The embodiment of the application provides an electronic device, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the method when running the program.

The present embodiments provide a storage medium storing a computer readable program which, when executed, performs the method as described above.

Compared with the prior art, the technical scheme provided by the embodiment of the application has at least the following advantages:

in the embodiment provided by the application, the gateway interface layer accesses the fusion operation end, the fusion service end and the fusion platform end into the fusion service system; the fusion center management module in the fusion service layer provides account management service for the fusion service provider and the fusion platform so that the fusion service provider and the fusion platform realize the butt joint of fusion service through the fusion service system; the blockchain network is used for realizing transaction corresponding to the fusion service between the fusion service provider and the fusion platform through the intelligent contract. Because the blockchain has the characteristics of decentralization, non-falsification, whole-course trace, disclosure transparency and the like, the characteristics ensure the integrity and transparency of the fusion service between the fusion service provider and the fusion platform realized based on the blockchain, thereby realizing the butt joint between the fusion service provider and the fusion platform with high efficiency and safety.

Drawings

The present application will be further illustrated by way of example embodiments, which will be described in detail with reference to the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:

FIG. 1 is an exemplary schematic diagram of a docking relationship between a fusion platform and a fusion service provider in the related art;

FIG. 2 is an exemplary schematic diagram illustrating a docking relationship between a fusion platform and a fusion service provider according to some embodiments of the present application;

FIG. 3 is an exemplary schematic diagram of a blockchain-based fusion service system shown in accordance with some embodiments of the present application;

FIG. 4 is an exemplary flow chart of a blockchain-based fusion service method shown in accordance with some embodiments of the present application;

FIG. 5 is an exemplary schematic diagram of a storage structure for account contracts shown in accordance with some embodiments of the present application;

FIG. 6 is an exemplary diagram of a storage structure of an invoice contract, shown in accordance with some embodiments of the present application;

FIG. 7 is an exemplary diagram of a plaintext structure of an invoice plaintext privacy information portion according to some embodiments of the present application;

fig. 8 is an exemplary structural schematic diagram of an electronic device, according to some embodiments of the present application.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the description of the embodiments will be briefly described below. It is apparent that the drawings in the following description are only some examples or embodiments of the present application, and it is obvious to those skilled in the art that the present application may be applied to other similar situations according to the drawings without inventive effort. Unless otherwise apparent from the context of the language or otherwise specified, like reference numerals in the figures refer to like structures or operations.

It will be appreciated that "system," "apparatus," "unit" and/or "module" as used herein is one method for distinguishing between different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words may be replaced by other expressions.

As used in this application and in the claims, the terms "a," "an," "the," and/or "the" are not specific to the singular, but may include the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus.

Flowcharts are used in this application to describe the operations performed by systems according to embodiments of the present application. It should be appreciated that the preceding or following operations are not necessarily performed in order precisely. Rather, the steps may be processed in reverse order or simultaneously. Also, other operations may be added to or removed from these processes.

Fig. 1 is an exemplary schematic diagram of a docking relationship between a fusion platform and a fusion service provider in the related art.

As shown in fig. 1, the fusion platform a needs to establish a business cooperation mode and perform system interfacing with the service providers a, B, C and D, respectively, so that a user (e.g., enterprise a) can apply for a fusion service provided by one or more of the service providers a, B, C and D through the fusion platform a.

FIG. 2 is an exemplary schematic diagram illustrating a docking relationship between a fusion platform and a fusion service provider according to some embodiments of the present application.

As shown in fig. 2, the fusion platform a only needs to access the fusion service system provided in the embodiment of the present application, and a user (for example, enterprise a) may apply for a fusion service provided by one or more of the service provider a, the service provider B, the service provider C and the service provider D that have access to the fusion service system through the fusion platform a.

For ease of understanding, the blockchain-based fusion service system provided herein is described below in connection with the accompanying drawings and embodiments.

FIG. 3 is an exemplary schematic diagram of a blockchain-based fusion service system shown in accordance with some embodiments of the present application.

In a specific implementation process, the architecture of the fusion service system can be implemented in various manners. By way of example only, embodiments provided herein employ a micro-service architecture to implement the overall architecture of a converged service system. In the architecture of a micro-service, there are multiple services receiving requests from external users (clients), and typically the services are not directly exposed to the external users, but a gateway is added in the middle as a control point for the external users to access the internal services. For external user access requests, we typically want to authenticate in the gateway, know who the user is, and can define access control policies.

As shown in fig. 3, the blockchain-based fusion service system includes a gateway interface layer, a data processing layer, and a fusion service layer.

In some embodiments, the gateway interface layer is configured to access the fusion operation end, the fusion service end, and the fusion platform end to the fusion service system; the fusion operation end is a terminal used by an operator of the fusion service system to access the fusion service system, the fusion service end is a terminal used by a fusion service provider to access the fusion service system, and the fusion platform end is a terminal used by a fusion platform to access the fusion service system.

The fusion service provider may include, but is not limited to: banking, non-banking financial institutions (non-bank financial institutions). Non-banking financial institutions may include small loan companies, insurance companies, and the like.

The fusion platform can be a service platform built by a large enterprise for asset management, and can also be a service platform built by a third party outside the enterprise and a fusion service provider for fusion service docking.

The operator of the fusion service system is an enterprise or other organization that performs operation management on the fusion service system.

And the operation end face of the production and fusion provides functions of access, auditing, service configuration and the like of the production and fusion service provider and the production and fusion platform for operators of the super node.

As shown in fig. 3, the fusion operation end, the fusion service end and the fusion platform end may send a communication request to the gateway interface layer through the network, and perform data or information interaction with the fusion service system. The network may be any one or more of a wired network or a wireless network. For example, the network may include a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), etc., or any combination thereof.

The gateway interface layer performs user login authentication verification on the registered function interface of the fusion service management class.

The gateway interface layer performs AppKey, appSecret authentication check on the open API interface. The AppKey is a public key (corresponding to an account number), and the AppSecret is a private key (corresponding to a password).

In some embodiments, the gateway interface layer provides the targeted services to the service platform of the non-registered user, which is either a converged service provider or a converged platform, by:

responding to an API request of a service platform carrying a group of APIkey and APISECret, and inquiring whether a target service corresponding to the API request exists or not to a production and fusion center management module; returning a token (access token) generated by the production center management module to the service platform when the target service exists; wherein the access token is valid for a preset period of time; responding to the service request carried by the service platform and accessing the token, and sending the service request to the production center management module so that the production center management module can carry out verification processing on the access token and provide service corresponding to the service request according to the result of the verification processing.

Correspondingly, the production and fusion center management module provides the target service for the service platform in the following manner:

Responding to the received API request sent by the gateway interface layer, and inquiring whether a target service corresponding to the API request exists; generating an access token in the presence of the target service, and associating the access token with the information of the service platform; returning the token to the gateway interface layer; and responding to the received service request carrying the access token from the gateway interface layer, checking the access token and providing the target service according to the result of the checking.

In some embodiments, the data processing layer includes a blockchain network and a database.

In the implementation process, the storage of data such as accounts, transactions and the like of the fusion service system and the cache function required by data processing in the running process of the fusion service system can be realized by using database management software such as MySQL, redis and the like.

The blockchain network provides complete blockchain base functions and intelligent contract functions. In the implementation process, the transaction corresponding to the fusion service between the fusion service provider and the fusion platform can be realized through intelligent contracts deployed in the blockchain network.

Smart contracts are a set of digitally defined commitments that include agreements on which contract participants can perform. Alternatively, a smart contract may be understood as a piece of program deployed on a computer system that may be automatically executed when a trigger condition of the smart contract is satisfied.

The advent of blockchains provides technical support for the implementation of smart contracts. The intelligent contracts are written into the blockchain in a digital mode, and the storage, reading and execution of the intelligent contracts are transparent, trackable and unchangeable through the characteristics of the blockchain technology. On the other hand, a set of state machine systems can be built by the self-contained consensus algorithm of the blockchain, so that the intelligent contracts can run efficiently.

After the intelligent contract is created, a contract account corresponding to the intelligent contract appears on the blockchain network and has a specific address, and the contract code and the account storage can be stored in the contract account. The behavior of the smart contract is controlled by the contract code, and the account store of the smart contract maintains the state of the contract. In other words, the smart contract causes a virtual account to be generated on the blockchain that includes the contract code and account store.

In the implementation process, a user can call the intelligent contract by submitting contract operation to the blockchain system, set the data recorded in the intelligent contract, and store the set intelligent contract in the blockchain. Accordingly, when a specific condition of the intelligent contract is triggered, the blockchain node may execute the intelligent contract and record an execution result of the intelligent contract, and an execution state of the intelligent contract.

In some embodiments, the data processing layer further includes a file storage system (e.g., minIO) through which high-performance, distributed file storage functions can be provided for service files in the fusion service system, and support for subsequent auxiliary storage, disaster recovery, and archiving, among other schemes.

In some embodiments, the basic service module further includes an parsing service unit, which can provide interface docking and unified data parsing functions for different fusion service providers and fusion platforms.

In some embodiments, as shown in fig. 3, the fusion service layer includes a fusion center management module and a base service module; the fusion center management module is used for providing account management service for the fusion service provider and the fusion platform so that the fusion service provider and the fusion platform realize the butt joint of fusion service through the fusion service system; the basic service module at least comprises a key management service unit, a uplink service unit, a file service unit, an analysis service unit and a timing task unit.

In some embodiments, the account management service includes a fusion service provisioning service. The production and fusion center management module can realize the production and fusion service opening service for the target service platform through the following steps:

Responding to the operation that the fusion operation terminal triggers to enable or disable the fusion service of the target service platform, and acquiring contract operation data for enabling or disabling the fusion service of the target service platform; assembling contract operation data, generating contract operations (such as BOLB data) executable by nodes of the blockchain, and sending the contract operations to a target service platform for signature operations; submitting the signed contract operation to a blockchain network; and modifying the state information of the fusion service of the target service platform in the database.

The target service platform may be a fusion service provider or a fusion platform. After the method enables the production and fusion service for the target platform, the target service platform can conduct the production and fusion service (such as financing clearing service and the like) related to the authorization.

In some embodiments, the account management service further includes an provisioning service account service. The production and fusion center management module can realize the service of opening the service account by the following steps:

in response to receiving an account opening request carrying account opening information sent by a target fusion platform, checking whether the account opening information is legal or not; under the condition that the account opening information is legal, sending an account opening request to a production and fusion service end corresponding to the account opening request, so that the production and fusion service end opens a service account for an initiator of the account opening request according to the account opening information, and generates service account information corresponding to the service account; acquiring service account information from a production and fusion server; encrypting the service account information by using the key acquired from the key management service unit; and (3) the encrypted service account information is uplink through the uplink service unit so as to establish a blockchain account corresponding to the service account in the blockchain network, and an intelligent contract is called to generate an address of the blockchain account.

By way of example only, enterprise a may establish an account for performing a fusion service at a fusion server B by the method described above, while establishing a blockchain account in a blockchain network of the fusion service system. After the blockchain account is established, the fusion service between the enterprise A and the fusion server B can be realized through the blockchain account.

In some embodiments, the account management service further includes an add bank card account service. The production and fusion center management module can realize the addition of the bank card account service by the following steps:

responding to a service request for adding a bank card, which is sent by a target fusion producing platform and carries account information of the bank card, and checking whether the service request is a service request for adding the bank card for the first time; under the condition that the service request is the service request for adding the bank card for the first time, encrypting the account information of the bank card by utilizing the key acquired from the key management service unit; the method comprises the steps that through a uplink service unit, the encrypted account information of the bank card is uplink to establish a corresponding blockchain account of the bank card in a blockchain network, and an intelligent contract is called to generate an address of the blockchain account; or returning to the blockchain account address corresponding to the bank card under the condition that the service request is the service request of not adding the bank card for the first time.

By way of example only, the fusion service system may establish blockchain accounts in the blockchain network for the user enterprise C of the fusion platform a to be on the bank card of the fusion service provider (e.g., bank B) by the method described above.

In some embodiments, the account management service further includes a sub-account management service for sub-accounts; the sub-account management service at least comprises a binding card service, a card releasing service, a recharging service, a cash-out service, a transfer service, a fund freezing service, a fund thawing service, a transaction receipt downloading service, an account fund information inquiry service and a transaction running water inquiry service.

In an implementation, the production center management module deploys account contracts in the blockchain network for the storage structure shown in FIG. 5.

Included in the account contract is an account service builder BID (blockchain account address). For example, enterprise A is the operator of the capacity service system, and this field is the account address of enterprise A on the blockchain.

An account service BID (blockchain account address) address list is included in the account contract. For example, a user enterprise B of the fusion platform a applies for opening a service account to a fusion service provider C through a fusion service system, and after the service account is opened, a blockchain account corresponding to the account is established in a blockchain network, wherein the blockchain account is an account service address.

The account contract includes the following contract function:

a contract initialization (init) function for initializing contract base information that is invoked at the time of account contract deployment, the function's entry function being: init, the afferent json structure is:

{

"params":{

"platformBid":"",

"platformSubBid":""

}

the core logic of the function includes: the headers information of the initialization contract, and the service builder BID and account service BID.

An account service BID address list authorization (authorization) function for authorizing a specified account service BID that can operate a business function of a contract after authorization. The function can authorize a plurality of addresses in the blockchain network, the authorized account can write data into the account contract, and the concurrency processing capability of the blockchain network can be improved by Tuesday. The entry function of this function is: main, join json structure is as follows:

{

"method":"authorize"

"params":{

"platformSubBid":""

}

the core logic of the function includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; verifying that the target service BID address is not in the authorization list; the specified BID is added to the authorization list.

The cancel account service BID address list authorization (cancelauthorization) function is used to cancel authorization to specify a service BID that does not allow operation of the contract business function after the authorization is canceled. The entry function of this function is: main. The parametrization json structure of this function is as follows:

{

"method":"cancel-authorize"

"params":{

"platformSubBid":""

}

The core logic of the function includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; verifying that the target service BID address is already in the authorization list; the specified BID is removed from the authorization list.

A closing contract (closecontact) function for closing the current contract, the closed contract no longer accepting the data change. The entry function of this function is: main. The parametrization json structure of this function is as follows:

{

"method":"close-contract"

}

the core logic of the function includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; the contract status is modified to header.status to END and the closing time endTime is updated.

A register account (register) function for: the bank account is registered on the chain and this function is invoked when the bank card account information is to be linked up. The entry function of this function is: main. The parametrization json structure of this function is as follows:

{

"method":"register"

"params":{

"accountBid":"",

"accountName":"",

"accountNo":"",

"accountHash":"",

"accountType":"",

"bankName":"",

"bankCnaps":"",

"headOfficeOfBankCode":"",

"headOfficeOfBankName":"",

"customerBid":"",

"ext":{

"serviceProviderMerchantCode":""

},

"status":"",

"verificationStatus":"",

"encrypt":{

"isEncrypted":"",

"algorithm":"",

"identity":"",

"encryptionType":""

}

the logic of the function core includes: checking the contract state header status as INIT; checking that only authorized service BID triggers are allowed; verifying that the target account BID does not exist in the contract; the account information is stored in the contract.

The modified account status (modified status) is used to update the status of the bank account and is invoked when the bank account is modified. The entry function of this function is: main. The parametrization json structure of this function is as follows:

{

"method":"modify-status"

"params":{

"accountBid":"",

"status":"",

"verificationStatus":""

}

the core logic of the function includes: checking the contract state header status as INIT; checking that only authorized service BID triggers are allowed; verifying that the target account exists in the contract; performing verification control on status and not performing control on the verifiability status; and updating the data of the appointed account.

And inquiring an account information (querybibid) function according to the account BID, wherein the function is used for acquiring all information of a designated account BID according to the account BID, and is called when inquiring the account information. The entry function of this function is: and query. The parametrization json structure of this function is as follows:

{

"method":"query-by-bid"

"params":{

"accountBid":""

}

the production and fusion center management module realizes sub-account management service of the target sub-account by executing the following steps:

responding to a sub-account management service request carrying sub-account information sent by a target fusion platform, and executing a preset operation corresponding to the sub-account management service; under the condition that the sub-account management service can be executed, sending a sub-account management service request to a fused service end corresponding to the sub-account management service request, so that the fused service end executes the sub-account management service; and updating the state information of the sub-account in the database according to the execution result of the fusion server, and returning the execution result to the target fusion platform.

For example, the enterprise A initiates a binding card (binding a bank card and an account number) service request through the fusion platform B, and the fusion platform management module checks whether the bank card is bound or not, and if so, the fusion platform prompts that the bank card is bound; if not, calling a binding card interface provided by the fusion producing service provider, and realizing binding operation by the fusion producing service provider; and the production and fusion center management module updates the bank card information of the sub-account of the enterprise A in the database according to the execution result of the production and fusion server, and returns the execution result to the target production and fusion platform.

In the specific implementation process, the card releasing service, the recharging service, the presenting service, the transferring service, the fund freezing service, the fund thawing service, the transaction receipt downloading service, the account fund information inquiry service, the transaction flow inquiry service and the like are realized by the method, and the detailed description is omitted.

In some embodiments, the fusion center management module is further configured to provide trade authenticity verification services for the fusion service provider and the fusion platform; the trade authenticity verification service at least comprises an invoice identification service and an invoice verification service.

In the specific implementation process, the production and fusion center management module can realize invoice identification service through the following steps of; receiving an OCR file of at least one invoice from a target fusion platform, storing the OCR file into a file service unit, and returning a file identification of the OCR file acquired from the file service unit to the target fusion platform; responding to an invoice identification service request which is triggered by a target production and fusion platform and carries a file identification of an invoice to be identified, and acquiring an OCR file of the invoice to be identified from a file service unit according to the file identification; the method comprises the steps of sending an OCR file of an invoice to be identified to a target producing and thawing service end so that the target producing and thawing service end carries out OCR identification on the invoice to be identified; and returning the result of OCR recognition to the target fusion platform.

In the financing business, if the financing enterprise needs to upload a large number of invoices, the invoices are uploaded in a manual filling mode, so that manpower resources are consumed, and meanwhile, errors in filling invoice information are difficult to avoid. The financing enterprise can accurately and efficiently submit the invoice from the production and fusion platform to the production and fusion server through the method.

In some embodiments, the production and fusion center management module may provide invoice verification services for the target production and fusion server platform by; responding to an invoice verification service request carrying information of an invoice to be verified, triggered by a target production and fusion platform, and determining whether the invoice to be verified is verified and whether the invoice to be verified is in a revocation state or a red punching state according to the information of the invoice to be verified; under the conditions that the invoice to be verified is not verified, and the invoice to be verified is in a non-revocation state or a red flushing state, the invoice to be verified is sent to the target producing and thawing service end, so that the target producing and thawing service end carries out verification on the invoice to be verified; under the condition that the verification result is successful, inputting the information of the invoice to be verified into a database, and setting the blockchain state of the invoice to be verified as initialization; and returning the verification result to the target fusion platform. And directly returning the checking result under the condition that the invoice to be checked is checked or the invoice to be checked is in a revocation state or a red punching state.

In the specific implementation process, the financing enterprise can take the invoice as a certificate to carry out bill financing to the financing service provider. Bill financing refers to a bank credit service in which bill holders transfer commercial bills to banks when funds are insufficient, the banks deduct the cash interest according to the amount of the bill, and pay the balance to the payee, and is a financial requirement of enterprises for accelerating the turnover of funds and promoting commodity transaction.

In the bill financing process, the payoff service provider needs to verify the invoice for financing provided by the financing enterprise, and proves that the receivables are generated by a real trade behavior, so that risk control is performed. An invoice may have a number of states: a normal state, a voided state, and a red flush state, only invoices in the normal state may be used for financing.

In the specific implementation process, the production and fusion service provider can verify the invoice provided by the financing enterprise through the invoice verification service provided by the production and fusion service system, so that the authenticity of the invoice can be verified, the invoice with the state of being voided or red flushed can be filtered, and the safety guarantee is provided for bill financing.

In a specific implementation, the timing task unit in the basic service module may be implemented based on XXL-JOB. XXL-JOB is an open-source middleware for managing timing tasks, is a central scheduling platform, is lightweight, is used after being opened, and is easy to operate.

In some embodiments, a timed task unit in the base service module may perform invoice chaining operations. The timing task unit can realize invoice linking operation in a preset time interval through the following steps:

acquiring information of a to-be-uplink invoice with a blockchain state being initialized from a database; inquiring whether the invoice contract deployed in the blockchain network has the information of the invoice to be uploaded; submitting contract operation for updating invoice information to the blockchain network under the condition that the invoice information to be uploaded is recorded in the invoice contract; or submitting contract operation for registering invoice information to the blockchain network under the condition that the information of the invoice to be uploaded is not recorded in the invoice contract; and changing the blockchain state of the invoice to be uploaded in the database into submitted state.

In the production and fusion business, a large amount of invoices are involved, and a large amount of invoice information needs to be collected so as to search and verify the invoices later. In the embodiment provided by the application, the invoice is stored into the blockchain network through the contract by the timing task unit, and then the required invoice information can be accurately and conveniently searched from the blockchain network through inquiring contract operation.

In some embodiments, the timed task unit is further configured to perform a query transaction status task. The timing task unit realizes the task of inquiring the transaction state within a preset time interval through the following steps: acquiring record information of a transaction to be updated of a transaction state of an un-updated blockchain from a database; submitting a contract operation for inquiring a transaction state of a transaction to be updated to the blockchain network; under the condition that the blockchain network returns a transaction result of the transaction to be updated, updating the transaction state of the transaction to be updated in the database according to the transaction result; and under the condition that the blockchain network does not return the transaction result of the transaction to be updated and the submitting time of the transaction to be updated exceeds the preset time, determining the transaction state of the transaction to be updated as transaction failure, and updating the transaction state of the transaction to be updated in the database as transaction failure.

In the embodiment provided by the application, the task of inquiring the transaction state is executed by the timing task unit, so that the state of the transaction performed on the blockchain network can be recorded in the database in time, and the accuracy of the transaction state is ensured.

In an implementation, the production run management module may deploy in the blockchain an invoice contract for a storage structure as shown in fig. 6 that would be deployed in the blockchain network. The plain text structure design of the plain text privacy information portion of the invoice in the invoice contract is shown in fig. 7.

The invoice contract includes the following contract function:

a contract initialization (init) function is used to initially compound the contract base information. The entry function of this function is: init. The parametrization json structure of this function is as follows:

{

"params":{

"platformBid":"",

"platformSubBid":""

}

the function core logic includes: the headers information of the initialization contract, and the service builder BID and the service BID.

A trade authenticity verification service BID address list authorization (authorization) function for: to authorize a given service BID, the BID may operate the business functions of the contract after authorization. The entry function of this function is: main. The parametrization json structure of this function is as follows:

{

"method":"authorize"

"params":{

"platformSubBid":""

}

the function core logic includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; verifying that the target service BID address is not in the authorization list; the specified BID is added to the authorization list.

A cancel trade authenticity verification service BID address list authorization (cancelAuthorize) function for: the authorization to specify a service BID is canceled, and the BID does not allow operation of the contract business function after the authorization is canceled. The entry function of this function is: main. The afferent json structure of the function includes:

{

"method":"cancel-authorize"

"params":{

"platformSubBid":""

}

the function core logic includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; verifying that the target service BID address is already in the authorization list; the specified BID is removed from the authorization list.

A close contract (closecontact) function for: closing the current contract, wherein the closed contract does not accept the data change any more. The entry function of this function is: main. The afferent json structure of the function includes:

{

"method":"close-contract"

}

the function core logic includes: checking the contract state header status as INIT; verifying that only authorized service constructors BID triggers are allowed; the contract status is modified to header.status to END and the closing time endTime is updated.

A register invoice (register) function, which is used to: the invoice is logged in the chain. The entry function of this function is: main. The afferent json structure of the function includes:

{

"method":"register",

"params":{

"invoiceHash":"",

"pub":{

"serviceProviderBid":"",

"serviceProviderName":"",

"annexLabel":"",

"status":""

},

"priv":"",

"encrypt":{

"isEncrypted":"",

"algorithm":"",

"identity":"",

"encryptionType":""

}

the function core logic includes: checking the contract state header status as INIT; checking that only authorized service BID triggers are allowed; checking that the corresponding invoice Hash is not registered in the contract yet; invoice information is stored in the contract.

Modifying invoice information (modification) functions for: the invoice information is modified. The entry function of this function is: main. The afferent json structure of the function includes:

{

"method":"register",

"params":{

"invoiceHash":"",

"pub":{

"annexLabel":"",

"status":""

},

"priv":""

}

the function core logic includes: checking the contract state header status as INIT; checking that only authorized service BID triggers are allowed; verifying that the corresponding invoice Hash exists in the contract; and modifying the corresponding invoice information.

Inquiring an invoice detail function according to the invoice hash, wherein the function is used for: and inquiring the appointed invoice details according to the invoice hash. The entry function of this function is: and query. The afferent json structure of the function includes:

{

"method":"query-by-invoice-hash",

"params":{

" invoiceHash":""

}

the function core logic includes: and inquiring information of the appointed invoice, and throwing exception if the invoice record does not exist.

A function for specifying whether the invoice is in a contract according to the invoice hash check, the function being for: and checking whether the specified invoice is in the contract according to the invoice hash. The entry function of this function is: and query. The afferent json structure of the function includes:

{

"method":"check-by-invoice-hash",

"params":{

" invoiceHash":""

}

the function core logic includes: inquiring whether a specified invoice is in a contract or not, and returning true exists; there is no return false.

In the implementation process, the production and fusion service system further comprises a plurality of operation and maintenance tool systems so as to ensure the normal operation of the production and fusion service system. The operation tool system may include, but is not limited to: prometaus, an open source monitoring alarm system based on a time sequence database; the K8s cluster is managed daily based on the web interface by the KuBoard, and the K8s daily operation and maintenance operation can be greatly simplified through interface operation; loki, horizontally extensible, high availability, multi-tenant log aggregation system; jenkins, an automatic construction tool, a researcher and a developer submit codes to a gitlab, jenkins is triggered to pull the codes on the gitlab, then compiling is completed to construct a jar package, mirror images can be generated inside Jenkins through pipeline configuration, the mirror images are pushed to a harbour warehouse, and service deployment is completed through K8 s; and an allowable, which realizes functions of batch system configuration, batch program deployment, batch operation command and the like.

FIG. 4 is an exemplary flow chart of a blockchain-based fusion service method shown in accordance with some embodiments of the present application. The blockchain-based fusion service method is applied to the blockchain-based fusion service system as described above, and as shown in fig. 4, the method includes the following steps:

in step S410, the target fusion platform interfaces with one or more fusion service providers through account management services provided by the fusion service system.

For detailed descriptions of the fusion platform, the fusion service provider, and the account management service, refer to relevant contents in fig. 3, and are not repeated here.

By way of example only, as shown in fig. 2, after registering as a user of the fusion service system, user enterprise B of fusion platform a may open a service account at one or more of service provider a, service provider B, service provider C, and service provider D, add and bind a bank card account through account management service provided by the fusion service system, after which enterprise B may apply for providing a service of the fusion service through fusion platform a with one or more of service provider a, service provider B, service provider C, and service provider D using a service account opened at one or more of service provider a, service provider B, service provider C, and service provider D.

In the implementation process, the fusion service system provides different access opening flows for different users.

For enterprise users of the fusion platform, the fusion service system can be logged in through the following steps:

clicking a shortcut authorized login control; popping up a wallet to select an account needing to be logged in; the background returns the corresponding super node and the enterprise list; an enterprise login specifying a login is selected. The specific implementation process is as follows:

generating a login random number (nonce) by the fusion service system; the user signs the login random number by using the BID private key to be logged in; the fusion server performs signature verification on the signed login random number; after successful verification of the production and fusion service system, acquiring a super node list or an enterprise list associated with the login BID, and generating an optional identity information list according to the super node list or the enterprise list; and the user selects the enterprise designated by the login from the optional identity information list returned by the fusion service system.

After the user logs in, the fusion service system displays the logged-in menu interface by the following modes: refreshing a page acquisition menu; the background returns to the menu according to the login identity and whether the normal trusted certificate exists.

In a specific implementation, the trusted credential may be displayed to the user by: the non-super node identity acquires a trusted certificate in a normal state; the user clicks the enterprise trusted voucher to call the wallet; and acquiring and displaying enterprise credential information.

In a specific implementation process, the fusion service platform can manage information of the fusion service provider in the following manner: inputting information such as service provider BID; judging whether the service provider BID is valid or not and whether the service provider BID is occupied by the service provider or not; verifying wallet signature data; and storing legal data.

In a specific implementation process, the fusion platform may submit the access application in the following manner: the user selects an access mode, which is used as a block chain link point direct access system or indirectly accesses a block chain system through a current node; filling platform information; and (5) background verification and data storage.

The super node service platform of the fusion service system examines and approves the access application in the following way: the user checks the data to be examined and approved; selecting an approval result and filling approval opinions; and (5) checking and storing in the background.

In step S420, the target fusion service provider provides the trade authenticity verification service to the target fusion platform through the trade authenticity verification service provided by the fusion service system in response to the service request of the target fusion platform.

For a detailed description of the trade authenticity verification service, see relevant contents in fig. 3, which are not repeated here.

By way of example only, the business B in the example of step S410 may upload a large number of invoices to the service provider C through the product fusion platform a using the trade authenticity verification service provided by the product fusion service platform, and the service provider C may identify and verify the uploaded invoices, and the business B may apply for providing the ticket financing service to the service provider C by means of the verified invoices.

As shown in fig. 8, the electronic device includes: at least one processor 801, at least one communication interface 802, at least one memory 803, and at least one communication bus 804; alternatively, the communication interface 802 may be an interface of a communication module, such as an interface of a GSM module; the processor 801 may be a processor CPU or a specific integrated circuit ASIC (Application Specific Integrated Circuit) or one or more integrated circuits configured to implement embodiments of the present invention. The memory 803 may comprise a high-speed RAM memory or may further comprise a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The memory 803 stores a program, and the processor 801 calls the program stored in the memory 803 to execute some or all of the above-described method embodiments.

The present application relates to a storage medium storing a computer readable program which, when executed, performs some or all of the method embodiments described above.

Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Based on the same inventive concept, the embodiments of the present application also provide a computer program product, comprising a computer program, which when executed by a processor, implements some or all of the above-mentioned method embodiments.

While the basic concepts have been described above, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations of the present application may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this application, and are therefore within the spirit and scope of the exemplary embodiments of this application.

Meanwhile, the present application uses specific words to describe embodiments of the present application. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present application. Thus, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this application are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present application may be combined as suitable.

Furthermore, the order in which the elements and sequences are presented, the use of numerical letters, or other designations are used in the application and are not intended to limit the order in which the processes and methods of the application are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements included within the spirit and scope of the embodiments of the present application. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing server or mobile device.

Likewise, it should be noted that in order to simplify the presentation disclosed herein and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure, however, is not intended to imply that more features than are presented in the claims are required for the subject application. Indeed, less than all of the features of a single embodiment disclosed above.

In some embodiments, numbers describing the components, number of attributes are used, it being understood that such numbers being used in the description of embodiments are modified in some examples by the modifier "about," approximately, "or" substantially. Unless otherwise indicated, "about," "approximately," or "substantially" indicate that the number allows for a 20% variation. Accordingly, in some embodiments, numerical parameters set forth in the specification and claims are approximations that may vary depending upon the desired properties sought to be obtained by the individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and employ a method for preserving the general number of digits. Although the numerical ranges and parameters set forth herein are approximations that may be employed in some embodiments to confirm the breadth of the range, in particular embodiments, the setting of such numerical values is as precise as possible.

Each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., cited in this application is hereby incorporated by reference in its entirety. Except for application history documents that are inconsistent or conflicting with the present application, documents that are currently or later attached to this application for which the broadest scope of the claims to the present application is limited. It is noted that the descriptions, definitions, and/or terms used in the subject matter of this application are subject to such descriptions, definitions, and/or terms if they are inconsistent or conflicting with such descriptions, definitions, and/or terms.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present application. Other variations are also possible within the scope of this application. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present application may be considered in keeping with the teachings of the present application. Accordingly, embodiments of the present application are not limited to only the embodiments explicitly described and depicted herein.

Claims

1. A block chain-based fusion service system, which is characterized by comprising a gateway interface layer, a data processing layer and a fusion service layer; wherein the data processing layer comprises a blockchain network and a database;

the gateway interface layer is used for connecting the fusion operation end, the fusion service end and the fusion platform end into the fusion service system; the fusion service terminal is a terminal used by a fusion service provider for accessing the fusion service system, and the fusion platform terminal is a terminal used by a fusion platform for accessing the fusion service system;

the production and fusion service layer comprises a production and fusion center management module and a basic service module; the fusion center management module is used for providing account management service for the fusion service provider and the fusion platform so that the fusion service provider and the fusion platform can realize the butt joint of fusion service through the fusion service system; the basic service module at least comprises a key management service unit, a uplink service unit, a file service unit and a timing task unit;

The blockchain network is used for realizing transaction corresponding to the fusion service between the fusion service provider and the fusion platform through intelligent contracts.

2. The system of claim 1, wherein the gateway interface layer is further configured to provide the targeted service to a service platform of the non-registered user by:

responding to an API request of the service platform, which carries a group of APIkey and APISECret, and inquiring whether a target service corresponding to the API request exists or not to the production and fusion center management module;

returning an access token generated by the fused center station management module to the service platform under the condition that the target service exists; wherein the access token is valid within a preset time period;

responding to the service request carried by the service platform with the access token, and sending the service request to the fused center management module so that the fused center management module performs verification processing on the access token and provides service corresponding to the service request according to the result of the verification processing;

the production and fusion center management module is further configured to provide the target service to the service platform by:

Responding to the received API request sent by the gateway interface layer, and inquiring whether a target service corresponding to the API request exists or not;

generating the access token in the presence of the target service, and associating the access token with information of the service platform;

returning the token to a gateway interface layer; and

and responding to the service request carrying the access token from the gateway interface layer, performing verification processing on the access token, and providing the target service according to the result of the verification processing.

3. The system of claim 1, wherein the account management service comprises a fusion service provisioning service;

the production and fusion center management module realizes the production and fusion service opening service for the target service platform by the following steps:

responding to the operation that the fusion operation terminal triggers to enable or disable the fusion service of the target service platform, and acquiring contract operation data for enabling or disabling the fusion service of the target service platform;

assembling the contract operation data, generating contract operation executable by a node of a blockchain, and sending the contract operation to the target service platform for signature operation;

Submitting the signed contract operation to the blockchain network;

4. The system of claim 3, wherein the account management service further comprises an provisioning service account service;

the production and fusion center management module realizes the service of the opening service account by the following steps:

responding to receiving an account opening request carrying account opening information sent by a target fusion platform, and checking whether the account opening information is legal or not;

under the condition that the account opening information is legal, sending the account opening request to a fusion producing service end corresponding to the account opening request, so that the fusion producing service end opens a service account for an initiator of the account opening request according to the account opening information, and generates service account information corresponding to the service account;

acquiring the service account information from the fusion server;

encrypting the service account information by using a key acquired from the key management service unit;

and the service account information after encryption is uplink through the uplink service unit so as to establish a blockchain account corresponding to the service account in the blockchain network, and an intelligent contract is called to generate an address of the blockchain account.

5. The system of claim 4, wherein the account management service further comprises an add bank card account service;

the production and fusion center management module realizes the service of adding the bank card account by the following steps:

responding to a service request for adding a bank card, which is sent by a target fusion producing platform and carries account information of the bank card, and checking whether the service request is a service request for adding the bank card for the first time;

under the condition that the service request is the service request for adding the bank card for the first time, encrypting the account information of the bank card by utilizing the key acquired from the key management service unit; and

the information of the bank card account which is subjected to encryption processing is uplink through the uplink service unit so as to establish a corresponding block chain account of the bank card in the block chain network, and an intelligent contract is called to generate an address of the block chain account; or alternatively

And returning to the blockchain account address corresponding to the bank card under the condition that the service request is the service request for not adding the bank card for the first time.

6. The system of claim 5, wherein the account management service further comprises a sub-account management service for sub-accounts; the sub-account is an account of an enterprise accessing the target production platform, and the sub-account management service at least comprises a binding card service, a card releasing service, a recharging service, a cash withdrawal service, a transfer service, a fund freezing service, a fund thawing service, a transaction receipt downloading service, an account fund information inquiry service and a transaction running water inquiry service;

responding to a sub-account management service request carrying sub-account information sent by a target fusion platform, and executing a preset operation corresponding to the sub-account management service;

under the condition that the sub-account management service can be executed, sending the sub-account management service request to a fused service end corresponding to the sub-account management service request, so that the fused service end executes the sub-account management service;

and updating the state information of the sub-account in a database according to the execution result of the fusion server, and returning the execution result to the target fusion platform.

7. The system of claim 1, wherein the fusion center management module is further configured to provide trade authenticity verification services for the fusion service provider and the fusion platform; the trade authenticity verification service at least comprises an invoice identification service and an invoice verification service;

the production and fusion center management module realizes invoice identification service through the following steps of;

receiving an OCR file of at least one invoice from a target fusion platform, storing the OCR file into the file service unit, and returning a file identification of the OCR file acquired from the file service unit to the target fusion platform;

Responding to an invoice identification service request which is triggered by the target production and fusion platform and carries a file identification of an invoice to be identified, and acquiring an OCR file of the invoice to be identified from the file service unit according to the file identification;

the OCR file of the invoice to be identified is sent to a target producing and thawing service end, so that the target producing and thawing service end carries out OCR identification on the invoice to be identified;

and returning the OCR recognition result to the target fusion platform.

8. The system of claim 7, wherein the production and fusion platform management module provides invoice verification services to a target production and fusion platform by;

responding to an invoice verification service request which is triggered by a target production and fusion platform and carries information of an invoice to be verified, and determining whether the invoice to be verified is verified and whether the invoice to be verified is in a revocation state or a red-flushing state according to the information of the invoice to be verified;

under the condition that the invoice to be verified is not verified, and the invoice to be verified is in a non-revocation state or a red-flushing state, the invoice to be verified is sent to a target producing and thawing service end, so that the target producing and thawing service end carries out verification on the invoice to be verified;

If the verification result is successful, inputting the information of the invoice to be verified into the database, and setting the blockchain state of the invoice to be verified as initialization;

and returning the verification result to the target fusion platform.

9. The system of claim 1, wherein the timed task unit is configured to perform an invoice chaining operation;

the timing task unit realizes the invoice chaining operation in a preset time interval through the following steps:

acquiring information of a to-be-uplink invoice with a blockchain state being initialized from the database;

inquiring whether the invoice to be uploaded exists in an invoice contract deployed in the blockchain network;

submitting contract operations to update invoice information to the blockchain network under the condition that the invoice information to be uploaded is recorded in the invoice contract; or alternatively

Submitting a contract operation for registering invoice information to the blockchain network under the condition that the invoice information to be uploaded is not recorded in the invoice contract;

and changing the blockchain state of the invoice to be uploaded in the database into submitted.

10. The system of claim 9, wherein the timed task unit is further configured to perform a query transaction status task;

The timing task unit realizes the task of inquiring the transaction state within the preset time interval through the following steps:

acquiring record information of a transaction to be updated of a transaction state of an un-updated blockchain from the database;

submitting a contract operation to the blockchain network for querying a transaction state of the transaction to be updated;

under the condition that the blockchain network returns the transaction result of the transaction to be updated, updating the transaction state of the transaction to be updated in the database according to the transaction result;

and under the condition that the blockchain network does not return the transaction result of the transaction to be updated and the submitting time of the transaction to be updated exceeds the preset duration, determining the transaction state of the transaction to be updated as transaction failure, and updating the transaction state of the transaction to be updated in the database as transaction failure.

11. A blockchain-based fusion service method, wherein the method is applied to the blockchain-based fusion service system according to any of claims 1 to 10, and the method comprises:

12. The method of claim 11, wherein the method further comprises:

and the target fusion service provider responds to the service request of the target fusion platform and provides trade authenticity verification service for the target fusion platform through the trade authenticity verification service provided by the fusion service system.

13. An electronic device comprising a memory storing a computer program and a processor that when executing the program performs the method of claim 11 or 12.

14. A storage medium storing a computer readable program which, when executed, performs the method of claim 11 or 12.