WO2022105038A1

WO2022105038A1 - Method for defining on-chain data service specification in blockchain and applying service specification

Info

Publication number: WO2022105038A1
Application number: PCT/CN2020/142465
Authority: WO
Inventors: 吴志雄; 黄文峰; 汪翔; 朱秀桦
Original assignee: 南威软件股份有限公司
Priority date: 2020-11-18
Filing date: 2020-12-31
Publication date: 2022-05-27
Also published as: WO2022105049A1; CN112380219A; CN112380219B

Abstract

The present invention relates to a method for defining an on-chain data service specification in a blockchain and applying a service specification, comprising an industry template configuration, a service type configuration, and a service specification or data model configuration. Moreover, the fineness of the configurations supports a data type, whether to be a service natural key, and Chinese and English names. A portion which originally requires a code logic configuration is transferred to a service end for definition. Thus, the service flexibility is enhanced, and it is ensured that an on-chain data specification is adapted to a service change. The configuration of the service specification supports multiple versions, and after the configuration is completed, the specification can be automatically read by means of an SDK without deploying a blockchain network, thereby reducing the costs.

Description

A method for defining the data service specification and application service specification on the blockchain

technical field

The invention relates to the fields of blockchain, data on-chain, government affairs, blockchain application and business data model, in particular to a method for defining a blockchain on-chain data business protocol and an application business protocol.

Background technique

Blockchain technology is to use the block chain data structure to verify and store data, use distributed node consensus algorithm to generate and update data, use cryptography to ensure the security of data transmission and access, and use the intelligence composed of automated script codes. A new distributed infrastructure and computing paradigm that uses contracts to program and manipulate data.

Data on-chain means writing data to the blockchain. Currently, different blockchains in the market have different on-chain methods. For non-audited blockchains, basically no matter who or what content can be uploaded on the chain. Any transaction that occurs can be accompanied by text messages. The text content is not limited, but the text size affects the cost. There is basically no signature verification and encryption and decryption on the chain of this method, and the chain protocol does not make any restrictions, and there is a risk of insufficient security and storage within a certain range.

For a certain type of blockchain, only certain types of data can be uploaded to the chain, and other types of data cannot be uploaded to the chain. For example, blockchain invoices, transactions are invoiced, and invoices are reimbursed. The whole process is fully automatic and does not require users to worry about it. The entire link is on the chain and can be checked on the chain. This method limits the expansion of blockchain applications. Only one type of data can be uploaded for a specific application, and it is impossible to provide multiple types of data on the chain for the same application. What follows is that when the business changes, the cost of replacing the data type on the chain is too high, and it is difficult to adapt to the market demand.

At present, the data uploading requirements of various industries are different, and there will be frequent changes. Such businesses are usually processed at the smart contract layer. Smart contracts are the core thing. Frequent changes will bring business risks and loopholes, and different The on-chain demand during the period will change, so the business needs to be compatible with historical data.

Since there are many industrial applications of blockchain, in the field of government affairs, blockchain can shape many industrial applications, such as approval chain, supervision chain, license chain, sharing chain, etc. The various process stages in the implementation of blockchain applications are complex, and there will be frequent changes in business data on the chain, long approval processes, and a lot of business data. It is difficult for the data to adapt to business changes quickly. The most direct problem that follows is the need to re-develop the project. , resulting in an impact on business fluency and an increase in project costs. Therefore, there is a need for a flexible way to define the data service protocol on the chain to solve this problem.

technical problem

In view of this, the purpose of the present invention is to provide a method for defining a blockchain on-chain data service protocol and an application service protocol, which can effectively improve the security of on-chain data.

technical solutions

The present invention adopts the following scheme to achieve: a method for defining a blockchain on-chain data business protocol and an application business protocol, comprising the following steps: Step S1: creating an industry template for precipitating an industry on-chain data model: on the blockchain platform Create an industry template, enter the template name and template description; at the same time, create a bc_biz_type table in the mysql database to store the created industry template information to complete the precipitation of the industry on-chain data model; Step S2: Create the business type of the industry template; Step S3 : Create the business specification of this business type, that is, the data model on the chain; Step S4: After completing the definition of the industry template, the smart contract in the blockchain platform automatically obtains the definition content, and the blockchain platform administrator needs to open the API service and Industry template association, by establishing an association relationship, it is possible to read and use the business specifications under the industry template; Step S5: Create developer authorization information: establish authorization for chain application developers on the blockchain platform according to the feedback requirements of operators information; first register the basic information of the developer including the developer name, developer user name and password, and select the API interface service required by the business; after the information is recorded, output the authorization information to the developer, and the content of the authorization information includes the authorization appkey, secretkey , digital certificate, and provide the software development kit (SDK) to the developer. The developer obtains the specific certificate information and API interface method by calling the pem file in the SDK; Step S6: After the authorization information is registered, the chain application developer needs to integrate The blockchain SDK implements the initialization of the SDK; obtains the certificate information by calling the pem file, and caches the numerical certificate locally; obtains the gateway address and API service in the SDK to match whether the authorization information is available; if the authorization information matches, prompts If the authorization information is correct, you can continue to use it; if the authorization information does not match, it will prompt that the authorization is incorrect, please contact the administrator, and read the biz_name information in the SDK and store it; Step S7: When the application side uploads the data to the chain, it needs to To initiate a transaction request to the SDK side, the SDK side and the smart contract layer need to verify whether the digital certificate information of the user on the application side is consistent with the digital certificate distributed when the authorization was created, and at the same time call the authorized API service to read which application the application uses through biz_name Which business type version of the business specification in the industry template, after the SDK obtains the corresponding on-chain data specification information, it needs to compare it with the data format of the request information initiated by the application, including whether the comparison format is transmitted according to the configuration requirements, whether the fields are missing and Whether all required fields are transmitted, verify whether the request information initiated by the application meets its business specification; Step S8: For the same business service, multiple versions are allowed to run at the same time, depending on the content of the smart contract, when the contract content defines a certain The API service has V1\V2 versions of the data protocol used at the same time. It is agreed that V1 is used in scenario 1 and V2 is used in scenario 2. The smart contract layer only needs to decide which version to run based on the associated primary key biz_name Step S9: After the SDK verifies the application-side information and passes the verification, the SDK receives the on-chain request data, and requires the application-side developer to call the digital certificate to sign the on-chain information, and the sender's identity information and Data binding is used to prevent others from fraudulently using the sender, to ensure the tamper-proof of the information, and to authenticate the sender's identity to prevent denial; Step S10: The SDK sends the request information to the smart contract, and the smart contract runs the corresponding API service. biz_name obtains which version of the data specification in the business type corresponding to the industry template associated with the API service; the smart contract sends the data to the blockchain node according to the specification paradigm; Step S11: The same application SDK allows running multiple smart contracts, In order to meet the needs of different API services, it supports multiple contracts to schedule and run; Step S12: After the data is sent to the blockchain node, a blockchain transaction is formed and enters the stage of going on the chain, and the subsequent processing on the chain Enter the blockchain consensus process.

Further, the specific content of the step S2 is: add a business type through the blockchain platform, add the business type of the template, and the added content includes the Chinese name, English name and version number of the business type; namely, insert the business type Chinese in the bc_biz_type table. Name, English name and version number content, create different business types according to the needs of different business scenarios in the industry.

Further, the specific content of step S3 is: adding a data model through the blockchain platform, the content of the data model includes Chinese name, English name, data type, whether it is required and whether to set the transaction primary key; after the completion of steps S1 to S3 , the industry template definition is complete.

beneficial effect

Compared with the prior art, the present invention has the following beneficial effects: the present invention defines different uplink data protocols according to different business needs, and at the same time, along with the development of the business, the protocol supports multi-version issuance, and supports the use of this special protocol in different business situations. Business data specification.

Description of drawings

FIG. 1 is a block diagram of a method according to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

The present invention will be further described below with reference to the accompanying drawings and embodiments.

It should be noted that the following detailed description is exemplary and intended to provide further explanation of the application. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs.

It should be noted that the terminology used herein is for the purpose of describing specific embodiments only, and is not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly dictates otherwise, the singular is intended to include the plural as well, furthermore, it is to be understood that when the terms "comprising" and/or "including" are used in this specification, it indicates that There are features, steps, operations, devices, components and/or combinations thereof.

As shown in Figure 1, this embodiment provides a method for defining a blockchain on-chain data service protocol and an application service protocol, including the following steps: Step S1: Create an industry template for precipitation of the industry's on-chain data model: in the region The blockchain platform creates an industry template, and enters the template name and template description; at the same time, a bc_biz_type table is created in the mysql database to store the created industry template information to complete the precipitation industry on-chain data model; Step S2: Create the business type of the industry template ; Step S3: Create the business specification of the business type, that is, the data model on the chain; Step S4: After completing the definition of the industry template, the smart contract in the blockchain platform automatically obtains the definition content, and the blockchain platform management personnel need to open the The API service is associated with the industry template, and by establishing an association relationship, the business specifications under the industry template can be read and used; Step S5: Create developer authorization information: Develop chain applications on the blockchain platform according to the needs of the operator feedback The developer establishes authorization information; first, register the basic information of the developer including the developer name, developer user name and password, and select the API interface service required by the business; after the information is recorded, output the authorization information to the developer. The content of the authorization information includes the authorization appkey, secretkey, and digital certificate, and provide software development kit, namely SDK, to the developer. The developer obtains the specific certificate information and API interface method by calling the pem file in the SDK; Step S6: After the authorization information is registered, the chain application developer It is necessary to integrate the blockchain SDK first to realize the initialization of the SDK; obtain the certificate information by calling the pem file, and cache the numerical certificate locally; obtain the gateway address and API service in the SDK to match whether the authorization information is available; if the authorization information matches , it will prompt that the authorization information is correct and you can continue to use it; if the authorization information does not match, it will prompt that the authorization is incorrect, please contact the administrator, and read the information of biz_name in the SDK and store it; Step S7: the application side should upload the data to the chain At the same time, a transaction request needs to be initiated to the SDK side. The SDK side and the smart contract layer need to verify whether the digital certificate information of the user on the application side is consistent with the digital certificate distributed when the authorization was created, and at the same time call the authorized API service and read its The application uses the business specification of which business type and version in which industry template. After the SDK obtains the corresponding uplink data specification information, it needs to compare the data format of the request information initiated by the application, including whether the comparison format is transmitted according to the configuration requirements, and whether the fields are Whether there are missing and required fields are transmitted, and verify whether the request information initiated by the application meets its business specifications; Step S8: For the same business service, multiple versions are allowed to run at the same time, depending on the content of the smart contract, when the content of the contract Define that an API service has V1\V2 versions of the data protocol to be used at the same time. It is agreed that V1 is used in scenario 1 and V2 is used in scenario 2. The smart contract layer only needs to decide which version to run based on the associated primary key biz_name Step S9: After the SDK verifies the application-side information and passes the verification, the SDK receives the on-chain request data, and requires the application-side developer to call the digital certificate to sign the on-chain information, and the sender's identity information and Data binding is used to prevent others from fraudulently using the sender, to ensure the tamper-proof of the information, and to authenticate the sender's identity to prevent denial; Step S10: The SDK sends the request information to the smart contract, and the smart contract runs the corresponding API service. biz_name obtains which version of the data specification in the business type corresponding to the industry template associated with the API service; the smart contract sends the data to the blockchain node according to the specification paradigm; Step S11: The same application SDK allows running multiple smart contracts, In order to meet the needs of different API services, it supports multiple contracts to schedule and run; Step S12: After the data is sent to the blockchain node, a blockchain transaction is formed and enters the stage of going on the chain, and the subsequent processing on the chain Enter the blockchain consensus process.

In this embodiment, the specific content of step S2 is: adding a business type through the blockchain platform, adding the business type of the template, and the added content includes the Chinese name, English name and version number of the business type; that is, inserting in the bc_biz_type table The content of the Chinese name, English name and version number of the business type, according to the needs of different business scenarios in the industry, create different business types.

In this embodiment, the specific content of step S3 is: adding a data model through the blockchain platform, the content of the data model includes Chinese name, English name, data type, whether it is required and whether to set the transaction primary key; step S1 to step After S3 is completed, the industry template definition is completed.

Preferably, this embodiment solves the problems of frequent changes, multi-version operation, compliance verification, etc. of the blockchain management platform to the on-chain data protocol by flexibly setting the blockchain on-chain data service protocol. Through the flexible setting of business regulations on the blockchain platform, the flexible configuration of the blockchain regulations and multi-version applications can be realized on the business side, and the SDK to verify the regulations and user identity security on the application side. On the platform side, through a simple data model, it can adapt to a variety of blockchain application scenarios, and at the same time, it can quickly model by precipitation specifications, improve application efficiency, reduce project R&D labor costs, time costs for downtime and deployment, and application costs caused by unsmooth business applications. .

In this embodiment, the blockchain management platform provides a flexible configuration method for the blockchain application on-chain data business protocol, and the configuration content includes industry template configuration, business type configuration, business protocol or data model configuration. And the granularity of configuration supports data type, business primary key, Chinese and English names. Let the part that originally required code logic configuration be transferred to the business-side definition. Enhance business flexibility and ensure that the on-chain data protocol adapts to business changes.

The configuration of the business protocol supports multiple versions, and after the configuration of the protocol is completed, it can be automatically read through the SDK, and there is no need to deploy the blockchain network, reducing various costs. The SDK is used to verify the security and compliance of the business protocol, avoid irregular data uploading, improve the threshold of data on the chain, improve the validity of the data on the chain, and ensure the quality of the data on the chain; when the business protocol is configured, it can provide business traceability When the primary key configuration is used, the business side defines the business primary key by itself, so that the entire business behavior can be traced through the content of the primary key. This configuration is open to the application side, enabling flexible design of business scenario planning without being restricted by the primary key, so that the on-chain traceability can keep up with the business.

In this embodiment, different uplink data protocols are defined according to different business needs. At the same time, with the development of services, the protocol supports multi-version issuance, and supports the use of the data protocol of the special service in different business situations.

In this embodiment, the on-chain data protocols used in different business scenarios are precipitated to form an industry template, which can be quickly reused when other blockchain networks in the industry are created next time.

This embodiment provides a flexible verification method, supports the verification of the SDK and the smart contract layer, and controls it according to the traffic of the business.

In this embodiment, in addition to the configuration of the Chinese name, English name, data type, and whether it is required to be filled in the data on the chain, the configuration of the transaction primary key is also provided. Realize the traceability of the entire business behavior after it occurs. It is based on the high read-write efficiency of the storage structure of the blockchain platform "Key-Value" to solve the problem of complex data query.

This embodiment can effectively improve the security of the on-chain data. The verification of the on-chain data in the smart contract is realized through the SDK layer, and the on-chain data model is recorded in the smart contract. The content of data verification includes whether the content of the on-chain protocol is consistent with the rules agreed by each node, and whether the identity information of the transaction requester is consistent with the authorized information.

This embodiment provides a method for flexibly uploading a data service specification to the chain, and realizes rapid reuse, promotion and iteration in different projects by precipitating industry application templates. Different business categories can be set under different industry templates, and data models on the chain can be configured under different categories. The content of the model includes the Chinese name, English name, data type, and whether it is required. An industry application can support multiple versions of business classification, support data models of different versions to be executed together, and can be updated online in real time. It also provides configuration of transaction primary keys. Realize the traceability of the entire business behavior after it occurs.

The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

Claims

A method for defining a blockchain on-chain data service protocol and an application service protocol provides a blockchain platform, which is characterized by comprising the following steps:

Step S1: Create an industry template for precipitating the data model on the industry chain: create an industry template on the blockchain platform, enter the template name and template description; at the same time, create a bc_biz_type table in the mysql database to store the created industry template information, namely Complete the precipitation industry on-chain data model;

Step S2: create the business type of the industry template;

Step S3: Create a business specification of the business type, that is, an on-chain data model;

Step S4: After completing the definition of the industry template, the smart contract in the blockchain platform automatically obtains the definition content. At the same time, the blockchain platform administrator needs to associate the open API service with the industry template, and realize the industry template by establishing an association relationship. Read and use the business protocol below;

Step S5: Create developer authorization information: establish authorization information for chain application developers on the blockchain platform according to the feedback requirements of the operators; first register the basic information of the developer including the developer name, developer user name and password, select the API interface services required by the business; after the information is recorded, the authorization information is output to the developer. The content of the authorization information includes the authorization appkey, secretkey, and digital certificate. At the same time, the software development kit (SDK) is provided to the developer. pem file to obtain specific certificate information and API interface methods;

Step S6: After the authorization information is registered, the chain application developer needs to integrate the blockchain SDK first to realize the initialization of the SDK; obtain the certificate information by calling the pem file, and cache the numerical certificate locally; obtain the gateway address and API in the SDK service, to match whether the authorization information is available; if the authorization information matches, it will prompt that the authorization information is correct and you can continue to use it; if the authorization information does not match, it will prompt that the authorization is incorrect, please contact the administrator, and read the biz_name information in the SDK and to store;

Step S7: When the application side wants to upload the data to the chain, it needs to initiate a transaction request to the SDK side. The SDK side and the smart contract layer need to verify whether the digital certificate information of the user on the application side is consistent with the digital certificate distributed when the authorization was created. The authorized API service can read the business specification of which business type and version in which industry template the application uses through biz_name. After the SDK obtains the corresponding on-chain data specification information, it needs to be compared with the data format of the request information initiated by the application. Check whether the format is transmitted according to the configuration requirements, whether there are missing fields and whether all required fields are transmitted, and verify whether the request information initiated by the application side conforms to its business specification;

Step S8: For the same business service, multiple versions are allowed to run at the same time. It depends on the content of the smart contract. When the contract content defines that an API service has V1\V2 versions of the data protocol to be used at the same time, it is agreed to use V1 in scenario 1. When V2 is used in scenario 2, the smart contract layer only needs to decide which version of the protocol to run based on the associated primary key biz_name;

Step S9: After the SDK verifies the application-side information and passes the verification, the SDK receives the on-chain request data, and requires the application-side developer to call the digital certificate to sign the on-chain information, bind the sender's identity information to the data, and use In order to prevent others from fraudulently using the sender, to ensure the tamper-proof of the information, and to authenticate the sender's identity to prevent denial;

Step S10: The SDK sends the request information to the smart contract, the smart contract runs the corresponding API service, and obtains which version of the data specification in the business type corresponding to the industry template associated with the API service through biz_name; the smart contract sends the data according to the specification paradigm to the blockchain node;

Step S11: The same application SDK allows running multiple smart contracts to meet the needs of different API services, and supports multiple contracts to schedule and run;

Step S12: After the data is sent to the blockchain node, a blockchain transaction is formed and enters the stage of going on the chain, and the subsequent processing on the chain enters the blockchain consensus process.
The method for defining a blockchain on-chain data service protocol and an application service protocol according to claim 1, wherein the specific content of the step S2 is: adding a service type through the blockchain platform, adding the template The added content includes the Chinese name, English name and version number of the business type; that is, insert the Chinese name, English name and version number of the business type into the bc_biz_type table, and create different business types according to the needs of different business scenarios in the industry.
The method for defining a blockchain on-chain data service protocol and an application service protocol according to claim 1, wherein the specific content of the step S3 is: adding a data model through the blockchain platform, the content of the data model Including Chinese name, English name, data type, whether it is required, and whether to set the transaction primary key; after steps S1 to S3 are completed, the definition of the industry template is completed.