Vehicle diagnosis data management method and device
Technical Field
The invention relates to the technical field of block chains, in particular to a method and a device for managing vehicle diagnosis data.
Background
The second-hand market for automobiles, one of the major means of modern transportation, is also becoming increasingly large. The process of a vehicle from the former vehicle owner to the second-hand vehicle trading market to the second-hand vehicle owner is opaque to the second-hand vehicle owner. That is, the new owner cannot accurately know the historical diagnostic data of the vehicle.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for managing vehicle diagnostic data, so as to solve the problem that historical diagnostic data of a vehicle cannot be accurately obtained at present.
A first aspect of an embodiment of the present invention provides a method for managing vehicle diagnostic data, including:
receiving vehicle diagnostic data submitted by an on-board device;
carrying out structuralization processing on the diagnosis data according to a preset rule and storing the diagnosis data;
extracting a characteristic value of vehicle diagnosis data and generating a data index according to the characteristic value;
registering the data index in a blockchain;
receiving a data use request of a user;
and sending the corresponding diagnosis data to the user according to the type of the user.
Optionally, the performing the structured processing and storing on the diagnosis data according to the preset rule includes:
classifying the diagnostic data according to a plurality of fields to generate diagnostic data comprising a plurality of fields;
the fields include at least two of vehicle identification, diagnostic information, fault information, and mileage records; the diagnostic information includes diagnostic device identification, diagnostic time, location information, and diagnostic technician identification information.
Optionally, sending the corresponding diagnostic data to the user according to the type of the user includes:
when the user is of the first type, feeding back fault information and mileage information of a vehicle type corresponding to a vehicle identifier input by the user to the user;
when the user is of the second type, feeding back fault information of the vehicle type corresponding to the vehicle identification input by the user to the user;
and when the user is of the third type, feeding back the diagnosis information, the fault information and the mileage record corresponding to the vehicle identification input by the user to the user.
Optionally, after receiving the data usage request of the user, the method further includes:
and judging whether the data use request is legal or not.
Optionally, after the registering the data index in the blockchain, the method further comprises:
generating an intelligent contract according to the use condition of the vehicle diagnosis data and registering the intelligent contract in a block chain;
the judging whether the data use request is legal comprises the following steps:
receiving keywords input by a user;
judging whether a data index matched with the keyword exists or not based on the keyword;
if the data index matched with the keyword exists, judging whether the transaction commitment in the data use request meets the intelligent contract or not;
and if so, determining that the data use request is legal.
A second aspect of an embodiment of the present invention provides a management apparatus of vehicle diagnostic data, including:
the first receiving module is used for receiving vehicle diagnosis data submitted by the vehicle-mounted equipment;
the data processing module is used for carrying out structuralized processing on the diagnosis data according to a preset rule and storing the diagnosis data;
the generating module is used for extracting a characteristic value of the vehicle diagnostic data and generating a data index according to the characteristic value;
the registration broadcasting module is used for registering the data index in a block chain and broadcasting the data index in the whole network;
the second receiving module is used for receiving a data use request of a user;
and the sending module is used for sending the corresponding diagnosis data to the user according to the type of the user.
Optionally, the data processing module includes:
a classification generation unit configured to classify the diagnostic data according to a plurality of fields and generate diagnostic data including the plurality of fields;
the fields include at least two of vehicle identification, diagnostic information, fault information, and mileage records; the diagnostic information includes diagnostic device identification, diagnostic time, location information, and diagnostic technician identification information.
Optionally, the sending module includes:
the first sending unit is used for feeding back fault information and mileage information of a vehicle type corresponding to a vehicle identifier input by a user to the user when the user is of a first type;
the first sending unit is used for feeding back fault information of a vehicle type corresponding to the vehicle identification input by the user to the user when the user is of the second type;
and the first sending unit is used for feeding back the diagnosis information, the fault information and the mileage record corresponding to the vehicle identification input by the user to the user when the user is of the third type.
Optionally, the management apparatus of vehicle diagnostic data further includes:
and the judging module is used for judging whether the data use request is legal or not.
Optionally, the management apparatus of vehicle diagnostic data further includes:
the generation registration unit generates an intelligent contract according to the use condition of the vehicle diagnosis data and registers the intelligent contract in a block chain;
the judging module comprises:
the receiving unit is used for receiving keywords input by a user;
a first judgment unit configured to judge whether there is a data index matching the keyword based on the keyword;
the second judgment unit is used for judging whether the transaction commitment in the data use request meets the intelligent contract or not if the data index matched with the keyword exists;
and the determining unit is used for determining that the data use request is legal if the data use request is met.
A third aspect of the embodiments of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps in the method of the first aspect when executing the computer program.
A fourth aspect of embodiments of the present invention provides a computer-readable storage medium, which stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method of the first aspect.
In an embodiment of the present invention, vehicle diagnostic data submitted by an on-board device is received; carrying out structuralization processing on the diagnosis data according to a preset rule and storing the diagnosis data; extracting a characteristic value of vehicle diagnosis data and generating a data index according to the characteristic value; registering the data index in a blockchain; receiving a data use request of a user; according to the embodiment of the invention, the reliability of the automobile diagnosis data is firstly ensured, and then the corresponding diagnosis data is sent according to the difference of the users, so that the users can accurately acquire the required automobile diagnosis data.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic flow chart illustrating an implementation of a method for managing vehicle diagnostic data according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a specific implementation of step S106 according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating an implementation of a method for managing vehicle diagnostic data according to a second embodiment of the present invention;
fig. 4 is a schematic diagram of a specific implementation flow of step S307 in the second embodiment of the present invention;
fig. 5 is a block diagram showing a configuration of a vehicle diagnostic data management apparatus according to a third embodiment of the present invention;
fig. 6 is a schematic diagram of a terminal device according to a fourth embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when … …" or "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
Example one
Fig. 1 is a schematic flow chart illustrating an implementation of a method for managing vehicle diagnostic data according to an embodiment of the present invention. As shown in fig. 1, the method for managing vehicle diagnostic data specifically includes steps S101 to S106 as follows.
Step S101: vehicle diagnostic data submitted by the on-board device is received.
Among them, the in-vehicle apparatus is preferably an in-vehicle diagnosis apparatus. The vehicle uploads vehicle diagnostic data through the on-board diagnostic device. The diagnostic data includes vehicle type information, may include fault information corresponding to the vehicle type information, and may include mileage information, and may also include other types of diagnostic information.
Step S102: and carrying out structured processing on the diagnosis data according to a preset rule and storing the diagnosis data.
Specifically, the structured processing and storing of the diagnostic data according to a preset rule includes:
classifying the diagnostic data according to a plurality of fields to generate diagnostic data comprising a plurality of fields;
the fields include at least two of vehicle identification, diagnostic information, fault information, and mileage records; the diagnostic information includes diagnostic device identification, diagnostic time, location information, and diagnostic technician identification information.
After the automobile leaves the factory, the unique Vehicle Identification, such as a Vehicle Identification Number (VIN) code, is recorded into the system, and the system is used in nodes of automobile manufacturers, vendors, automobile insurance, 4s stores, leasing companies and the like.
When the automobile is maintained or maintained, namely the automobile enters the node, the hardware diagnosis equipment is inserted to diagnose the automobile or receive the vehicle diagnosis data uploaded by the vehicle-mounted diagnosis equipment. The diagnostic data is classified according to a plurality of fields, generating diagnostic data comprising a plurality of fields. Wherein the field includes at least a vehicle identification and further includes diagnostic information, fault information, and/or mileage records corresponding to the vehicle identification. In order to avoid data falsification, the reliability of the diagnosis data is ensured, and the diagnosis information includes diagnosis equipment identification, diagnosis time, place information, and diagnosis technician identification information.
Step S103: characteristic values of the vehicle diagnostic data are extracted and a data index is generated according to the characteristic values.
And extracting the characteristic value of the vehicle diagnosis data, and generating a data index according to the characteristic value by adopting a one-way irreversible encryption algorithm such as a Hash encryption algorithm. And the data information corresponding to the data index can be quickly accessed through the data index.
Step S104: the data index is registered in a blockchain.
Wherein the blockchain may be a car chain of an enterprise. And registering the data index in a blockchain and broadcasting the data index in the whole network.
Step S105: a data usage request of a user is received.
The user may be a client (e.g. APP) initiating a usage request on the terminal device or the terminal device.
Step S106: and sending the corresponding diagnosis data to the user according to the type of the user.
Specifically, sending the corresponding diagnostic data to the user according to the type of the user includes:
step S201: and when the user is of the first type, feeding back fault information and mileage information of the vehicle type corresponding to the vehicle identification input by the user to the user.
Wherein the first type may be a vehicle owner. And when the user is the vehicle owner, feeding back the fault information and the mileage information of the vehicle type corresponding to the vehicle identification input by the vehicle owner to the vehicle owner.
Step S202: and when the user is of the second type, feeding back fault information of the vehicle type corresponding to the vehicle identification input by the user to the user.
Wherein the second type may be a technician. When the user is a technician, the trouble information of the vehicle type corresponding to the vehicle identification input by the technician is fed back to the technician.
Step S203: and when the user is of the third type, feeding back the diagnosis information, the fault information and the mileage record corresponding to the vehicle identification input by the user to the user.
Wherein the third type may be a full vehicle manufacturer. And when the user is the finished automobile manufacturer, feeding back the fault information of the automobile type corresponding to the automobile identification input by the finished automobile manufacturer to the finished automobile manufacturer.
In an embodiment of the present invention, vehicle diagnostic data submitted by an on-board device is received; carrying out structuralization processing on the diagnosis data according to a preset rule and storing the diagnosis data; extracting a characteristic value of vehicle diagnosis data and generating a data index according to the characteristic value; registering the data index in a blockchain; receiving a data use request of a user; according to the embodiment of the invention, the reliability of the automobile diagnosis data is firstly ensured, and then the corresponding diagnosis data is sent according to the difference of the users, so that the users can accurately acquire the required automobile diagnosis data.
Example two
Fig. 3 is a schematic flow chart illustrating an implementation of a management method for vehicle diagnostic data according to a second embodiment of the present invention. As shown in fig. 3, the method comprises the following steps:
step S301: vehicle diagnostic data submitted by the on-board device is received.
Step S302: and carrying out structured processing on the diagnosis data according to a preset rule and storing the diagnosis data.
Step S303: characteristic values of the vehicle diagnostic data are extracted and a data index is generated according to the characteristic values.
Step S304: the data index is registered in a blockchain.
The steps S301 to S304 are the same as the steps S101 to S104, and are not described herein again.
Step S305: and generating an intelligent contract according to the using condition of the vehicle diagnosis data and registering the intelligent contract in a block chain.
Wherein the intelligent contract is stored on the block chain, and the intelligent contract is equivalent to a digital contract which can execute the code on the CPU. The intelligent contract may be defined, and the intelligent contract may be generated according to a use condition of the vehicle diagnostic data, wherein the use condition of the vehicle diagnostic data may be set according to the right of ownership of the vehicle diagnostic data. Further, the intelligent contracts are registered in the blockchain and broadcast to the various nodes of the blockchain. Since each node of the block chain has no authority to modify the intelligent contract, the normalization of the intelligent contract is ensured.
Step S306: a data usage request of a user is received.
Step S306 is the same as step S105, and is not described herein again.
Step S307: and judging whether the data use request is legal or not.
Specifically, the step of determining whether the data use request is legal includes the following steps:
step S401: keywords input by a user are received.
The user can be a vehicle owner, a vehicle enterprise and other types of users. For example, when the user is an owner of a vehicle, the owner of the vehicle may enter keywords related to the performance of the vehicle. After the user inputs the keywords, the keywords input by the user are received.
Step S402: and judging whether a data index matched with the keyword exists or not based on the keyword.
For example, if the user aims to inquire the mileage of a car and inputs "mileage is within 10 KM", it is determined whether an index matching the keyword exists in the block chain based on "mileage is within 10 KM".
Step S403: and if the data index matched with the keyword exists, judging whether the transaction commitment in the data use request meets the intelligent contract.
The keywords and the index may be in a one-to-one relationship or a one-to-many relationship. It is not assumed that index a, index B, and index C are queried based on "mileage within 10KM," and obviously there is an index matching the keyword, and it is determined whether the transaction commitment in the data usage request satisfies the smart contract.
Illustratively, determining whether the transaction commitment in the data usage request satisfies the smart contract comprises:
determining whether the user has paid a predetermined fee; and if the user pays a preset fee, determining that the user meets the condition of the intelligent contract.
Step S404: and if the intelligent contract is met, determining that the data use request is legal.
For example, when the owner of the vehicle wants to inquire about the relevant diagnostic data, the owner pays a predetermined fee to obtain the right to view, i.e., to satisfy the intelligent contract. If the owner does not pay the predetermined fee, the intelligent contract is not satisfied, and the system returns the word 'not satisfied'. The predetermined fee may be set in advance in the smart contract. It will be appreciated that the user need not pay when viewing his own authorized diagnostic report.
Step S308: and sending the corresponding diagnosis data to the user according to the type of the user.
Step S308 is the same as step S106, and is not described herein again.
In this embodiment, whether an index matched with a keyword exists in a block chain is judged by receiving the keyword input by a user, whether a transaction commitment in the data use request meets an intelligent contract is further judged, if yes, corresponding diagnostic data is sent to the user according to the type of the user, and normalization of an acquisition condition of the diagnostic data is ensured, so that safety of the diagnostic data is ensured.
EXAMPLE III
Referring to fig. 5, a block diagram of a vehicle diagnostic data management device according to a third embodiment of the present invention is shown. The management device 50 for vehicle diagnostic data includes: a first receiving module 51, a data processing module 52, an extraction generating module 53, a registration broadcasting module 54, a second receiving module 55, and a transmitting module 56. The specific functions of each module are as follows:
a first receiving module 51 for receiving vehicle diagnostic data submitted by the vehicle-mounted device;
the data processing module 52 is configured to perform structured processing on the diagnostic data according to a preset rule and store the diagnostic data;
an extraction generation module 53, configured to extract a feature value of the vehicle diagnostic data and generate a data index according to the feature value;
a registration broadcasting module 54, configured to register the data index in a block chain and broadcast the data index over the whole network;
a second receiving module 55, configured to receive a data usage request of a user;
and a sending module 56, configured to send the corresponding diagnostic data to the user according to the type of the user.
Optionally, the data processing module 52 includes:
a classification generation unit configured to classify the diagnostic data according to a plurality of fields and generate diagnostic data including the plurality of fields;
the fields include at least two of vehicle identification, diagnostic information, fault information, and mileage records; the diagnostic information includes diagnostic device identification, diagnostic time, location information, and diagnostic technician identification information.
Optionally, the sending module 56 includes:
the first sending unit is used for feeding back fault information and mileage information of a vehicle type corresponding to a vehicle identifier input by a user to the user when the user is of a first type;
the first sending unit is used for feeding back fault information of a vehicle type corresponding to the vehicle identification input by the user to the user when the user is of the second type;
and the first sending unit is used for feeding back the diagnosis information, the fault information and the mileage record corresponding to the vehicle identification input by the user to the user when the user is of the third type.
Optionally, the management device 50 for vehicle diagnostic data further includes:
and the judging module is used for judging whether the data use request is legal or not.
Optionally, the management device 50 for vehicle diagnostic data further includes:
and the generation and registration module is used for generating an intelligent contract according to the use condition of the vehicle diagnosis data and registering the intelligent contract in the block chain.
Optionally, the determining module includes:
and the receiving unit is used for receiving the keywords input by the user.
And the first judging unit is used for judging whether a data index matched with the keyword exists or not based on the keyword.
And the second judging unit is used for judging whether the transaction commitment in the data use request meets the intelligent contract or not if the data index matched with the keyword exists.
And the determining unit is used for determining that the data use request is legal if the data use request is met.
In an embodiment of the present invention, vehicle diagnostic data submitted by an on-board device is received; carrying out structuralization processing on the diagnosis data according to a preset rule and storing the diagnosis data; extracting a characteristic value of vehicle diagnosis data and generating a data index according to the characteristic value; registering the data index in a blockchain; receiving a data use request of a user; according to the embodiment of the invention, the reliability of the automobile diagnosis data is firstly ensured, and then the corresponding diagnosis data is sent according to the difference of the users, so that the users can accurately acquire the required automobile diagnosis data.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
It will also be understood that, although the terms first, second, etc. may be used herein in some embodiments to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first receiving module may be named a second receiving module, and similarly, a second receiving module may be named a first receiving module, without departing from the scope of the various described embodiments. The first receiving module and the second receiving module are both receiving modules, but they are not the same receiving module.
Example four
Fig. 6 is a schematic diagram of a terminal device according to a fourth embodiment of the present invention. As shown in fig. 6, the terminal device 6 of this embodiment includes: a processor 60, a memory 61 and a computer program 62, such as a program for a method of managing vehicle diagnostic data, stored in said memory 61 and operable on said processor 60. The processor 60, when executing the computer program 62, implements the steps in the various vehicle diagnostic data management method embodiments described above, such as steps S101-S106 shown in fig. 1. Alternatively, the processor 60, when executing the computer program 62, implements the functions of the modules in the above-described device embodiments, such as the functions of the modules 51 to 56 shown in fig. 5.
Illustratively, the computer program 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60 to implement the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 62 in the terminal device 6. For example, the computer program 62 may be divided into a first receiving module, a data processing module, an extraction generation module, a registration broadcasting module, a second receiving module, and a transmitting module. The specific functions of each module are as follows:
the first receiving module is used for receiving vehicle diagnosis data submitted by the vehicle-mounted equipment;
the data processing module is used for carrying out structuralized processing on the diagnosis data according to a preset rule and storing the diagnosis data;
the extraction generation module is used for extracting a characteristic value of the vehicle diagnosis data and generating a data index according to the characteristic value;
the registration broadcasting module is used for registering the data index in a block chain and broadcasting the data index in the whole network;
the second receiving module is used for receiving a data use request of a user;
and the sending module is used for sending the corresponding diagnosis data to the user according to the type of the user.
The terminal device 6 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 60, a memory 61. Those skilled in the art will appreciate that fig. 6 is merely an example of a terminal device and is not limiting and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input output devices, network access devices, buses, etc.
The Processor 60 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like provided on the terminal device 6. Further, the memory 61 may also include both an internal storage unit of the terminal device 6 and an external storage device. The memory 61 is used for storing the computer programs and other programs and data required by the terminal device. The memory 61 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
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 place, or may be distributed on a plurality of 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 invention 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 modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.