CN111259070A - 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
- CN111259070A CN111259070A CN201911194837.3A CN201911194837A CN111259070A CN 111259070 A CN111259070 A CN 111259070A CN 201911194837 A CN201911194837 A CN 201911194837A CN 111259070 A CN111259070 A CN 111259070A
- Authority
- CN
- China
- Prior art keywords
- data
- service data
- hash value
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 100
- 238000003860 storage Methods 0.000 claims abstract description 46
- 238000013500 data storage Methods 0.000 claims abstract description 10
- 238000004364 calculation method Methods 0.000 claims description 42
- 238000012795 verification Methods 0.000 claims description 36
- 238000004422 calculation algorithm Methods 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 10
- 238000004140 cleaning Methods 0.000 claims description 8
- 238000013480 data collection Methods 0.000 claims description 3
- 230000008520 organization Effects 0.000 claims description 3
- 238000012954 risk control Methods 0.000 claims 1
- 230000005611 electricity Effects 0.000 description 31
- 230000008569 process Effects 0.000 description 20
- 238000010586 diagram Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 239000000306 component Substances 0.000 description 6
- 238000013210 evaluation model Methods 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000005538 encapsulation Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000010248 power generation Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000011156 evaluation Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012502 risk assessment Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 239000008358 core component Substances 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
- 230000010354 integration Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000003892 spreading Methods 0.000 description 1
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Bioethics (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a method and a related device for storing and acquiring service data, wherein the method comprises the following steps: the method comprises the steps that a block chain application service platform obtains set service data; performing multi-stage encryption on set service data to obtain a target hash value; and performing uplink storage on the target hash value according to the type of the set service data. According to the technical scheme, after the set service data are subjected to multi-level encryption, uplink storage is carried out according to the type of the set service data, and therefore the safety of the service data and the orderliness of data storage are improved.
Description
Technical Field
The present application relates to the field of networks, and in particular, to a method and a related apparatus for storing and acquiring service data.
Background
With the continuous deepening of the information construction and application of the power enterprises, the cross-service coordination requirements of the power grid enterprises are increased greatly, and the existing centralized data center cannot meet the requirement of expandability and low delay of the power grid service data storage; in addition, because data of the data center generally has the characteristics of large quantity, diversity, fast increment and low value density, when an enterprise operates, each information system is difficult to acquire credible, 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 a technical scheme capable of solving the technical problems is needed.
Disclosure of Invention
The technical problem mainly solved by the application is to provide a method and a related device for storing and acquiring business data, which can improve the safety of the business data.
In order to solve the technical problem, the application adopts a technical scheme that: a method of providing business data storage, the method comprising:
the method comprises the steps that a block chain application service platform obtains set service data;
performing multi-stage encryption on the set service data to obtain a target hash value;
and performing uplink storage on the target hash value according to the type of the set service data.
In order to solve the above technical problem, another technical solution adopted by the present application is to provide a method for acquiring service data, where the method includes:
the data demand node sends a data acquisition request to the data providing node to request to acquire 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 performing preset hash calculation on the target service data, and the target data packet 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 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 above technical problem, another technical solution adopted by the present application is to provide an electronic device, including 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.
In order to solve the above technical problem, another technical solution adopted by the present application is to provide a storage medium storing a computer program, wherein the computer program can be executed by a processor to perform the method as described above.
According to the technical scheme, the block chain application service platform conducts multi-stage encryption on the set service data by acquiring the set service data, further obtains the target hash value, conducts cochain storage on the target hash value according to the type of the set service data, can well improve the safety of the service data by cochain storage on the target hash value obtained through multi-stage encryption, conducts cochain storage according to the type of the set service data when the target hash value of the set service data is stored, and can well improve the orderliness of data storage.
Drawings
Fig. 1 is a block chain technical architecture diagram in an embodiment of a method for storing service data according to the present application;
fig. 2 is a block encapsulation diagram of a block chain according to an embodiment of a method for storing service data in the present application;
fig. 3 is a schematic flowchart illustrating an embodiment of a method for storing service data according to 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 schematic flowchart of another embodiment of a method for storing service data according to the present application;
fig. 6 is a schematic view of an application scenario in another embodiment of a method for storing service data according to the present application;
fig. 7 is a schematic flowchart illustrating an embodiment of a method for acquiring service data according to the present application;
fig. 8 is a schematic flowchart of another embodiment of a method for acquiring service data according to the present application;
fig. 9 is an interaction diagram in an embodiment of a method for acquiring service data according to the present application;
FIG. 10 is a schematic structural diagram of an embodiment of an electronic device of the present application;
FIG. 11 is a schematic structural diagram of an embodiment of a storage medium according to 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 drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively 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 can be included in at least one embodiment of the application. The appearances of the phrase 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. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
To facilitate understanding of the technical solutions provided in the present application, before explaining the technical solutions provided in the present application, first, the key terms or technical abbreviations mentioned in the specification of the present application are explained:
the block chain technology is a novel distributed data organization method and an operation mode which are developed along with digital encryption currencies such as bitcoin and the like. The method is characterized in that: decentralization enables the data to realize distributed collective maintenance, and greatly improves the efficiency of data operation, management and maintenance; and (3) consensus, wherein the nodes are based on a set of consensus mechanism, the whole block chain is maintained together through competition calculation, any node fails, and other nodes can still work normally. Meanwhile, the block chain carrying the asymmetric encryption technology has high safety and traceability, and can effectively prevent data leakage or illegal tampering. A blockchain may also be understood as a decentralized database, with data stored as a series of blocks in chronological order, each block referencing the hash pointer of the preceding block to form an interconnected chain. The blockchain comprises a plurality of nodes which can be called blockchain nodes, each node of the blockchain stores a complete copy, the blockchain can automatically synchronize and verify data on all the nodes, and the blockchain has the characteristics of distribution and synchronization. The present application proposes to implement data storage based on a block chain technique, such as storage of power grid service related data, which is described in detail in the following related embodiments. The power grid service related data at least includes one of power consumption of a user, power generation amount sent to a power grid, account information of the user, power consumption of each region in different time periods, power generation amount and the like, and it can be understood that the power grid service related data can be adjusted according to actual storage requirements, and is not limited herein.
To facilitate understanding of the blockchain network of the present application, the blockchain technique employed in the present application is first exemplified. Referring to fig. 1, fig. 1 is a block chain technical architecture diagram in an embodiment of a method for storing service data according to the present application. In one embodiment, the electronic device runs the blockchain technique to become a node of the blockchain network, and the blockchain technique is configured as shown in fig. 1 and includes a blockchain data layer 11, a presence layer 12, a presence 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 the management of data, the blockchain may be a blockfederation chain or an enterprise private chain. When the blockchain is a federation chain, it can be guaranteed that the blockchain is not completely public and only accessible to registered member nodes, and when the blockchain is an enterprise private chain, the blockchain can only be accessible to nodes within the enterprise.
The presence layer 12, which is also a network layer, encapsulates elements of a P2P networking mode, a message propagation protocol, a data verification mechanism, and the like of the blockchain network system, so that nodes are in peer-to-peer status and communicate with each other in a flat topology structure, and have the characteristics of distribution, autonomy, openness, free access, and the like. Each node in the block chain network can participate in the checking and accounting process of the block data, and the block chain can be recorded only after the block data passes verification of most nodes in the whole network. The decentralized design of the block chain ensures that the file data cannot be tampered and forged.
The evidence storage layer 13 encapsulates elements such as data access mode, encryption, storage and the like. The data stored in the block chain can be signed by a related node or other related parties by using an encryption technology such as SHA-256 or SHA-512, and then stored in the block chain. 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 the blockchain technology to the related processing of the data (such as the data related to the power grid service) required to be stored, such as user registration, generation and signing of power purchase and sale contracts, settlement of power fees, and the like. Taking the application that the data required to be stored is the related data of the power grid service as an example, the application layer provides a data interaction interface for users such as power consumers, power plants, transaction centers, power selling companies, power grid enterprises, and monitoring organizations.
The blockchain network collects, packages and secures data to be stored in a decentralized manner, and anchors digital fingerprints of the data to be stored to the blockchain. In particular, the blockchain may be implemented using a network of blockfederation chains or enterprise private chains. The nodes of the block chain continuously change the responsibility born by the network system, and only one node can never control the whole network system, namely only one accounting node can not carry out accounting. Each node is only part of the network system. The node timing of the blockchain changes roles, e.g., once every minute, and 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, the block 20 of the block chain includes a block Header (Header)21 and a block Body (Body)22, wherein, in the current embodiment, the data to be stored is defined as the set service data. The block 22 stores at least one Hash value (Hash)221 obtained by performing Hash operation on the configured service data, where the Hash operation is described below. The block header 21 may be packaged 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 a PoW (workload proof) consensus process of the current block, a Merkle root (Merkle-root)215, and a timestamp 216. Wherein, the current version number 211 is used for marking the relevant version information of software and protocol; the previous block address 212, which may also be referred to as the target hash value of the previous block, by which each block is end-to-end grouped into a block chain; the solution random number 214 is a value of the answer to record the decrypted block-related mathematical question; the Merkle root 215 may be a hash value 222 and a hash value 223 obtained by sequentially calculating the hash values of all stored set service data in the block 22 by hashing two by two step, or may be a hash value used for checking whether file data exists in the block in the set hash operation process; the timestamp 216 is used to record the time when the block 20 was generated. It is understood that the structure of the block can be adjusted according to the block chain technique, for example, instead of using the Pow consensus mechanism, the random number solution does not exist, or the Merkle root can be obtained by using other set calculation processes or hash calculation processes.
In one embodiment, the Block chain underlying system may be comprised of hierarchically structured blocks (blocks). The root is a Directory Block (Directory Block). These blocks form a mini chain, on which compressed references (references) are stored. In order to avoid the data size being too large, the reference in the Directory Block (Directory Block) is only the hash value of the recording Block (Entry Block).
The directory block corresponds to the first layer of the system and records the integrity (Hash value) proof block of the recording block. The directory block is created by combining all the recording blocks defined in all the servers together. Thus, each server has all recording blocks, all directory blocks, and all records (entries).
The recording Block (Entry Block) corresponds to the second layer of the system and is a Block for recording an Entry integrity (Hash value) certificate. In applications where records are sought, the record blocks may be required, and records of all possible relevant grid service related data may be searched from one digital fingerprint. The recording block contains the electronically recorded hash value. The electronically recorded hash value simultaneously proves the existence of the data and the key to find the record in a Distributed Hash Table (DHT) network.
The recording Block (Entry Block) contains all entries associated with one chain ID. An Entry may be considered not to exist if it is associated to a recording Block (Entry Block). The design can ensure that the application program can be easily certified and can conveniently identify which entries are real and reliable.
An Entry details the details of a set transaction, and determines where to record in the chain based on the type of such transaction. Specifically, the Entry is a digital fingerprint, such as a hash value, of the set service data. One or more of the block link points used for auditing may reference the hash record of the set transaction data on their own chain and add a cryptographic signature to indicate whether the record is valid or invalid.
In the following related embodiments, a software and hardware environment having a blockchain core component and capable of providing basic research and development for building upper-layer applications is defined as a blockchain application service platform. The blockchain node runs on the blockchain application service platform to complete data transmission and service processing. A blockchain application service platform may also be understood in some embodiments to allow users to build, host, and use their own blockchain applications, intelligent contracts, and functionality on blockchains using cloud-based solutions.
The hash value is a function for compressing a message of an arbitrary length to a message digest of a fixed length according to a set calculation rule.
Referring to fig. 3, fig. 3 is a schematic flowchart illustrating an embodiment of a method for storing service data according to the present application.
S310: and the block chain application service platform acquires the set service data.
Further, the step S310 of obtaining the set service data by the blockchain application service platform includes: the block chain application service platform acquires set service data from a 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 a script. The service data center refers to a full-service unified data center which is built by being promoted by a national power grid of China, and it should be noted that the full-service unified data center is simply referred to as the service data center in each embodiment below.
The service data center collects service data collected by at least one power utilization information collection system or power utilization information collection 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 process of the business data center.
In one embodiment, the front-end power data collection system 100 at least includes the 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 information collecting system 40 may also be defined as an electricity information collecting terminal.
It should be noted that, the distributed power generation equipment is installed by electricity consumers, electricity industry and business general users, electricity consumers and other electricity consumers, the users are allowed to use the generated electricity spontaneously, meanwhile, the rest electricity of the generated electricity is allowed to be networked to the power grid company, and the generated energy data, the electricity consumption data and the networked electricity quantity data generated in the process can be metered through the smart meter 10. Hereinafter, the residential power consumers, the commercial power consumers, the large power consumers, and the power plants will be referred to as power consumers, and the smart meter 10 can measure the amount of electricity supplied to and from the power supply network in both directions.
The smart meter 10 may automatically collect data of the user power terminal according to a time interval set by the collection task, and may set a collection time, a collection content, and a collection object. When the timing automatic data acquisition fails, the data acquisition can be automatically adjusted to be a manual complementary acquisition mode, and the integrity of the acquired power consumer data is further ensured.
By adopting a message queue component (based on Kafka optimized packaging) + a flow calculation component (based on Storm optimized packaging), the electric quantity, the electric price, the tax rate and the transaction settlement data generated from information systems such as an electricity utilization information acquisition system 40, an electricity 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) and the like are accessed to a business data center 50, and bottom data resource support is provided for data mining.
The power grid service data acquisition process comprises the following steps: the intelligent electric meter 10 arranged between an electric power consumer and a power supply network collects the electricity consumption of the electric power consumer or the generated energy of a power plant, the monitored electricity consumption of the electric power consumer or the monitored generated energy of the power plant is uploaded to the collection terminal 60, the collection terminal 60 determines specific data of the electricity consumption and/or the generated energy through calculation, the collection terminal 60 uploads the calculated electricity consumption and/or generated energy 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 electric meter 10 in the coverage area of the electricity consumption information collection system to the service 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 is connected to an electricity marketing service application MIS system, a marketing system, a financial management and control system, an ERP system, and the like, and it is to be understood that the service data center 50 may be connected to each of the above systems only. The service data center 50 may enable access of grid service data from various systems to the service data center 50 based on queue components and flow computation components. Further, it is possible to access grid service data from various systems to the service data center 50 based on Kafka optimized encapsulation and Storm optimized encapsulation.
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, the power data 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 is understood 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, and the like, which are only described herein by way of example with reference to power grid service data, and the other types of data are not listed.
The setting of the service data refers to data required for completing the setting of the evaluation model or the accounting model, and in some embodiments, the data required for completing the evaluation model or the accounting model may also be referred to as key service data, and the specific information type included in the setting of the service data may be determined according to the executed evaluation model or the accounting model, or may be selected and set by a user according to actual requirements, 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 unit price of the area where the user is located, the time period of the electricity consumption time of the user, the electricity consumption unit price of different time periods of the area where the user is located, and the like can be set as service data, and correspondingly, the block chain application service platform needs to obtain the various types of information of the area corresponding to the block chain application service platform or the designated area from the service data center.
S320: and performing multi-stage encryption on the set service data to obtain a target hash value.
After the block chain application service platform obtains the set service data, the block chain application service platform further performs multi-stage encryption operation on the obtained set service data to obtain a target hash value. In the present embodiment, the target hash value is a hash value obtained through multi-stage encryption and stored in the blockchain. The multi-level encryption is to encrypt the set service data multiple times by using an encryption algorithm, wherein it should be noted that the encryption algorithm called by the multiple encryption may be the same, or may be different encryption algorithms according to the preset encryption algorithm.
Further, the multi-stage encryption means that the set service data is encrypted for multiple times by using a hash algorithm. For example, in an embodiment, a hash algorithm may be used to perform a first hash calculation on set service data to obtain a hash value, and then perform a hash calculation on the obtained hash value and timestamp information corresponding to the hash value again to obtain a target hash value. It is understood that in other embodiments, the multi-stage 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 hash calculation twice and/or three times on the obtained first encrypted value and other types of data that have unique correspondence with the set service data to finally obtain the target hash value.
S330: and performing uplink storage on the target hash value according to the type of the set service data.
After the target hash value is obtained in step S320, the target hash value is further uplink-stored according to the type of the corresponding set service data. If the business data corresponding to the target hash value belongs to the public data, the target hash value is stored to the accessible block chain, and if the business data corresponding to the target hash value belongs to the secret class data which can not be disclosed, the target hash value is stored to the private block chain and is only accessed by the users or the nodes which meet the access conditions.
In the embodiment corresponding to fig. 3, after the blockchain application service platform acquires the set service data, the obtained set service data is subjected to multi-level encryption to obtain a target hash value, the obtained target hash value is respectively subjected to uplink storage according to the category to which the set service data corresponding to the target hash value belongs, the security of the service data is better improved by storing the target hash value obtained by the multi-level encryption, the security protection capability of the data against tampering is enhanced, the obtained target hash value is subjected to uplink storage according to the category to which the set service data corresponding to the target hash value belongs, and then a standard blockchain original data sub-center is formed, so that the orderliness of data storage is improved on the premise of ensuring the security of the data, and the integration of the data is better completed.
Referring to fig. 5, fig. 5 is a schematic flowchart illustrating another embodiment of a method for storing service data according to the present application. The embodiment corresponding to fig. 5 mainly further expands and explains the step S320.
In the present embodiment, before performing multi-stage encryption on the set service data to obtain the target hash value in step S320, the method provided by the present application further includes step S501.
S501: and cleaning and converting the set service data to obtain metadata meeting the set requirement.
When data of a service data center is acquired from a plurality of different service data acquisition systems or service data acquisition terminals, formats of corresponding data stored in the service data center may be different, or data abnormality may be caused due to various reasons in a data transmission process, or process data of service data storage data is lost, or data acquired by the service data acquisition systems or the service data acquisition terminals is incomplete, and based on the reasons, after a block chain application service platform acquires set service data, before performing multi-level encryption on the set service data, the method provided by the application may further include: and cleaning and converting the set service data to obtain metadata meeting the set requirement.
Wherein the cleaning conversion at least comprises: extracting and cleaning multi-source heterogeneous data, finding error values, missing values, abnormal values, suspicious data and the like, and correcting and completing correctable error values, missing values, abnormal values, correctable data and the like to obtain high-quality data, thereby ensuring the quality of metadata.
In one embodiment, meeting the set requirements includes at least: and converting the set service data into a preset format. Specifically, the specific type of the preset format may be adjusted and set according to actual requirements.
Further, step S301 may further include: and performing data cleaning conversion by using an Extract-Transform-Load (ETL) tool. In an embodiment, the blockchain application service platform is further configured to load and upload the metadata obtained through the cleansing conversion to a local database of a data administrator of the blockchain application service platform. The ETL tool can be used for sequentially extracting, cleaning and converting the set service data and then loading the set service data to the data manager local server so as to integrate the scattered, disordered and standard non-uniform data acquired from the service data center together and provide a data basis for data storage, data analysis and subsequent data calling.
Further, in another embodiment, after performing cleansing 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, unpublished data and supervisory data. The public data, the non-public 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 published and at least comprise power consumption data such as power generation amount and power consumption of a user, non-publicable data such as user identity, bank account information, a power charge settlement list and power transaction data, and the supervision data at least comprises data required by an energy industry supervision organization.
In another embodiment, after the service data center accesses data in each system, the accessed data is classified according to three types of data, namely, public data, non-public data and supervisory data, and is marked according to a classification result, then the method provided by the present application, after step S501, includes: and further determining the category of each metadata to judge whether the classification of the service data center is accurate or not, thereby avoiding the problem that 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 category labels of the set service data corresponding to each metadata with the corresponding data content to judge whether the current classification of the set service data is accurate or not, and if not, re-classifying.
In the present embodiment, the step S320 of performing multi-stage encryption on the setting service data to obtain the target hash value includes steps S502 to S504.
S502: and carrying out one-time hash calculation on the metadata to obtain a first hash value.
And carrying out one-time Hash calculation on the metadata obtained after cleaning and conversion to obtain a first Hash value. Further, in an embodiment, in step S502, the obtained set data content is subjected to Hash calculation (Hash operation) by using SDK (Software Development Kit) to obtain a first Hash value.
Further, in an embodiment, the SHA-512 algorithm is used for performing hash calculation to ensure data security by using the encryption technology, the SHA-512 algorithm is an algorithm with higher security performance in SHA-2, and mainly comprises parts such as plaintext filling, message spreading function transformation, random number transformation and the like, and an initial value and an intermediate calculation result comprise 8 shift registers with 64 bits. The SHA-512 algorithm allows the maximum length of input to be 2^168 bits, and generates a 512-bit hash value (in other embodiments, the hash calculation process is also called digest calculation, and the hash value obtained by the hash calculation is called message digest), and the input message is divided into 1024-bit blocks for processing, which is currently recognized as a 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 first hash operation in step S502, the first hash value and the timestamp information corresponding to the first hash value are further subjected to a second hash operation, so as to obtain a second hash value. The timestamp information may be time information of the first hash value calculated.
In the current 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 as that in step S502, or may be a different algorithm, and is not limited herein.
S504: the second hash value is digitally signed to obtain a target hash value.
After obtaining the second hash value through the hash calculation in step S503, the blockchain application service platform performs digital signature on the obtained second hash value to obtain the target hash value. And the target hash value is a second hash value subjected to digital signature.
In the present embodiment, when the type of the set service data is public data, the step S330 of performing uplink storage on the target hash value according to the type of the set service data may include steps S505 to S506.
S505: and carrying out consensus verification on the target hash value.
When the class to which the service data belongs is set to be public data, the obtained target hash value is subjected to consensus verification. Further, in an embodiment, the target hash value may be consensus verified by a blockchain node running on the blockchain application service platform and the blockchain network where the blockchain node is located. In another embodiment, the target hash value may be verified by a set blockchain network or a plurality of blockchain nodes set in the set blockchain network.
S506: and storing the common identification verified target hash value into an enterprise private chain account book.
In some embodiments, the enterprise private chain defines that only block link points inside an enterprise can read and access data stored in the enterprise private chain, and each block link point in the enterprise private chain at least comprises an account held by each department or each user in the enterprise. The enterprise private chain account book refers to an account book corresponding to each block link point in the enterprise private chain. For example, an enterprise private chain may be deployed inside a power grid enterprise itself to store data essential for enterprise management with a high security level requirement, such as power transaction data.
And (4) performing uplink storage on the target hash value subjected to the consensus verification in the step S505 by using a chain code API interface, wherein the target hash value is stored in an enterprise private chain account book because the set service data corresponding to the current target hash value is public data. The data stored in the private chain account book of the enterprise can be accessed and obtained by all nodes on the private chain, or can be accessed and obtained by the block chain link point with access right in the alliance chain where the current private chain of the enterprise is located, or the block chain link points in all the alliance chains.
The alliance chain refers to a blockchain in which the consensus process is controlled by the preselected node, and in the current embodiment, the alliance chain may refer to a blockchain which is composed of various power domain enterprises and in which the consensus process is controlled by the preselected node. In particular, the federation chain may be in a "partially decentralized" form. Such as: in order to improve cross-business collaboration among different power grid enterprises, organizations jointly construct a alliance chain, and multiple agents in the alliance can jointly conduct data transaction and alliance chain maintenance, such as the above-mentioned various organizations illustrated in fig. 1, wherein energy industry regulatory agencies can join the alliance chain to quickly acquire the electric power market transaction situation.
Further, in another embodiment, when the category of the service data is set as the public data, step S330 may also include: and calculating all target hash values of the set service data which belong to the public data and are generated in a set time period according to the Mercker tree principle to generate root hash values, and carrying out consensus verification on the root hash values.
The set time period can be set and adjusted by an administrator according to actual needs. After the target hash value is obtained, further according to the merck tree principle, performing hash calculation on the target hash value of the set service data which belongs to the public data and is generated in the time period of the foodlines by adopting the SHA-512 algorithm, further obtaining a root hash value, and then performing consensus verification on the obtained root hash value in the block chain network where the root hash value is located.
Further, after the consensus verification is performed on the root hash value, the method provided by the application further includes: 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 chain ledger for the set business data can be further increased by storing the root hash value subjected to the consensus verification on the enterprise private chain ledger.
After the target hash value is stored in the enterprise private chain ledger book, or after the root hash value subjected to the consensus verification is stored in the enterprise private chain ledger book, the method provided by the application further includes: and storing the set service data belonging to the public data to a local storage and/or a cloud.
And further, storing the set service data belonging to the public data to a local storage and/or a cloud according to a set rule. For example, the set service data acquired by the current blockchain application service platform may include user account information of different regions, power consumption information of a user, and a risk assessment report of the user, and may be stored according to the region to which the user belongs, and in other embodiments, when the administrator sets that the storage needs to be performed according to the risk level to which the result of the user risk assessment report belongs, the storage may be performed according to the risk level category to which the result of the user risk assessment report belongs.
Referring to fig. 6, fig. 6 is a schematic flowchart illustrating a method for storing service data according to another embodiment of the present application. In the present embodiment, when the class of the service data is set as the confidential data,
the step S320 of performing uplink storage on the target hash value 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 type of the set service data is confidential data, 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 used for uplink storage. The attribute information of the set service data comprises at least one of the type of the set service data, the energy type corresponding to the set service data, the generation time of the set service data, the account address of the set service data and the data signature.
S602: and storing the target hash value after consensus verification and the attribute information of the set service data into a preset enterprise private chain account book.
And storing the target hash value after consensus verification and the attribute information of the set service data into a preset enterprise private chain account book for the access of nodes or users with the authority of accessing confidential data. In the current embodiment, the enterprise private chain ledger may refer to a blockchain for accounting on the enterprise private chain, and the preset enterprise private chain ledger is only accessed by a node or a user with an access right.
For example, in one embodiment, for confidential and non-public enterprise management data, a target hash value is obtained, the calculated target hash value is added with energy types, data generation time, account addresses and data signatures and then packaged into blocks, the blocks are verified through consensus and stored in an enterprise private chain account book built by the block, and then self-management of the data is supported and a point-to-point data sharing function inside the block is organized, so that reasonable sharing of information resources can be performed while data privacy is guaranteed to the maximum extent.
With continuing reference to fig. 6, further in the current embodiment, the method provided by the present application further includes:
s603: and storing the set service data belonging to the confidential data to a local storage and/or a cloud.
The set business data belonging to the confidential data is stored in a local storage of the block chain application service platform and/or is stored in a cloud terminal through a network, so that the set business data can be obtained in the local storage and/or the cloud terminal when a block chain node or a user accesses the set business data. It is understood that in other embodiments, the setting service of the confidential data may be stored to a location where other blockchain application service platforms may perform data interaction, 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 service data belonging to the confidential data.
Further, when the type of the set service data is the supervision data, the step S330 of performing uplink storage on the target hash value according to the type of the set service data includes:
and carrying out consensus verification on the target hash value.
And carrying out consensus verification on the target hash value of the supervision data so as to judge the legality of the data. After the consensus verification is performed on the target hash value, the method provided by the application may further include: and storing the target hash value subjected to consensus verification on a federation chain general ledger.
When the type of the set service data is the supervision data required by the energy agency, 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 consensus verification is stored in a federation chain general ledger, so that when the supervision agency needs to obtain the supervision data, the federation chain can be accessed. Wherein, the alliance chain: refers to a chain of blocks whose consensus process is controlled by a preselected node. The federation chain can be viewed as a "partially decentralized" modality.
Further, before storing the target hash value on the federation chain ledger, the method provided by the present application further includes: and sending a request to other block chain nodes or storage authority management nodes in the alliance chain to obtain other block chain nodes or storage authority management nodes to approve the passing request, and further storing the target hash value of the supervision data to the alliance chain.
Further, after storing the target hash value on the federation chain ledger, the method provided by the present application further includes:
and storing the set service data belonging to the supervision data to a storage space and/or cloud end associated with the supervision institution.
It should be noted that, in different embodiments, it is not limited that the target hash value of the supervision data is first stored in the federation chain general ledger, and then the set service data belonging to the supervision data is stored in the storage space and/or cloud associated with the supervision authority, for example, according to actual requirements, the target hash value of the supervision data is stored in the federation chain general ledger, and meanwhile, the set service data belonging to the supervision data is stored in the storage space and/or cloud associated with the supervision authority.
Referring to fig. 7, fig. 7 is a schematic flowchart illustrating an embodiment of a method for acquiring service data according to the present application.
S701: and the data demand node sends a data acquisition request to the data providing node to request to acquire the target service data.
The data providing node at least includes one or more of any one node in an enterprise private chain, any one node in a federation chain, a cloud, and a blockchain application service platform, and in some embodiments described below, the data requiring node is also referred to as a data requiring party, and the data providing node is referred to as a data providing party. In the current embodiment, the target service data refers to data required by the data demand node, and may be divided into confidential data, public data and supervisory data according to data types. It should be noted that the data demand node can share the data stored in the enterprise private chain or the alliance chain point to point only after identity verification, signature verification and authorization, so as to implement cross-business management of the data.
S702: and receiving a target data packet sent by the data providing node.
After receiving a data acquisition request sent by a data demand node, a 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 also directly send the target data packet to the data requiring node, or indirectly send the target data packet to the data requiring node through, for example, a block chain application service platform.
The target data packet at least comprises target service data and a target hash value for performing preset hash calculation on the target service data, and the target data packet is encrypted by using a private key of the data providing node.
S703: and 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.
Further, in another embodiment, before step S703, the method provided by the present application further includes: and verifying the digital signature to judge the legality of the target service data.
It should be noted that, in step S703, the process of performing the preset hash calculation on the yuu target service data is the same as the process of performing the hash calculation on the set service data by the blockchain application service platform side, that is, the same hash algorithm and hash calculation process are adopted. For example, when the block chain application service platform adopts the SHA-512 algorithm to perform the first hash calculation on the set service data to obtain the first hash value, then the SHA-512 algorithm is used to perform the second hash calculation on the first hash value and the timestamp information corresponding to the first hash value to obtain the target hash value, after the data demand node side receives the target service data in the target data packet, the SHA-512 algorithm is also used to perform the first hash calculation on the target service data to obtain the third hash value, and then the SHA-512 algorithm is used to perform the second hash calculation on the third hash value and the timestamp information corresponding to the third hash value to obtain the verification hash value. And finally, after the verification hash value is obtained, comparing the verification hash value with the target hash value to judge the legality of the target business 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 consistent with the target hash value, it is determined that the target service data in the target data packet is legal, that is, the target service data is not modified in the transmission process, and abnormal situations such as data loss do not occur, so that it is determined that the target service data can be adopted by the evaluation model or the accounting model.
After the target service data is judged to be 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 can also feed back/display the front end of the operation result to a user, so that the power service processing is completed.
Further, please refer to fig. 8, where fig. 8 is a schematic flowchart illustrating an embodiment of a method for acquiring service data according to the present application. In the present embodiment, it is mainly stated that before the data requiring node sends the data obtaining request to the data providing node in step S701, the method provided by the present application further includes:
s801: and receiving a service operation request input by a user.
The business operation request at least comprises a business operation request carried out by utilizing 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 charge-balance reconciliation, and the business operation request performed by the evaluation model at least comprises risk evaluation control, wherein the risk evaluation control can be evaluation on power supply pressure or electric power safety. It should be noted that different service operation requests correspond to different service models, and the service models are set according to actual application scenarios or actual requirements, so that the service models are not limited herein.
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 electricity fee settlement, the target service data at least comprises at least one of account information of the 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 an embodiment of a method for acquiring service data according to the present application. In the current 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.
In the current embodiment, the data provider is composed of a blockchain application service platform, blockchain nodes and a cloud. It is to be understood that in other embodiments, the data provider and the data consumer are not limited to including only the above-described components.
In another embodiment, the client may also directly send a data acquisition request to the blockchain node and the cloud, the blockchain node responds to the request after receiving the data acquisition request and sends the target hash value of the corresponding data to the client, and the cloud responds to the request after receiving the data acquisition request and sends the original data of the corresponding data to the client.
2. And the block chain application service platform responds to the data acquisition request.
The blockchain application service platform responds to the data acquisition request and executes the contents described in the following 3.
3. And sending a request for acquiring the hash value corresponding to the data to the block link point.
4. And sending an original data request for acquiring data to the cloud.
It should be noted that, although fig. 9 illustrates that step 3 and step 4 are performed first, the order between step 3 and step 4 is not limited in the current embodiment.
5. And responding to the request for acquiring the hash value corresponding to the data by the block chain node, and sending 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 the data demander.
6. The cloud responds to the original data request for acquiring the data, and sends the original data to the block chain application service platform.
The original data is data required by a corresponding data demand side, or one of the data required by the data demand side.
7. And the block chain application service platform packs the original data and the target hash value into a target data packet.
And the block chain application service platform packs the acquired original data and the target hash value into a target data packet to be sent to the client, and then responds to the data acquisition request. It is understood that, in other embodiments, the blockchain application service platform may also directly send the acquired original data and the target hash value to the client, so as to respond to the data acquisition request.
8. And sending the target data packet to the client to respond to the data acquisition request.
9. And 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.
The preset hash calculation of the target service data by using the hash algorithm further comprises performing a first hash calculation of the target service data by using the hash algorithm to obtain a first hash value, and performing a second hash calculation of the first hash value and timestamp information corresponding to the first hash value to obtain a hash value to be verified. The two hash calculation hash algorithms may be the same or different, and the hash algorithm at least includes 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.
According to the business data acquisition method, whether the hash value to be verified is consistent with the target hash value or not is compared, whether the target data is legal or not can be judged accurately, the data source is verified, the identity of the data main body identification is checked, and the content can be considered not to be tampered by the party who verifies the consistency.
Referring to fig. 10, fig. 10 is a schematic structural diagram of an embodiment of an electronic device according to the present application. In the present embodiment, the electronic device 1000 provided herein includes a processor 1001 and a memory 1002 coupled thereto. The electronic device 1000 may be a block chain application service platform for performing the method described in any one of the embodiments of fig. 1 to 9 and corresponding embodiments thereof.
The memory 1002 includes a local storage (not shown) and stores a computer program, and the computer program implements the method described in any one of the embodiments of fig. 1 to 9 and the corresponding embodiments when executed.
The processor 1001 is coupled to the memory 1002, and the processor 1001 is configured to execute a computer program to perform the method described in any one of the embodiments of fig. 1 to 9 and the corresponding embodiments.
Referring to fig. 11, fig. 11 is a schematic structural diagram of an embodiment of a storage medium according to the present application. The storage medium 1100 stores a computer program 1101 capable of being executed by a processor, the computer program 1101 being configured to implement the method as described above with reference to fig. 1 to 9 and any one of the corresponding embodiments thereof. Specifically, the storage medium 1100 may be one of a memory, a personal computer, a server, a network device, or a usb disk.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for storing service data, comprising:
the method comprises the steps that a block chain application service platform obtains set service data;
performing multi-stage encryption on the set service data to obtain a target hash value;
and performing uplink storage on the target hash value according to the type of the set service data.
2. The method for service data storage according to claim 1,
before the multi-stage encrypting the set service data to obtain the target hash value, the method further includes:
cleaning and converting the set service data to obtain metadata meeting the set requirements;
the performing multi-stage encryption on the set service data to obtain a target hash value includes:
performing hash calculation on the metadata once 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.
3. The method for storing service data according to claim 1, wherein when the category of the service data is configured to be public data,
the step of performing uplink storage on the target hash value 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 an enterprise private chain account book;
or,
calculating all target hash values of set service data which belong to public data and are generated in a set time period according to the Mercker tree principle to generate root hash values, and carrying out consensus verification on the root hash values; and
and storing the root hash value subjected to the consensus verification to the enterprise private chain account book.
The method further comprises the following steps:
and storing the set service data belonging to the public data to a local storage and/or a cloud.
4. The method for storing service data according to claim 1, wherein when the category of the set service data is confidential data,
the step of performing uplink storage on the target hash value 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; the attribute information of the set service data comprises at least one of the category of the set service data, the energy type corresponding to the set service data, the generation time of the set service data, the account address of the set service data and a data signature;
storing the target hash value and the attribute information of the set service data after the consensus verification to a preset enterprise private chain account book;
the method further comprises the following steps:
and storing the set service data belonging to the confidential data to a local storage and/or a cloud.
5. The method for storing service data according to claim 1, wherein when the category of the set service data is supervision data,
the step of performing uplink storage on the target hash value 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 consensus verification to a federation chain total account book;
the method further comprises the following steps:
and storing the set service data belonging to the supervision data to a storage space and/or a cloud end associated with a supervision organization.
6. The method for storing business data according to claim 1, wherein the acquiring the set business data by the blockchain application service platform comprises:
the method comprises the steps that a block chain application service platform obtains set service data from a service data center; the service data center collects service data collected by at least one service data collection end;
the service data is power grid service data.
7. A method for service data acquisition, the method comprising:
the data demand node sends a data acquisition request to the data providing node to request to acquire 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 performing preset hash calculation on the target service data, and the target data packet 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 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 for service data acquisition according to claim 7, wherein before the data requiring 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 reconciliation;
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 the memory-stored computer program to perform the method of any one of claims 1 to 8.
10. A storage medium, characterized in that the storage medium stores a computer program executable by a processor to perform the method according to any one of claims 1 to 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 true CN111259070A (en) | 2020-06-09 |
| CN111259070B 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) |
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111401916A (en) * | 2020-06-05 | 2020-07-10 | 支付宝(杭州)信息技术有限公司 | Transaction risk identification method and device |
| CN111563130A (en) * | 2020-07-15 | 2020-08-21 | 成都无右区块链科技有限公司 | Data credible data management method and system based on block chain technology |
| CN111698254A (en) * | 2020-06-15 | 2020-09-22 | 中国银行股份有限公司 | Alliance chain Baas platform building method based on sharing organization |
| CN111917861A (en) * | 2020-07-28 | 2020-11-10 | 广东工业大学 | Knowledge storage method and system based on block chain and knowledge graph and application thereof |
| CN111930851A (en) * | 2020-09-25 | 2020-11-13 | 腾讯科技（深圳）有限公司 | Control data processing method, device, medium and electronic equipment of block chain network |
| CN111984614A (en) * | 2020-08-04 | 2020-11-24 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN111984613A (en) * | 2020-08-04 | 2020-11-24 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN112039972A (en) * | 2020-08-26 | 2020-12-04 | 支付宝(杭州)信息技术有限公司 | Service processing method, device and equipment |
| CN112560097A (en) * | 2020-12-22 | 2021-03-26 | 广州技象科技有限公司 | Storage management method and device for power business data |
| CN112560098A (en) * | 2020-12-22 | 2021-03-26 | 广州技象科技有限公司 | Business data management method and device of power Internet of things |
| CN112733211A (en) * | 2021-01-15 | 2021-04-30 | 重庆邮电大学 | Intelligent power grid data storage scheme based on block chain |
| CN112822224A (en) * | 2021-04-19 | 2021-05-18 | 国网浙江省电力有限公司 | Safe transmission method for financial data query |
| CN112883428A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Tamper-proof method for IT asset management system |
| CN112883414A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | IT asset management and renovation platform |
| CN112883431A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Method for operating IT asset data on data management platform |
| CN112967149A (en) * | 2021-02-03 | 2021-06-15 | 广东电力信息科技有限公司 | Method and system for sharing multi-party electric quantity statistical information based on block chain technology |
| CN113254969A (en) * | 2021-06-08 | 2021-08-13 | 挂号网（杭州）科技有限公司 | Service data processing method and device, electronic equipment and storage medium |
| CN113407958A (en) * | 2021-06-03 | 2021-09-17 | 广东辰宜信息科技有限公司 | Signature data processing method, device, equipment and medium |
| CN113419894A (en) * | 2021-07-20 | 2021-09-21 | 网易（杭州）网络有限公司 | Data inspection method, data inspection device, storage medium and computer equipment |
| CN113434909A (en) * | 2021-06-25 | 2021-09-24 | 湖北央中巨石信息技术有限公司 | Data on-demand evidence storing method based on block chain |
| CN113468551A (en) * | 2021-05-31 | 2021-10-01 | 南京邮电大学 | Domestic intelligent electric meter data storage system and method based on alliance block chain |
| CN113630425A (en) * | 2021-10-08 | 2021-11-09 | 国网浙江省电力有限公司金华供电公司 | Financial data safe transmission method for multiple power bodies |
| WO2022021696A1 (en) * | 2020-07-30 | 2022-02-03 | 中诚区块链研究院(南京)有限公司 | Multi-information source-based whole-process blockchain system |
| CN114154189A (en) * | 2021-01-29 | 2022-03-08 | 北京天德科技有限公司 | Two-section type Hash chain link certificate storing method for data or file |
| CN114169009A (en) * | 2021-12-07 | 2022-03-11 | 中国联合网络通信集团有限公司 | Precise information processing method, device, equipment and storage medium |
| WO2022051924A1 (en) * | 2020-09-09 | 2022-03-17 | 中诚区块链研究院(南京)有限公司 | Transaction blockchain capable of providing multiple encryption modes |
| CN114936249A (en) * | 2022-06-23 | 2022-08-23 | 成都质数斯达克科技有限公司 | File analysis and conversion method, device, equipment and readable storage medium |
Citations (7)
| 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 |
| US20190332921A1 (en) * | 2018-04-13 | 2019-10-31 | Vosai, Inc. | Decentralized storage structures and methods for artificial intelligence systems |
| CN110493007A (en) * | 2019-09-06 | 2019-11-22 | 腾讯科技（深圳）有限公司 | A kind of Information Authentication method, apparatus, equipment and storage medium based on block chain |
-
2019
- 2019-11-28 CN CN201911194837.3A patent/CN111259070B/en active Active
Patent Citations (7)
| 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 |
| US20190332921A1 (en) * | 2018-04-13 | 2019-10-31 | Vosai, Inc. | Decentralized storage structures and methods for artificial intelligence systems |
| 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 |
Cited By (40)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111401916A (en) * | 2020-06-05 | 2020-07-10 | 支付宝(杭州)信息技术有限公司 | Transaction risk identification method and device |
| CN111401916B (en) * | 2020-06-05 | 2020-10-02 | 支付宝(杭州)信息技术有限公司 | Transaction risk identification method and device |
| CN111698254A (en) * | 2020-06-15 | 2020-09-22 | 中国银行股份有限公司 | Alliance chain Baas platform building method based on sharing organization |
| 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 |
| WO2022021696A1 (en) * | 2020-07-30 | 2022-02-03 | 中诚区块链研究院(南京)有限公司 | Multi-information source-based whole-process blockchain system |
| CN111984614A (en) * | 2020-08-04 | 2020-11-24 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN111984613A (en) * | 2020-08-04 | 2020-11-24 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN111984614B (en) * | 2020-08-04 | 2023-05-26 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN111984613B (en) * | 2020-08-04 | 2023-06-16 | 中国人民银行数字货币研究所 | Method, device and system for sharing files |
| CN112039972B (en) * | 2020-08-26 | 2023-10-27 | 蚂蚁胜信(上海)信息技术有限公司 | Service processing method, device and equipment |
| CN112039972A (en) * | 2020-08-26 | 2020-12-04 | 支付宝(杭州)信息技术有限公司 | Service processing method, device and equipment |
| WO2022051924A1 (en) * | 2020-09-09 | 2022-03-17 | 中诚区块链研究院(南京)有限公司 | Transaction blockchain capable of providing multiple encryption modes |
| CN111930851A (en) * | 2020-09-25 | 2020-11-13 | 腾讯科技（深圳）有限公司 | Control data processing method, device, medium and electronic equipment of block chain network |
| CN112560098A (en) * | 2020-12-22 | 2021-03-26 | 广州技象科技有限公司 | Business data management method and device of power Internet of things |
| CN112560098B (en) * | 2020-12-22 | 2024-05-14 | 广州技象科技有限公司 | Service data management method and device of electric power Internet of things |
| CN112560097A (en) * | 2020-12-22 | 2021-03-26 | 广州技象科技有限公司 | 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 |
| CN112883428A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Tamper-proof method for IT asset management system |
| CN112883414A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | IT asset management and renovation platform |
| CN112883431A (en) * | 2021-01-21 | 2021-06-01 | 贵州电网有限责任公司 | Method for operating IT asset data on data management platform |
| CN114154189A (en) * | 2021-01-29 | 2022-03-08 | 北京天德科技有限公司 | Two-section type Hash chain link certificate storing method for data or file |
| CN112967149A (en) * | 2021-02-03 | 2021-06-15 | 广东电力信息科技有限公司 | Method and system for sharing multi-party electric quantity statistical information based on block chain technology |
| 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 |
| CN112822224A (en) * | 2021-04-19 | 2021-05-18 | 国网浙江省电力有限公司 | 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 |
| CN113407958A (en) * | 2021-06-03 | 2021-09-17 | 广东辰宜信息科技有限公司 | 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 |
| CN113254969A (en) * | 2021-06-08 | 2021-08-13 | 挂号网（杭州）科技有限公司 | Service data processing method and device, electronic equipment and storage medium |
| CN113434909A (en) * | 2021-06-25 | 2021-09-24 | 湖北央中巨石信息技术有限公司 | Data on-demand evidence storing method based on block chain |
| 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 |
| CN113419894A (en) * | 2021-07-20 | 2021-09-21 | 网易（杭州）网络有限公司 | 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 |
| CN113630425A (en) * | 2021-10-08 | 2021-11-09 | 国网浙江省电力有限公司金华供电公司 | Financial data safe transmission method for multiple power bodies |
| CN114169009A (en) * | 2021-12-07 | 2022-03-11 | 中国联合网络通信集团有限公司 | Precise information processing method, device, equipment and storage medium |
| CN114936249A (en) * | 2022-06-23 | 2022-08-23 | 成都质数斯达克科技有限公司 | File analysis and conversion method, device, equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111259070B (en) | 2024-04-19 |
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 | |
| Bodkhe et al. | Blockchain for industry 4.0: A comprehensive review | |
| TWI666902B (en) | Robust ATM network system and information processing method based on blockchain technology | |
| Minoli et al. | Blockchain mechanisms for IoT security | |
| CN110120868B (en) | Smart power grid safety data aggregation method and system based on block chain technology | |
| CN114499895B (en) | Data trusted processing method and system fusing trusted computing and block chain | |
| Wang et al. | Distributed meter data aggregation framework based on Blockchain and homomorphic encryption | |
| Xiao et al. | Non-repudiation in neighborhood area networks for smart grid | |
| CN110032545A (en) | File memory method, system and electronic equipment based on block chain | |
| CN109472164A (en) | The verification method and its network and electronic equipment of contract dataset | |
| CN109086585A (en) | History data processing method, system and computer readable storage medium | |
| TW201947446A (en) | Blockchain-based information supervision method and device | |
| CN111526200A (en) | Data storage access method and system based on block chain and cloud platform | |
| CN109491965A (en) | The storage method and its network and electronic equipment of purchase sale of electricity contract | |
| CN109951490A (en) | Webpage integrity assurance, system and electronic equipment based on block chain | |
| CN112214544A (en) | Ubiquitous power Internet of things edge data safe storage method based on permission block chain | |
| Abouyoussef et al. | Blockchain-based networking strategy for privacy-preserving demand side management | |
| Huang et al. | A data storage and sharing scheme for cyber-physical-social systems | |
| CN111352999A (en) | National data circulation and data right confirming method and platform based on block chain | |
| CN112019338A (en) | Lightweight safety smart power grid communication method and system based on block chain | |
| Sheikh et al. | Blockchain-based decentralized, flexible, and transparent energy market | |
| EP3859652A1 (en) | Technique for trustless cryptographic verification of energy allocations | |
| Singh | Internet-of-Things with blockchain technology: state-of-the art and potential challenges |
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 |