CN111259070B - Method and related device for storing and acquiring service data - Google Patents
Method and related device for storing and acquiring service data Download PDFInfo
- Publication number
- CN111259070B CN111259070B CN201911194837.3A CN201911194837A CN111259070B CN 111259070 B CN111259070 B CN 111259070B CN 201911194837 A CN201911194837 A CN 201911194837A CN 111259070 B CN111259070 B CN 111259070B
- Authority
- CN
- China
- Prior art keywords
- data
- hash value
- service data
- target
- storing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 95
- 238000003860 storage Methods 0.000 claims abstract description 29
- 238000013500 data storage Methods 0.000 claims abstract description 10
- 238000004364 calculation method Methods 0.000 claims description 41
- 238000012795 verification Methods 0.000 claims description 38
- 238000004422 calculation algorithm Methods 0.000 claims description 34
- 238000004140 cleaning Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 9
- 238000013210 evaluation model Methods 0.000 claims description 7
- 238000013480 data collection Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 230000001105 regulatory effect Effects 0.000 claims description 2
- 238000012954 risk control Methods 0.000 claims 1
- 230000005611 electricity Effects 0.000 description 29
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 238000010248 power generation Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 230000008520 organization Effects 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000011156 evaluation Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012502 risk assessment Methods 0.000 description 3
- 230000009466 transformation Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000007418 data mining Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000003892 spreading Methods 0.000 description 1
- 238000000844 transformation Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
Abstract
The application discloses a method and a related device for storing and acquiring service data, wherein the method comprises the following steps: the block chain application service platform acquires setting service data; performing multi-stage encryption on the set service data to obtain a target hash value; and storing the target hash value in a uplink manner according to the category to which the set service data belong. According to the technical scheme provided by the application, after the set service data is subjected to multi-stage encryption, uplink storage is performed according to the category to which the set service data belongs, so that the safety of the service data and the regularity of data storage are improved.
Description
Technical Field
The present application relates to the field of networks, and in particular, to a method and related device for storing and acquiring service data.
Background
With the continuous deep informatization construction and application of power enterprises, the cross-business cooperative demand of power grid enterprises is increased gradually, and the existing centralized data center cannot meet the expandable and low-delay performance required by the power grid business data storage; in addition, as the data of the data center generally has the characteristics of large quantity, diversification, quick increment and low value density, when an enterprise operates, each information system is difficult to acquire reliable, real, complete and accurate required data from the data center to process various services, and meanwhile, the existing centralized data center cannot meet the requirement of data security, so that a technical scheme capable of solving the technical problems is needed.
Disclosure of Invention
The application mainly solves the technical problem of providing a method for storing and acquiring service data and a related device capable of improving the safety of the service data.
In order to solve the technical problems, the application adopts a technical scheme that: there is provided a method of business data storage, the method comprising:
the block chain application service platform acquires setting service data;
Performing multi-stage encryption on the set service data to obtain a target hash value;
And storing the target hash value in a uplink manner according to the category to which the set service data belong.
In order to solve the above technical problems, another technical solution adopted by the present application is to provide a method for acquiring service data, the method includes:
The data demand node sends a data acquisition request to the data providing node to request acquisition of target service data;
receiving a target data packet sent by the data providing node; the target data packet at least comprises the target service data and a target hash value for carrying out preset hash calculation on the target service data, and is encrypted by using a private key of the data providing node;
decrypting the target data packet by using the public key of the data providing node to obtain the target data, and performing the preset hash calculation on the target data by using a hash algorithm to obtain a hash value to be verified;
and if the hash value to be verified is consistent with the target hash value, judging that the target data is legal.
In order to solve the technical problem, another technical scheme adopted by the application is to provide electronic equipment, which comprises a memory and a processor, wherein,
The processor is configured to execute the computer program stored in the memory to perform the method as described in any one of the above.
To solve the above-mentioned technical problem, another technical solution adopted by the present application is to provide a storage medium storing a computer degree, and the computer program can be executed by a processor to perform the method as described above.
According to the technical scheme provided by the application, the block chain application service platform performs multi-level encryption on the set service data by acquiring the set service data, so as to obtain the target hash value, and performs uplink storage on the target hash value obtained by the multi-level encryption according to the category to which the set service data belongs, so that the security of the service data can be better improved, and the uplink storage is performed according to the category to which the set service data belongs when the target hash value of the set service data is stored, so that the regularity of data storage can be better improved.
Drawings
FIG. 1 is a block chain architecture diagram of a method for storing service data according to an embodiment of the present application;
FIG. 2 is a block diagram illustrating a block encapsulation of a blockchain in an embodiment of a method of traffic data storage according to the present application;
FIG. 3 is a flow chart illustrating a method for storing business data according to an embodiment of the present application;
FIG. 4 is a schematic view of an application scenario in another embodiment of a method for storing service data according to the present application;
FIG. 5 is a flow chart illustrating a method for storing business data according to another embodiment of the present application;
Fig. 6 is a schematic view of an application scenario in a method for storing service data according to another embodiment of the present application;
FIG. 7 is a flowchart illustrating a method for acquiring service data according to an embodiment of the present application;
FIG. 8 is a flowchart illustrating a method for acquiring service data according to another embodiment of the present application;
FIG. 9 is an interactive diagram of a method for acquiring service data according to an embodiment of the present application;
FIG. 10 is a schematic diagram of an electronic device according to an embodiment of the present application;
FIG. 11 is a schematic diagram illustrating the structure of a storage medium according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the description of the present application, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined otherwise. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to facilitate understanding of the technical solutions provided by the present application, before explaining the technical solutions provided by the present application, key terms or technical abbreviations mentioned in the description of the present application are explained first:
The block chain technology is a novel distributed data organization method and operation mode which are raised along with digital encryption currency such as bitcoin and the like. The method has the greatest characteristics that: decentralizing enables data to be maintained in a distributed mode, and data operation, management and maintenance efficiency is greatly improved; and the nodes are commonly known, the whole block chain is commonly maintained through competition calculation based on a set of common known mechanism, any node fails, and other nodes can still work normally. Meanwhile, the blockchain carrying the asymmetric encryption technology has high safety and traceability, and can effectively prevent data leakage or illegal tampering. A blockchain is also understood to be a de-centralized database in which data is stored in time order as a series of blocks, each referencing a hash pointer of a preceding block to form an interconnected chain. The blockchain comprises a plurality of nodes, which can be called as blockchain nodes, each node of the blockchain stores a complete copy, the blockchain can automatically synchronize and verify data on all nodes, and the blockchain has the characteristics of distribution and synchronism. The present application proposes to implement data storage based on a blockchain technology, such as storage of grid business related data, and the like, and is described in detail in the related embodiments below. The power grid business related data at least comprises one of user electricity consumption, power generation amount fed into the power grid, account information of the user, power consumption in different time periods in each region, power generation amount and the like, and it is understood that the power grid business related data can be adjusted according to actual storage requirements and are not limited herein.
To facilitate an understanding of the blockchain network of the present application, the blockchain technique employed by the present application is first illustrated. Referring to fig. 1, fig. 1 is a schematic block chain architecture diagram of a method for storing service data according to an embodiment of the present application. In one embodiment, the electronic device runs the blockchain technology to become a node of the blockchain network, and the blockchain technology architecture is shown in fig. 1, and includes a blockchain data layer 11, a forensic layer 12, a forensic layer 13, and an application layer 14.
The blockchain data layer 11 is used to encapsulate underlying data blocks and associated data encryption and time stamping techniques. Also, the file data may be computed using an irreversible encryption algorithm (e.g., SHA-256 algorithm, SHA-512 algorithm, etc.) to generate a unique blockchain ID, i.e., a Hash (Hash) value. Specifically, for management of data, the blockchain may be a blockcoalition chain or an enterprise private chain. When the blockchain is a federation chain, it can be ensured that the blockchain is not fully public and only registered member nodes are accessible, and when the blockchain is an enterprise private chain, the blockchain can only be accessed for nodes inside the enterprise.
The surviving layer 12, which is also a network layer, encapsulates elements such as a P2P networking mode, a message propagation protocol, a data verification mechanism and the like of the blockchain network system, so that nodes are equivalent in status and mutually communicated in a flat topology structure, and has the characteristics of distribution, autonomy, openness, free access and the like. Each node in the blockchain network can participate in the checksum accounting process of the blockdata, and the blockchain can be recorded only after the blockdata is verified by most nodes in the whole network. The design of the block chain for decentralization ensures that file data cannot be tampered and counterfeited.
The certification layer 13 encapsulates the data access mode, encryption, storage, and other elements. The stored data can be encrypted by SHA-256 or SHA-512, and signed by the relevant node or other relevant party, and stored in the blockchain. Even if the file data is acquired by an unauthorized user, the user cannot acquire the original data content by decryption.
The user layer 14 applies blockchain techniques to the relevant processing of data that needs to be stored (e.g., grid business related data), such as user registration, purchase and sale of electricity contracts generation and signing, settlement of electricity fees, and the like. Taking the application of data to be stored as power grid business related data as an example, the application layer provides a data interaction interface for users such as power users, power plants, transaction centers, electricity selling companies, power grid enterprises, supervision institutions and the like.
The blockchain network gathers, packages and secures the data to be stored in a decentralized manner and anchors the digital fingerprint of the data to be stored to the blockchain. In particular, the blockchain may be implemented using a network of blockwise federation chains or enterprise private chains. The nodes of the blockchain continuously transform the responsibilities assumed in the network system, and only one node can never control the whole network system, namely only one billing node can not perform billing. Each node is only part of the network system. The node timing of the blockchain changes roles once every minute, for example, no node will permanently control any part of the network system.
Referring to fig. 2, fig. 2 is a block encapsulation diagram of a block chain in an embodiment of a method for storing service data according to the present application. As shown in fig. 2, in one embodiment, a block 20 of the blockchain includes a block Header (Header) 21 and a block Body (Body) 22, wherein in the current embodiment, data to be stored is defined as set traffic data. The block 22 stores at least one Hash value (Hash) 221 obtained by performing a set Hash operation on the set service data, where the set Hash operation is described below. The block header 21 may be encapsulated with information such as a current version number 211, a previous block address 212, a target hash value 213 of the current block, a solution random number 214 of the current block PoW (proof of work) consensus process, a Merkle root 215, and a timestamp 216. The current version number 211 is used for marking related version information of software and protocols; the previous block address 212, which may also be referred to as a target hash value for the previous block, is the value by which each block is joined end-to-end to form a blockchain; the solution random number 214 is a value for recording an answer for decrypting the block-related mathematical questions; the Merkle root 215 may be a hash value 222 and a hash value 223 which are sequentially calculated from hash values of all the stored set service data in the block 22 step by step, or may be a hash value 222 and a hash value 223 which are sequentially calculated from hash values of all the stored set service data in the block, or may be a hash value which are used for checking whether file data exist in the block in the set hash operation process; the time stamp 216 is used to record the time at which the block 20 was created. It will be appreciated that the structure of the block may be adjusted according to the adopted blockchain technique, for example, a Pow consensus mechanism is not adopted, so that the above-mentioned solution random number does not exist, or the Merkle root may also adopt other set calculation processes or hash calculation processes to obtain.
In one implementation, the blockchain underlying system may be comprised of blocks (blocks) in a hierarchy. The root is the Directory Block (Directory Block). These blocks form a micro-chain on which compressed references are stored. To avoid data size oversizing, references in Directory blocks (Directory blocks) are just hash values of record blocks (Entry blocks).
The directory block corresponds to the first hierarchy of the system, and is a block in which the record block integrity (Hash value) is recorded. A directory block is created by combining all recording blocks defined in all servers together. Thus, each server has all record blocks, all directory blocks, and all records (Entry).
The record Block (Entry Block) corresponds to the second layer of the system and is a Block in which Entry integrity (Hash value) is recorded. The application in finding the records would require a record block from which all possible relevant grid business related data records can be searched for. The record block contains electronically recorded hash values. The electronically recorded hash value simultaneously proves the existence of the data and the key to find the record in the Distributed Hash Table (DHT) network.
The record Block (Entry Block) contains all the entries associated with one chain ID. An Entry may be considered to be absent if it is associated with a certain record Block (Entry Block). The design can enable the application program to easily and pseudo, and can conveniently identify which Entry is true and reliable.
An Entry details a set of business data and determines where in the chain to record based on the type of transaction. Specifically, the Entry is a digital fingerprint, such as a hash value, of the set service data. One or more blockchain nodes for auditing may reference this hash value record of the set business data on their own chain and add a cryptographic signature to indicate that this record is valid or invalid.
In the following related embodiments, a software and hardware environment having a blockchain kernel component that can provide a basic development for building an upper layer application is defined as a blockchain application service platform. The blockchain node operates on the blockchain application service platform to complete data transmission and business processing. The blockchain application service platform may also be understood in some embodiments to allow users to build, host and use their own blockchain applications, smart contracts and functions on the blockchain using cloud-based solutions.
The hash value is a function of a message digest that compresses a message of arbitrary length to a certain fixed length according to a set calculation rule.
Referring to fig. 3, fig. 3 is a flow chart illustrating a method for storing service data according to an embodiment of the application.
S310: the block chain application service platform obtains the set service data.
Further, step S310 of the blockchain application service platform obtaining the setting service data includes: the blockchain application service platform obtains setting service data from the service data center.
Specifically, the blockchain application service platform may read the set service data from the service data center through an application program or script. The service data center refers to a full service unified data center which is pushed by a national power grid, and it should be noted that in the following embodiments, the full service unified data center will be simply referred to as a service data center.
The service data center collects service data collected by at least one electricity consumption information collecting system or an electricity consumption information collecting end. Referring to fig. 4, fig. 4 is a schematic view of an application scenario in another embodiment of a method for storing service data according to the present application. Fig. 4 mainly shows a data collection flow of the service data center.
In one embodiment, the front-end power data collection system 100 includes at least a smart meter 10, a collection terminal 60, a concentrator 30, a power consumption information collection system 40, and a service data center 50. In some embodiments, the electricity consumption information collection system 40 may be defined as an electricity consumption information collection terminal.
It should be noted that, the distributed power generation device is installed by the power consumers such as the power resident users, the power industry and commerce general users, the power large users and the like, the users are allowed to self-use the generated electric quantity, and the residual electricity of the generated electric quantity is allowed to be connected to the power grid company, and the generated energy data, the used electric quantity data and the online electric quantity data generated in the process can be measured by the intelligent electric meter 10. Hereinafter, the electric power residential customers, electric power industry and commerce general customers, electric power large customers, power plants and the like will be collectively referred to as electric power customers, and the intelligent ammeter 10 can simultaneously perform bidirectional metering of the up-and-down electric power between the electric power customers and the power supply network.
The smart meter 10 can automatically collect user power terminal data according to a time interval set by a collection task, and can set collection time, content and objects. When the timing automatic data acquisition fails, the timing automatic data acquisition can be automatically adjusted to be manually supplemented, so that the integrity of the acquired power user data is ensured.
The message queue component (based on Kafka optimizing package) +the stream computing component (based on Storm optimizing package) is adopted to realize that electric quantity, electricity price, tax rate and transaction settlement data generated in information systems such as an electricity consumption information acquisition system 40, an electric power marketing business application MIS system (not shown), a marketing system (not shown), a financial management and control system (not shown), an ERP system (not shown) are accessed to a business data center 50, and the data mining provides bottom data resource support.
The power grid business data acquisition flow is as follows: the intelligent ammeter 10 arranged between the power consumer and the power supply network collects the electricity consumption of the power consumer or the power generation amount of the power plant, the monitored electricity consumption of the power consumer or the power generation amount of the power plant is uploaded to the collection terminal 60, the collection terminal 60 calculates specific data for determining the electricity consumption and/or the power generation amount, the collection terminal 60 uploads the calculated electricity consumption and/or the calculated power generation amount to the electricity consumption information collection system 40 through the concentrator 30, and the electricity consumption information collection system 40 is used for uploading the electricity data collected by the intelligent ammeter 10 in the coverage area to the business data center 50. The service data center 50 accesses and stores the power data collected by the power consumption information collection system 40 through the message queue component.
Further, in other embodiments, the service data center 50 may further include a power marketing service application MIS system, a marketing system, a financial management system, an ERP system, etc., and it is understood that the service data center 50 is not limited to being connected to only the above systems. Service data center 50 may enable access of grid service data from various systems to service data center 50 based on a queuing component and a flow computation component. Still further, grid business data may be accessed from the various systems to the business data center 50 based on a Kafka optimized package and based on a Storm optimized package.
Further, in another embodiment, after the service data center 50 accesses the power data, the power data may be stored according to a set rule, for example, may be stored according to a region and/or a time.
Further, as described above, in some embodiments, the method for storing service data provided by the present application may be used to store power grid service data, and it may be appreciated that in other embodiments, the technical solution provided by the present application may also be used to store other types of service data, such as financial service data, teaching service data, etc., where only power grid service data is used as an example, and other types of data are not listed.
The set business data refers to data required for completing setting the evaluation model or the accounting model, in some embodiments, the data required for completing the evaluation model or the accounting model may also be referred to as key business data, and the specific information type included in the set business data may be determined according to the executed evaluation model or the accounting model, or may be set by a user according to the actual requirement, which is not limited herein. For example, in the electricity fee accounting model, the user name and other user information of the user, the electricity consumption of the user, the electricity unit price of the region where the user is located, the time period where the electricity consumption time of the user is located, the unit price of electricity consumption of different time periods of the region where the user is located, and the like may be set service data, and if the service data corresponds to the user name and other user information, the electricity unit price of the region where the user is located, the unit price of electricity consumption of the region where the user is located, and the like, the blockchain application service platform is required to acquire the various information of the corresponding region or the designated region from the service data center.
S320: and carrying out multi-stage encryption on the set service data to obtain a target hash value.
After the set service data is acquired, the blockchain application service platform further performs multi-stage encryption operation on the acquired set service data to acquire a target hash value. In the current embodiment, the target hash value is a hash value obtained through multi-stage encryption and stored on a blockchain. The multi-level encryption refers to multiple encryption of the set service data by using an encryption algorithm, wherein the encryption algorithm called by the multiple encryption can be the same or can be different according to preset encryption algorithms.
Further, the multi-level encryption means that the set service data is encrypted for a plurality of times by using a hash algorithm. In one embodiment, a hash algorithm may be used to perform a first hash calculation on the set service data to obtain a hash value, and then perform a hash calculation on the obtained hash value and the timestamp information corresponding to the hash value again to obtain the target hash value. It may be understood that in other embodiments, the multi-level encryption may also be implemented by calculating the set service data by using other types of encryption algorithms to obtain a first encrypted value, and then performing a second and/or third hash calculation on the data having a unique correspondence with the set service data and using the obtained first encrypted value and other types of data, so as to finally obtain the target hash value.
S330: and storing the target hash value in a uplink manner according to the category to which the set service data belong.
After the target hash value is obtained in step S320, the target hash value is further stored in a uplink manner according to the type to which the corresponding set service data belongs. If the service data corresponding to the target hash value belongs to the data which can be disclosed, the target hash value is stored in the accessible blockchain, and if the service data corresponding to the target hash value belongs to the confidential data which cannot be disclosed, the target hash value is stored in the private blockchain and is only accessed by users or nodes meeting the access condition.
In the embodiment corresponding to fig. 3, after the set service data is acquired, the blockchain application service platform performs multi-level encryption on the acquired set service data to obtain target hash values, performs uplink storage on the acquired target hash values according to the categories to which the set service data corresponding to the acquired target hash values belongs, better improves the security of the service data by storing the target hash values obtained by multi-level encryption, enhances the security protection capability of data non-falsification, performs uplink storage on the obtained target hash values according to the categories to which the set service data corresponding to the target hash values belongs, and further forms a standard blockchain original data partition center, so that the data storage regularity is improved on the premise of guaranteeing the data security, and the data integration is better completed.
Referring to fig. 5, fig. 5 is a flow chart of another embodiment of a method for storing service data according to the present application. The embodiment corresponding to fig. 5 is mainly further described in step S320.
In the present embodiment, before performing multi-level encryption on the set service data in step S320 to obtain the target hash value, the method provided by the present application further includes step S501.
S501: and cleaning and converting the setting business data to obtain metadata meeting the setting requirements.
When data of a service data center are acquired from a plurality of different service data acquisition systems or service data acquisition terminals, the corresponding data stored in the service data center may have different formats, or data abnormality may be caused during the data transmission process due to various reasons, or data in the process of storing data of the service data may be lost, or the data acquired by the service data acquisition systems or the service data acquisition terminals may be incomplete, based on the reasons, after the blockchain application service platform acquires the set service data, before performing multi-stage encryption on the set service data, the method provided by the application further includes: and cleaning and converting the setting business data to obtain metadata meeting the setting requirements.
Wherein, the cleaning conversion at least comprises: extracting and cleaning the multi-source heterogeneous data, finding error values, missing values, abnormal values, suspicious data and the like, and correcting and complementing the correctable error values, missing values, abnormal values, correctable data and the like to obtain high-quality data, thereby realizing the guarantee of the quality of metadata.
In one embodiment, the meeting the setting requirement at least includes: and converting the set business data into a preset format. Specifically, the specific type of the preset format can be adjusted and set according to the actual requirement.
Further, step S301 may further include: data cleansing transformations are performed using a blockchain ETL (Extract-Transform-Load) tool. In one embodiment, the blockchain application service platform is further configured to upload the metadata obtained through the cleaning conversion to a blockchain application service platform data manager local database. The ETL tool can be used for sequentially extracting, cleaning and converting set service data and then loading the set service data to a local server of a data manager so as to integrate scattered, scattered and non-uniform data acquired from a service data center and provide a data basis for data storage, data analysis and subsequent data calling.
Further, in another embodiment, after performing the cleaning conversion on the setting service data in step S501 to obtain metadata meeting the setting requirement, the method provided by the present application further includes: the obtained metadata is classified according to data attributes, and the metadata is classified into publicable data, non-publicable data, and administrative data. The publicable data, the non-publicable data and the supervision data can be preset, and the category of the data can be obtained after the block chain application service platform identifies the service data. When the service data is power grid service data, the data can be disclosed, at least comprises power consumption data such as user generated energy and power consumption, and the data cannot be disclosed, comprises user identity, bank account information, electric charge settlement statement, power transaction data and the like, and the supervision data at least comprises data required by an energy industry supervision organization.
In yet another embodiment, after the service data center accesses the data in each system, the accessed data is classified according to the data of the publicable data, the non-publicable data and the supervision data, and marked according to the classification result, the method provided by the present application includes, after step S501: and further determining the category to which each metadata belongs to judge whether the classification of the service data center is accurate or not, so as to avoid the problem that the data storage cannot be accurately stored according to the service data category due to inaccurate data classification of the service data center. And checking the class mark of the set business data corresponding to each metadata with the corresponding data content to judge whether the current classification of the set business data is accurate or not, and reclassifying if the current classification is inaccurate.
In the current embodiment, step S320 of performing multi-level encryption on the set service data to obtain the target hash value includes steps S502 to S504.
S502: and carrying out hash calculation on the metadata once to obtain a first hash value.
And carrying out one-time hash calculation on the metadata obtained after the cleaning conversion to obtain a first hash value. Further, in an embodiment, step S502 is to perform hash computation (hash operation) on the obtained set data content by using the SDK (Software Development Kit software development kit) to obtain a first hash value.
Further, in an embodiment, the SHA-512 algorithm is used to perform hash computation to ensure data security by using the encryption technology, where the SHA-512 algorithm is an algorithm with higher security performance in SHA-2, and mainly consists of plaintext padding, message spreading function transformation, random number transformation, and the like, and the initial value and the intermediate computation result consist of 8 shift registers with 64 bits. The SHA-512 algorithm allows the maximum length of the input to be 2-168 bits and generates a 512-bit hash value (in other embodiments, the hash process is also referred to as digest calculation, the hash value obtained through the hash calculation is referred to as message digest), and the input message is divided into 1024-bit blocks for processing, which is a currently accepted high-strength encryption algorithm.
S503: and performing secondary hash calculation on the first hash value and the timestamp information corresponding to the first hash value to obtain a second hash value.
After the first hash value is obtained through the primary hash operation in step S502, a secondary hash calculation is further performed on the first hash value and the timestamp information corresponding to the first hash value, so as to obtain a second hash value. The timestamp information may be time information for calculating the first hash value.
In the present embodiment, the algorithm used for performing the second hash calculation on the first hash value and the timestamp information corresponding to the first hash value may be the same algorithm as in step S502, or may be a different algorithm, and in particular, the present invention is not limited in any way.
S504: and carrying out digital signature on the second hash value to obtain a target hash value.
After the second hash value is obtained through the hash calculation in step S503, the blockchain application service platform digitally signs the obtained second hash value to obtain the target hash value. The target hash value is a second hash value after digital signature.
In the present embodiment, when the class of the set service data is publicable data, step S330 of storing the target hash value in the uplink according to the class to which the set service data belongs may include steps S505 to S506.
S505: and performing consensus verification on the target hash value.
When the category to which the service data belongs is set as the publicable data, the obtained target hash value is subjected to consensus verification. Further, in an embodiment, the target hash value may be authenticated by a blockchain link point running on a blockchain application service platform and a blockchain network in which the blockchain point is located. In another embodiment, the target hash value may be authenticated by the set blockchain network or by a plurality of blockchain nodes set in the set blockchain network.
S506: and storing the target hash value subjected to the consensus verification into an enterprise private ledger.
The private enterprise link refers to a blockchain network that limits read access rights or external open rights, and in some embodiments, the private enterprise link defines that only blockchain nodes inside the enterprise can read and access data stored in the private enterprise link, and each blockchain node in the private enterprise link at least includes accounts held by each department or each user in the enterprise. The enterprise private chain ledger refers to the ledger corresponding to each blockchain node in the enterprise private chain. For example, an enterprise private chain can be deployed inside the power grid enterprise itself to store data, such as power transaction data, necessary for enterprise management with higher security level requirements.
The target hash value subjected to the common verification in step S505 is stored in the uplink by using the chain code API interface, and the target hash value is stored on the private ledger of the enterprise because the set service data corresponding to the current target hash value is publicable data. The data stored on the enterprise private chain account book can be accessed and obtained by all nodes on the private chain, or can be accessed and obtained by blockchain nodes with access rights in the alliance chain where the current enterprise private chain is located or blockchain nodes in all the alliance chains.
Where the federated chain refers to a blockchain whose consensus process is controlled by preselected nodes, in the present embodiment it may refer to a blockchain that is made up of individual power domain enterprises and whose consensus process is controlled by preselected nodes. In particular, a federated chain may be a "partially decentralised" modality. Such as: in order to improve cross-business collaboration among different power grid enterprises, organizations jointly construct a alliance chain, multiple subjects in the alliance can jointly conduct data transaction and maintenance of the alliance chain, such as the above-mentioned party institutions illustrated in fig. 1, wherein an energy industry supervision institution can join the alliance chain to quickly learn about the electric power market transaction condition.
Further, in another embodiment, when the class of the service data is set as the publicable data, the step S330 may also include: and calculating target hash values of all the set business data belonging to the publicable data, which are generated in the set time period, according to the Merker tree principle, generating a root hash value, and performing consensus verification on the root hash value.
The setting time period can be set and adjusted by an administrator according to actual needs. After the target hash value is obtained, further carrying out hash calculation on the target hash value of the set service data which belongs to the publicable data and is generated in the foolproof line time period by adopting an SHA-512 algorithm according to the Merker tree principle, further obtaining a root hash value, and then carrying out consensus verification on the obtained root hash value in a block chain network.
Further, after performing consensus verification on the root hash value, the method provided by the application further comprises the following steps: and storing the root hash value subjected to the consensus verification to an enterprise private chain account book. In the current embodiment, the storage capacity of the enterprise private ledger pair set business data can be further increased by storing the root hash value subjected to the consensus verification on the enterprise private ledger.
After storing the target hash value in the enterprise private ledger or storing the root hash value subjected to the consensus verification in the enterprise private ledger, the method provided by the application further comprises the following steps: and storing the setting business data belonging to the publicable data to a local storage and/or a cloud.
Still further, the setting business data belonging to the publicable data is stored to the local storage and/or the cloud according to the setting rule. For example, the setting service data obtained by the current blockchain application service platform includes user account information of different regions, user electricity consumption information and risk assessment reports of the user, which may be stored according to regions to which the user belongs, and in other embodiments, when an administrator setting needs to be stored according to a risk level to which a result of the user risk assessment report belongs, the setting service data is stored according to a risk level class to which the result of the user risk assessment report belongs.
Referring to fig. 6, fig. 6 is a flow chart of a method for storing service data according to another embodiment of the present application. In the present embodiment, when the category of the business data is set as the confidential data,
The step S320 of storing the target hash value in the uplink according to the category to which the set service data belongs includes:
s601: and performing consensus verification on the target hash value and the attribute information of the set service data.
When the category of the set service data is confidential data, and after the target hash value is obtained, performing consensus verification on the obtained target hash value and the attribute information of the set service data to confirm whether the current target hash value can be stored in a uplink. The attribute information of the setting service data comprises at least one of the category of the setting service data, the energy category corresponding to the setting service data, the setting service data generation time, the account address of the setting service data and the data signature.
S602: and storing the target hash value after the consensus verification and the attribute information of the set business data into a preset enterprise private chain account book.
And storing the target hash value after the consensus verification and the attribute information of the set business data into a preset enterprise private chain account book for accessing by the node or the user with the authority to access the confidential data. In the current embodiment, the private chain ledger of the enterprise may refer to a blockchain used for accounting on the private chain of the enterprise, and the preset private chain ledger of the enterprise is only accessed by nodes or users with access rights.
In an embodiment, for confidential and unpublishable enterprise management data, after obtaining a target hash value, adding an energy type, a data generation time, an account address and a data signature into the calculated target hash value, packaging the obtained target hash value into a block, after common identification verification, storing the block on an enterprise private chain account book built by the block, further completing self-management of support data and point-to-point data sharing function in an organization, and realizing reasonable sharing of information resources while guaranteeing data privacy to the greatest extent.
With continued reference to fig. 6, in a current embodiment, the method provided by the present application further includes:
S603: and storing the setting business data belonging to the confidential data to a local storage and/or a cloud.
The setting business data belonging to the confidential data is stored in a local storage of the blockchain application service platform and/or stored in a cloud through a network so as to be obtained in the local storage and/or the cloud when the blockchain node or a user accesses the setting business data. It will be appreciated that in other embodiments, the setting service of the confidential data may be stored to a location where other blockchain application service platforms can interact with data, and the setting service may be stored according to a setting rule. For example, the confidential data may be stored on a server dedicated to storing the setting business data pertaining to the confidential data.
Further, when the category of the set service data is the supervision data, step S330 includes storing the target hash value in a uplink manner according to the category to which the set service data belongs:
And performing consensus verification on the target hash value.
And carrying out consensus verification on the target hash value of the supervision data to judge the validity of the data. After the target hash value is subjected to consensus verification, the method provided by the application further comprises the following steps: and storing the target hash value subjected to the consensus verification on the alliance chain ledger.
When the category of the set service data is the supervision data required by the energy source organization, after the target hash value of the set service data is obtained, the obtained target hash value is subjected to consensus verification, and the target hash value subjected to the consensus verification is stored on the federation chain general ledger, so that when the supervision organization needs to acquire the supervision data, the supervision organization can access the federation chain. Wherein, alliance chain: refers to a blockchain in which the consensus process is controlled by preselected nodes. The federated chain may be considered as a "partially decentralised" modality.
Further, before storing the target hash value on the federation chain ledger, the method provided by the application further comprises the following steps: and sending requests to other blockchain nodes or storage authority management nodes in the alliance chain to obtain approval of the other blockchain nodes or the storage authority management nodes to pass the requests, and further storing the target hash value of the supervision data onto the alliance chain.
Further, after storing the target hash value on the federation chain ledger, the method provided by the application further comprises:
And storing the setting business data belonging to the supervision data into a storage space and/or a cloud end associated with the supervision institution.
It should be noted that in different embodiments, it is not limited to store the target hash value of the supervision data on the federation chain ledger, and then store the set service data of the supervision data in the storage space and/or the cloud end associated with the supervision institution, for example, according to the actual requirement, store the target hash value of the supervision data on the federation chain ledger, and store the set service data of the supervision data in the storage space and/or the cloud end associated with the supervision institution.
Referring to fig. 7, fig. 7 is a flow chart of a method for acquiring service data according to an embodiment of the application.
S701: the data demand node sends a data acquisition request to the data providing node to request acquisition of target service data.
The data request node may directly send a data acquisition request to the data providing node, or may send a data acquisition request to the data providing node through the blockchain application service platform, where the data providing node at least includes one or more of any one node in the enterprise private chain, any one node in the alliance chain, the cloud end, and the blockchain application service platform, and in some embodiments, the data request node will also be referred to as a data demander, and the data providing node will be referred to as a data provider. In the current embodiment, the target business data is data required for the data demand node, and may be classified into confidential data, publicable data, and regulatory data according to data types. It should be noted that, the data demand node can only point-to-point share the data stored on the private chain or the alliance chain of the enterprise after identity verification, signature verification and authorization, so as to realize data cross-service management.
S702: and receiving a target data packet sent by the data providing node.
After receiving the data acquisition request sent by the data demand node, the data providing node responds to the data acquisition request and sends a target data packet corresponding to the data acquisition request to the data demand node. The data providing node may directly send the target data packet to the data demand node, or indirectly send the target data packet to the data demand node through, for example, a blockchain application service platform.
The target data packet at least comprises target service data and a target hash value for carrying out preset hash calculation on the target service data, and the target data packet is encrypted by utilizing a private key of the data providing node.
S703: decrypting the target data packet by using the public key of the data providing node to obtain target service data, and performing preset hash calculation on the target service data by using a hash algorithm to obtain a hash value to be verified.
After receiving the target data packet, the data demand node further decrypts the target data packet by using the public key of the data providing node to obtain target service data, performs preset hash calculation on the target service data by using a hash algorithm after obtaining the target service data to obtain a verification hash value, and compares the verification hash value with the target hash value in the target data packet after obtaining the verification hash value to judge whether the target service data is legal or not.
In a further embodiment, before step S703, the method provided by the present application further includes: and verifying the digital signature to judge the validity of the target service data.
It should be noted that, in step S703, the process of performing the preset hash calculation on the dumet target service data is the same as the process of performing the hash calculation on the set service data on the blockchain application service platform side, that is, the same hash algorithm and the hash calculation process are adopted. If the blockchain application service platform adopts the SHA-512 algorithm to perform primary hash calculation on the set service data to obtain a first hash value, then performs secondary hash calculation on the first hash value and timestamp information corresponding to the first hash value by using the SHA-512 algorithm to obtain a target hash value, then performs primary hash calculation on the target service data by using the SHA-512 algorithm to obtain a third hash value after receiving the target service data in the target data packet at the data demand node, and then performs secondary hash calculation on the third hash value and timestamp information corresponding to the third hash value by using the SHA-512 algorithm to obtain a verification hash value. Finally, after the verification hash value is obtained, the verification hash value is compared with the target hash value to judge the validity of the target service data.
S704: and if the hash value to be verified is consistent with the target hash value, judging that the target service data is legal.
If the hash value to be verified is obtained through comparison, when the hash value to be verified is consistent with the target hash value, the target service data in the target data packet is legal, namely, the target service data is not modified in the process of transmitting the target service data, and abnormal conditions such as data loss and the like are not generated, and further, the target service data can be determined to be adopted by an evaluation model or an accounting model.
After judging that the target service data is legal, the data demand node can use the received decrypted target service data to complete the model operation required to be performed, and the data demand node also feeds back/displays the operation result front end to the user, so that the power service processing is completed.
Further, referring to fig. 8, fig. 8 is a flow chart illustrating a method for acquiring service data according to an embodiment of the present application. In the present embodiment, it is mainly explained that, before the data demand node sends the data acquisition request to the data providing node in step S701, the method provided by the present application further includes:
s801: and receiving a business operation request input by a user.
Wherein the business operation request at least comprises a business operation request made by using an evaluation model or an accounting model. The business operation performed by the accounting model at least comprises at least one of electric charge settlement, financial auditing and balance checking, and the business operation request performed by the evaluation model at least comprises risk evaluation control, wherein the risk evaluation control can be the evaluation of power supply pressure or the evaluation of electric power safety. It should be noted that, different business operation requests correspond to different business models, and the business models are set according to actual application scenarios or actual requirements, so the present invention is not limited thereto.
S802: and determining target service data required by the service operation request, and generating a data acquisition request based on the required target service data.
The target service data required by the service operation request is determined according to the service model, for example, when the service operation request is electric charge settlement, the target service data at least comprises at least one of account information of a user, electricity consumption type, electricity consumption in different time periods, unit price of electricity consumption in different time periods and the like.
Referring to fig. 9, fig. 9 is an interaction diagram of a method for acquiring service data according to an embodiment of the application. In the present embodiment, the method for acquiring service data provided by the present application includes the following contents 1 to 11, and specifically, the method provided by the present application includes:
1. and sending a data acquisition request. The client sends a data acquisition request to the blockchain service platform to acquire the required data.
The client refers to a data requesting party, which may be a data requesting node, and in the current embodiment, the data provider is composed of a blockchain application service platform, a blockchain node and a cloud. It will be appreciated that in other embodiments the data provider and the data demander are not limited to include only the various components described above.
In another embodiment, the client may directly send a request for obtaining data to the blockchain node and the cloud end, where the blockchain node responds to the request to send the target hash value of the corresponding data to the client after receiving the request for obtaining data, and the cloud end responds to the request to send the original data of the corresponding data to the client after receiving the request for obtaining data.
2. The blockchain application service platform responds to the data acquisition request.
The blockchain application service platform responds to the data acquisition request and performs the contents described in 3 below.
3. And sending a request for obtaining the hash value corresponding to the data to the block chain link point.
4. And sending an original data request for acquiring data to the cloud.
It should be noted that, although fig. 9 shows that the steps 3 and 4 are performed first, the sequence between the steps 3 and 4 is not limited in the present embodiment.
5. And the block chain link point responds to a request for acquiring the hash value corresponding to the data and sends the target hash value to the block chain application server platform.
The target hash value refers to a hash value corresponding to data required by a data requiring party.
6. And the cloud responds to an original data request for acquiring data, and sends the original data to the blockchain application service platform.
The original data is data required by the corresponding data demander or one of the data required by the data demander.
7. The blockchain application service platform packages the original data and the target hash value into a target data packet.
And the block chain application service platform packages the acquired original data and the target hash value into a target data packet to be sent to the client so as to respond to the data acquisition request. It will be appreciated that in other embodiments, the blockchain application service platform may also directly send the obtained original data and the target hash value to the client, so as to implement the response data obtaining request.
8. And sending the target data packet to the client to respond to the data acquisition request.
9. Decrypting the target data packet by using the public key of the block chain node to obtain target service data and a target hash value, and performing preset hash calculation on the target service data by using a hash algorithm to obtain a hash value to be verified.
Further, performing preset hash calculation on the target service data by using a hash algorithm comprises performing first hash calculation on the target service data by using the hash algorithm to obtain a first hash value, and performing secondary hash calculation on the first hash value and timestamp information corresponding to the first hash value to obtain a hash value to be verified. The hash algorithm for the two hash calculations can be the same or different, and at least comprises SHA-512 algorithm.
10. And comparing the hash value to be verified with the target hash value.
11. And if the hash value to be verified is consistent with the target hash value, judging that the target data is legal.
In the method for acquiring the service data, whether the target data is legal or not can be well judged by comparing whether the hash value to be verified is consistent with the target hash value, the data source is verified, the identity of the data main body is checked, and the content can be considered to be not tampered by the verification consistency.
Referring to fig. 10, fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the application. In the current embodiment, the electronic device 1000 provided by the present application includes a processor 1001 and a memory 1002 coupled. The electronic device 1000 may be a blockchain application service platform that performs the methods described in any of the embodiments of fig. 1-9 and corresponding thereto.
The memory 1002 includes a local storage (not shown), and stores a computer program, where the computer program is executed to implement the methods described in any of the embodiments of fig. 1 to 9 and corresponding embodiments.
The processor 1001 is coupled to the memory 1002, the processor 1001 being configured to execute a computer program for performing the method as described in any of the above fig. 1-9 and their corresponding embodiments.
Referring to fig. 11, fig. 11 is a schematic diagram illustrating a structure of a storage medium according to an embodiment of the application. The storage medium 1100 stores a computer program 1101 that can be executed by a processor, the computer program 1101 being configured to implement the method as described in any of the above fig. 1 to 9 and their corresponding embodiments. Specifically, the storage medium 1100 may be one of a memory, a personal computer, a server, a network device, a usb disk, and the like.
The foregoing description is only of embodiments of the present application, and is not intended to limit the scope of the application, and all equivalent structures or equivalent processes using the descriptions and the drawings of the present application or directly or indirectly applied to other related technical fields are included in the scope of the present application.
Claims (10)
1. A method of business data storage, comprising:
the method comprises the steps that a block chain application service platform obtains set service data from a service data center, wherein the service data are power grid service data;
Judging whether a data classification result of a service data center is accurate or not, wherein the data classification result comprises publicable data, confidential data and supervision data;
In response to the data classification result being accurate, carrying out multi-stage encryption on the set service data to obtain a target hash value, wherein the multi-stage encryption represents that the set service data is encrypted for a plurality of times by utilizing an encryption algorithm; wherein the performing multi-stage encryption on the set service data to obtain a target hash value includes: performing primary hash calculation on the set service data to obtain a first hash value; performing secondary hash calculation on the first hash value and timestamp information corresponding to the first hash value to obtain a second hash value; digitally signing the second hash value to obtain the target hash value;
storing the target hash value in a uplink manner according to the category to which the set service data belong so as to enable a user or a node meeting access conditions to access; the public data and the target hash value corresponding to the confidential data are stored in an enterprise private chain ledger, and the target hash value corresponding to the supervision data is stored in a alliance chain ledger.
2. The method of claim 1, wherein,
Before the multi-stage encryption is performed on the set service data to obtain a target hash value, the method further includes:
Cleaning and converting the setting service data to obtain metadata meeting the setting requirements;
the step of performing multi-stage encryption on the set service data to obtain a target hash value includes:
performing primary hash calculation on the metadata to obtain a first hash value;
performing secondary hash calculation on the first hash value and timestamp information corresponding to the first hash value to obtain a second hash value;
And carrying out digital signature on the second hash value to obtain the target hash value.
3. The method of claim 1, wherein when the category of the service data is the publicable data,
The step of storing the target hash value in a uplink manner according to the category to which the set service data belongs includes:
performing consensus verification on the target hash value; and
Storing the target hash value subjected to consensus verification into the enterprise private chain account book;
Or alternatively
Calculating target hash values of all set business data belonging to the publicable data generated in a set time period according to the Merker tree principle, generating a root hash value, and performing consensus verification on the root hash value; and
Storing the root hash value subjected to the consensus verification to the enterprise private chain account book;
the method further comprises the steps of:
And storing the setting business data belonging to the publicable data to a local storage and/or a cloud.
4. The method of claim 1, wherein when the set service data is classified as the confidential data,
The step of storing the target hash value in a uplink manner according to the category to which the set service data belongs includes:
Performing consensus verification on the target hash value and the attribute information of the set service data; wherein the attribute information of the set service data comprises at least one of a category of the set service data, an energy category corresponding to the set service data, a set service data generation time, an account address of the set service data and a data signature;
Storing the target hash value after the consensus verification and the attribute information of the set business data into a preset enterprise private ledger;
the method further comprises the steps of:
and storing the setting business data belonging to the confidential data to a local storage and/or a cloud.
5. The method of claim 1, wherein when the category of the set service data is the regulatory data,
The step of storing the target hash value in a uplink manner according to the category to which the set service data belongs includes:
performing consensus verification on the target hash value;
storing the target hash value subjected to the consensus verification to the alliance chain ledger;
the method further comprises the steps of:
And storing the setting business data belonging to the supervision data into a storage space and/or a cloud end associated with the supervision institution.
6. The method of claim 1, wherein the blockchain application service platform obtaining the set service data comprises:
The service data center collects service data collected by at least one service data collection terminal.
7. A method for acquiring service data, the method comprising:
The data demand node sends a data acquisition request to the data providing node to request acquisition of target service data, wherein the target service data is set service data which is stored in a uplink, and the step of storing the set service data comprises the following steps: the method comprises the steps that a blockchain application service platform obtains setting service data from a service data center, wherein the setting service data refers to power grid service data required by completing setting an evaluation model or an accounting model; judging whether a data classification result of a service data center is accurate or not, wherein the data classification result comprises publicable data, confidential data and supervision data; in response to the data classification result being accurate, carrying out multi-stage encryption on the set service data to obtain a target hash value, wherein the multi-stage encryption represents that the set service data is encrypted for a plurality of times by utilizing an encryption algorithm; wherein the performing multi-stage encryption on the set service data to obtain a target hash value includes: performing primary hash calculation on the set service data to obtain a first hash value; performing secondary hash calculation on the first hash value and timestamp information corresponding to the first hash value to obtain a second hash value; digitally signing the second hash value to obtain the target hash value; storing the target hash value in a uplink manner according to the category to which the set service data belong; the public data and the target hash value corresponding to the confidential data are stored in an enterprise private chain ledger, and the target hash value corresponding to the supervision data is stored in a alliance chain ledger;
receiving a target data packet sent by the data providing node; the target data packet at least comprises the target service data and a target hash value for carrying out preset hash calculation on the target service data, and is encrypted by using a private key of the data providing node;
Decrypting the target data packet by using the public key of the data providing node to obtain the target service data, and performing the preset hash calculation on the target service data by using a hash algorithm to obtain a hash value to be verified;
And if the hash value to be verified is consistent with the target hash value, judging that the target service data is legal.
8. The method of traffic data acquisition according to claim 7, wherein before the data demand node sends a data acquisition request to a data providing node, the method further comprises:
receiving a business operation request input by a user, wherein the business operation request comprises at least one of electric charge settlement, risk control, financial auditing and balance checking;
and determining target service data required by the service operation request, and generating the data acquisition request based on the required target service data.
9. An electronic device comprising a memory and a processor, wherein,
The processor is configured to execute a computer program stored in the memory to perform the method according to any one of claims 1 to 8.
10. A storage medium storing a computer program executable by a processor to perform the method of any one of claims 1to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911194837.3A CN111259070B (en) | 2019-11-28 | 2019-11-28 | Method and related device for storing and acquiring service data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911194837.3A CN111259070B (en) | 2019-11-28 | 2019-11-28 | Method and related device for storing and acquiring service data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111259070A CN111259070A (en) | 2020-06-09 |
| CN111259070B true CN111259070B (en) | 2024-04-19 |
Family
ID=70948508
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911194837.3A Active CN111259070B (en) | 2019-11-28 | 2019-11-28 | Method and related device for storing and acquiring service data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111259070B (en) |
Families Citing this family (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111401916B (en) * | 2020-06-05 | 2020-10-02 | 支付宝(杭州)信息技术有限公司 | Transaction risk identification method and device |
| CN111698254B (en) * | 2020-06-15 | 2022-11-15 | 中国银行股份有限公司 | Alliance chain Baas platform building method based on sharing organization |
| CN111563130A (en) * | 2020-07-15 | 2020-08-21 | 成都无右区块链科技有限公司 | Data credible data management method and system based on block chain technology |
| CN111917861A (en) * | 2020-07-28 | 2020-11-10 | 广东工业大学 | Knowledge storage method and system based on block chain and knowledge graph and application thereof |
| CN111914274A (en) * | 2020-07-30 | 2020-11-10 | 南京中诚区块链研究院有限公司 | Full-process block chain system based on multiple information sources |
| CN111984613B (en) * | 2020-08-04 | 2023-06-16 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN111984614B (en) * | 2020-08-04 | 2023-05-26 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN112039972B (en) * | 2020-08-26 | 2023-10-27 | 蚂蚁胜信(上海)信息技术有限公司 | Service processing method, device and equipment |
| WO2022051924A1 (en) * | 2020-09-09 | 2022-03-17 | 中诚区块链研究院(南京)有限公司 | Transaction blockchain capable of providing multiple encryption modes |
| CN111930851B (en) * | 2020-09-25 | 2021-05-14 | 腾讯科技（深圳）有限公司 | Control data processing method, device, medium and electronic equipment of block chain network |
| CN112560097B (en) * | 2020-12-22 | 2022-09-30 | 广州技象科技有限公司 | Storage management method and device for power business data |
| CN112733211A (en) * | 2021-01-15 | 2021-04-30 | 重庆邮电大学 | Intelligent power grid data storage scheme based on block chain |
| CN112883414A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | IT asset management and renovation platform |
| CN112883428A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Tamper-proof method for IT asset management system |
| CN112883431A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Method for operating IT asset data on data management platform |
| CN114154189B (en) * | 2021-01-29 | 2022-06-24 | 北京天德科技有限公司 | Two-section type Hash chain link evidence storing method for data or files |
| CN112967149B (en) * | 2021-02-03 | 2024-01-26 | 广东电力信息科技有限公司 | Multi-party electric quantity statistical information sharing method and system based on block chain technology |
| CN112822224B (en) * | 2021-04-19 | 2021-06-22 | 国网浙江省电力有限公司 | Safe transmission method for financial data query |
| CN113468551A (en) * | 2021-05-31 | 2021-10-01 | 南京邮电大学 | Domestic intelligent electric meter data storage system and method based on alliance block chain |
| CN113407958B (en) * | 2021-06-03 | 2023-08-25 | 广东辰宜信息科技有限公司 | Signature data processing method, device, equipment and medium |
| CN113254969B (en) * | 2021-06-08 | 2022-10-11 | 挂号网（杭州）科技有限公司 | Business data processing method and device, electronic equipment and storage medium |
| CN113434909B (en) * | 2021-06-25 | 2023-12-29 | 湖北央中巨石信息技术有限公司 | Data on-demand evidence-storing method based on blockchain |
| CN113419894B (en) * | 2021-07-20 | 2022-11-15 | 网易（杭州）网络有限公司 | Data inspection method, data inspection device, storage medium and computer equipment |
| CN113630425B (en) * | 2021-10-08 | 2022-01-07 | 国网浙江省电力有限公司金华供电公司 | Financial data safe transmission method for multiple power bodies |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107135661A (en) * | 2016-12-26 | 2017-09-05 | 深圳前海达闼云端智能科技有限公司 | Data processing method, device, system and information collecting device |
| CN107609844A (en) * | 2017-10-10 | 2018-01-19 | 厦门易采购电子商务有限公司 | A kind of intelligence engineering network transaction data management system based on block chain |
| CN109409122A (en) * | 2018-09-13 | 2019-03-01 | 远光软件股份有限公司 | File memory method and its electronic equipment, storage medium |
| CN109831501A (en) * | 2019-01-30 | 2019-05-31 | 京东数字科技控股有限公司 | Information dispensing method and system based on block chain |
| CN110010212A (en) * | 2018-01-04 | 2019-07-12 | 苏州同济区块链研究院有限公司 | Archives Sharing Management platform based on block chain |
| CN110493007A (en) * | 2019-09-06 | 2019-11-22 | 腾讯科技（深圳）有限公司 | A kind of Information Authentication method, apparatus, equipment and storage medium based on block chain |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190332921A1 (en) * | 2018-04-13 | 2019-10-31 | Vosai, Inc. | Decentralized storage structures and methods for artificial intelligence systems |
-
2019
- 2019-11-28 CN CN201911194837.3A patent/CN111259070B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107135661A (en) * | 2016-12-26 | 2017-09-05 | 深圳前海达闼云端智能科技有限公司 | Data processing method, device, system and information collecting device |
| CN107609844A (en) * | 2017-10-10 | 2018-01-19 | 厦门易采购电子商务有限公司 | A kind of intelligence engineering network transaction data management system based on block chain |
| CN110010212A (en) * | 2018-01-04 | 2019-07-12 | 苏州同济区块链研究院有限公司 | Archives Sharing Management platform based on block chain |
| CN109409122A (en) * | 2018-09-13 | 2019-03-01 | 远光软件股份有限公司 | File memory method and its electronic equipment, storage medium |
| CN109831501A (en) * | 2019-01-30 | 2019-05-31 | 京东数字科技控股有限公司 | Information dispensing method and system based on block chain |
| CN110493007A (en) * | 2019-09-06 | 2019-11-22 | 腾讯科技（深圳）有限公司 | A kind of Information Authentication method, apparatus, equipment and storage medium based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111259070A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111259070B (en) | Method and related device for storing and acquiring service data | |
| CN111737724B (en) | Data processing method and device, intelligent equipment and storage medium | |
| CN109409122B (en) | File storage method, electronic device and storage medium | |
| CN109413087B (en) | Data sharing method and device, digital gateway and computer readable storage medium | |
| TWI666902B (en) | Robust ATM network system and information processing method based on blockchain technology | |
| CN106254374B (en) | A kind of cloud data public audit method having duplicate removal function | |
| CN109472164A (en) | The verification method and its network and electronic equipment of contract dataset | |
| Jawurek et al. | Plug-in privacy for smart metering billing | |
| CN110120868B (en) | Smart power grid safety data aggregation method and system based on block chain technology | |
| Wang et al. | Distributed meter data aggregation framework based on Blockchain and homomorphic encryption | |
| CN114499895B (en) | Data trusted processing method and system fusing trusted computing and block chain | |
| CN104506487B (en) | The credible execution method of privacy policy under cloud environment | |
| CN109491965A (en) | The storage method and its network and electronic equipment of purchase sale of electricity contract | |
| CN111526200A (en) | Data storage access method and system based on block chain and cloud platform | |
| CN109889497A (en) | A kind of data integrity verification method for going to trust | |
| CN112257085A (en) | Bidding processing method, system, equipment and medium based on block chain | |
| CN112508733A (en) | Big data intelligence service system in electric wire netting space-time based on big dipper | |
| Huang et al. | A data storage and sharing scheme for cyber-physical-social systems | |
| Baniata et al. | Prifob: a privacy-aware fog-enhanced blockchain-based system for global accreditation and credential verification | |
| Khan et al. | A blockchain based secure decentralized transaction system for energy trading in microgrids | |
| KR101120059B1 (en) | Billing verifying apparatus, billing apparatus and method for cloud computing environment | |
| CN110232283A (en) | The method and relevant apparatus of blacklist cloud shared authentication based on homomorphic cryptography | |
| KR102494873B1 (en) | Transaction execution device to implement a virtual machine based on a zero-knowledge proof circuit for general operation verification | |
| CN108616497A (en) | Data integrity verification method and system, terminal and authentication server under cloud environment | |
| EP3859652A1 (en) | Technique for trustless cryptographic verification of energy allocations |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |