CN115168822A

CN115168822A - System and method for managing live asset electronic file and electronic device

Info

Publication number: CN115168822A
Application number: CN202210677784.6A
Authority: CN
Inventors: 董林华; 张丽琴
Original assignee: Beijing Muguo Technology Co ltd
Current assignee: Beijing Muguo Technology Co ltd
Priority date: 2022-06-15
Filing date: 2022-06-15
Publication date: 2022-10-11

Abstract

The application provides a system and a method for managing an electronic file of a living asset and an electronic device. The system comprises: the acquisition terminal subsystem comprises a plurality of acquisition terminals for collecting living asset information; the identification subsystem is used for establishing a uniform identity for the living asset information based on the identity code; the middleware subsystem receives the living body asset information from the acquisition terminal subsystem and processes the living body asset information into uplink information and archive information; a block chain subsystem comprising a plurality of block chain nodes for storing the uplink information; the archive database subsystem is used for storing the archive information; an electronic archive subsystem that generates an electronic archive of the live asset using information from the blockchain subsystem and the archive database subsystem. The system according to example embodiments may ensure reliability and accuracy of the generated electronic archive.

Description

System and method for managing living assets electronic file and electronic device

Technical Field

The application relates to the technical field of animal husbandry information, in particular to a system and a method for managing an electronic file of a living asset and electronic equipment.

Background

At present, most herdsmen adopt extensive and stocking beef cattle breeding modes, and the herdsmen cannot master specific data of all the bred beef cattle, such as breed, age, weight records and the like. Although some professional beef cattle raising companies establish and manage beef cattle living asset archives in a paper standing book or an electronic standing book mode, the modes have the defects that the operation is not easy, the credibility is low, information is easy to tamper and the like.

Herdsmen or beef cattle raising companies often fail due to lack of beef cattle living asset archive data when applying subsidies and funds for development of their businesses to organizations such as governments, banks and insurance companies.

Accordingly, the present application provides a system and method for managing an electronic archive of live assets.

Disclosure of Invention

The application aims to provide a method and a system for managing an electronic file of a living asset and electronic equipment, which can ensure the reliability and accuracy of the generated electronic file.

This user characteristic and advantage of the present application will become apparent from the detailed description to follow, or may be learned in part by practice of the present application.

According to an aspect of the present application, there is provided a system for managing an electronic archive of live assets, the system comprising: the system comprises an acquisition terminal subsystem and a monitoring terminal subsystem, wherein the acquisition terminal subsystem comprises a plurality of acquisition terminals for collecting living body asset information, and the living body asset information comprises an identity code acquired by a corresponding acquisition terminal; the identification subsystem is used for establishing a unified identification for the living body asset information based on the identification code; the middleware subsystem receives the living asset information from the acquisition terminal subsystem and processes the living asset information into uplink information and archive information, wherein the uplink information and the archive information comprise the unified identity; a block chain subsystem comprising a plurality of block chain nodes for storing the uplink information; the archive database subsystem is used for storing the archive information; an electronic archive subsystem that generates an electronic archive of the live asset using information from the blockchain subsystem and the archive database subsystem.

According to another aspect of the present application, there is provided a method of managing an electronic archive of a live asset, the method comprising: initializing and generating a uniform identity of the living assets; receiving living body asset information, wherein the living body asset information comprises an identity code corresponding to the living body asset; obtaining the uniform identity mark by using the identity code; processing the living asset information into uplink information and archive information, wherein the uplink information and the archive information comprise the unified identity; storing the uplink information to a block chain; storing the archive information to an archive database; generating an electronic archive of the live asset using information from the blockchain and the archive database.

According to another aspect of the present application, there is provided an electronic device including: a processor; a memory having a computer program stored thereon; the aforementioned method is implemented when the processor executes the computer program.

According to the embodiment, the identity of the live assets is confirmed through the live asset unified identity, a malicious attacker cannot derive the unified identity by means of part of the identity, and cannot restore all the identity codes of the live assets from the unified identity, so that the information security is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

FIG. 1 illustrates a system for managing an electronic archive of live assets according to an exemplary embodiment of the application.

Fig. 2 shows a schematic architecture of a blockchain subsystem according to an example embodiment.

FIG. 3 illustrates a flowchart of a method of managing an electronic archive of live assets, according to an example embodiment.

FIG. 4 illustrates a flowchart of a method for generating an electronic archive of live assets using information from a blockchain and archive database, according to an example embodiment.

Fig. 5 shows a block diagram of an electronic device according to an example embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the embodiments of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. 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 but may alternatively include other steps or elements not expressly 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. One skilled in the art will appreciate that the embodiments described herein can be combined with other embodiments.

Before describing the embodiments of the present application, some terms referred to in the embodiments of the present application are explained.

JSON: javaScript Object Notation, a JS Object numbered Notation, is a lightweight data exchange format, is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.

(block chain) channel: a channel is a dedicated "subnet" of communications between two or more specific network nodes in a blockchain system for private transactions, and other nodes not in the channel are not authorized to view corresponding information. And all nodes in the same channel share the same account book data. Each transaction on the blockchain network is performed on one lane.

fabric: the fabric is a distributed ledger platform supporting cross-language written intelligent contracts, which is maintained by IBM corporation and developed under Linux foundation.

A level DB: the world state database used by default in the fabric stores intelligent contract data among key-value pairs.

CouchDB: and storing formatted intelligent contract data in the JSON format file. CouchDB is a standby world state database, when data needing to be stored in a network is in a JSON format, the CouchDB supports rich query, does not simply store key value pair data, and is a database supporting storing JSON format files.

Intelligent contract: an intelligent contract is essentially business logic that runs on a blockchain. Intelligent contracts can be simple and efficient in updating data, and can be as complex as executing conditional contracts. The intelligent agent is generally referred to in the fabric as a chain code (Chaincode).

The technical solution applied in this year will be described below by taking beef cattle as an example of livestock products. It should be understood that the technical solutions and protection scope of the present application are not limited thereto, but rather should be understood to make the technical solutions of the present application easier to understand and understand for those skilled in the art.

Referring to fig. 1, a system for managing an electronic archive of a live asset according to an exemplary embodiment includes an acquisition terminal subsystem 110, an identification subsystem 120, a middleware subsystem 130, a block chain subsystem 140, an archive database subsystem 150, and an electronic archive subsystem 160.

The acquisition terminal subsystem 110 includes a variety of acquisition terminals to collect the live asset information, including the respective identification codes acquired by the respective acquisition terminals. According to some embodiments, the multiple collection terminals include one or more of an ultrahigh frequency RFID reader, a low frequency RFID reader, a photoelectric identifier, a camera, and a position collector, and can collect feeding information, production information, processing information, and the like, during the whole process of production, processing, and logistics of living assets.

For example, data in a high-frequency RFID chip ear tag worn by a beef cattle, such as the identity of the beef cattle, can be read by an RFID handheld reader. Can read RFID chip through the fixed recognizer of RFID on a large scale, can realize functions such as ox only fixes a position through this equipment.

According to some embodiments, the breeding enterprises use RFID tags capable of identifying cattle, the cattle are tagged at birth, and the identity codes of the cattle can be stored in the chips. In addition, a temperature sensor may be integrated on the RFID tag. The temperature information and the identity code of the cow can be obtained simultaneously through the RFID reader, and the temperature information and the identity code can be uploaded to a background system through an upper controller connected with the RFID reader.

For another example, according to some embodiments, the cow may carry a physical number plate on his or her body. In some scenarios, for example, animal vaccine data and the like can be manually collected through an intelligent terminal, and the identity code on the physical number plate is uploaded at the same time.

That is, currently, because there are multiple systems for real-time management and information collection, and unified management is not formed, a cow may have different identity codes in different systems. When various acquisition terminals are used for collecting living asset information, the acquired identity codes may also be different, but all point to or represent the same object.

The identification subsystem 120 establishes a unified identification for the live asset information based on the identification code. According to some embodiments, the identification subsystem 120 may include a hashing module and an association module. The hash module is configured to generate a unified identity based on all identity codes of the input live assets and generate corresponding identity hash values based on a single identity code of the input live asset.

For example, the identification subsystem 120 generates a unified identification for the cow by using an identification code obtained and uploaded from an RFID tag worn by the cow by an RFID reader, an identification code read or identified from a physical number plate and collected by an intelligent terminal, cow face identification data, and the like as input parameters of a hash function. The unified id can be used as the unique id of the cow during the whole supply chain process of the cow product. Meanwhile, in order to enable the cattle information and the identity codes obtained through various ways to be unified under the unique identity code in the system, the hash module respectively generates corresponding identity code hash values through the hash module based on each single identity code, and therefore the association module establishes an association relation between the identity code hash values and the unified identity identifier. Therefore, no matter what identity code is included in the information transmitted by the acquisition terminal subsystem 110, the information can be associated and fused with the information under the unified identity.

According to the embodiment, the living assets are subjected to identity confirmation through the living asset unified identity, a malicious attacker cannot derive the unified identity by means of part of identity codes, and cannot restore all identity codes of the living assets from the unified identity, so that the information safety is improved. In addition, the technical scheme according to the example embodiment can be compatible with the existing independent application systems, and information from the application systems can be unified under the corresponding same target project.

The middleware subsystem 130 receives the live asset information from the acquisition terminal subsystem and processes the live asset information into uplink information and archive information, where the uplink information and the archive information include a unified identity. Some of the living asset information from the acquisition terminal subsystem includes information to be tracked, and some includes information to be supervised, and these information to be supervised or tracked have higher requirements on integrity and non-tamper property, and therefore are extracted as uplink information stored in the block chain. In addition, the living body asset information from the acquisition terminal subsystem can be processed and stored as archive information. In addition to these processes, the middleware subsystem 130 may log, authorize, validate, cache, etc. the entire process of information processing.

According to some embodiments, the middleware subsystem 130 includes logging middleware, authentication middleware, rights middleware, data formatting middleware, caching middleware, and business middleware.

For example, the logging middleware may record information such as the user ID, name, IP address, request interface, etc. that initiated the request into a log file for auditing or monitoring as needed.

The authentication middleware may perform authentication of the user's identity using a token form. When a user logs in the system for the first time, the back-end system issues a token for the user and sets the expiration time to be 1 hour. And then when the user accesses other interfaces, the token needs to be carried as the identity certificate of the user. And if the token is expired, a new token is issued again.

The authority control middleware can verify whether the user has corresponding roles, such as herdsman roles, supervision roles and the like. The herdsman role corresponds to the list of interfaces that the herdsman role can access, and the user of the herdsman role can only access the interfaces and cannot access the interfaces of other roles such as an administrator.

The data formatting middleware can process the data, such as screening, unifying formats and the like. According to some embodiments, the data formatting middleware may use a data processing tool, such as ETL, to process the collected data, such as sort summarization, and encapsulate the processed data in a prescribed format, such as JSON, for storage in a database such as CouchDB or LevelDB that is backed up by a blockchain.

The cache middleware may use, for example, redis, and after parsing the request data, a url path, a request parameter, and the like are obtained as a key value of the Redis. Firstly, whether corresponding data exist in the cache is inquired, and if the corresponding data exist, the data are directly returned. And if the update operation is needed, traversing all keys in the Redis, and clearing the cache corresponding to the read operation to avoid reading the dirty data.

The business middleware may include a live asset module, a pasture module, a primary livestock module, a traceability module, and the like.

The living asset module can process data related to living assets such as cows and the like in the living asset electronic file, such as variety, sex, age, fetal time, body temperature, vaccines, medication, position, origin and the like.

The pasture module can process data related to pastures in the living asset electronic file, such as pasture names, pasture positions, pasture owners, pasture types, pasture information, temperature information, rainfall information, cultivation types and the like.

The livestock master module can process data related to livestock owners in the live asset electronic files, such as livestock owner names, livestock owner unified social credit codes/identification card numbers, contact ways, mailboxes, breeding histories, credit records, supervision histories and the like.

The middleware subsystem 130 may further include an entry module, which opens the 8080 port and/or 443 port, receives http requests and https requests from the client, and delivers the requests to subsequent middleware for processing.

The blockchain subsystem 140 includes a plurality of blockchain nodes for storing uplink information. The establishment of the living body asset electronic file and related important operations can generate transactions, the transactions are collected by the consensus node to be packaged into blocks, the blocks are distributed to the storage node, and the new blocks are stored in the account book.

For example, traceability information of each key link in the production, transportation, processing, and logistics processes needs to be managed in a full cycle, and can be stored in the blockchain subsystem 140, so that a decentralized distributed storage ledger that is difficult to be tampered with in a blockchain network can be used to ensure that data on the chain is transparent and credible.

The blockchain subsystem 140 may include a plurality of blockchain nodes for storing traceability, regulatory, etc. information. According to an example embodiment, a fabric may be employed as the blockchain underlying platform, but the application is not limited thereto. The blockchain subsystem 140 may include a traceability intelligence contract, an optional consensus mechanism, membership management, blockchain distributed storage, etc., which are not described herein. According to an example embodiment, the blockchain nodes may include nodes owned by aquaculture enterprise organizations, transportation enterprise organizations, slaughter enterprise organizations, sales organizations, industry associations, and the like. According to some embodiments, the block link points may also include nodes owned by a regulatory body.

The archive database subsystem 150 is used for storing archive information and is responsible for persistent storage of electronic archive information of living assets. According to some embodiments, archive database subsystem 150 may include a relational database and/or a non-relational database.

The electronic archive subsystem 160 generates an electronic archive of the live assets using information from the blockchain subsystem 140 and the archive database subsystem 150.

According to some embodiments, the electronic archive subsystem 160 may be configured to obtain some or all of the uplinked information of the live asset under examination from the block chain subsystem 140, obtain some or all of the archive information of the live asset under examination from the archive database subsystem 150, and verify some or all of the archive information using some or all of the uplinked information. And after the verification is passed, generating an electronic file by using part or all of the file information.

In the prior art, if a number plate worn by a live beef cattle falls off, the property of the live beef cattle cannot be ensured, and the normal operation of insurance, loan and other businesses is influenced. According to the technical scheme of the application, the living assets in the system can be determined through various identification codes of the living assets. Through being compatible with each existing independent information acquisition system, the information from each application system can be integrated together through the unified identity, so that the collection, processing, query and storage of the living body asset archive information by multiple platforms and multiple systems are supported.

In the prior art, the live asset electronic file is only stored by one party, is easy to be tampered and has no credibility. According to the technical scheme of the embodiment of the application, the information of the file database subsystem can be verified and confirmed by utilizing the uplink information of the block chain subsystem, so that the credibility and reliability of the generated electronic file are ensured.

As shown in fig. 2, each participant in the production to the sale of the living assets can be designed as an organization, and the whole block chain subsystem comprises a cultivation enterprise organization, a transportation enterprise organization, a slaughtering enterprise organization and a sale organization.

In each organization, there is at least one node to interact with other parts of the blockchain subsystem. For example, a farm enterprise organization may have multiple farms that interact through a pathway with slaughter house nodes and carrier pickups.

In addition, the blockchain subsystem may also include other organizations such as a supervisory organization, a consumer organization, and so on.

The node interaction channel may include a public channel and a private channel. Because different slaughtering enterprise organizations or sales organizations have competition relations, the arrangement of the private channel prevents the transaction information from being leaked, and the public channel can be used for functions of supervision of information of all parties by a supervision mechanism and the like.

In terms of channel design, for example, the design can be performed according to the business process of the living asset supply chain, and the characteristics of the fabric multi-chain multi-channel are utilized, that is, each node can participate in multiple channels at the same time, and different accounts are maintained respectively.

According to some embodiments, channels may be created using a docker container command through a sh scripting language, and nodes are added to the corresponding channels.

The method shown in fig. 3 may be used for processing and storing the live asset information at the server side or the cloud side.

Referring to FIG. 3, at S301, a unified identity for a live asset is initially generated.

According to some embodiments, the unified identity may be generated by a hash function using all of the identity codes of the live assets that are input, the corresponding identity hash value may be generated by a hash function using a single identity code of the live asset that is input, and an association relationship may be established between the identity hash value and the unified identity.

At S303, live asset information is received, where the live asset information includes an identity code corresponding to the live asset.

According to some embodiments, since there are a plurality of systems for real-world management and information collection, and uniform management is not formed, a cow may have different identity codes in different systems. When multiple collection terminals are used for collecting living asset information, the collected identity codes may also be different, but all point to or represent the same living asset target.

At S305, a unified identity is obtained using the identity code.

According to some embodiments, a hash function is used for generating an identity code hash value from an identity code, and then a unified identity is obtained by using an association relationship established between the identity code hash value and the unified identity, so that the received living asset information and the information under the unified identity can be associated and fused.

In S307, the live asset information is processed into uplink information and archive information. The uplink information and the profile information include a unified identity.

According to some embodiments, the live asset information from the acquisition terminal subsystem includes some information to be monitored and some information to be monitored, and the information to be monitored or monitored has higher requirements for integrity and non-tamper property, and therefore is extracted as uplink information stored to the block chain. In addition, the living body asset information from the acquisition terminal subsystem can be processed and stored as archive information.

At S309, the uplink information is stored to the block chain. For example, traceability information of each key link in the production, transportation, processing, and logistics processes needs to be managed in a full cycle, and can be stored in the blockchain subsystem 140, so that a decentralized distributed storage ledger that is difficult to be tampered with in a blockchain network can be used to ensure that data on the chain is transparent and credible.

In S311, the archive information is stored in the archive database. The archive database is responsible for the persistent storage of the electronic archive information of the living assets. According to some embodiments, archive database subsystem 150 may include a relational database and/or a non-relational database.

At S313, an electronic archive of the live asset is generated using information from the blockchain and archive databases. When the electronic file is generated, the uplink information of the block chain subsystem can be used for verifying and confirming the information of the file database subsystem, so that the reliability and the accuracy of the generated electronic file are ensured.

As shown in fig. 4, in S401, part or all of the uplink information of the live asset to be checked is acquired from the blockchain subsystem.

According to some embodiments, part or all of the uplink information of the live assets to be checked, such as the breeding production stage tracing information, the slaughtering stage tracing information, the logistics stage tracing information and the like, can be acquired from the block chain subsystem according to the generation conditions of the electronic file.

At S403, part or all of the archive information of the living property to be examined is acquired from the archive database subsystem.

According to some embodiments, part or all of the archive information of the living assets to be examined, such as the production stage archive information of the living breeding, the slaughter stage archive information, the logistics stage archive information, and the like, can be acquired from the archive database subsystem according to the generation conditions of the electronic archive.

In S405, part or all of the file information is verified by using part or all of the uplink information.

Based on the non-tamper property of the block chain information, the file information can be verified and confirmed by using the block chain information. If the two are confirmed to be identical, the other part of the archive information can be considered to be intact, otherwise the information of the archive database is suspected to be damaged.

At S407, after the verification is passed, an electronic archive is generated using part or all of the archive information.

After the verification is passed, the inquired part or all of the file information can be generated into an electronic file according to a certain format requirement, and the electronic file is provided for file requesters, including industry associations, partners, regulatory agencies, consumers and the like.

Because the archive information is integrated together based on the uniform identity, the archive information has sensibility to data tampering, and is verified and confirmed by the block chain data, so that the finally generated electronic archive is ensured to have reliability and integrity.

