Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any inventive step based on the embodiments of the present disclosure, shall fall within the scope of protection of the present application.
Fig. 1 is a schematic flowchart of an asset transaction-based reconciliation method provided in an embodiment of the present specification, and from a program perspective, an execution subject of the flow may be an application client installed on a terminal used by a user, for example, a client of a commodity rental application, a client of a payment application, a client of an instant messaging application, and the like. The terminal is, for example, a mobile phone, a tablet computer, a smart watch, or a vehicle machine. In addition, there may be a third party application client to assist the execution of the process, and the execution subjects all belong to the first asset node.
The process in fig. 1 may include the following steps:
s101: a first asset node receives asset transaction data broadcast to all asset nodes.
In practical application, business scenarios such as registration, transfer, revenue generation and clearing exist in the process of flowing the securitized assets among asset organizations, and the asset organizations usually involve the transfer-in and transfer-out of funds of the asset organizations when processing business, so that the asset organizations have the requirement of accounting and reconciliation.
In order to implement the requirement of accounting for the accounting of each asset mechanism, in the embodiment of the present specification, the requirement of accounting for each asset mechanism can be implemented based on a block chain technology.
In the embodiment of the present specification, in order to implement the requirement of accounting for each asset organization based on the blockchain technology, it is first required to broadcast asset transaction data generated by an asset transaction that has been completed at a certain asset node to all asset nodes, for example, assuming that the asset transaction data generated by the completed asset transaction includes "asset transaction type, asset transaction parties, transaction time, transaction amount", the asset transaction data is broadcast to all asset nodes, that is, asset node a, asset node B, asset node C, and the like.
It should be noted that the asset transaction data generated by the asset transaction that has been completed at a certain asset node is broadcast to all asset nodes, including the asset node that generates the asset transaction data.
Further, since only one asset node can record the asset transaction data broadcasted to all asset nodes in the blockchain technique, that is, only one asset node can account for the broadcasted asset transaction, in the embodiment of the present specification, after the asset transaction data is broadcasted to all asset nodes, it is necessary to determine which asset node to record the broadcasted asset transaction data, that is, it is necessary to determine which asset node to account for the broadcasted asset transaction data.
Further, in the illustrative embodiment, determining which asset node to record the broadcasted asset transaction data may determine the asset node that records the broadcasted asset transaction data through a blockchain consensus algorithm.
It should be noted that the blockchain consensus algorithm may be a work load proving consensus algorithm, a rights and interests proving algorithm, a delayed work load proving algorithm, or other consensus algorithms, and which algorithm is specifically used may be determined according to actual needs. In addition, in the embodiment of the present specification, in order to distinguish between the asset node to be booked and the asset node to be subsequently synchronized, the asset node to be booked is positioned as a first asset node, that is, the first asset node is determined by the blockchain consensus algorithm, the first asset node records the asset transaction data to be broadcast, and the asset node to be subsequently synchronized is defined as a second asset node.
S102: recording the asset transaction data.
In order to prevent the problem of transaction errors between two asset transaction parties, in this embodiment of the present specification, after the first asset node receives the asset transaction data broadcasted to all asset nodes, the first asset node needs to verify the received asset transaction data and determine whether the received asset transaction data is correct.
In addition, since each asset node stores the same block chain, and each block on the block chain represents the asset transaction situation between each past asset node, in this embodiment of the present specification, it may be determined whether the received asset transaction data is correct according to the historical asset transaction data in the block chain.
In summary, in the embodiments of the present specification, the specific step of determining whether the received asset transaction data is correct may be to acquire historical asset transaction data stored in a block chain, verify the correctness of the asset transaction data according to the recorded asset transaction data and the historical asset transaction data, and record the asset transaction data when the correctness of the asset transaction data is verified.
It should be noted that when it is verified that the asset transaction data is incorrect, the asset transaction data generated by the asset transaction is not recorded.
S103: and sending data synchronization requests to at least two second asset nodes.
In order to prevent errors in accounting of the first asset node, after the first asset node records asset transaction data, the other asset nodes need to check and confirm whether the asset transaction data recorded by the first asset node is correct, and each asset node needs to store one same block chain.
It should be noted that the data synchronization request includes recorded asset transaction data, such as asset transaction type, both asset transaction parties, transaction time, and transaction amount.
S104: and receiving a consensus result returned by the second asset node according to the data synchronization request.
Since other asset nodes need to check and confirm whether the asset transaction data recorded by the first asset node is correct, in this embodiment of the present specification, after each second asset node receives the data synchronization request sent by the first asset node, it needs to determine whether the asset transaction data recorded by the first asset node is correct according to the asset transaction data carried by the data synchronization request, specifically, obtain historical asset transaction data stored in the block chain, verify the correctness of the asset transaction data carried by the data synchronization request according to the asset transaction data carried by the data synchronization request and the historical asset transaction data, when the asset transaction data carried by the data synchronization request is verified to be correct, return the consensus result to the first asset node as consensus, and send the consensus result to the first asset node, and when the asset transaction data carried by the verification data synchronization request is incorrect, the consensus result returned to the first asset node is that consensus is not achieved, and the consensus result is sent to the first asset node.
S105: and determining the legality of the record according to the consensus result.
S106: when the record is determined to be legitimate, the recorded asset transaction data is added to the blockchain.
In practical applications, there are at least two second asset nodes, that is, the first asset node receives at least two consensus results, which may be the same or different, so in this embodiment of the present specification, it is necessary to determine the validity of the recorded asset transaction data according to the received consensus results, specifically, count the number of achieved consensus and the number of unachieved consensus, determine whether the number of achieved consensus exceeds the number of unachieved consensus, if so, determine that the recording is legal, and if not, determine that the recording is illegal.
Further, when the record is determined to be legal, the recorded asset transaction data is added to the blockchain, and when the record is determined to be illegal, the recorded asset transaction data is not added to the blockchain, so that the legality of the asset transaction data needs to be determined again.
It should be noted that, since the accounting and reconciliation of asset transactions in the existing asset management field are independent and separate business processes, thus, each asset node can not quickly acquire the required asset transaction data, so that the account checking process of the whole asset transaction has certain hysteresis, therefore, by introducing the blockchain technology into the asset management field, the first asset node sends data synchronization requests to at least two second asset nodes to achieve consensus, therefore, the accounting is completed, the same asset transaction data copies are ensured to exist in different asset nodes during asset transaction, the original asynchronous and synchronous bill mode is simplified into the mode that complete transaction data are generated in the asset transaction process, the time consumption of the accounting link is greatly simplified and reduced, the timeliness of the accounting is effectively improved, and the hysteresis of the whole asset transaction is avoided.
In addition, the asset transaction data can be prevented from being mistaken or tampered by means of the common identification of all asset nodes and the legality of the asset transaction.
In practical applications, because asset transaction data is transmitted through a network channel, and a third-party network has data leakage, unreliability and other factors, which may cause problems that the asset transaction data may be tampered, in this embodiment of the present specification, a first asset node that receives asset transaction data broadcast to all asset nodes needs to verify correctness of the asset transaction data and also needs to verify whether the received asset transaction data is tampered, specifically, the first asset node receives encrypted asset transaction data, a public key and a first hash value broadcast to all asset nodes, subsequently decrypts the encrypted asset transaction data through the public key, performs hash operation on the decrypted asset transaction data to obtain a second hash value, and verifies whether the asset transaction data is tampered according to the first hash value and the second hash value, and then acquiring historical asset transaction data stored in the blockchain, verifying the correctness of the asset transaction data according to the recorded asset transaction data and the historical asset transaction data, recording the asset transaction data when the asset transaction data is correct and is not tampered, and not recording the asset transaction data when the asset transaction data is incorrect or is tampered.
It should be noted that the encrypted asset transaction data is obtained by encrypting, by using a private key, asset nodes that complete asset transactions and generate asset transaction data, and the first hash value is obtained by performing hash operation on the generated asset transaction data by the asset nodes that complete asset transactions and generate asset transaction data, and then, the asset nodes broadcast all the encrypted asset transaction data, the public key, and the first hash value to all the asset nodes.
It should be further noted that, verifying whether the asset transaction data is tampered according to the first hash value and the second hash value specifically includes: when the first hash value is the same as the second hash value, the asset transaction data is not tampered, and when the first hash value is different from the second hash value, the asset transaction data is illegally tampered.
In addition, in step S104, the first asset node sends the recorded asset transaction data to other second asset nodes, which also relates to the problem of data transmission through a network channel, that is, the asset transaction data is transmitted through a network channel, and a third-party network has data leakage and unreliable factors, which cause the asset transaction data to be possibly tampered with, so in this embodiment of the present specification, the second asset node receiving the asset transaction data needs to verify the correctness of the asset transaction data and also needs to verify whether the received asset transaction data is tampered, and specifically, the second asset node receives a data synchronization request sent by the first asset node, where the data synchronization request includes: the recorded encrypted asset transaction data, the public key and the third hash value are decrypted by the public key, the decrypted asset transaction data is subjected to hash operation to obtain a fourth hash value, whether the asset transaction data is tampered or not is verified according to the third hash value and the fourth hash value, historical asset transaction data stored in a block chain is obtained, the correctness of the asset transaction data carried by the data synchronization request is verified according to the asset transaction data carried by the data synchronization request and the historical asset transaction data, when the asset transaction data carried by the data synchronization request is verified to be correct and not tampered, the consensus result returned to the first asset node is consensus, the consensus result is sent to the first asset node, and when the transaction asset transaction data carried by the data synchronization request is verified to be incorrect or tampered, the consensus result returned to the first asset node is that consensus is not achieved, and the consensus result is sent to the first asset node.
It should be noted that the encrypted asset transaction data is obtained by the first asset node encrypting the asset transaction data through the private key, the third hash value is obtained by the first asset node performing hash operation on the generated asset transaction data, and subsequently, the first asset node broadcasts all the encrypted asset transaction data, the public key, and the third hash value to all the asset nodes.
It should be further noted that, verifying whether the asset transaction data is tampered according to the third hash value and the fourth hash value specifically includes: and when the third hash value is the same as the fourth hash value, the asset transaction data is not tampered, and when the third hash value is different from the fourth hash value, the asset transaction data is illegally tampered.
Although the asset transaction data on the blockchain are all public, the asset transaction data in the transmission process are encrypted, so that the transaction is only checked by authorized users, and the unauthorized users cannot check and process the data, therefore, the property transaction data are prevented from being tampered by the unauthorized users in a high probability, and the safety of the asset transaction data is ensured.
In addition, the asset transaction accounting and reconciliation based on the block chain are jointly completed by asset nodes distributed in different places, and each asset node stores complete asset transaction data, so that the consistency of the asset transaction data among the asset nodes is ensured, namely, all the asset nodes store the same account book, and meanwhile, because the asset transaction data are stored on a plurality of asset nodes, if the asset transaction data are tampered in a few asset nodes or the asset transaction data are damaged, the integrity of the whole asset transaction data cannot be influenced, namely, the data error of the whole accounting system and the tampering prevention caused by the unauthorized operation of any one asset node are avoided.
As long as more than half of the asset nodes are not invalid or tampered, the stability and reliability of the data of the whole financial system can be guaranteed, and all the asset nodes share one set of accounting data copy, so that the problem of inconsistent accounting data is fundamentally solved.
The method for reconciliation based on asset transaction provided by the embodiment of the present specification is mainly used in the field of asset management, and the implementation process of reconciliation based on asset transaction is exemplarily described below with reference to fig. 2, specifically as follows:
s201: the asset node A completes the asset transaction;
it is noted that completing an asset transaction results in asset transaction data.
S202: the asset transaction data is broadcast to asset node B, asset node C, asset node D, and asset management platform nodes.
Assume that asset node B is determined to be an accounting node (i.e., the first asset node) by the blockchain consensus algorithm.
S203: the asset node B records asset transaction data.
S204: a data synchronization request is sent to asset node a.
It should be noted that the recorded asset transaction data is included in the data synchronization request.
S205: the asset node a agrees based on the asset transaction data in the data synchronization request.
S206: and returning to reach the consensus.
S207: a data synchronization request is sent to asset node C.
S208: and the asset node C achieves consensus according to the asset transaction data in the data synchronization request.
S209: and returning to reach the consensus.
S210: a data synchronization request is sent to asset node D.
S211: the asset node D does not agree based on the asset transaction data in the data synchronization request.
S212: returning to the failure to reach consensus.
S213: and sending a data synchronization request to the asset management platform node.
S214: and the asset management platform node achieves consensus according to the asset transaction data in the data synchronization request.
S215: and returning to reach the consensus.
S216: and determining the legality of the record according to the consensus result.
It should be noted that, the number of agreement achieved is counted as 3, the number of agreement not achieved is counted as 1, and if the number of agreement achieved 3 is judged to exceed the number of agreement not achieved 1, it is determined that the record is legal.
S217: the asset node B adds the recorded asset transaction data to the blockchain.
Based on the same idea, the embodiment of the present specification further provides a device corresponding to the above method, as shown in fig. 3.
Fig. 3 is a schematic structural diagram of an asset transaction-based reconciliation apparatus corresponding to fig. 1 provided in an embodiment of the present specification, the apparatus including:
a first receiving module 301, configured to receive, by a first asset node, asset transaction data broadcasted to all asset nodes;
a recording module 302 for recording the asset transaction data;
a sending module 303, configured to send data synchronization requests to at least two second asset nodes, where the data synchronization requests include the recorded asset transaction data;
a second receiving module 304, configured to receive a consensus result returned by the second asset node according to the data synchronization request;
a determining module 305, configured to determine validity of the record according to the consensus result;
an adding module 306 for adding the recorded asset transaction data to the blockchain when the determining module 305 determines that the recording is legitimate.
The device further comprises:
a node determining module 307, configured to determine, by using a blockchain consensus algorithm, a first asset node before the first asset node of the first receiving module 301 receives the asset transaction data broadcasted to all asset nodes.
The recording module 302 is specifically configured to obtain historical asset transaction data stored in a block chain, verify correctness of the asset transaction data according to the recorded asset transaction data and the historical asset transaction data, and record the asset transaction data when the correctness of the asset transaction data is verified.
The consensus results include: consensus and non-consensus was achieved; the determining module 305 is specifically configured to count the number of achieved consensus and the number of unachieved consensus, determine whether the number of achieved consensus exceeds the number of unachieved consensus, determine that the record is legal if the number of achieved consensus exceeds the number of unachieved consensus, and determine that the record is illegal if the number of achieved consensus does not exceed the number of unachieved consensus.
The first receiving module 301 is specifically configured to receive, by a first asset node, encrypted asset transaction data, a public key, and a first hash value that are broadcast to all asset nodes, before acquiring historical asset transaction data stored in a blockchain, the recording module 302 is further configured to decrypt the encrypted asset transaction data by using the public key, perform hash operation on the decrypted asset transaction data to obtain a second hash value, verify whether the asset transaction data is tampered according to the first hash value and the second hash value, and record the asset transaction data when the asset transaction data is correct and is not tampered.
Based on the same idea, the embodiment of the present specification further provides an apparatus and a non-volatile computer storage medium corresponding to the above method.
An asset transaction-based reconciliation device provided by the embodiment of the specification and corresponding to fig. 1 comprises:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to:
a first asset node receives asset transaction data broadcast to all asset nodes;
recording the asset transaction data;
sending a data synchronization request to at least two second asset nodes, wherein the data synchronization request contains the recorded asset transaction data;
receiving a consensus result returned by the second asset node according to the data synchronization request;
determining the legality of the record according to the consensus result;
when the record is determined to be legitimate, the recorded asset transaction data is added to the blockchain.
A non-volatile computer storage medium corresponding to fig. 1 provided by the embodiments of the present description stores computer-executable instructions configured to:
a first asset node receives asset transaction data broadcast to all asset nodes;
recording the asset transaction data;
sending a data synchronization request to at least two second asset nodes, wherein the data synchronization request contains the recorded asset transaction data;
receiving a consensus result returned by the second asset node according to the data synchronization request;
determining the legality of the record according to the consensus result;
when the record is determined to be legitimate, the recorded asset transaction data is added to the blockchain.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the apparatus, the device, and the nonvolatile computer storage medium, since they are substantially similar to the embodiments of the method, the description is simple, and for the relevant points, reference may be made to the partial description of the embodiments of the method.
The apparatus, the device, the nonvolatile computer storage medium, and the method provided in the embodiments of the present specification correspond to each other, and therefore, the apparatus, the device, and the nonvolatile computer storage medium also have advantageous technical effects similar to those of the corresponding method.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, the present specification embodiments may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, the embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.