CN111026732B - Dynamic inspection tour method and system - Google Patents
Dynamic inspection tour method and system Download PDFInfo
- Publication number
- CN111026732B CN111026732B CN201911219956.XA CN201911219956A CN111026732B CN 111026732 B CN111026732 B CN 111026732B CN 201911219956 A CN201911219956 A CN 201911219956A CN 111026732 B CN111026732 B CN 111026732B
- Authority
- CN
- China
- Prior art keywords
- acquisition
- model
- strategy
- interface
- mining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000007689 inspection Methods 0.000 title abstract description 53
- 238000005065 mining Methods 0.000 claims abstract description 70
- 238000010276 construction Methods 0.000 claims abstract description 35
- 238000013507 mapping Methods 0.000 claims abstract description 21
- 238000012216 screening Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 21
- 230000006870 function Effects 0.000 claims description 14
- 230000004044 response Effects 0.000 claims description 9
- 238000001514 detection method Methods 0.000 claims description 7
- 230000008859 change Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 20
- 238000005070 sampling Methods 0.000 description 15
- 238000002372 labelling Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000737 periodic effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
- G06F16/213—Schema design and management with details for schema evolution support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a dynamic inspection tour method and a dynamic inspection tour system, wherein the method comprises the following steps: responding to the construction operation of the acquisition object model of the user, and constructing the acquisition object model; responding to the construction operation of the mining strategy model of the user, and constructing the mining strategy model; generating a relational database table according to the acquisition object model; generating a mining interface according to the mining object model and the mining strategy model; and mapping the mining data input on the mining interface to a relational database table. According to the embodiment of the application, the acquisition object model and the acquisition strategy model are dynamically constructed according to the service requirement, the dynamic acquisition interface is generated based on the acquisition object model and the acquisition strategy model, and the acquisition data on the dynamic acquisition inspection interface is mapped to the relational database table for storage, so that the dynamic acquisition inspection according to the service change is realized.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a dynamic inspection tour method and system.
Background
At present, the inspection tour is mainly based on a single-table tiled or waterfall type dynamic acquisition page for a user, and the traditional inspection systems cannot dynamically adjust an interface in real time according to service changes, types of acquisition objects and the like to perform dynamic inspection tour. Thus, when new demands and new changes exist, parts such as the acquisition content form of the acquisition system need to be redeveloped, which is very troublesome.
That is, the current mining system cannot realize dynamic inspection tour.
Disclosure of Invention
The embodiment of the application provides a dynamic inspection tour method and a dynamic inspection tour system, which aim to solve the problem that the current inspection system cannot realize dynamic inspection tour.
In a first aspect, an embodiment of the present application provides a dynamic inspection method, including:
responding to the construction operation of the acquisition object model of the user, and constructing the acquisition object model;
responding to the construction operation of the mining strategy model of the user, and constructing a mining strategy model;
generating a relational database table according to the acquisition object model;
generating a mining interface according to the mining object model and the mining strategy model;
and mapping the mining data input on the mining interface to the relational database table.
It can be seen that the embodiment of the application dynamically constructs the acquisition object model and the acquisition strategy model according to the service requirement, generates a dynamic acquisition interface based on the acquisition object model and the acquisition strategy model, and then realizes the dynamic inspection according to the service change by mapping the acquisition data on the dynamic inspection interface to the relational database table for storage.
With reference to the first aspect, in a possible implementation manner, the acquisition object model is a graph model including vertices and directed edges, where the vertices represent acquisition objects and the directed edges represent acquisition object relationships;
in response to a user's acquisition object model construction operation, constructing an acquisition object model comprising:
responding to the construction operation of the acquisition object model of the user, and acquiring acquisition object information, acquisition object attribute information and acquisition object relation information;
establishing a vertex according to the acquisition object information and the acquisition object attribute information;
and connecting the vertexes by using directed edges according to the acquired object relation information to generate the graph model.
With reference to the first aspect, in one possible implementation manner, in response to a search policy model construction operation of the user, constructing a search policy model includes:
responding to the strategy creation operation of the user, and creating a search strategy;
and responding to the strategy configuration operation of the user, and labeling the searching strategy for the vertexes and/or the directed edges in the graph model.
With reference to the first aspect, in one possible implementation manner, generating a mining interface according to the mining object model and the mining policy model includes:
generating an interface acquisition field template according to the acquisition object attribute;
generating a screening function item template of the screening strategy according to the screening strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the acquisition object model;
and according to the interface acquisition field template, the acquisition strategy screening function item template and the rule template, generating the acquisition interface.
With reference to the first aspect, in a possible implementation manner, generating a relational database table according to the acquisition object model includes:
analyzing the attribute description information in the acquisition object model to obtain database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL sentence template;
and generating the relational database table according to the data in the preset data format and the SQL sentence template.
With reference to the first aspect, in a possible implementation manner, mapping the search data input on the search interface to the relational database table includes:
and mapping the search data input on the search interface to the relational database through the object identification code.
In a second aspect, an embodiment of the present application provides a dynamic patrol system, including:
the acquisition and detection object model construction module is used for responding to the acquisition and detection object model construction operation of a user to construct an acquisition and detection object model;
the acquisition strategy model construction module is used for responding to the acquisition strategy model construction operation of the user and constructing an acquisition strategy model;
the database table generating module is used for generating a relational database table according to the acquisition object model;
the acquisition interface generation module is used for generating an acquisition interface according to the acquisition object model and the acquisition strategy model;
and the mapping module is used for mapping the acquisition data input on the acquisition interface to the relational database table.
With reference to the second aspect, in a possible implementation manner, the acquisition object model is a graph model including vertices and directed edges, where the vertices represent acquisition objects and the directed edges represent acquisition object relationships;
the acquisition object model construction module is specifically used for:
responding to the construction operation of the acquisition object model of the user, and acquiring acquisition object information, acquisition object attribute information and acquisition object relation information;
establishing a vertex according to the acquisition object information and the acquisition object attribute information;
and connecting the vertexes by using directed edges according to the acquired object relation information to generate the graph model.
In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the method according to any one of the first aspects when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program which, when executed by a processor, implements a method as in any of the first aspects above.
In a fifth aspect, an embodiment of the application provides a computer program product for, when run on a terminal device, causing the terminal device to perform the method of any of the first aspects described above.
It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic block diagram of a flow chart of a dynamic patrol method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a graph model provided in an embodiment of the present application;
FIG. 3 is a schematic block diagram of a process for constructing a sampling object model according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a sampling object relationship according to an embodiment of the present application;
FIG. 5 is a schematic block diagram of a process for constructing a mining strategy model according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a correspondence between a sampling object model and a sampling strategy model according to an embodiment of the present application;
FIG. 7 is a schematic block diagram of a relational database table generation process according to an embodiment of the present application;
FIG. 8 is a schematic block diagram of a process for generating a search interface according to an embodiment of the present application;
FIG. 9 is a block diagram schematically illustrating a structure of a dynamic patrol system according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application 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 application with unnecessary detail.
The dynamic patrol method provided by the embodiment of the application can be realized based on a dynamic patrol platform system, the dynamic patrol platform system can be operated on terminal equipment, and the terminal equipment can be terminal equipment such as a server, a desktop computer, a notebook computer or an ultra-mobile personal computer (UMPC) and the like, and the embodiment of the application does not limit the specific type of the terminal equipment.
In some embodiments, the dynamic patrol platform system operates on a cloud server. The user dynamically builds a mining and checking object model and a mining and checking strategy model according to the service requirement, and the dynamic inspection and checking platform system generates a mining and checking interface according to the mining and checking object model and the mining and checking strategy model so as to dynamically generate the mining and checking interface according to the service change; and then, the dynamic patrol platform system displays the generated patrol interface on user terminal equipment (such as a mobile phone). And finally, the dynamic inspection tour and inspection platform system maps the inspection data on the inspection interface to a relational database for storage, so that dynamic inspection tour and inspection according to service changes is realized.
In other embodiments, the dynamic inspection platform system may also operate on a user terminal device (e.g., a mobile phone), and the user may dynamically construct an inspection object model and an inspection policy model according to service requirements; the dynamic inspection tour platform system generates an inspection interface based on the inspection object model and the inspection strategy model; after the user inputs the acquisition data in the generated acquisition interface, the dynamic inspection platform system maps the acquisition data to a relational database table for storage, so that dynamic inspection is realized according to service changes.
It should be noted that, for simplicity and convenience, the inspection tour may be simply referred to as an inspection tour, and in some contents below, an inspection object is expressed as an inspection tour object, an inspection object model is expressed as an inspection tour object model, an inspection object attribute is expressed as an inspection tour object attribute, an inspection object relationship is expressed as an inspection tour object relationship, and so on.
The technical scheme provided by the embodiment of the application will be described through a specific embodiment.
Referring to fig. 1, a flow schematic block diagram of a dynamic patrol method according to an embodiment of the present application may include the following steps:
and step S101, responding to the construction operation of the acquisition object model of the user, and constructing the acquisition object model.
It should be noted that the above-mentioned sampling object model is predefined, and includes, but is not limited to: one or more of an object identification code, an object identification name, a VR identification, an object classification identification, an object information description, major class information to which an object belongs, icon information, acquisition object attribute information, acquisition object relationship information, a check rule and a display rule. Wherein the verification rules include, but are not limited to: one or more of null check, digital check, length check, asynchronous check, telephony check, association check, and custom check.
The above object refers to a subject for acquisition, for example, when a user needs to acquire building data, the subject for acquisition is a building, a unit, a floor, a house, a fire-fighting facility, and the like.
Based on the above-defined sampling object model, the sampling object, the configuration sampling object attribute and the configuration sampling object relation need to be added or subtracted when the sampling object model is constructed according to the business change.
In some embodiments, the acquisition object model is a graph model that includes vertices representing acquisition objects and directed edges representing acquisition object relationships. That is, the object-under-examination model is expressed in terms of a relational graph, each vertex in the graph model being one object-under-examination, the vertex comprising an object attribute that includes each object-under-examination, each directed edge representing a relationship between two objects-under-examination.
Referring to the schematic diagram of the graph model shown in fig. 2, the graph model comprises three search objects, namely a building, a unit and a floor, wherein the three search objects respectively correspond to one vertex, the vertexes are connected through directed edges, and the directed edges represent the relationship between the two objects.
In the embodiment of the application, the vertexes comprise two types, one is an acquisition vertex, and the other is a classification vertex. Different types of vertices can be established according to different inspected objects. For example, vertices corresponding to the objects to be inspected such as buildings, units, and floors are collection vertices, and information on these vertices needs to be collected. Classification vertices are used for classification only, and classification vertices include collection vertices. For example, vertices corresponding to the detection objects such as fire-fighting facilities are classified vertices, and the information of the fire-fighting facilities is not collected, but is only used for classification, and the fire-fighting facilities are classified into collection vertices such as fire hydrants and fire extinguishers.
The two acquisition objects (namely, the two vertexes) are connected through a directed edge, and the directed edge represents the relation between the acquisition objects. Directed edges may be classified from different dimensions. The relationships are classified into association, dependence, combination, aggregation, realization, generalization and the like, namely, the relationships between the acquisition objects and the acquisition objects comprise, but are not limited to, association, dependence, combination, aggregation, realization, generalization and the like.
One vertex may not be connected to other vertices, may be connected to 1 vertex, or may be connected to n vertices, i.e., 1..0, 1..1, 1..n.
Based on this, referring to the flow schematic block diagram of the process of constructing the acquisition object model shown in fig. 3, the above-described specific process of constructing the acquisition object model in response to the user's acquisition object model constructing operation may include:
step S301, acquiring acquisition object information, acquisition object attribute information, and acquisition object relationship information in response to a user acquisition object model construction operation.
Specifically, the user can select or create corresponding acquisition objects according to the service requirement, and configure the acquisition object attribute and the acquisition object relation. And the dynamic inspection platform system acquires the inspection object information, the inspection object attribute information and the inspection object relation information according to the user operation.
The user may dynamically add or subtract the search object based on the business changes. For example, when building data needs to be collected, building, unit, floor, house and other objects are created. The user configures the acquisition object attribute for the created acquisition object through the object attribute configuration operation. The acquisition object attribute refers to the basic information of acquisition.
For example, after creating a building, unit, floor, house, fire facility, etc. to search for an object, the user configures the building with search object attributes including, but not limited to, building code, building name, building address, etc. The search object attributes configured for a unit include, but are not limited to, a unit code, a unit name, and a unit floor. The checked object attributes for the floor configuration include, but are not limited to, floor codes and number of floors. The acquisition object attributes configured for the house include, but are not limited to, house number and house resident information.
After the acquisition object is created, it is necessary to configure the object relationship between the respective acquisition objects in addition to the acquisition object attribute for the acquisition object. The acquisition object relationship refers to an association relationship between two acquisition objects, through which the two acquisition objects can be bound to form a relationship, and each relationship is identified by an object identification code.
See, for example, the schematic diagram of the acquisition object relationship shown in fig. 4. Building and unit are bound together through building code and unit code, and the relation between building and unit is identified by object identification code X. The two search objects of the unit and the house are bound together through the unit code and the house code, and the relation between the unit and the house is identified by the object identification code Y.
Step S302, establishing a vertex according to the acquisition object information and the acquisition object attribute information.
Specifically, after the dynamic inspection tour platform system acquires the information of the inspected object and the inspected object attribute required to be created by the user, a vertex comprising the inspected object attribute is established.
It will be appreciated that different types of vertices are created based on the subject. When the vertex is an acquisition vertex, the acquisition vertex includes an acquisition object attribute. When the vertex is a classification vertex, the classification vertex does not include the search object attribute.
Step S303, connecting the vertexes by using the directed edges according to the collected object relation information to generate a graph model.
It will be appreciated that the directed edges represent the object relationship between two objects, and that after connecting the vertices using the directed edges, a graph model, i.e., a model of the acquisition object, is generated.
The user creates a picking object according to the service requirement, and after configuring the picking object attribute and the picking object relation for the picking object, a picking object model corresponding to the service requirement is generated.
For example, when a certain area A is required to be searched, the certain area A is searched to include properties such as building codes, building names, building addresses and the like; when a certain unit information is searched, the unit comprises attributes such as a unit code, a unit name, a unit floor and the like; when a certain unit floor is searched, the floor comprises floor codes, several floors and other attributes; when the condition of a house on a certain floor is checked, the house comprises house codes, house resident information and other attributes.
Step S102, responding to the construction operation of the mining strategy model of the user, and constructing the mining strategy model.
It should be noted that, after the user builds the image picking and checking model according to the service requirement, when the image picking and checking model is used to pick and check data, there may be too much data to be checked, and the data to be checked may not be all required. To reduce the screening data, a relevant screening strategy may be constructed. For example, the policy is constructed as to which of the picking objects or picking object attributes are necessary to be picked, which of the picking objects or picking object attributes are periodic picking, and so on.
In some embodiments, referring to the schematic flow diagram of the process of constructing the mining strategy model shown in fig. 5, the specific process of constructing the mining strategy model in response to the mining strategy model constructing operation of the user may include:
step S501, responding to the strategy creation operation of the user, and creating the acquisition strategy.
Specifically, the user can create a required search strategy according to the data acquisition requirements in the service requirements.
For example, depending on the user's business needs, the required screening policies including, but not limited to, must-check, tightly-check, periodically-check, whether to take a picture, whether to use VR devices, etc., are created.
And step S502, labeling the searching strategy for the vertexes and/or the directed edges in the graph model in response to the strategy configuration operation of the user.
Specifically, the user configures a corresponding acquisition strategy according to the service requirement, namely, the user can configure the corresponding acquisition strategy for one or more of the acquisition object, the acquisition object attribute and the acquisition object relation according to the requirement.
Referring to a schematic diagram of the correspondence between the acquisition object model and the acquisition strategy model shown in fig. 6, as shown in fig. 6, the acquisition object model includes three acquisition objects, and the acquisition objects are connected by a directed edge. And labeling corresponding mining strategies for the vertexes and/or the edges by using the mining strategies in the mining strategy model.
For example, the created search objects are buildings, units, floors, houses, and the like. And a mining strategy is established for the configuration of buildings, units, floors, houses and the like according to the mining requirements. The building is configured to be necessary to be searched, and the house is configured to be periodically searched.
As another example, the attribute of the object to be picked up of the building includes building code, building name, building address, etc. And configuring the established mining strategy for the configured mining object attribute according to the service requirement. The building codes are specifically configured to be necessary to search.
It should be noted that, after the acquisition policy is configured for the acquisition object, the configured acquisition policy does not change entirely according to the change of the acquisition object relationship. For example, a building and a fire-fighting facility are in one relationship, a house and a fire-fighting facility are in one relationship, and the mining strategies of the fire-fighting facilities are different under different relationships. Therefore, strategies are required to be configured for different mining and checking object relationships, and particularly, when floor data are required to be checked, fire-fighting facilities are required to be checked; when the house data is collected, the fire-fighting facilities are periodically collected.
After the mining strategy model is constructed, the mining process can screen out which mining objects are necessary to be checked and which mining objects are periodic to be checked through the mining strategy, so that the mining is more convenient, and the mining data quantity is reduced.
And step S103, generating a relational database table according to the acquisition object model.
It should be noted that, the object model includes description information of the database, and the relational database may be automatically generated according to the description information of the database.
In some embodiments, referring to the schematic flow diagram of the relational database table generation process shown in fig. 7, the specific process of generating a relational database table according to the look-up object model may include:
and step 701, analyzing and checking the attribute description information in the object model to acquire database description information in the attribute description information.
Step S702, converting the database description information into data with a preset data format.
It should be noted that, the database description information refers to description of database definition in the attribute of the object model. After the database description information is acquired, the database description information is packaged into data in a preset format, wherein the preset data format refers to a format which can be identified by an engine.
Step S703, acquiring an SQL sentence template.
Specifically, an executable SQL statement template is created by the engine.
Step S704, generating a relational database table according to the data in the preset data format and the SQL sentence template.
Specifically, filling data with a preset data format into an SQL statement template to generate an executable SQL statement. Then, the database executes the generated executable SQL statement to generate a relational database table.
And step S104, generating a mining interface according to the mining object model and the mining strategy model.
Specifically, the acquisition object attribute in the acquisition object model is packaged, the acquisition strategy in the acquisition strategy model is packaged, and the acquisition rule data is packaged to obtain a corresponding template; and then reading the generated template by using an engine to generate the acquisition interface.
In some embodiments, referring to the schematic flow diagram of the process of generating a sampling interface shown in fig. 8, the specific process of generating a sampling interface according to the sampling object model and the sampling strategy model may include:
step S801, generating an interface acquisition field template according to the acquisition object attribute.
Specifically, the acquisition object attributes in the acquisition object model are assembled into a data object format which can be identified by a template language through a mapping method, and an interface acquisition field template is formed according to the acquisition object attributes of the data object format.
For example, the object to be inspected is a building, the attribute of the object to be inspected includes building code, floor name and floor address, and the options displayed on the interface include building code, floor name and floor address.
And step S802, a screening function item template of the screening strategy is generated according to the screening strategy.
Specifically, the mining strategy in the mining strategy model is packaged, and a mining strategy screening function item template is generated.
For example, the search policy includes a search-for-necessary, a search-for-strict, a periodic search, a photograph of whether or not, and a VR device is used, the generated interface includes a search-for-necessary option, a search-for-strict option, a photograph of whether or not, and a VR device use option, and these options may exist in a drop-down box, and the user may select different options according to a search object, a search object attribute, and the like.
Step 803, according to the predefined rules in the collected object model, a rule template corresponding to the predefined rules is generated.
It should be noted that the predefined rules include, but are not limited to, display rules and verification rules. And respectively corresponding to the display rule, the check rule and the like to form a display rule template, a check rule template and the like.
Step S804, screening the function item templates and the rule templates according to the interface acquisition field templates and the acquisition strategies to generate an acquisition interface.
Specifically, the above-described screening interface is generated using an engine through the generated template. After the acquisition interface is generated, the acquisition interface may be displayed on a terminal interface of the user.
Step S105, mapping the acquisition data input on the acquisition interface to a relational database table.
In a specific application, the search data input on the search interface can be mapped to the relational database through the object identification code. The object identification code is a unique identifier of the object model, from which the object and the strategy can be determined.
The mapping process is a process of data storage, and the mapping is to store the data filled in the acquisition interface in a database table. The acquisition interface and the database table are identified by the object identification code, and then the data is transmitted from the acquisition interface to the database for storage.
According to the embodiment of the application, the acquisition object model and the acquisition strategy model are dynamically constructed according to the service requirement, the dynamic acquisition interface is generated based on the acquisition object model and the acquisition strategy model, and the acquisition data on the dynamic acquisition inspection interface is mapped to the relational database table for storage, so that the dynamic acquisition inspection according to the service change is realized.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
Corresponding to the dynamic patrol inspection method described in the above embodiments, fig. 9 is a schematic block diagram of a dynamic patrol inspection system provided in the embodiment of the present application, and for convenience of explanation, only the portions relevant to the embodiment of the present application are shown.
Referring to fig. 9, the system may include:
a mining-inspection-object-model construction module 91 for constructing a mining-inspection-object model in response to a mining-inspection-object-model construction operation by a user;
the mining strategy model construction module 92 is configured to respond to a mining strategy model construction operation of a user to construct a mining strategy model;
a database table generating module 93 for generating a relational database table according to the sampling object model;
a mining interface generation module 94 for generating a mining interface according to the mining object model and the mining strategy model;
and a mapping module 95, configured to map the acquisition data input on the acquisition interface to a relational database table.
In one possible implementation, the acquisition object model is a graph model including vertices representing acquisition objects and directed edges representing acquisition object relationships;
the acquisition object model construction module is specifically used for:
responding to the construction operation of the acquisition object model of the user, and acquiring acquisition object information, acquisition object attribute information and acquisition object relation information;
establishing a vertex according to the acquisition object information and the acquisition object attribute information;
and connecting the vertexes by using directed edges according to the acquired object relation information to generate a graph model.
In one possible implementation manner, the above-mentioned mining strategy model construction module may be specifically used for:
responding to the strategy creation operation of the user, and creating a search strategy;
and labeling the searching strategy for the vertexes and/or the directed edges in the graph model in response to the strategy configuration operation of the user.
In one possible implementation manner, the above-mentioned acquisition interface generation module may be specifically configured to:
generating an interface acquisition field template according to the acquisition object attribute;
generating a screening function item template of the screening strategy according to the screening strategy;
generating a rule template corresponding to the predefined rule according to the predefined rule in the acquisition object model;
and screening the function item templates and the rule templates according to the interface acquisition field templates, the acquisition strategy to generate an acquisition interface.
In one possible implementation manner, the database table generating module may be specifically configured to:
analyzing and checking attribute description information in the object model to obtain database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL sentence template;
and generating a relational database table according to the data in the preset data format and the SQL sentence template.
In one possible implementation manner, the mapping module is specifically configured to:
and mapping the acquisition data input on the acquisition interface to a relational database through the object identification code.
It should be noted that, because the content of information interaction and execution process between the above system modules is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.
Fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 10, the terminal device 10 of this embodiment includes: at least one processor 100, a memory 101, and a computer program 102 stored in the memory 101 and executable on the at least one processor 100, the processor 100 implementing the steps in any of the various method embodiments described above when executing the computer program 102.
The terminal device 10 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal device may include, but is not limited to, a processor 100, a memory 101. It will be appreciated by those skilled in the art that fig. 10 is merely an example of the terminal device 10 and is not intended to limit the terminal device 10, and may include more or fewer components than shown, or may combine certain components, or may include different components, such as input-output devices, network access devices, etc.
The processor 100 may be a central processing unit (Central Processing Unit, CPU), and the processor 100 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 101 may in some embodiments be an internal storage unit of the terminal device 10, such as a hard disk or a memory of the terminal device 10. The memory 101 may in other embodiments also be an external storage device of the terminal device 10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 10. Further, the memory 101 may also include both an internal storage unit and an external storage device of the terminal device 10. The memory 101 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs, etc., such as program codes of the computer program. The memory 101 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps for implementing the various method embodiments described above.
Embodiments of the present application provide a computer program product enabling a terminal device to carry out the steps of the method embodiments described above when the computer program product is run on the terminal device.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
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 solution. 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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (10)
1. The dynamic patrol method is characterized by comprising the following steps:
responding to the construction operation of the acquisition object model of the user, and constructing the acquisition object model;
responding to the construction operation of the mining strategy model of the user, and constructing a mining strategy model;
generating a relational database table according to the acquisition object model;
generating a mining interface according to the mining object model and the mining strategy model;
mapping the mining data input on the mining interface to the relational database table;
wherein, responding to the construction operation of the mining strategy model of the user, constructing the mining strategy model comprises the following steps:
responding to the strategy creation operation of the user, and creating a search strategy;
responding to the strategy configuration operation of the user, marking the corresponding acquisition strategy for the vertexes and/or the directed edges in the graph model by using the acquisition strategy, wherein the vertexes of the graph model represent acquisition objects, and the directed edges of the graph model represent the relationship between the two acquisition objects;
the acquisition object model is a graph model comprising vertexes and directed edges, wherein the vertexes represent acquisition objects, and the directed edges represent acquisition object relations;
in response to a user's acquisition object model construction operation, constructing an acquisition object model comprising:
responding to the construction operation of the acquisition object model of the user, and acquiring acquisition object information, acquisition object attribute information and acquisition object relation information;
establishing a vertex according to the acquisition object information and the acquisition object attribute information;
and connecting the vertexes by using directed edges according to the acquired object relation information to generate the graph model.
2. The method of claim 1, wherein generating a screening interface from the screening object model and the screening policy model comprises:
generating an interface acquisition field template according to the acquisition object attribute;
generating a screening function item template of the screening strategy according to the screening strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the acquisition object model;
and according to the interface acquisition field template, the acquisition strategy screening function item template and the rule template, generating the acquisition interface.
3. The method of claim 1, wherein generating a relational database table from the query object model comprises:
analyzing the attribute description information in the acquisition object model to obtain database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL sentence template;
and generating the relational database table according to the data in the preset data format and the SQL sentence template.
4. A method according to any one of claims 1 to 3, wherein mapping the screening data entered on the screening interface to the relational database table comprises:
and mapping the search data input on the search interface to the relational database through the object identification code.
5. A dynamic patrol system, comprising:
the acquisition and detection object model construction module is used for responding to the acquisition and detection object model construction operation of a user to construct an acquisition and detection object model;
the acquisition strategy model construction module is used for responding to the acquisition strategy model construction operation of the user and constructing an acquisition strategy model;
the database table generating module is used for generating a relational database table according to the acquisition object model;
the acquisition interface generation module is used for generating an acquisition interface according to the acquisition object model and the acquisition strategy model;
the mapping module is used for mapping the acquisition data input on the acquisition interface to the relational database table;
the mining strategy model construction module is specifically used for: responding to the strategy creation operation of the user, and creating a search strategy;
responding to the strategy configuration operation of the user, marking the corresponding acquisition strategy for the vertexes and/or the directed edges in the graph model by using the acquisition strategy, wherein the vertexes of the graph model represent acquisition objects, and the directed edges of the graph model represent the relationship between the two acquisition objects;
the acquisition object model is a graph model comprising vertexes and directed edges, wherein the vertexes represent acquisition objects, and the directed edges represent acquisition object relations;
the acquisition object model construction module is specifically used for:
responding to the construction operation of the acquisition object model of the user, and acquiring acquisition object information, acquisition object attribute information and acquisition object relation information;
establishing a vertex according to the acquisition object information and the acquisition object attribute information;
and connecting the vertexes by using directed edges according to the acquired object relation information to generate the graph model.
6. The system of claim 5, wherein the screening interface generation module is specifically configured to:
generating an interface acquisition field template according to the acquisition object attribute;
generating a screening function item template of the screening strategy according to the screening strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the acquisition object model;
and according to the interface acquisition field template, the acquisition strategy screening function item template and the rule template, generating the acquisition interface.
7. The system of claim 5, wherein the database table generation module is specifically configured to:
analyzing the attribute description information in the acquisition object model to obtain database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL sentence template;
and generating the relational database table according to the data in the preset data format and the SQL sentence template.
8. The system of any of claims 5-7, wherein the mapping module is further to:
and mapping the search data input on the search interface to the relational database through the object identification code.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the computer program.
10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911219956.XA CN111026732B (en) | 2019-12-03 | 2019-12-03 | Dynamic inspection tour method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911219956.XA CN111026732B (en) | 2019-12-03 | 2019-12-03 | Dynamic inspection tour method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111026732A CN111026732A (en) | 2020-04-17 |
| CN111026732B true CN111026732B (en) | 2023-11-17 |
Family
ID=70204065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911219956.XA Active CN111026732B (en) | 2019-12-03 | 2019-12-03 | Dynamic inspection tour method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026732B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104424338A (en) * | 2013-09-11 | 2015-03-18 | 北大方正集团有限公司 | Automatic generation device and automatic generation method for web system |
| CN106227800A (en) * | 2016-07-21 | 2016-12-14 | 中国科学院软件研究所 | The storage method of the big data of a kind of highlights correlations and management system |
| CN107479904A (en) * | 2017-05-25 | 2017-12-15 | 成都九洲电子信息系统股份有限公司 | A kind of more application scenarios information collecting methods |
| CN107609052A (en) * | 2017-08-23 | 2018-01-19 | 中国科学院软件研究所 | A kind of generation method and device of the domain knowledge collection of illustrative plates based on semantic triangle |
| CN107643932A (en) * | 2017-08-31 | 2018-01-30 | 深圳天珑无线科技有限公司 | A kind of collecting method, harvester and storage device |
| CN107992600A (en) * | 2017-12-13 | 2018-05-04 | 中国建设银行股份有限公司福建省分行 | A kind of method and computer equipment of intelligence generation data acquisition webpage |
| CN108154569A (en) * | 2017-12-27 | 2018-06-12 | 广州奥格智能科技有限公司 | A kind of inspection acquisition method based on object modelization configuration |
| CN108206747A (en) * | 2016-12-16 | 2018-06-26 | 中国移动通信集团山西有限公司 | Method for generating alarm and system |
| CN108595178A (en) * | 2018-05-04 | 2018-09-28 | 武汉极意网络科技有限公司 | A kind of collecting method, device and equipment based on hook |
| CN109150610A (en) * | 2018-08-29 | 2019-01-04 | 深圳市未来交互信息技术有限公司 | The network event acquisition method of rule-based adaptation |
| CN109284463A (en) * | 2018-08-15 | 2019-01-29 | 山东鲁能软件技术有限公司 | A kind of method of data capture and system based on dynamic template |
| CN110020358A (en) * | 2017-11-07 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Method and apparatus for generating dynamic page |
-
2019
- 2019-12-03 CN CN201911219956.XA patent/CN111026732B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104424338A (en) * | 2013-09-11 | 2015-03-18 | 北大方正集团有限公司 | Automatic generation device and automatic generation method for web system |
| CN106227800A (en) * | 2016-07-21 | 2016-12-14 | 中国科学院软件研究所 | The storage method of the big data of a kind of highlights correlations and management system |
| CN108206747A (en) * | 2016-12-16 | 2018-06-26 | 中国移动通信集团山西有限公司 | Method for generating alarm and system |
| CN107479904A (en) * | 2017-05-25 | 2017-12-15 | 成都九洲电子信息系统股份有限公司 | A kind of more application scenarios information collecting methods |
| CN107609052A (en) * | 2017-08-23 | 2018-01-19 | 中国科学院软件研究所 | A kind of generation method and device of the domain knowledge collection of illustrative plates based on semantic triangle |
| CN107643932A (en) * | 2017-08-31 | 2018-01-30 | 深圳天珑无线科技有限公司 | A kind of collecting method, harvester and storage device |
| CN110020358A (en) * | 2017-11-07 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Method and apparatus for generating dynamic page |
| CN107992600A (en) * | 2017-12-13 | 2018-05-04 | 中国建设银行股份有限公司福建省分行 | A kind of method and computer equipment of intelligence generation data acquisition webpage |
| CN108154569A (en) * | 2017-12-27 | 2018-06-12 | 广州奥格智能科技有限公司 | A kind of inspection acquisition method based on object modelization configuration |
| CN108595178A (en) * | 2018-05-04 | 2018-09-28 | 武汉极意网络科技有限公司 | A kind of collecting method, device and equipment based on hook |
| CN109284463A (en) * | 2018-08-15 | 2019-01-29 | 山东鲁能软件技术有限公司 | A kind of method of data capture and system based on dynamic template |
| CN109150610A (en) * | 2018-08-29 | 2019-01-04 | 深圳市未来交互信息技术有限公司 | The network event acquisition method of rule-based adaptation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111026732A (en) | 2020-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8484231B2 (en) | System and method for data mapping and information sharing | |
| CN109479061A (en) | Compliance violates detection | |
| EP3433732A1 (en) | Converting visual diagrams into code | |
| CN111427971B (en) | Business modeling method, device, system and medium for computer system | |
| US20150006517A1 (en) | Generating business intelligence geospatial elements | |
| CN111538774B (en) | Data storage and display method, system, equipment and storage medium | |
| CN113806434B (en) | Big data processing method, device, equipment and medium | |
| CN110245128B (en) | Meta-model establishing method and device, storage medium and electronic device | |
| CN111435304B (en) | Method and device for generating space unit, storage medium and processor | |
| US10628465B2 (en) | Generating a ranked list of best fitting place names | |
| CN110503409B (en) | Information processing method and related device | |
| CN105357204A (en) | Method and apparatus for generating terminal identifying information | |
| CN110795697A (en) | Logic expression obtaining method and device, storage medium and electronic device | |
| CN113868528A (en) | Information recommendation method and device, electronic equipment and readable storage medium | |
| CN111142863B (en) | Page generation method and device | |
| US20210312174A1 (en) | Method and apparatus for processing image, device and storage medium | |
| CN111026732B (en) | Dynamic inspection tour method and system | |
| US10268979B2 (en) | Intermediate resource allocation tracking in data models | |
| CN111652741B (en) | User preference analysis method, device and readable storage medium | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN114996369A (en) | Method and device for constructing data warehouse index library | |
| CN115022397A (en) | Interface parameter simplifying method and device, electronic equipment and storage medium | |
| CN111291196A (en) | Method and device for improving knowledge graph and method and device for processing data | |
| CN113516083B (en) | Ecological restoration modeling method for vegetation in abandoned farmland in grassland area | |
| CN110909191A (en) | Graph data processing method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220223 Address after: 518000 2515, building 2, Huilong business center, North Station community, Minzhi street, Longhua District, Shenzhen, Guangdong Province Applicant after: Shenzhen Zhongke Baotai Aerospace Technology Co.,Ltd. Address before: Room 1101-1102, building 1, Changfu Jinmao building, No.5, Shihua Road, free trade zone, Fubao street, Futian District, Shenzhen, Guangdong 518000 Applicant before: Shenzhen Zhongke Baotai Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230117 Address after: 1602, 16th floor, building B, Datang times commercial complex, 2203 Meilong Avenue, Qinghua community, Longhua street, Longhua District, Shenzhen, Guangdong 518000 Applicant after: Shenzhen Woven Brain Intelligence Technology Co.,Ltd. Address before: 518000 2515, building 2, Huilong business center, North Station community, Minzhi street, Longhua District, Shenzhen, Guangdong Province Applicant before: Shenzhen Zhongke Baotai Aerospace Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |