CN111026732A - Dynamic patrolling method and system - Google Patents
Dynamic patrolling method and system Download PDFInfo
- Publication number
- CN111026732A CN111026732A CN201911219956.XA CN201911219956A CN111026732A CN 111026732 A CN111026732 A CN 111026732A CN 201911219956 A CN201911219956 A CN 201911219956A CN 111026732 A CN111026732 A CN 111026732A
- Authority
- CN
- China
- Prior art keywords
- acquisition
- model
- search
- check
- strategy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000007689 inspection Methods 0.000 claims abstract description 70
- 238000010276 construction Methods 0.000 claims abstract description 25
- 238000013507 mapping Methods 0.000 claims abstract description 18
- 238000004590 computer program Methods 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 17
- 238000005065 mining Methods 0.000 claims description 15
- 230000006870 function Effects 0.000 claims description 13
- 238000012216 screening Methods 0.000 claims description 9
- 238000012552 review Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 22
- 238000010586 diagram Methods 0.000 description 20
- 230000008859 change Effects 0.000 description 6
- 238000011835 investigation Methods 0.000 description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction 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
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 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
- 238000002372 labelling Methods 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
- 230000000737 periodic effect Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/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 patrolling and patrolling method and a system, wherein the method comprises the following steps: responding to the construction operation of the object model of the acquisition and check of the user, and constructing the object model of the acquisition and check; responding to the construction operation of the acquisition and search strategy model of the user, and constructing the acquisition and search strategy model; generating a relational database table according to the acquisition and check object model; generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search strategy model; and mapping the acquisition and search data input on the acquisition and search 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 business needs, 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 and inspection interface is mapped to the relational database table for storage, so that the dynamic acquisition and inspection according to business changes is realized.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a dynamic patrolling and inspecting method and system.
Background
At present, the inspection tour is mainly based on a single-table tiled or waterfall type to provide a dynamic acquisition page for a user, and the traditional inspection systems cannot dynamically adjust an interface in real time according to changes such as service changes and acquisition object types to perform dynamic inspection tour. Thus, when there is a new demand and a new change, it is necessary to redevelop the parts of the acquisition and inspection content form of the acquisition and inspection system, which is very troublesome.
That is, a dynamic patrol cannot be realized based on the current acquisition system.
Disclosure of Invention
The embodiment of the application provides a dynamic patrolling and patrolling method and a system, which aim to solve the problem that the dynamic patrolling and patrolling cannot be realized based on the current patrolling and patrolling system.
In a first aspect, an embodiment of the present application provides a dynamic patrolling and inspecting method, including:
responding to the construction operation of the object model of the acquisition and check of the user, and constructing the object model of the acquisition and check;
responding to the construction operation of the acquisition and search strategy model of the user, and constructing an acquisition and search strategy model;
generating a relational database table according to the acquisition and check object model;
generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search strategy model;
and mapping the acquisition and search data input on the acquisition and search interface to the relational database table.
It can be seen that, in the embodiment of the application, the acquisition object model and the acquisition strategy model are dynamically constructed according to the business needs, 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 and inspection interface is mapped to the relational database table for storage, so that the dynamic acquisition and inspection according to the business changes is realized.
With reference to the first aspect, in a possible implementation manner, the object model to be checked is a graph model including a vertex and a directed edge, where the vertex represents an object to be checked, and the directed edge represents a relation between the object to be checked;
responding to the mining and checking object model building operation of a user, building a mining and checking object model, comprising the following steps:
acquiring acquisition and check object information, acquisition and check object attribute information and acquisition and check object relation information in response to acquisition and check object model construction operation of the user;
establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked;
and connecting each vertex by using a directed edge according to the acquisition and check object relation information to generate the graph model.
With reference to the first aspect, in a possible implementation manner, the constructing an acquisition and search policy model in response to an acquisition and search policy model construction operation of the user includes:
creating a mining and searching strategy in response to the strategy creating operation of the user;
and marking the acquisition strategy for the vertexes and/or directed edges in the graph model in response to the strategy configuration operation of the user.
With reference to the first aspect, in a possible implementation manner, generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search policy model includes:
generating an interface acquisition field template according to the attributes of the acquisition and search objects;
generating an acquisition and search strategy screening function item template according to the acquisition and search strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the collection object model;
and generating the acquisition and inspection interface according to the interface acquisition field template, the acquisition and inspection strategy screening function item template and the rule template.
With reference to the first aspect, in a possible implementation manner, generating a relational database table according to the query object model includes:
analyzing the attribute description information in the acquisition object model to acquire database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL statement template;
and generating the relational database table according to the data in the preset data format and the SQL statement template.
With reference to the first aspect, in a possible implementation manner, mapping the query data input on the query interface to the relational database table includes:
and mapping the acquisition and search data input on the acquisition and 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 inspection system, including:
the acquisition and inspection object model building module is used for responding to acquisition and inspection object model building operation of a user and building an acquisition and inspection object model;
the acquisition and search strategy model construction module is used for responding to the acquisition and search strategy model construction operation of the user and constructing an acquisition and search strategy model;
the database table generating module is used for generating a relational database table according to the acquisition and check object model;
the acquisition and search interface generation module is used for generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search strategy model;
and the mapping module is used for mapping the acquisition and search data input on the acquisition and search interface to the relational database table.
With reference to the second aspect, in a possible implementation manner, the object model to be checked is a graph model including a vertex and a directed edge, the vertex represents an object to be checked, and the directed edge represents a relation between the object to be checked and the vertex;
the acquisition and inspection object model building module is specifically used for:
acquiring acquisition and check object information, acquisition and check object attribute information and acquisition and check object relation information in response to acquisition and check object model construction operation of the user;
establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked;
and connecting each vertex by using a directed edge according to the acquisition and check object relation information to generate the graph model.
In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor, when executing the computer program, implements the method according to any one of the above first aspects.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the method according to any one of the above first aspects.
In a fifth aspect, the present application provides a computer program product, which when run on a terminal device, causes the terminal device to execute the method of any one of the above first aspects.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, 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 application, 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 block diagram of a flow of a dynamic patrolling method provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of a graphical model provided in an embodiment of the present application;
FIG. 3 is a schematic block diagram of a process for constructing an interview object model according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of an object relationship acquisition and check provided in an embodiment of the present application;
FIG. 5 is a schematic block diagram of a flow of a search strategy model construction process according to an embodiment of the present application;
fig. 6 is a schematic diagram of a correspondence relationship between an acquisition and query object model and an acquisition and query policy model provided in an embodiment of the present application;
FIG. 7 is a schematic block flow diagram illustrating a relational database table generation process provided by an embodiment of the present application;
FIG. 8 is a schematic block diagram of a flow of a mining and inspection interface generation process provided in an embodiment of the present application;
fig. 9 is a schematic block diagram of a structure of a dynamic patrol inspection system provided in 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 particular system structures, 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 inspection method provided by the embodiment of the application can be implemented based on a dynamic patrol inspection platform system, the dynamic patrol inspection platform system can be operated on a terminal device, the terminal device can be a server, a desktop computer, a notebook computer or an ultra-mobile personal computer (UMPC) or other terminal devices, and the embodiment of the application does not limit the specific type of the terminal device.
In some embodiments, the dynamic patrolling platform system runs on a cloud server. A user dynamically constructs an acquisition and inspection object model and an acquisition and inspection strategy model according to business requirements, and a dynamic acquisition and inspection platform system generates an acquisition and inspection interface according to the acquisition and inspection object model and the acquisition and inspection strategy model so as to dynamically generate the acquisition and inspection interface according to business changes; then, the dynamic patrol platform system displays the generated patrol interface on the user terminal device (for example, a mobile phone). The acquisition user can input the acquisition data of the corresponding acquisition items in the acquisition interface displayed by the user terminal equipment, and finally, the dynamic inspection patrol platform system maps the acquisition data on the acquisition interface to the relational database for storage, so as to realize dynamic inspection patrol according to service changes.
In other embodiments, the dynamic patrol acquisition and patrol platform system may also be run on a user terminal device (e.g., a mobile phone), and a user may dynamically construct an acquisition object model and an acquisition policy model according to business needs; the dynamic patrolling platform system generates a patrolling interface based on a patrolling object model and a patrolling strategy model; after the user inputs the data to be inspected in the generated inspection interface, the dynamic inspection platform system maps the data to be inspected to the relational database table for storage, and dynamic inspection according to the service change is realized.
It should be noted that the patrol inspection can be referred to as acquisition for short, so for the sake of simple representation, some contents in the following are to use acquisition to represent patrol inspection, acquisition object to represent patrol inspection object, acquisition object model to represent patrol inspection object model, acquisition object attribute to represent patrol inspection object attribute, acquisition object relationship to represent patrol inspection object relationship, and the like.
The technical solutions provided in the embodiments of the present application will be described below by specific embodiments.
Referring to fig. 1, a schematic flow diagram of a dynamic patrolling method provided in an embodiment of the present application is shown, where the method may include the following steps:
and S101, responding to the construction operation of the mining and examining object model of the user, and constructing the mining and examining object model.
It should be noted that the above mentioned model of the subject to be investigated is predefined, and includes but is not limited to: the object identification code, the object identification name, the VR identification, the object classification identification, the object information description, the object belonging large class information, the icon information, the object attribute information, the object relation information, the check rule and the display rule. Wherein, the check rule includes but is not limited to: one or more of a null check, a digit check, a length check, an asynchronous check, a telephone check, an association check, and a custom check.
The above objects are taken as the inspection objects, for example, when the user needs to acquire the data of the building, the inspection objects are the building, the unit, the floor, the house, the fire fighting facility and the like.
Based on the above defined object model, the object model is constructed according to the service change, and the object to be searched needs to be added or deleted, the object attribute to be searched is configured, and the object relationship to be searched is configured.
In some embodiments, the check object model is a graph model that includes vertices representing check objects and directed edges representing check object relationships. That is, the object model is expressed in the form of a relational graph, each vertex in the graph model is an object to be searched, the vertex includes an object attribute including each object to be searched, and each directed edge represents a relationship between two objects to be searched.
Referring to fig. 2, a diagram model schematic diagram is shown, which includes three acquisition and check objects, namely a building, a unit and a floor, wherein the three acquisition and check objects correspond to one vertex respectively, the vertices are connected through directed edges, and the directed edges represent the relationship between two objects.
In the embodiment of the application, the vertex comprises two types, namely a collection vertex and a classification vertex. Different types of vertices can be created depending on the object under investigation. For example, vertices corresponding to an object to be examined such as a building, a cell, and a floor are acquisition vertices, and information on these vertices needs to be acquired. The classification vertices are used for classification only, including the collection vertices. For example, the vertices corresponding to the targets to be inspected in fire fighting facilities are classified vertices, and are used only for classification without collecting information on fire fighting facilities, and fire fighting facilities are classified into fire plugs, fire extinguishers, and other collection vertices.
Two checked objects (namely two vertexes) are connected through a directed edge, and the directed edge represents the relation between the checked objects. Directed edges can be classified from different dimensions. The relationship is divided into categories of association, dependency, combination, aggregation, implementation, generalization and the like, that is, the relationship between the acquisition and investigation object and the acquisition and investigation object includes, but is not limited to, association, dependency, combination, aggregation, implementation, generalization and the like.
One vertex may be connected to 1 vertex as well as to n vertices, i.e., 1.. 0, 1.. 1,1.. n.
Based on this, referring to the schematic flow chart of the mining object model building process shown in fig. 3, the specific process of building the mining object model in response to the mining object model building operation of the user may include:
step S301, responding to the model construction operation of the object to be checked of the user, and acquiring the information of the object to be checked, the attribute information of the object to be checked and the relation information of the object to be checked.
Specifically, the user may select or create a corresponding query object according to the service requirement, and configure the attribute and relationship of the query object. The dynamic patrol acquisition and inspection platform system acquires acquisition and inspection object information, acquisition and inspection object attribute information and acquisition and inspection object relation information according to user operation.
The user can add or delete the searching objects dynamically according to the service change. For example, when building data needs to be collected, the objects to be collected, such as buildings, units, floors, and houses, are created. And configuring the attribute of the acquisition object for the created acquisition object by the user through object attribute configuration operation. The attribute of the object is collected and checked basic information.
For example, after creating a site, a unit, a floor, a house, a fire facility, etc., the site attributes configured for the site by the user include, but are not limited to, a site code, a site name, a site address, etc. The interview attributes configured for a unit include, but are not limited to, the unit code, the unit name, and the unit floor. The interview object attributes configured for a floor include, but are not limited to, a floor code and a number of floors. The interview attributes configured for the house include, but are not limited to, house number and house resident information.
After the acquisition object is created, in addition to the acquisition object attributes for the acquisition object, object relationships between the respective acquisition objects need to be configured. The relation of the acquisition and examination objects refers to the association relation between the two acquisition and examination objects, the two acquisition and examination objects can be bound together to form a relation through the association relation, and each relation is identified through the object identification code.
See, for example, figure 4 for a schematic diagram of the subject relationship being investigated. The buildings and the units are bound together through the building codes and the unit codes, and the relationship between the buildings and the units is identified by the object identification codes X. The unit and the house are bound together by the unit code and the house code, and the relationship between the unit and the house is identified by the object identification code Y.
And step S302, establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked.
Specifically, after the dynamic patrol acquisition and patrol platform system acquires the acquisition object and the attribute information of the acquisition object, which need to be created by the user, a vertex including the attribute of the acquisition object is established.
It will be appreciated that different types of vertices are created, depending on the object under investigation. When the vertex is a collection vertex, the collection vertex includes a collection object attribute. When the vertex is a classification vertex, the classification vertex does not include the attribute of the object under investigation.
And step S303, connecting each vertex by using a directed edge according to the acquired object relation information to generate a graph model.
It is understood that the directed edge represents the object relationship between two objects, and after connecting each vertex using the directed edge, a graph model, i.e., an acquisition object model, is generated.
And the user creates the acquisition and check object according to the business requirement, and generates an acquisition and check object model corresponding to the business requirement after configuring the acquisition and check object attribute and the acquisition and check object relation for the acquisition and check object.
For example, when a certain area A needs to be searched, the certain area A including attributes such as a building code, a building name, a building address and the like is searched; when information of a certain unit is searched, the unit comprises attributes such as unit codes, unit names, unit floors and the like; when a unit floor is searched, the floor comprises the properties of a floor code, a plurality of floors and the like; when the condition of a house on a certain floor is checked, the house comprises attributes such as house codes, house resident information and the like.
And S102, responding to the construction operation of the acquisition and examination strategy model of the user, and constructing the acquisition and examination strategy model.
It should be noted that, after the user constructs the acquisition and search object model according to the business requirements, when the acquisition and search object model is used to acquire and search data, there may be situations where the acquired and searched data is too much and not all the acquired and searched data is needed. To reduce the acquisition data, relevant acquisition strategies can be constructed. For example, the constructed policy is which acquisition objects or acquisition object attributes are necessary to be acquired and checked, which acquisition objects or acquisition object attributes are periodic acquisition and check, and the like.
In some embodiments, referring to the schematic flow diagram of the acquisition and search strategy model building process shown in fig. 5, the specific process of building the acquisition and search strategy model in response to the acquisition and search strategy model building operation of the user may include:
step S501, creating a sampling and checking strategy in response to the strategy creating operation of the user.
Specifically, the user may create a required acquisition and review policy according to the data acquisition requirement in the service requirement.
For example, according to the business requirements of the users, the required checking strategies including but not limited to must check, strictly check, periodically check, whether to take a picture and whether to use VR equipment are created.
And step S502, responding to the strategy configuration operation of the user, and labeling the acquisition strategy for the vertex and/or the directed edge in the graph model.
Specifically, the user configures a corresponding acquisition and check strategy according to the service requirement, that is, the user can configure the corresponding acquisition and check strategy for one or more of the acquisition and check object, the acquisition and check object attribute and the acquisition and check object relationship according to the requirement.
Referring to a schematic diagram of a corresponding relationship between an acquisition and search object model and an acquisition and search policy model shown in fig. 6, as shown in fig. 6, the acquisition and search object model includes three acquisition and search objects, and the acquisition and search objects are connected by directed edges. And marking corresponding acquisition strategies for the vertexes and/or edges by using the acquisition strategies in the acquisition strategy model.
For example, the created interview objects are buildings, units, floors, houses, and the like. And (4) configuring and creating the acquisition and inspection strategies for buildings, units, floors, houses and the like according to the acquisition and inspection requirements. Specifically, the buildings are configured to be collected and searched for when necessary, and the houses are configured to be collected and searched for periodically.
Also for example, the checked object attributes of a building include a building code, a building name, a building address, and the like. And configuring the created acquisition and check strategy for the configured acquisition and check object attributes according to the service requirements. Particularly, the building code is configured to be acquired and checked.
It should be noted that, after configuring the acquisition and inspection policy for the acquisition and inspection object, the configured acquisition and inspection policy does not change at all according to the change of the relationship of the acquisition and inspection object. 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 fire-fighting facility is different in the acquisition strategy under different relationships. Therefore, strategies need to be configured for different object relation acquisition and check, and fire fighting facilities need to be acquired and checked when the data of the floor are acquired and checked; when the data of the house is collected and checked, the fire-fighting facilities are collected and checked periodically.
After the acquisition and check strategy model is built, the acquisition and check process can screen out which acquisition and check objects are necessary to be acquired and checked and which acquisition and check objects are periodically acquired and checked and the like through the acquisition and check strategy, so that the acquisition and check are more convenient and the acquisition and check data volume is reduced.
And step S103, generating a relational database table according to the model of the object to be checked.
It should be noted that, the object model includes description information of the database, and the relational database can be automatically generated according to the description information of the database.
In some embodiments, referring to the schematic flow chart diagram of the process of generating the relational database table shown in fig. 7, the specific process of generating the relational database table according to the model of the subject of the investigation may include:
and S701, analyzing the attribute description information in the acquisition object model to acquire database description information in the attribute description information.
Step S702, converting the database description information into data in a preset data format.
It should be noted that the above-mentioned database description information refers to the description of the database definition in the attributes of the object model to be searched. After the database description information is acquired, the database description information is packaged into data in a preset format, and the preset data format refers to a format which can be recognized by an engine.
And step S703, acquiring the SQL statement 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 statement template.
Specifically, a SQL statement template is filled with data in a preset data format, and an executable SQL statement is generated. The database then executes the generated executable SQL statement, generating a relational database table.
And step S104, generating an acquisition and inspection interface according to the acquisition and inspection object model and the acquisition and inspection strategy model.
Specifically, the acquisition and check strategy in the acquisition and check strategy model is encapsulated through encapsulating the acquisition and check object attribute in the acquisition and check object model, and the acquisition and check rule data is encapsulated to obtain a corresponding template; and then reading the generated template by using an engine to generate the acquisition and search interface.
In some embodiments, referring to the schematic flow diagram of the acquisition and search interface generation process shown in fig. 8, the specific process of generating the acquisition and search interface according to the acquisition and search object model and the acquisition and search policy model may include:
and step S801, generating an interface acquisition field template according to the attributes of the acquisition object.
Specifically, the attributes of the objects to be checked in the object model to be checked are assembled into a data object format which can be identified by the template language through a mapping method, and an interface acquisition field template is formed according to the attributes of the objects to be checked in the data object format.
For example, the object to be checked is a building, the attributes of the object to be checked include a building code, a floor name, a floor address and the like, and the options displayed on the interface to be checked include the building code, the floor name and the floor address.
And S802, generating an acquisition and search strategy screening function item template according to the acquisition and search strategy.
Specifically, the acquisition and search strategies in the acquisition and search strategy model are encapsulated to generate an acquisition and search strategy screening function item template.
For example, the checking strategy includes must check, strictly check, periodically check, whether to take a picture and whether to use VR equipment, the generated interface includes a "must check" option, a "strictly check" option, a "periodically check" option, a "whether to take a picture" option and a "whether to use VR equipment" option, and these options may exist in a drop-down manner, and the user may select different options according to the checking object and the checking object attribute.
And S803, generating a rule template corresponding to the predefined rule according to the predefined rule in the acquisition object model.
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.
And step S804, generating an acquisition and inspection interface according to the interface acquisition field template, the acquisition and inspection strategy screening function item template and the rule template.
Specifically, the above-mentioned acquisition and search interface is generated by using an engine through the generated template. After the interview interface is generated, the interview interface can be displayed on a terminal interface of a user.
And step S105, mapping the acquisition and search data input on the acquisition and search interface to a relational database table.
In specific application, the acquisition and search data input on the acquisition and search interface can be mapped to the relational database through the object identification code. The object identification code is a unique identifier of the acquisition and inspection object model, and the acquisition and inspection object and the acquisition and inspection strategy can be determined through the object identification code.
The mapping process is a data storage process, and the mapping process is to store data filled in the acquisition and search interface in a database table. The acquisition and check interface and the database table are identified by the object identification code, and then the data are transmitted to the database from the acquisition and check interface for storage.
According to the embodiment of the application, the acquisition object model and the acquisition strategy model are dynamically constructed according to business needs, 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 and inspection interface is mapped to the relational database table for storage, so that the dynamic acquisition and inspection according to business changes is realized.
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 application.
Corresponding to the dynamic patrol method described in the foregoing embodiment, fig. 9 shows a schematic block diagram of a structure of the dynamic patrol system provided in the embodiment of the present application, and for convenience of description, only the parts related to the embodiment of the present application are shown.
Referring to fig. 9, the system may include:
an acquisition object model construction module 91 for constructing an acquisition object model in response to an acquisition object model construction operation by a user;
an acquisition and search strategy model construction module 92, configured to respond to an acquisition and search strategy model construction operation of a user, and construct an acquisition and search strategy model;
a database table generating module 93, configured to generate a relational database table according to the query object model;
an acquisition and search interface generating module 94, configured to generate an acquisition and search interface according to the acquisition and search object model and the acquisition and search policy model;
and the mapping module 95 is configured to map the mining and searching data input on the mining and searching interface to the relational database table.
In one possible implementation mode, the object model is a graph model comprising a vertex and a directed edge, wherein the vertex represents an object to be checked, and the directed edge represents the relation of the object to be checked;
the acquisition and inspection object model construction module is specifically used for:
acquiring acquisition and check object information, acquisition and check object attribute information and acquisition and check object relation information in response to acquisition and check object model construction operation of a user;
establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked;
and connecting each vertex by using directed edges according to the acquired and searched object relation information to generate a graph model.
In a possible implementation manner, the acquisition and search policy model building module may be specifically configured to:
creating a mining and checking strategy in response to the strategy creating operation of the user;
and marking the vertexes and/or directed edges in the graph model with the marking and checking strategies in response to the strategy configuration operation of the user.
In a possible implementation manner, the acquisition and search interface generating module may be specifically configured to:
generating an interface acquisition field template according to the attributes of the acquisition and search objects;
generating an acquisition and search strategy screening function item template according to an acquisition and search strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the collection object model;
and generating an acquisition and inspection interface according to the interface acquisition field template, the acquisition and inspection strategy screening function item template and the rule template.
In a possible implementation manner, the database table generation module may be specifically configured to:
analyzing 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 statement template;
and generating a relational database table according to the data in the preset data format and the SQL statement template.
In a possible implementation manner, the mapping module is specifically configured to:
and mapping the acquisition and search data input on the acquisition and search interface to a relational database through the object identification code.
It should be noted that, because the contents of information interaction, execution process, and the like between the system modules are based on the same concept as that of the embodiment of the method of the present application, specific functions and technical effects thereof may be specifically referred to a part of the embodiment of the method, and details are not described here.
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, a palm computer, and a cloud server. The terminal device may include, but is not limited to, a processor 100, a memory 101. Those skilled in the art will appreciate that fig. 10 is merely an example of the terminal device 10, and does not constitute a limitation of the terminal device 10, and may include more or less components than those shown, or combine some of the components, or different components, such as an input-output device, a network access device, etc.
The Processor 100 may be a Central Processing Unit (CPU), and the Processor 100 may be 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, a discrete Gate or transistor logic device, a discrete hardware component, 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. In other embodiments, the memory 101 may 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 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, an application program, a BootLoader (BootLoader), data, and other programs, 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-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.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.
The embodiments of the present application provide a computer program product, which when running on a terminal device, enables the terminal device to implement the steps in the above method embodiments when executed.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. 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 at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), random-access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments 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 may be 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.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 application and are intended to be included within the scope of the present application.
Claims (10)
1. A dynamic patrolling and patrolling method is characterized by comprising the following steps:
responding to the construction operation of the object model of the acquisition and check of the user, and constructing the object model of the acquisition and check;
responding to the construction operation of the acquisition and search strategy model of the user, and constructing an acquisition and search strategy model;
generating a relational database table according to the acquisition and check object model;
generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search strategy model;
and mapping the acquisition and search data input on the acquisition and search interface to the relational database table.
2. The method of claim 1, wherein the scout object model is a graph model comprising vertices and directed edges, the vertices representing scout objects, the directed edges representing scout object relationships;
responding to the mining and checking object model building operation of a user, building a mining and checking object model, comprising the following steps:
acquiring acquisition and check object information, acquisition and check object attribute information and acquisition and check object relation information in response to acquisition and check object model construction operation of the user;
establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked;
and connecting each vertex by using a directed edge according to the acquisition and check object relation information to generate the graph model.
3. The method of claim 2, wherein building an acquisition and review policy model in response to an acquisition and review policy model building operation by the user comprises:
creating a mining and searching strategy in response to the strategy creating operation of the user;
and marking the acquisition strategy for the vertexes and/or directed edges in the graph model in response to the strategy configuration operation of the user.
4. The method of claim 3, wherein generating an acquisition and review interface from the acquisition and review object model and the acquisition and review strategy model comprises:
generating an interface acquisition field template according to the attributes of the acquisition and search objects;
generating an acquisition and search strategy screening function item template according to the acquisition and search strategy;
generating a rule template corresponding to a predefined rule according to the predefined rule in the collection object model;
and generating the acquisition and inspection interface according to the interface acquisition field template, the acquisition and inspection strategy screening function item template and the rule template.
5. The method of claim 3, wherein generating a relational database table from the interview object model comprises:
analyzing the attribute description information in the acquisition object model to acquire database description information in the attribute description information;
converting the database description information into data in a preset data format;
acquiring an SQL statement template;
and generating the relational database table according to the data in the preset data format and the SQL statement template.
6. The method of any one of claims 1 to 5, wherein mapping the censored data entered on the censoring interface to the relational database table comprises:
and mapping the acquisition and search data input on the acquisition and search interface to the relational database through the object identification code.
7. A dynamic patrolling system, comprising:
the acquisition and inspection object model building module is used for responding to acquisition and inspection object model building operation of a user and building an acquisition and inspection object model;
the acquisition and search strategy model construction module is used for responding to the acquisition and search strategy model construction operation of the user and constructing an acquisition and search strategy model;
the database table generating module is used for generating a relational database table according to the acquisition and check object model;
the acquisition and search interface generation module is used for generating an acquisition and search interface according to the acquisition and search object model and the acquisition and search strategy model;
and the mapping module is used for mapping the acquisition and search data input on the acquisition and search interface to the relational database table.
8. The system of claim 7, wherein the scout object model is a graph model including vertices and directed edges, the vertices representing scout objects, the directed edges representing scout object relationships;
the acquisition and inspection object model building module is specifically used for:
acquiring acquisition and check object information, acquisition and check object attribute information and acquisition and check object relation information in response to acquisition and check object model construction operation of the user;
establishing a vertex according to the information of the object to be checked and the attribute information of the object to be checked;
and connecting each vertex by using a directed edge according to the acquisition and check object relation information to generate the graph model.
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 6 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 6.
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 true CN111026732A (en) | 2020-04-17 |
| CN111026732B 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 |
|---|---|
| CN111026732B (en) | 2023-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20140337390A1 (en) | Space-time-node engine signal structure | |
| CN111427971B (en) | Business modeling method, device, system and medium for computer system | |
| CN113806434B (en) | Big data processing method, device, equipment and medium | |
| CN114090838B (en) | Method, system, electronic device and storage medium for visually displaying big data | |
| CN110633726A (en) | Room source identification method and device, storage medium and electronic equipment | |
| CN105357204A (en) | Method and apparatus for generating terminal identifying information | |
| CN111538774A (en) | Data storage and display method, system, equipment and storage medium | |
| CN110795697A (en) | Logic expression obtaining method and device, storage medium and electronic device | |
| CN110661665A (en) | Alarm method based on Internet of things cloud platform, computer storage medium and equipment | |
| CN111400393A (en) | Data processing method and device based on multi-application platform and storage medium | |
| CN114116065A (en) | Method and device for acquiring topological graph data object and electronic equipment | |
| CN111414410A (en) | Data processing method, device, equipment and storage medium | |
| KR101810518B1 (en) | Object query system and method using BIM data of IFC format | |
| CN108345620B (en) | Brand information processing method, brand information processing device, storage medium and electronic equipment | |
| CN111142863A (en) | Page generation method and device | |
| CN111026732B (en) | Dynamic inspection tour method and system | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN111652741B (en) | User preference analysis method, device and readable storage medium | |
| CN114996369A (en) | Method and device for constructing data warehouse index library | |
| CN114296696A (en) | Business function operation method and device, storage medium and electronic equipment | |
| CN113935847A (en) | Online process risk processing method, device, server and medium | |
| CN114328686A (en) | Data docking method and related equipment | |
| CN113204592A (en) | Data processing method, system and device under scene of Internet of things and storage medium | |
| CN112052398A (en) | Media information recommendation method and device, electronic equipment and storage medium | |
| CN111222739A (en) | Task allocation method and task allocation system of nuclear power station |
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 |