As shown in fig. 5, the electronic device 30 includes a processor 12 and a memory 14. Electronic device 30 may also include bus 22, network interface 16, and I/O interface 18. The processor 12, memory 14, network interface 16, and I/O interface 18 may communicate with each other via a bus 22.

Processor 12 may include one or more general purpose CPUs (Central Processing units), microprocessors, application specific integrated circuits, or the like, for executing associated program instructions.

The memory 14 may include a machine-system-readable medium in the form of volatile memory, such as Random Access Memory (RAM), read Only Memory (ROM), and/or cache memory. Memory 14 is used to store one or more programs containing instructions and data. The processor 12 may read instructions stored in the memory 14 to perform the methods described above according to embodiments of the present application. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile storage devices.

Electronic device 12 may also communicate with one or more networks through network interface 16. The network interface 16 may be a wired network interface or a wireless network interface, or may be a virtual network interface.

The electronic device 12 may also communicate with one or more external devices (e.g., audio input device, audio output device, camera, keyboard, mouse, display, various sensors, etc.) via an input/output (I/O) interface 18.

The bus 22 may include an address bus, a data bus, a control bus, and the like. Bus 22 provides a path for exchanging information between the various components.

It should be noted that, in the implementation process, the electronic device 30 may further include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the above-mentioned method. The computer-readable storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, DVDs, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), network storage devices, cloud storage devices, or any type of media or device suitable for storing instructions and/or data.

Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any one of the methods as recited in the above method embodiments.

It is clear to a person skilled in the art that the solution of the present application can be implemented by means of software and/or hardware. "Unit" and "module" in this specification may refer to software and/or hardware, such as field programmable gate arrays, integrated circuits, etc., that perform a particular function either individually or in combination with other components.

It should be noted that for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some service interfaces, indirect coupling or communication connection of devices or units, and may be electrical or in other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application.

The embodiments of the present application have been described and illustrated in detail above. It should be clearly understood that this application describes how to make and use particular examples, but the application is not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.

Through the description of the example embodiments, those skilled in the art will readily appreciate that the technical solutions according to the embodiments of the present application have at least one or more of the following advantages.

According to the embodiment, the living assets are subjected to identity confirmation through the living asset unified identity, a malicious attacker cannot derive the unified identity by means of part of identity codes, and cannot restore all identity codes of the living assets from the unified identity, so that the information safety is improved.

The technical scheme according to the example embodiment can be compatible with the existing independent application systems, and information from the application systems can be unified under the corresponding same target project.

According to some embodiments, by being compatible with existing independent information acquisition systems, information from application systems can be integrated together through a unified identity, so that collection, processing, query and storage of living asset archive information by multiple platforms and multiple systems are supported.

According to an example embodiment, information of the archive database subsystem may be verified and validated using uplink information of the blockchain subsystem, thereby improving the reliability and accuracy of the generated electronic archive.

The foregoing may be better understood in light of the following clauses:

1. a system for managing an electronic archive of live assets, the system comprising:

the system comprises an acquisition terminal subsystem and a monitoring subsystem, wherein the acquisition terminal subsystem comprises a plurality of acquisition terminals for collecting living body asset information, and the living body asset information comprises an identity code acquired by a corresponding acquisition terminal;

the identification subsystem is used for establishing a uniform identity for the living asset information based on the identity code;

the middleware subsystem receives the living asset information from the acquisition terminal subsystem and processes the living asset information into uplink information and archive information, wherein the uplink information and the archive information comprise the unified identity;

a block chain subsystem comprising a plurality of block chain nodes for storing the uplink information;

the archive database subsystem is used for storing the archive information;

and the electronic archive subsystem is used for generating an electronic archive of the living body asset by using the information from the block chain subsystem and the archive database subsystem.

2. The system of clause 1, wherein the plurality of acquisition terminals comprise one or more of an ultra-high frequency RFID reader, a low frequency RFID reader, a photoelectric identifier, a camera, and a location acquirer.

3. The system of clause 1, wherein the identification subsystem comprises a hashing module configured to generate the unified identification based on all identity codes of the input live asset and to generate a corresponding identity code hash value based on a single identity code of the input live asset.

4. The system of clause 3, wherein the identification subsystem further comprises an association module for establishing an association between the identity code hash value and the unified identity.

5. The system of clause 4, wherein the middleware subsystem includes logging middleware, validation middleware, rights middleware, caching middleware, and business middleware.

6. The system of clause 1, wherein the electronic filing subsystem is configured to:

acquiring part or all uplink information of the live assets to be checked from the block chain subsystem;

acquiring part or all of archive information of the living assets to be checked from the archive database subsystem;

verifying the part or all of the file information by using the part or all of the uplink information;

and after the verification is passed, generating an electronic file by using the part or all of the file information.

7. A method of managing an electronic archive of live assets, the method comprising:

initializing and generating a uniform identity of the living assets;

receiving living body asset information, wherein the living body asset information comprises an identity code corresponding to the living body asset;

obtaining the uniform identity mark by using the identity code;

processing the living asset information into uplink information and archive information, wherein the uplink information and the archive information comprise the unified identity;

storing the uplink information to a block chain;

storing the archive information to an archive database;

generating an electronic archive of the live asset using information from the blockchain and the archive database.

8. The method of clause 7, wherein the initializing generates a unified identity for the live asset, comprising:

generating the uniform identity mark by using all input identity codes of the living assets through a hash function;

generating a corresponding identity code hash value by using the input single identity code of the living body asset through a hash function;

and establishing an association relation between the identity code hash value and the uniform identity identifier.

9. The method of clause 7, wherein generating the electronic archive of the live asset using information from the blockchain and the archive database comprises:

acquiring partial or all uplink information of the live assets to be checked from the block chain subsystem;

10. An electronic device, comprising:

a processor;

a memory having a computer program stored thereon;

the method of any of clauses 7-9 is implemented when the computer program is executed by the processor.

Exemplary embodiments of the present application are specifically illustrated and described above. It is to be understood that the application is not limited to the details of construction, arrangement or method of operation set forth herein; on the contrary, the application is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

the system comprises an acquisition terminal subsystem and a monitoring terminal subsystem, wherein the acquisition terminal subsystem comprises a plurality of acquisition terminals for collecting living body asset information, and the living body asset information comprises an identity code acquired by a corresponding acquisition terminal;

the archive database subsystem is used for storing the archive information;

2. The system of claim 1, wherein the plurality of collection terminals comprise one or more of an ultra high frequency RFID reader, a low frequency RFID reader, a photoelectric identifier, a camera, and a location collector.

3. The system of claim 1, wherein the identification subsystem comprises a hashing module configured to generate the unified identification based on all identity codes of the input live asset and to generate a corresponding identity code hash value based on a single identity code of the input live asset.

4. The system of claim 3, wherein the identification subsystem further comprises an association module to establish an association between the identity code hash value and the unified identity.

5. The system of claim 4, wherein the middleware subsystem includes logging middleware, authentication middleware, rights middleware, caching middleware, and business middleware.

6. The system of claim 1, wherein the electronic archive subsystem is configured to:

and after the verification is passed, generating an electronic file by using part or all of the file information.

initializing and generating a uniform identity of the living assets;

receiving living asset information, wherein the living asset information comprises an identity code corresponding to the living asset;

obtaining the uniform identity mark by using the identity code;

storing the uplink information to a block chain;

storing the archive information to an archive database;

8. The method of claim 7, wherein the initializing generates a unified identity for the live asset, comprising:

9. The method of claim 7, wherein generating an electronic archive of the live asset using information from the blockchain and the archive database comprises:

10. An electronic device, comprising:

a processor;

a memory having a computer program stored thereon;

the method according to any of claims 7-9, when executed by the processor.